You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
I agree with you.
But now I see that after
SIP/2.0 180 Ringing
From: <sip:1111@1.2.3.4>;tag=14003117305244
To: <sip:2222@5.6.7.8>;tag=S7nIf9Z
Call-ID: 0KaR2073911201UQbcGhEfDeMek
CSeq: 669313 INVITE Content-Length: 0
Via: SIP/2.0/UDP 1.2.3.4:5060;rport=5060;received=10.56.63.10;branch=z9hG4bK00000005167007511555
Contact: <sip:atpsh-5bf3d61d-2547-1@10.56.42.33>
Record-Route: <sip:KITS1.MSS.LIFE.COM:5060;transport=UDP;lr>
I getting BYE from SBC as
BYE sip:atpsh-5bf4031e-3f23-1@10.56.42.33 SIP/2.0
From: <sip:1111@1.2.3.4>;tag=14003117305244
To: <sip:2222@5.6.7.8>;tag=S7nIf9Z
Max-Forwards: 70
Via: SIP/2.0/UDP KITS1.MSS.LIFE.COM:5060;branch=z9hG4bK00000016862453278154
Call-ID: 9afY9565014201gpbcGhEfCmGjd@KITS1.MSS.LIFE.COM
CSeq: 670210 BYE
Reason: Q.850;cause=16 Content-Length: 0
But kamailio sends to Linphone BYE with second route in r-uri
BYE sip:5.6.7.8:5081;transport=tcp;r2=on;lr;ftag=02003459426351;did=96e.f6f2;vsf=AAAAAAoLCAsBCQcKAnVzehQYeHoeYn1jHxpoCWcFCmN4Oj5lcj1waG9uZQ--;vst=AAAAAAoLAQ4DAA4DAHlnYg4HGh59BRloCWcFCmN4Oj5eB04VGlIeDW9uZQ--;nat=yes SIP/2.0
From: <sip:1111@1.2.3.4>;tag=14003117305244
To: <sip:2222@5.6.7.8>;tag=S7nIf9Z
Max-Forwards: 70
Via: SIP/2.0/UDP KITS1.MSS.LIFE.COM:5060;branch=z9hG4bK00000016862453278154
Call-ID: 9afY9565014201gpbcGhEfCmGjd@KITS1.MSS.LIFE.COM
CSeq: 670210 BYE
Reason: Q.850;cause=16 Content-Length: 0
How I can got r-uri from original INVITE in this case?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.