Hi
dialog timeout is occurred if 200 ok having mixed loose and strict routing entries in record route header
conf file attached
INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: sip:123455555@176.204.26.157:63939;ob Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Route: sip:11.11.11.11:345;lr Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Content-Type: application/sdp Content-Length: 320
v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 10.123.11.223 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 407 Proxy Authentication required Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK3d4f.6f8dff1ec0806cb23f56d847d5fe3934.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Proxy-Authenticate: Digest nonce="6b24dc6996de20028c78dbeaf13edc55",realm="22.22.22.22",opaque="",stale=FALSE,algorithm=MD5 Content-Length: 0
ACK sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 ACK Route: sip:11.11.11.11:345;lr Content-Length: 0
INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: sip:123455555@176.204.26.157:63939;ob Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Route: sip:11.11.11.11:345;lr Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Proxy-Authorization: Digest username="123455555", realm="22.22.22.22", nonce="6b24dc6996de20028c78dbeaf13edc55", uri=" sip:123456789@22.22.22.22:5060", response="554a1da255084f7a95d3b6e7a0c48933", algorithm=MD5 Content-Type: application/sdp Content-Length: 320
v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 34.220.83.191 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 100 Trying Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Content-Length: 0
SIP/2.0 183 Session progress Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22;tag=GB-1445011078679 CSeq: 14603 INVITE Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh Contact: sip:22.22.22.22:5060 Content-Type: application/sdp Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345;lr Content-Length: 298
v=0 o=- 3653999880 3653999880 IN IP4 50.56.154.204 s=zeodialer c=IN IP4 50.33.154.204 b=AS:25 t=0 0 m=audio 53128 RTP/AVP 18 96 c=IN IP4 50.33.154.204 b=TIAS:8000 a=rtpmap:18 G729/8000 a=sendrecv a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 183 Session Progress Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE P-Early-Media: sendrecv Contact: sip:22.22.22.22:5060 Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Content-Type: application/sdp From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212
v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.22.154.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20
SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE Contact: sip:22.22.22.22:5060 Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Content-Type: application/sdp From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212
v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.33.44.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20
ACK sip:11.11.11.11:345 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjldbprXw3ybGOxoeKWwvtdxLmNp8jXsOX Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 ACK Route: sip:22.22.22.22:5060;lr Route: sip:22.22.22.22:5060 Content-Length: 0
Hello,
On 17/10/15 10:24, Arun Kumar wrote:
Hi
dialog timeout is occurred if 200 ok having mixed loose and strict routing entries in record route header
[...] this really brief phrase is making it hard to figure out what is the problem -- can you provide more details about what the issue is, symptoms, etc.? Otherwise, dialog timeout should occur at some point for all calls, if they are not ended by caller/callee.
Cheers, Daniel
Daniel ,
dialog timeout happen only for below scenario
SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345
so ack is
ACK sip:11.11.11.11:345 SIP/2.0
ack message ruri is overwritten by strict route uri , in this case dialog module is returning dialog matching failed error after receiving ack from UAC , so dialog timeout is occurred after 2 min because of not confirmed dialog state
but below scenario is working fine (both record route entries have loose route )
SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345;lr
so ack is
ACK sip:22.22.22.22:5060 SIP/2.0
On Sat, Oct 17, 2015 at 1:54 PM, Arun Kumar mi2arun@gmail.com wrote:
Hi
dialog timeout is occurred if 200 ok having mixed loose and strict routing entries in record route header
conf file attached
INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: sip:123455555@176.204.26.157:63939;ob Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Route: sip:11.11.11.11:345;lr Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Content-Type: application/sdp Content-Length: 320
v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 10.123.11.223 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 407 Proxy Authentication required Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK3d4f.6f8dff1ec0806cb23f56d847d5fe3934.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Proxy-Authenticate: Digest nonce="6b24dc6996de20028c78dbeaf13edc55",realm="22.22.22.22",opaque="",stale=FALSE,algorithm=MD5 Content-Length: 0
ACK sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 ACK Route: sip:11.11.11.11:345;lr Content-Length: 0
INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: sip:123455555@176.204.26.157:63939;ob Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Route: sip:11.11.11.11:345;lr Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Proxy-Authorization: Digest username="123455555", realm="22.22.22.22", nonce="6b24dc6996de20028c78dbeaf13edc55", uri=" sip:123456789@22.22.22.22:5060", response="554a1da255084f7a95d3b6e7a0c48933", algorithm=MD5 Content-Type: application/sdp Content-Length: 320
v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 34.220.83.191 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 100 Trying Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Content-Length: 0
SIP/2.0 183 Session progress Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22;tag=GB-1445011078679 CSeq: 14603 INVITE Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh Contact: sip:22.22.22.22:5060 Content-Type: application/sdp Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345;lr Content-Length: 298
v=0 o=- 3653999880 3653999880 IN IP4 50.56.154.204 s=zeodialer c=IN IP4 50.33.154.204 b=AS:25 t=0 0 m=audio 53128 RTP/AVP 18 96 c=IN IP4 50.33.154.204 b=TIAS:8000 a=rtpmap:18 G729/8000 a=sendrecv a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value
SIP/2.0 183 Session Progress Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE P-Early-Media: sendrecv Contact: sip:22.22.22.22:5060 Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Content-Type: application/sdp From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212
v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.22.154.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20
SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,sip:11.11.11.11:345 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE Contact: sip:22.22.22.22:5060 Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Content-Type: application/sdp From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212
v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.33.44.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20
ACK sip:11.11.11.11:345 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjldbprXw3ybGOxoeKWwvtdxLmNp8jXsOX Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 ACK Route: sip:22.22.22.22:5060;lr Route: sip:22.22.22.22:5060 Content-Length: 0
Can you run with debug=3 in kamailio.cfg and send me the log messages for processing the ACK?
The matching should be done on call-id, from-tag and to-tag.
Cheers, Daniel
On 19/10/15 19:29, Arun Kumar wrote:
Daniel , dialog timeout happen only for below scenario SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,<sip:11.11.11.11:345 http://11.11.11.11:345> so ack is ACK sip:11.11.11.11:345 http://11.11.11.11:345 SIP/2.0 ack message ruri is overwritten by strict route uri , in this case dialog module is returning dialog matching failed error after receiving ack from UAC , so dialog timeout is occurred after 2 min because of not confirmed dialog state but below scenario is working fine (both record route entries have loose route ) SIP/2.0 200 OK Record-Route: sip:22.22.22.22:5060;lr,<sip:11.11.11.11:345 http://11.11.11.11:345;lr> so ack is ACK sip:22.22.22.22:5060 http://22.22.22.22:5060SIP/2.0
On Sat, Oct 17, 2015 at 1:54 PM, Arun Kumar <mi2arun@gmail.com mailto:mi2arun@gmail.com> wrote:
Hi dialog timeout is occurred if 200 ok having mixed loose and strict routing entries in record route header conf file attached INVITE sip:123456789@22.22.22.22:5060 <http://sip:123456789@22.22.22.22:5060> SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22> Contact: <sip:123455555@176.204.26.157:63939;ob> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Route: <sip:11.11.11.11:345;lr> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Content-Type: application/sdp Content-Length: 320 v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 10.123.11.223 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 407 Proxy Authentication required Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK3d4f.6f8dff1ec0806cb23f56d847d5fe3934.0,SIP/2.0/UDP176.204.26.157:63939;rport=63939;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW;received=176.204.26.157 From: <sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Proxy-Authenticate: Digest nonce="6b24dc6996de20028c78dbeaf13edc55",realm="22.22.22.22",opaque="",stale=FALSE,algorithm=MD5 Content-Length: 0 ACK sip:123456789@22.22.22.22:5060 <http://sip:123456789@22.22.22.22:5060> SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 ACK Route: <sip:11.11.11.11:345;lr> Content-Length: 0 INVITE sip:123456789@22.22.22.22:5060 <http://sip:123456789@22.22.22.22:5060> SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939;rport;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI Max-Forwards: 70 From: sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22> Contact: <sip:123455555@176.204.26.157:63939;ob> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Route: <sip:11.11.11.11:345;lr> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Proxy-Authorization: Digest username="123455555", realm="22.22.22.22", nonce="6b24dc6996de20028c78dbeaf13edc55", uri="sip:123456789@22.22.22.22:5060", response="554a1da255084f7a95d3b6e7a0c48933", algorithm=MD5 Content-Type: application/sdp Content-Length: 320 v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 34.220.83.191 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 100 Trying Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP176.204.26.157:63939;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: <sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Content-Length: 0 SIP/2.0 183 Session progress Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP176.204.26.157:63939;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: <sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>>;tag=GB-1445011078679 CSeq: 14603 INVITE Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh Contact: <sip:22.22.22.22:5060 <http://22.22.22.22:5060>> Content-Type: application/sdp Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345;lr> Content-Length: 298 v=0 o=- 3653999880 3653999880 IN IP4 50.56.154.204 s=zeodialer c=IN IP4 50.33.154.204 b=AS:25 t=0 0 m=audio 53128 RTP/AVP 18 96 c=IN IP4 50.33.154.204 b=TIAS:8000 a=rtpmap:18 G729/8000 a=sendrecv a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 183 Session Progress Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345 <http://11.11.11.11:345>> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE P-Early-Media: sendrecv Contact: <sip:22.22.22.22:5060 <http://22.22.22.22:5060>> Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP176.204.26.157:63939;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: <sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>>;tag=GB-1445011078679 Content-Type: application/sdp From: <sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212 v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.22.154.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20 SIP/2.0 200 OK Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345 <http://11.11.11.11:345>> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE Contact: <sip:22.22.22.22:5060 <http://22.22.22.22:5060>> Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP176.204.26.157:63939;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: <sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>>;tag=GB-1445011078679 Content-Type: application/sdp From: <sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212 v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.33.44.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20 ACK sip:11.11.11.11:345 <http://11.11.11.11:345> SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939;rport;branch=z9hG4bKPjldbprXw3ybGOxoeKWwvtdxLmNp8jXsOX Max-Forwards: 70 From: sip:123455555@22.22.22.22 <mailto:sip%3A123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 <mailto:sip%3A123456789@22.22.22.22>;tag=GB-1445011078679 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 ACK Route: <sip:22.22.22.22:5060;lr> Route: <sip:22.22.22.22:5060 <http://22.22.22.22:5060>> Content-Length: 0
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Arun Kumar -
Daniel-Constantin Mierla