Wrong Contact header on SIP 200 OK

236 views

Skip to first unread message

Guna Ramanujam

unread,

Feb 27, 2015, 12:13:03 PM2/27/15

to sip...@googlegroups.com

Bob's leg of the call seems to be generating wrong and multiple Contact header in response to INVITE. This only happens spuriously on Chrome. This is causing response ACK from peer to be ignored with: Request-URI does not point to us

Any idea why this may be?

Log:

INVITE sip:7e9e...@192.0.2.28;transport=ws SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>
Call-ID: 1f9a1f4c096f2823...@XX.XX.XX.XX:0
CSeq: 102 INVITE
User-Agent: Asterisk PBX 13.2.0
Date: Fri, 27 Feb 2015 11:47:01 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1086
.....................

SIP/2.0 100 Trying
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
Call-ID: 1f9a1f4c096f2823...@XX.XX.XX.XX:0
CSeq: 102 INVITE
Supported: outbound
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
Call-ID: 1f9a1f4c096f2823...@XX.XX.XX.XX:0
CSeq: 102 INVITE
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
Call-ID: 1f9a1f4c096f2823...@XX.XX.XX.XX:0
CSeq: 102 INVITE
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Type: application/sdp
Content-Length: 1854
.............

ACK sip:l1po...@192.0.2.52;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK5d19cbe8;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>
Call-ID: 1f9a1f4c096f2823...@XX.XX.XX.XX:0
CSeq: 102 ACK
User-Agent: Asterisk PBX 13.2.0
Content-Length: 0

sip-0.6.4.js:2680 Fri Feb 27 2015 17:16:54 | sip.ua | Request-URI does not point to us

-g

Eric Green

unread,

Mar 3, 2015, 3:44:09 PM3/3/15

to sip...@googlegroups.com

Hi Guna,

Can you please attach a gist with full javascript logs and traceSip turned on?

Thanks.

-Eric Green

On Friday, February 27, 2015 at 12:13:03 PM UTC-5, Guna Ramanujam wrote:

Bob's leg of the call seems to be generating wrong and multiple Contact header in response to INVITE. This only happens spuriously on Chrome. This is causing response ACK from peer to be ignored with: Request-URI does not point to us

Any idea why this may be?

Log:

INVITE sip:7e9e...@192.0.2.28;transport=ws SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
User-Agent: Asterisk PBX 13.2.0
Date: Fri, 27 Feb 2015 11:47:01 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1086
.....................

SIP/2.0 100 Trying
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Supported: outbound
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Type: application/sdp
Content-Length: 1854
.............

ACK sip:l1po...@192.0.2.52;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK5d19cbe8;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 ACK
User-Agent: Asterisk PBX 13.2.0
Content-Length: 0

Guna Ramanujam

unread,

Mar 10, 2015, 5:21:59 PM3/10/15

to sip...@googlegroups.com

Gist:

https://gist.github.com/57255016fe4deec15665.git

Includes log from register and multiple calls. Thought you might need all, incase. To jump right to the log point where issue occurs, search for “Request-URI does not point to us”

ps: my earlier reply somehow got lost, just noticed thats why the delay

Guna

On Friday, February 27, 2015 at 10:43:03 PM UTC+5:30, Guna Ramanujam wrote:

Bob's leg of the call seems to be generating wrong and multiple Contact header in response to INVITE. This only happens spuriously on Chrome. This is causing response ACK from peer to be ignored with: Request-URI does not point to us

Any idea why this may be?

Log:

INVITE sip:7e9e...@192.0.2.28;transport=ws SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
User-Agent: Asterisk PBX 13.2.0
Date: Fri, 27 Feb 2015 11:47:01 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1086
.....................

SIP/2.0 100 Trying
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Supported: outbound
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK65839aee;rport
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 INVITE
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:l1po...@192.0.2.52;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE,MESSAGE
Content-Type: application/sdp
Contact: <sip:7e9e...@192.0.2.28;transport=ws>
Supported: outbound
Content-Type: application/sdp
Content-Length: 1854
.............

ACK sip:l1po...@192.0.2.52;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS XX.XX.XX.XX:0;branch=z9hG4bK5d19cbe8;rport
Max-Forwards: 70
From: "1083" <sip:10...@XX.XX.XX.XX:0>;tag=as310863e4
To: <sip:7e9e...@192.0.2.28;transport=ws>;tag=iqi4u1lvlh
Contact: <sip:10...@XX.XX.XX.XX:0;transport=WS>

Call-ID: 1f9a1f4c096f282343075dba5c38b72...@XX.XX.XX.XX:0

CSeq: 102 ACK
User-Agent: Asterisk PBX 13.2.0
Content-Length: 0

Reply all

Reply to author

Forward

0 new messages