Carsten you're the man!
it was a simple case of add_contact_alias(); vs fix_nated_contact();
thanks for the insights guys
Kelvin Chua
On Fri, Nov 29, 2013 at 12:24 AM, Carsten Bock carsten@ng-voice.com wrote:
Hi,
i see. However in the request from Twinkle, there is something else wrong: For subsequent requests, the User-Agents should send it to the URI in the Contact-Header.
It is done correctly for the ACK Contact in 200 OK: Contact: sip:kelvin@1X5.6X.1X6.2X3:62280. URI in ACK: ACK sip:kelvin@1X5.6X.1X6.2X3:62280 SIP/2.0
But it is done wrong for the BYE: Contact from INVITE: Contact: sip:+1178@192.168.47.68:5060. URI in BYE: BYE sip:+1178@6X.2X1.4.1X5:5060 SIP/2.0.
There's either a problem with your carrier or with your Kamailio config. I'd assume it's somewhere in your config.
Kind regards, Carsten
2013/11/28 Kelvin Chua kelchy@gmail.com:
just to illustrate further, now i used twinkle to be on the termination
side
and generate the BYE (notice twinkle does not send a routeset)
U 2013/11/28 10:53:14.919998 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 INVITE sip:+18X88X441X1@2X8.1X1.3X.2X SIP/2.0. Record-Route: sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab. Record-Route: sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab. Accept: application/sdp. Allow: INVITE,ACK,CANCEL,BYE. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKd65d.2ef8f8e7.0. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b3c49f52df34fb7. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. To: sip:+18X88X441X1@6X.2X1.4.9X. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 INVITE. Max-Forwards: 97. Contact: sip:+1178@192.168.47.68:5060. Content-Length: 326. Content-Disposition: session; handling=required. Content-Type: application/sdp. Remote-Party-ID: sip:+1178@192.168.47.68:5060;privacy=off;screen=no. . v=0. o=Sonus_UAC 3659 8203 IN IP4 192.168.47.68. s=SIP Media Capabilities. c=IN IP4 6X.2X1.4.9X. t=0 0. m=audio 17594 RTP/AVP 0 18 96 101. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:96 iLBC/8000. a=fmtp:96 mode=30. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv. a=maxptime:30.
U 2013/11/28 10:53:14.921900 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 183 Session Progress. Record-Route: sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab. Record-Route: sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKd65d.2ef8f8e7.0;rport=5060. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b3c49f52df34fb7. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. To: <sip:+18X88X441X1@6X.2X1.4.9X ;tag=bbd932f8f9dbf9743f9b7cadcbf622ac.61d8. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 INVITE. Server: kamailio (4.0.4 (x86_64/linux)). Content-Length: 0. .
U 2013/11/28 10:53:14.922678 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKd65d.2ef8f8e7.0;rport=5060. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b3c49f52df34fb7. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. To: sip:+18X88X441X1@6X.2X1.4.9X. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 INVITE. Server: kamailio (4.0.4 (x86_64/linux)). Content-Length: 0. .
U 2013/11/28 10:53:15.191701 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 6X.2X1.4.1X5;rport=5060;branch=z9hG4bKd65d.2ef8f8e7.0,SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.0,SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b3c49f52df34fb7. Record-Route:
sip:2X8.1X1.3X.2X;lr=on;did=144.c791;nat=yes,sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab,sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab.
To: sip:+18X88X441X1@6X.2X1.4.9X;tag=vkcxq. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 INVITE. Contact: sip:kelvin@1X5.6X.1X6.2X3:62280. Server: Twinkle/1.4.2. Content-Length: 0. .
U 2013/11/28 10:53:20.348039 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 6X.2X1.4.1X5;rport=5060;branch=z9hG4bKd65d.2ef8f8e7.0,SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.0,SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b3c49f52df34fb7. Record-Route:
sip:2X8.1X1.3X.2X;lr=on;did=144.c791;nat=yes,sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab,sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab.
To: sip:+18X88X441X1@6X.2X1.4.9X;tag=vkcxq. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 INVITE. Contact: sip:kelvin@1X5.6X.1X6.2X3:62280. Content-Type: application/sdp. Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE. Server: Twinkle/1.4.2. Supported: replaces,norefersub. Content-Length:255. . v=0. o=twinkle 1795412414 1134840794 IN IP4 2X8.1X1.3X.2X. s=-. i=(o=IN IP4 10.0.193.243). c=IN IP4 2X8.1X1.3X.2X. t=0 0. m=audio 10292 RTP/AVP 0 101. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=nortpproxy:yes.
U 2013/11/28 10:53:20.376096 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 ACK sip:kelvin@1X5.6X.1X6.2X3:62280 SIP/2.0. Record-Route: sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab. Record-Route: sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKd65d.2ef8f8e7.2. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKd65d.cfcf924.2. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cB0b511583722bddcb. From: sip:+1178@192.168.47.68;tag=gK0c12d2ab. To: sip:+18X88X441X1@6X.2X1.4.9X;tag=vkcxq. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 20920 ACK. Max-Forwards: 68. Route: sip:2X8.1X1.3X.2X:5060;lr=on;did=144.c791;nat=yes. Content-Length: 0. .
U 2013/11/28 10:53:30.412621 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 BYE sip:+1178@6X.2X1.4.1X5:5060 SIP/2.0. Via: SIP/2.0/UDP 2X8.1X1.3X.2X;branch=z9hG4bK35da.9a689a04.0. Via: SIP/2.0/UDP 1X5.6X.1X6.2X3:62280;rport=62280;branch=z9hG4bKfimfuiyp. Route:
sip:6X.2X1.4.1X5;lr=on;ftag=gK0c12d2ab,sip:6X.2X1.4.9X;lr=on;ftag=gK0c12d2ab.
Max-Forwards: 16. To: sip:+1178@192.168.47.68;tag=gK0c12d2ab. From: sip:+18X88X441X1@6X.2X1.4.9X;tag=vkcxq. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 887 BYE. User-Agent: Twinkle/1.4.2. Content-Length: 0. .
U 2013/11/28 10:53:30.426129 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 SIP/2.0 500 Invalid routeset. Via: SIP/2.0/UDP 2X8.1X1.3X.2X;branch=z9hG4bK35da.9a689a04.0. Via: SIP/2.0/UDP 1X5.6X.1X6.2X3:62280;rport=62280;branch=z9hG4bKfimfuiyp. To: sip:+1178@192.168.47.68;tag=gK0c12d2ab. From: sip:+18X88X441X1@6X.2X1.4.9X;tag=vkcxq. Call-ID: 1443638876_56966636@192.168.47.68. CSeq: 887 BYE. Server: Bandwidth.com CLEC. Content-Length: 0. .
Kelvin Chua
On Thu, Nov 28, 2013 at 11:49 PM, Kelvin Chua kelchy@gmail.com wrote:
i am using only record_route() and my setup is dialog-aware. (dialog)
it's worth noting that i am doing serial fork, but this particular call
is
the first branch.
On Nov 28, 2013 11:38 PM, "Carsten Bock" carsten@ng-voice.com wrote:
Hi Olle,
actually it's an extension, i wanted to do sooner or later. If Kamailio is Dialog-Aware (e.g. dialog or dialog_ng is loaded), Kamailio "knows" what the route-set should be and could check and optionally enforce the route-set.
By the way: In the Record-Route of the "200 OK" it's "lr" and in the "ACK" the Record-Route is "lr=on". @Kelvin: You use only "record_route()" or do you have anything special in this regards in your config?
Kind regards, Carsten
2013/11/28 Olle E. Johansson oej@edvina.net:
On 28 Nov 2013, at 16:23, Alex Balashov abalashov@evaristesys.com wrote:
On 11/28/2013 10:22 AM, Kelvin Chua wrote: > hi alex, > is there a way for kamailio to force lr=on before relay? this
carrier
> is > driving me nuts
No, Kamailio (as a SIP proxy) cannot modify the Route set after the dialog is set up, in a sequential (in-dialog request) furthermore.
The client changed the syntax of the route set - but do you really consider that a change of the route set, Alex?
I guess the URI's are different.
The question here is really - can Kamailio somehow clean up the URI's in the route set for this buggy client?
/O _______________________________________________ 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
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
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
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
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
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