[SR-Users] Bad request when INVITE relayed to another kamailio

[Alex Balashov]

It is certainly possible that I am mistaken about the root cause. 

—
Sent from my iPad

> On Jan 27, 2020, at 2:37 AM, Zhan Bazarov <chiefkeeft at gmail.com> wrote:
> 
> hello! Thanks for reply! 
> 
> So, now I have two INVITE requests with interval in few seconds:
> 
> INVITE sip:jyu3xsfkrz6c5qn at 10.3.0.116;transport=tcp SIP/2.0
> Record-Route:
> <sip:34.202.130.141:5078;transport=tcp;r2=on;lr;nat=yes;rtp=bridge>
> Record-Route: <sip:34.202.130.141:5078;r2=on;lr;nat=yes;rtp=bridge>
> Record-Route: <sip:3.220.42.184:5078;lr>
> Via: SIP/2.0/TCP
> some.proxy.net:5078;branch=z9hG4bK24ec.940ea1b24f9ae5d68a6f97928661dbb6.0
> Via: SIP/2.0/UDP
> some.proxy.net:5078;rport=5078;received=10.199.240.135;branch=z9hG4bK24ec.73c81b0f32164242a9bf0beb0f96f7bb.0
> Via: SIP/2.0/UDP
> 10.199.240.176:7060;received=10.199.240.176;rport=7060;branch=z9hG4bKPj726e453b-eb1b-4e07-b49d-45703bc42e38
> From: "Rick"
> <sip:1022 at 10.199.240.176>;tag=1c95c3be-0c2a-44ef-8715-28735586ad95
> To: <sip:jyu3xsfkrz6c5qn at 10.199.240.135>
> Contact: <sip:asterisk at 10.199.240.176:7060;alias=10.199.240.176~7060~1>
> Call-ID: 63cf568c-eef4-4262-8e6b-db3f6caedfbb
> CSeq: 23870 INVITE
> Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE,
> CANCEL, UPDATE, MESSAGE, REFER
> Supported: timer, replaces, norefersub
> Session-Expires: 1800
> Min-SE: 90
> P-Asserted-Identity: "Rick" <sip:1022 at 10.199.240.176>
> Max-Forwards: 68
> User-Agent: Awesome Calling Platform 3.0
> Content-Type: application/sdp
> Content-Length:   463
> 
> v=0
> o=- 128351188 128351188 IN IP4 34.206.126.53
> s=Asterisk
> c=IN IP4 34.206.126.53
> t=0 0
> m=audio 30010 RTP/AVP 0 101
> a=maxptime:150
> a=rtpmap:0 PCMU/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-16
> a=sendrecv
> a=rtcp:30011
> a=ptime:20
> a=ice-ufrag:Cw3k5LF5
> a=ice-pwd:SyzlcKXcD2CnOT4hOw72yyvq4c
> a=candidate:aUPmOZbVuTuCQ7B9 1 UDP 2130706431 34.206.126.53 30010 typ host
> a=candidate:aUPmOZbVuTuCQ7B9 2 UDP 2130706430 34.206.126.53 30011 typ host 
> 
> 
> 2020/01/26 19:07:01.211105 37.17.41.5:25171 -> 10.199.240.19:5078
> SIP/2.0 400 Bad Request
> Via: SIP/2.0/TCP
> some.proxy.net:5078;branch=z9hG4bK24ec.940ea1b24f9ae5d68a6f97928661dbb6.0
> Via: SIP/2.0/UDP
> some.proxy.net:5078;rport=5078;received=10.199.240.135;branch=z9hG4bK24ec.73c81b0f32164242a9bf0beb0f96f7bb.0
> Via: SIP/2.0/UDP
> 10.199.240.176:7060;received=10.199.240.176;rport=7060;branch=z9hG4bKPj726e453b-eb1b-4e07-b49d-45703bc42e38
> From: "Rick"
> <sip:1022 at 10.199.240.176>;tag=1c95c3be-0c2a-44ef-8715-28735586ad95
> To: <sip:jyu3xsfkrz6c5qn at 10.199.240.135>;tag=F6209FFC-FB2B5291
> CSeq: 23870 INVITE
> Call-ID: 63cf568c-eef4-4262-8e6b-db3f6caedfbb
> Record-Route:
> <sip:34.202.130.141:5078;transport=tcp;r2=on;lr;nat=yes;rtp=bridge>,
> <sip:34.202.130.141:5078;r2=on;lr;nat=yes;rtp=bridge>,
> <sip:3.220.42.184:5078;lr>
> User-Agent: PolycomVVX-VVX_450-UA/5.8.0.13851
> Accept-Language: en
> Content-Length: 0
> 
> 
> *And few seconds later: *
> 
> 2020/01/26 19:07:06.187829 10.199.240.19:5078 -> 37.17.41.5:25171
> INVITE sip:jyu3xsfkrz6c5qn at 10.3.0.116;transport=tcp SIP/2.0
> Record-Route:
> <sip:34.202.130.141:5078;transport=tcp;r2=on;lr;nat=yes;rtp=bridge>
> Record-Route: <sip:34.202.130.141:5078;r2=on;lr;nat=yes;rtp=bridge>
> Record-Route: <sip:3.220.42.184:5078;lr>
> Via: SIP/2.0/TCP
> some.proxy.net:5078;branch=z9hG4bK32d3.45058b373afc3bd5897903a83bc0de7d.0
> Via: SIP/2.0/UDP
> some.proxy.net:5078;rport=5078;received=10.199.240.135;branch=z9hG4bK32d3.257af0eab041dbd2a240416d1c6e454f.0
> Via: SIP/2.0/UDP
> 10.199.240.179:7060;received=10.199.240.179;rport=7060;branch=z9hG4bKPjc442ef42-b769-4fdc-81cf-33453aeaae67
> From: "Rick"
> <sip:1022 at 10.199.240.179>;tag=b44068d2-d1af-4b56-87c0-2ea334784c94
> To: <sip:jyu3xsfkrz6c5qn at 10.199.240.135>
> Contact: <sip:asterisk at 10.199.240.179:7060;alias=10.199.240.179~7060~1>
> Call-ID: f9f4006d-8df9-4501-a77d-d3f7ba45c327
> CSeq: 14602 INVITE
> Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE,
> CANCEL, UPDATE, MESSAGE, REFER
> Supported: timer, replaces, norefersub
> Session-Expires: 1800
> Min-SE: 90
> P-Asserted-Identity: "Rick" <sip:1022 at 10.199.240.179>
> Max-Forwards: 68
> User-Agent: Awesome Calling Platform 3.0
> Content-Type: application/sdp
> Content-Length:   461
> 
> v=0
> o=- 95944032 95944032 IN IP4 34.206.126.53
> s=Asterisk
> c=IN IP4 34.206.126.53
> t=0 0
> m=audio 30082 RTP/AVP 0 101
> a=maxptime:150
> a=rtpmap:0 PCMU/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-16
> a=sendrecv
> a=rtcp:30083
> a=ptime:20
> a=ice-ufrag:qgZIRgJo
> a=ice-pwd:mT7rDx0qrjOkoC4Yzlodqfl7ma
> a=candidate:aUPmOZbVuTuCQ7B9 1 UDP 2130706431 34.206.126.53 30082 typ host
> a=candidate:aUPmOZbVuTuCQ7B9 2 UDP 2130706430 34.206.126.53 30083 typ host
> 
> 
> 
> but this one was succeed
> 
> 2020/01/26 19:07:07.349559 37.17.41.5:25171 -> 10.199.240.19:5078
> SIP/2.0 180 Ringing
> Via: SIP/2.0/TCP 
> some.proxy.net:5078;branch=z9hG4bK32d3.45058b373afc3bd5897903a83bc0de7d.0
> Via: SIP/2.0/UDP
> some.proxy.net:5078;rport=5078;received=10.199.240.135;branch=z9hG4bK32d3.257af0eab041dbd2a240416d1c6e454f.0
> Via: SIP/2.0/UDP
> 10.199.240.179:7060;received=10.199.240.179;rport=7060;branch=z9hG4bKPjc442ef42-b769-4fdc-81cf-33453aeaae67
> From: "Rick"
> <sip:1022 at 10.199.240.179>;tag=b44068d2-d1af-4b56-87c0-2ea334784c94
> To: "1030_DEV" <sip:jyu3xsfkrz6c5qn at 10.199.240.135>;tag=63F0AFCC-6C807D61
> CSeq: 14602 INVITE
> Call-ID: f9f4006d-8df9-4501-a77d-d3f7ba45c327
> Contact: <sip:jyu3xsfkrz6c5qn at 10.3.0.116;transport=tcp>
> Record-Route:
> <sip:34.202.130.141:5078;transport=tcp;r2=on;lr;nat=yes;rtp=bridge>,
> <sip:34.202.130.141:5078;r2=on;lr;nat=yes;rtp=bridge>,
> <sip:3.220.42.184:5078;lr>
> User-Agent: PolycomVVX-VVX_450-UA/5.8.0.13851
> Allow-Events: conference,talk,hold
> Accept-Language: en
> Call-Info: <sip:some.proxy.net>;appearance-index=1
> Content-Length: 0
> 
> 
> 
> 
> 
> --
> Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
> 
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users