Bogdan, thanks I had a feeling the VIA branch was off limits.
Following is a network dump that shows the loop detect response from
sip.broadvoice.com which is the PSTN gateway. I assumed the problem
was due to the VIA 1 branch being the same before and after
authentication, but I'm not certain.
Thanks,
15:02:21.270625 IP sip.client.5060 > sip.openser.com.5060: UDP, length 781
E..).[..u..H...>..C$........INVITE sip:15085551212@voip.company.edu SIP/2.0
Via: SIP/2.0/UDP
192.168.0.127:23954;rport;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:3021@voip.company.edu>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Contact: <sip:3021@192.168.0.127:23954>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
Max-Forwards: 70
Content-Type: application/sdp
User-Agent: X-Lite release 1103m
Content-Length: 302
v=0
o=3021 3736209468 3736209656 IN IP4 192.168.0.127
s=X-Lite
c=IN IP4 192.168.0.127
t=0 0
m=audio 24254 RTP/AVP 0 8 3 98 97 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:3 gsm/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:97 speex/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:02:21.272266 IP sip.openser.com.5060 > sip.client.5060: UDP, length 615
E.....@.@..9..C$...>.....o[.SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:3021@voip.company.edu>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
Server: OpenSer (1.1.0-dev3 (i386/linux))
Content-Length: 0
Warning: 392 134.241.67.36:5060 "Noisy feedback tells: pid=12809
req_src_ip=192.168.0.127 req_src_port=5060
in_uri=sip:15085551212@voip.company.edu
out_uri=sip:15085551212@sip.broadvoice.com:5060 via_cnt==1"
15:02:21.272449 IP sip.openser.com.5060 > sip.broadvoice.com.5060:
UDP, length 942
E.....@.@.....C$..........a.INVITE
sip:15085551212@sip.broadvoice.com:5060 SIP/2.0
Record-Route: <sip:134.241.67.36;ftag=3677179691;lr=on>
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.0
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Contact: <sip:3021@192.168.0.127:23954>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
Max-Forwards: 69
Content-Type: application/sdp
User-Agent: X-Lite release 1103m
Content-Length: 302
P-hint: usrloc applied
v=0
o=3021 3736209468 3736209656 IN IP4 192.168.0.127
s=X-Lite
c=IN IP4 192.168.0.127
t=0 0
m=audio 24254 RTP/AVP 0 8 3 98 97 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:3 gsm/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:97 speex/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:02:21.312439 IP sip.broadvoice.com.5060 > sip.openser.com.5060:
UDP, length 377
E.......8.........C$........SIP/2.0 100 Trying
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.0
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
15:02:21.323308 IP sip.broadvoice.com.5060 > sip.openser.com.5060:
UDP, length 498
E.......8..+......C$........SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.0
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>;tag=SD38i6c99-
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
WWW-Authenticate: DIGEST
realm="BroadWorks",algorithm=MD5,nonce="1136923341303"
Content-Length: 0
15:02:21.323644 IP sip.openser.com.5060 > sip.broadvoice.com.5060:
UDP, length 385
E.....@.@..!..C$.........._.ACK sip:15085551212@sip.broadvoice.com:5060 SIP/2.0
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.0
From: SER User <sip:3021@voip.company.edu>;tag=3677179691
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
To: <sip:15085551212@voip.company.edu>;tag=SD38i6c99-
CSeq: 49363 ACK
User-Agent: OpenSer (1.1.0-dev3 (i386/linux))
Content-Length: 0
15:02:21.324301 IP sip.openser.com.5060 > sip.broadvoice.com.5060:
UDP, length 1139
E.....@.@.....C$.........{b.INVITE
sip:15085551212@sip.broadvoice.com:5060 SIP/2.0
Record-Route: <sip:134.241.67.36;ftag=3677179691;lr=on>
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.1
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Contact: <sip:3021@192.168.0.127:23954>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
Max-Forwards: 69
Content-Type: application/sdp
User-Agent: X-Lite release 1103m
Content-Length: 302
P-hint: usrloc applied
Authorization: Digest username="5175133123", realm="BroadWorks",
nonce="1136923341303", uri="sip:15085551212@sip.broadvoice.com:5060",
response="df5216891db0aaaa7e006ef408dce50e", algorithm="MD5"
v=0
o=3021 3736209468 3736209656 IN IP4 192.168.0.127
s=X-Lite
c=IN IP4 192.168.0.127
t=0 0
m=audio 24254 RTP/AVP 0 8 3 98 97 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:3 gsm/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:97 speex/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:02:21.361036 IP sip.broadvoice.com.5060 > sip.openser.com.5060:
UDP, length 377
E.......8.........C$........SIP/2.0 100 Trying
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.1
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
15:02:21.367782 IP sip.broadvoice.com.5060 > sip.openser.com.5060:
UDP, length 441
E.......8..\......C$......{ SIP/2.0 482 Loop detected
Via: SIP/2.0/UDP 134.241.67.36;branch=z9hG4bK38c8.b8c634d5.1
Via: SIP/2.0/UDP
192.168.0.127:23954;rport=5060;branch=z9hG4bK9BCC444A092044218C01377C79CA1078
From: SER User <sip:5175133123@sip.broadvoice.com>;tag=3677179691
To: <sip:15085551212@voip.company.edu>;tag=SD38i6c99-140264986-1136923341349
Call-ID: BC74A63E-99AE-49B1-832F-B951AB522D03(a)192.168.0.240
CSeq: 49363 INVITE
Content-Length: 0
On 1/10/06, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro> wrote:
Hi Scott,
playing with the VIA branch parameter is not something you should try -
you will brake transaction matching on downstream proxies.
maybe you can post a network dump to try to see what the problem is and
if there are any solutions.
regards,
bogdan
Scott MacGregor wrote:
Is there a way to change the branch parameter in
any
of the Via headers in an INVITE? I am getting a 482
loop detected which I think is due to the same branch
parameter in two requests.
Thanks,
Scott
__________________________________________
Yahoo! DSL – Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
--
Scott MacGregor