Hello all,
Is there any way to rewrite "tu" in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE's "tu" modification before t_relay.
It works fine, but it doesn't work for CANCEL (INVITE re-parsing is disabled).
Ths,
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite “tu” in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE’s “tu” modification before t_relay.
It works fine, but it doesn’t work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite “tu” in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE’s “tu” modification before t_relay.
It works fine, but it doesn’t work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW.
INVITE --> Kam INVIRE --> ru=a ru=c tu=a tu=c fu=b fu=d <---100 <--- 100 <---180 <---180 CANCEL --> CANCEL --> ru=a ru=c tu=a tu=a fu=b fu=b <--481 Call/Transaction does not exist
Thank you,
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite tu in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITEs tu modification before t_relay.
It works fine, but it doesnt work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers, Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW.
INVITE --> Kam INVIRE --> ru=a ru=c tu=a tu=c fu=b fu=d <---100 <--- 100 <---180 <---180 CANCEL --> CANCEL --> ru=a ru=c tu=a tu=a fu=b fu=b <--481 Call/Transaction does not exist
Thank you,
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite “tu” in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE’s “tu” modification before t_relay.
It works fine, but it doesn’t work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
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
We get the same result with modparam("tm", "reparse_invite", 1) and modparam("tm", "reparse_invite", 0)
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 31, 2013 1:24 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers, Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW.
INVITE --> Kam INVIRE --> ru=a ru=c tu=a tu=c fu=b fu=d <---100 <--- 100 <---180 <---180 CANCEL --> CANCEL --> ru=a ru=c tu=a tu=a fu=b fu=b <--481 Call/Transaction does not exist
Thank you,
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite tu in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITEs tu modification before t_relay.
It works fine, but it doesnt work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
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
I checked the sources and found that building CANCEL with From/To headers used in the INVITE sent out is done when using uac functions for changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or alternatively export a function to explicitely set these internal flags from config (do be used by the script writer when knowing the from/to headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers, Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with modparam("tm", "reparse_invite", 1) and modparam("tm", "reparse_invite", 0)
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 31, 2013 1:24 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers, Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW.
INVITE --> Kam INVIRE --> ru=a ru=c tu=a tu=c fu=b fu=d <---100 <--- 100 <---180 <---180 CANCEL --> CANCEL --> ru=a ru=c tu=a tu=a fu=b fu=b <--481 Call/Transaction does not exist
Thank you,
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite “tu” in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE’s “tu” modification before t_relay.
It works fine, but it doesn’t work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
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
Thank you, we will try to test it.
-----Original Message----- From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, January 31, 2013 1:57 PM To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
I checked the sources and found that building CANCEL with From/To headers used in the INVITE sent out is done when using uac functions for changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or alternatively export a function to explicitely set these internal flags from config (do be used by the script writer when knowing the from/to headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers, Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with modparam("tm", "reparse_invite", 1) and modparam("tm", "reparse_invite", 0)
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 31, 2013 1:24 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers, Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW.
INVITE --> Kam INVIRE --> ru=a ru=c tu=a tu=c fu=b fu=d <---100 <--- 100 <---180 <---180 CANCEL --> CANCEL --> ru=a ru=c tu=a tu=a fu=b fu=b <--481 Call/Transaction does not exist
Thank you,
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O 30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3)
Kind regards, Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite tu in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITEs tu modification before t_relay.
It works fine, but it doesnt work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
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
Hello Daniel,
We tested in version 3.3.0 and got some problems:
1) Modified To header sent in CANCEL only when we add msg_apply_changes() after uac_replace_to()command in INVITE set out.
2) When we add msg_apply_changes(),INVITE is being sent out with additional Record-route header (without IP):
S<:E"@<F<INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:172.16.60.70;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnAB BXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK5653.9713646.0 Via: SIP/2.0/UDP 192.168.225.2:50602;branch=z9hG4bK00000000005ffc5d511f5cf933dcd0456cb2ffe587 4d2a08 Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ffc5 d-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone> Call-ID: 1bf13574-02e3a8c0-00010c35@192.168.225.2 CSeq: 2 INVITE Contact: sip:39936646@192.168.225.2:50602 User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x000210043a000154010010043b00015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436
v=0 o=10.203.22.10 14111 2 IN IP4 10.203.22.10 s=SIP Call c=IN IP4 10.203.22.10 t=0 0 a=sendrecv m=audio 8368 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=ptime:20
3) If TOPOH module is used, mask IP address (10.1.1.10) is sent in the second Record-route (instead of local host IP).
J5INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ff136-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:10.1.1.10;line=sr-N6IAzBFwMJZfWJZ6MGZwMx1LMBu5oB1dNB1EpSthH.yLg.WrzSMAO .KEgBFlWJu4O.VXphW4Hjt0Pjt0mtt0Pjtw.FtaC4IxoqtGPIregqW0jjtGpuI9a4tdmtenpFtGM tggKu3ugRa3.EfBCBtw3jNspKYaOm4* Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK7bff.5c4d0c12.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.qLOBF6zGZLMBj7MBvuMx3AMB1jmxuqC 93X3heroEWvH9vsCFN43qdAMxyAMxyAMxyAWRgEM.M63EMAzR3u3lpq3RV4MxprWRjuzRaBg.cw3 RMAz.PLzSM* Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ff13 6-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone> Call-ID: 3fe92128-02e3a8c0-00010c15@192.168.225.2 CSeq: 2 INVITE Contact: sip:10.1.1.10;line=sr-N6IAzBMsz.M6WBP6PxFsMJZfWBc7MBVuOBV-W.y6MxV* User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x0002100434000154010010043500015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436
v=0 o=10.203.22.10 14090 2 IN IP
Thank you,
Julia
-----Original Message----- From: Julia [mailto:juliabo@gmail.com] Sent: Thursday, January 31, 2013 2:03 PM To: 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Thank you,
we will try to test it.
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, January 31, 2013 1:57 PM
To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List'
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
I checked the sources and found that building CANCEL with From/To
headers used in the INVITE sent out is done when using uac functions for
changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or
alternatively export a function to explicitely set these internal flags
from config (do be used by the script writer when knowing the from/to
headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers,
Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with
modparam("tm", "reparse_invite", 1) and
modparam("tm", "reparse_invite", 0)
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, January 31, 2013 1:24 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers,
Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru;
tu = original tu;
fu = original fu.
In this case 481 received from GW.
INVITE --> Kam INVIRE -->
ru=a ru=c
tu=a tu=c
fu=b fu=d
<---100 <--- 100
<---180 <---180
CANCEL --> CANCEL -->
ru=a ru=c
tu=a tu=a
fu=b fu=b
<--481 Call/Transaction does not exist
Thank you,
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E.
Johansson
Sent: Thursday, January 31, 2013 10:52 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to
change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O
30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from
the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560
(tested with 3.3)
Kind regards,
Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite tu in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITEs tu modification before
t_relay.
It works fine, but it doesnt work for CANCEL (INVITE re-parsing is
disabled).
Ths,
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
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:
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
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
Hello,
On 2/4/13 2:17 PM, Julia wrote:
Hello Daniel,
We tested in version 3.3.0 and got some problems:
- Modified "To" header sent in CANCEL only when we add
*msg_apply_changes()* after uac_replace_to()command in INVITE set out.
it should work withoutmsg_apply_changes(). Can you run latest 3.3.x to be sure is not the effect of an issue already solved?
- When we add *msg_apply_changes(),*INVITE is being sent out with
additional "Record-route" header (without IP):
msg_apply_changes() should be used before record_route(), because in case of double record routing, the top one isfilled just before writing to the network, to use the address of the local socket to be used for sending.
S<:E"@<F<INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone SIP/2.0 *Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:172.16.60.70;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- *Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK5653.9713646.0 Via: SIP/2.0/UDP 192.168.225.2:50602;branch=z9hG4bK00000000005ffc5d511f5cf933dcd0456cb2ffe5874d2a08 Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ffc5d-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone> Call-ID: 1bf13574-02e3a8c0-00010c35@192.168.225.2 mailto:1bf13574-02e3a8c0-00010c35@192.168.225.2 CSeq: 2 INVITE Contact: <sip:39936646@192.168.225.2:50602 http://sip:39936646@192.168.225.2:50602> User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x000210043a000154010010043b00015503408000;ncx-info=0x407100330801C016653136343A303030303030393732333939333636343601B0020C000100113339393336363436203339393336363436
v=0 o=10.203.22.10 14111 2 IN IP4 10.203.22.10 s=SIP Call c=IN IP4 10.203.22.10 t=0 0 a=sendrecv m=audio 8368 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=ptime:20
- If TOPOH module is used, mask IP address (10.1.1.10) is sent in the
second "Record-route" (instead of local host IP).
That is fine because the next hop needs to know only the first (top) record-route address. But in your case is empty, because of double record-routing done due to msg_apply_changes() after record_route(). Again, if you do record routing after applying changes should be fine.
Cheers, Daniel
J5INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone SIP/2.0 *Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ff136-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:10.1.1.10;line=sr-N6IAzBFwMJZfWJZ6MGZwMx1LMBu5oB1dNB1EpSthH.yLg.WrzSMAO.KEgBFlWJu4O.VXphW4Hjt0Pjt0mtt0Pjtw.FtaC4IxoqtGPIregqW0jjtGpuI9a4tdmtenpFtGMtggKu3ugRa3.EfBCBtw3jNspKYaOm4* *Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK7bff.5c4d0c12.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.qLOBF6zGZLMBj7MBvuMx3AMB1jmxuqC93X3heroEWvH9vsCFN43qdAMxyAMxyAMxyAWRgEM.M63EMAzR3u3lpq3RV4MxprWRjuzRaBg.cw3RMAz.PLzSM* Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ff136-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone> Call-ID: 3fe92128-02e3a8c0-00010c15@192.168.225.2 mailto:3fe92128-02e3a8c0-00010c15@192.168.225.2 CSeq: 2 INVITE Contact: sip:10.1.1.10;line=sr-N6IAzBMsz.M6WBP6PxFsMJZfWBc7MBVuOBV-W.y6MxV* User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x0002100434000154010010043500015503408000;ncx-info=0x407100330801C016653136343A303030303030393732333939333636343601B0020C000100113339393336363436203339393336363436
v=0 o=10.203.22.10 14090 2 IN IP
Thank you,
Julia
-----Original Message----- From: Julia [mailto:juliabo@gmail.com] Sent: Thursday, January 31, 2013 2:03 PM To: 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Thank you,
we will try to test it.
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, January 31, 2013 1:57 PM
To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List'
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
I checked the sources and found that building CANCEL with From/To
headers used in the INVITE sent out is done when using uac functions for
changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or
alternatively export a function to explicitely set these internal flags
from config (do be used by the script writer when knowing the from/to
headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers,
Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with
modparam("tm", "reparse_invite", 1) and
modparam("tm", "reparse_invite", 0)
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, January 31, 2013 1:24 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers,
Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru;
tu = original tu;
fu = original fu.
In this case 481 received from GW.
INVITE --> Kam INVIRE -->
ru=a ru=c
tu=a tu=c
fu=b fu=d
<---100 <--- 100
<---180<---180
CANCEL --> CANCEL -->
ru=a ru=c
tu=a tu=a
fu=b fu=b
<--481 Call/Transaction does not existThank you,
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E.
Johansson
Sent: Thursday, January 31, 2013 10:52 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to
change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O
30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from
the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560
(tested with 3.3)
Kind regards,
Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite "tu" in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE's "tu" modification before
t_relay.
It works fine, but it doesn't work for CANCEL (INVITE re-parsing is
disabled).
Ths,
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-22767Hamburg / Germany
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:
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
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
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
Hello,
We solved problems by disabling double rr in rr module.
Now this works well! :)
Thank all of you,
Julia.
_____
From: Julia [mailto:juliabo@gmail.com] Sent: Monday, February 04, 2013 3:17 PM To: 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello Daniel,
We tested in version 3.3.0 and got some problems:
1) Modified To header sent in CANCEL only when we add msg_apply_changes() after uac_replace_to()command in INVITE set out.
2) When we add msg_apply_changes(),INVITE is being sent out with additional Record-route header (without IP):
S<:E"@<F<INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:172.16.60.70;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnAB BXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK5653.9713646.0 Via: SIP/2.0/UDP 192.168.225.2:50602;branch=z9hG4bK00000000005ffc5d511f5cf933dcd0456cb2ffe587 4d2a08 Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ffc5 d-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone> Call-ID: 1bf13574-02e3a8c0-00010c35@192.168.225.2 CSeq: 2 INVITE Contact: sip:39936646@192.168.225.2:50602 User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x000210043a000154010010043b00015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436
v=0 o=10.203.22.10 14111 2 IN IP4 10.203.22.10 s=SIP Call c=IN IP4 10.203.22.10 t=0 0 a=sendrecv m=audio 8368 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=ptime:20
3) If TOPOH module is used, mask IP address (10.1.1.10) is sent in the second Record-route (instead of local host IP).
J5INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ff136-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:10.1.1.10;line=sr-N6IAzBFwMJZfWJZ6MGZwMx1LMBu5oB1dNB1EpSthH.yLg.WrzSMAO .KEgBFlWJu4O.VXphW4Hjt0Pjt0mtt0Pjtw.FtaC4IxoqtGPIregqW0jjtGpuI9a4tdmtenpFtGM tggKu3ugRa3.EfBCBtw3jNspKYaOm4* Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK7bff.5c4d0c12.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.qLOBF6zGZLMBj7MBvuMx3AMB1jmxuqC 93X3heroEWvH9vsCFN43qdAMxyAMxyAMxyAWRgEM.M63EMAzR3u3lpq3RV4MxprWRjuzRaBg.cw3 RMAz.PLzSM* Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ff13 6-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone> Call-ID: 3fe92128-02e3a8c0-00010c15@192.168.225.2 CSeq: 2 INVITE Contact: sip:10.1.1.10;line=sr-N6IAzBMsz.M6WBP6PxFsMJZfWBc7MBVuOBV-W.y6MxV* User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x0002100434000154010010043500015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436
v=0 o=10.203.22.10 14090 2 IN IP
Thank you,
Julia
-----Original Message----- From: Julia [mailto:juliabo@gmail.com] Sent: Thursday, January 31, 2013 2:03 PM To: 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Thank you,
we will try to test it.
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, January 31, 2013 1:57 PM
To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List'
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
I checked the sources and found that building CANCEL with From/To
headers used in the INVITE sent out is done when using uac functions for
changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or
alternatively export a function to explicitely set these internal flags
from config (do be used by the script writer when knowing the from/to
headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers,
Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with
modparam("tm", "reparse_invite", 1) and
modparam("tm", "reparse_invite", 0)
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, January 31, 2013 1:24 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers,
Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru;
tu = original tu;
fu = original fu.
In this case 481 received from GW.
INVITE --> Kam INVIRE -->
ru=a ru=c
tu=a tu=c
fu=b fu=d
<---100 <--- 100
<---180 <---180
CANCEL --> CANCEL -->
ru=a ru=c
tu=a tu=a
fu=b fu=b
<--481 Call/Transaction does not exist
Thank you,
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E.
Johansson
Sent: Thursday, January 31, 2013 10:52 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to
change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O
30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from
the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560
(tested with 3.3)
Kind regards,
Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite tu in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITEs tu modification before
t_relay.
It works fine, but it doesnt work for CANCEL (INVITE re-parsing is
disabled).
Ths,
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
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:
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
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
Hello,
On 2/5/13 6:52 AM, Julia wrote:
Hello,
We solved problems by disabling double rr in rr module.
Now this works well! :)
this works well as long as you don't have kamailio bridging between networks or transport layers. In other words, if kamailio is listening on a single ip and port, all is fine.
Otherwise, like said inthe previous email, do record routing after applying changes.
Cheers, Daniel
Thank all of you,
Julia.
*From:*Julia [mailto:juliabo@gmail.com] *Sent:* Monday, February 04, 2013 3:17 PM *To:* 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' *Subject:* RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello Daniel,
We tested in version 3.3.0 and got some problems:
- Modified "To" header sent in CANCEL only when we add
*msg_apply_changes()* after uac_replace_to()command in INVITE set out.
- When we add *msg_apply_changes(),*INVITE is being sent out with
additional "Record-route" header (without IP):
S<:E"@<F<INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone SIP/2.0 *Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:172.16.60.70;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- *Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK5653.9713646.0 Via: SIP/2.0/UDP 192.168.225.2:50602;branch=z9hG4bK00000000005ffc5d511f5cf933dcd0456cb2ffe5874d2a08 Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ffc5d-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone> Call-ID: 1bf13574-02e3a8c0-00010c35@192.168.225.2 mailto:1bf13574-02e3a8c0-00010c35@192.168.225.2 CSeq: 2 INVITE Contact: <sip:39936646@192.168.225.2:50602 http://sip:39936646@192.168.225.2:50602> User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x000210043a000154010010043b00015503408000;ncx-info=0x407100330801C016653136343A303030303030393732333939333636343601B0020C000100113339393336363436203339393336363436
v=0 o=10.203.22.10 14111 2 IN IP4 10.203.22.10 s=SIP Call c=IN IP4 10.203.22.10 t=0 0 a=sendrecv m=audio 8368 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=ptime:20
- If TOPOH module is used, mask IP address (10.1.1.10) is sent in the
second "Record-route" (instead of local host IP).
J5INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone SIP/2.0 *Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ff136-t-2;vst=AAAAAHQAAAwLAQkICnABBXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:10.1.1.10;line=sr-N6IAzBFwMJZfWJZ6MGZwMx1LMBu5oB1dNB1EpSthH.yLg.WrzSMAO.KEgBFlWJu4O.VXphW4Hjt0Pjt0mtt0Pjtw.FtaC4IxoqtGPIregqW0jjtGpuI9a4tdmtenpFtGMtggKu3ugRa3.EfBCBtw3jNspKYaOm4* *Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK7bff.5c4d0c12.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.qLOBF6zGZLMBj7MBvuMx3AMB1jmxuqC93X3heroEWvH9vsCFN43qdAMxyAMxyAMxyAWRgEM.M63EMAzR3u3lpq3RV4MxprWRjuzRaBg.cw3RMAz.PLzSM* Max-Forwards: 68 From: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ff136-t-2 To: <sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6;user=phone> Call-ID: 3fe92128-02e3a8c0-00010c15@192.168.225.2 mailto:3fe92128-02e3a8c0-00010c15@192.168.225.2 CSeq: 2 INVITE Contact: sip:10.1.1.10;line=sr-N6IAzBMsz.M6WBP6PxFsMJZfWBc7MBVuOBV-W.y6MxV* User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: "39936646 39936646" sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x0002100434000154010010043500015503408000;ncx-info=0x407100330801C016653136343A303030303030393732333939333636343601B0020C000100113339393336363436203339393336363436
v=0 o=10.203.22.10 14090 2 IN IP
Thank you,
Julia
-----Original Message----- From: Julia [mailto:juliabo@gmail.com] Sent: Thursday, January 31, 2013 2:03 PM To: 'miconda@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite "tu" in CANCEL message ?
Thank you,
we will try to test it.
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, January 31, 2013 1:57 PM
To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List'
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
I checked the sources and found that building CANCEL with From/To
headers used in the INVITE sent out is done when using uac functions for
changing their value. Some internal flags are set by those functions.
So a patch should be done for remove_hf()/insert_hf() case or
alternatively export a function to explicitely set these internal flags
from config (do be used by the script writer when knowing the from/to
headers where changed in some way).
Without a patch, the uac module functions have to be used.
Cheers,
Daniel
On 1/31/13 12:29 PM, Julia wrote:
We get the same result with
modparam("tm", "reparse_invite", 1) and
modparam("tm", "reparse_invite", 0)
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, January 31, 2013 1:24 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello,
have you changed the value for tm parameter 'reparse_invite':
http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite
Cheers,
Daniel
On 1/31/13 12:02 PM, Julia wrote:
OK, but a problem is in partially re-parsing of CANCEL.
ru = modified ru;
tu = original tu;
fu = original fu.
In this case 481 received from GW.
INVITE --> Kam INVIRE -->
ru=a ru=c
tu=a tu=c
fu=b fu=d
<---100 <--- 100
<---180 <---180
CANCEL --> CANCEL -->
ru=a ru=c
tu=a tu=a
fu=b fu=b
<--481 Call/Transaction does not exist
Thank you,
-----Original Message-----
From: sr-users-bounces@lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E.
Johansson
Sent: Thursday, January 31, 2013 10:52 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
UsersMailing List
Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Unless you rewrote the To-URI in the INVITE, you really should not try to
change a CANCEL. It needs to be almost a copy of the matching INVITE.
/O
30 jan 2013 kl. 14:40 skrev Carsten Bock carsten@ng-voice.com:
Hi,
probably the best way is to simply use the uac_replace_to-method from
the uac module:
http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560
(tested with 3.3)
Kind regards,
Carsten
2013/1/30 Julia juliabo@gmail.com:
Hello all,
Is there any way to rewrite "tu" in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE's "tu" modification before
t_relay.
It works fine, but it doesn't work for CANCEL (INVITE re-parsing is
disabled).
Ths,
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-22767Hamburg / Germany
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:
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
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
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
Hello Julia,
There is a very real question that should probably be asked: why would you want to do that?
Kamailio provides many capabilities, but just because you can, doesn't mean you should. :-)
With that in mind, I don't know of any SIP scenario in which altering the To header in a CANCEL message to something other than what it was in the INVITE transaction to which it corresponds is appropriate, either as a UA or as a proxy. But, perhaps it is my ignorance or lack of imagination at fault.
-- Alex
Julia juliabo@gmail.com wrote:
Hello all,
Is there any way to rewrite "tu" in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE's "tu" modification before t_relay.
It works fine, but it doesn't work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in "ru" and "tu", because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified "tu" is not included.
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Wednesday, January 30, 2013 3:53 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
Hello Julia,
There is a very real question that should probably be asked: why would you want to do that?
Kamailio provides many capabilities, but just because you can, doesn't mean you should. :-)
With that in mind, I don't know of any SIP scenario in which altering the To header in a CANCEL message to something other than what it was in the INVITE transaction to which it corresponds is appropriate, either as a UA or as a proxy. But, perhaps it is my ignorance or lack of imagination at fault.
-- Alex
Julia juliabo@gmail.com wrote:
Hello all,
Is there any way to rewrite "tu" in CANCEL message in 3.2.1?
We use remove_hf / insert_hf for INVITE's "tu" modification before t_relay.
It works fine, but it doesn't work for CANCEL (INVITE re-parsing is disabled).
Ths,
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
On 01/30/2013 09:31 AM, Julia wrote:
We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in "ru" and "tu", because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified "tu" is not included.
I would say your PSTN GW is doing it wrong. No routing should ever be done on To. It is a purely cosmetic commentary on the intended logical destination of the call. Only the RURI should be used for that.
Yes, we know it's wrong. But if we really need it, is there a way to do it?
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Wednesday, January 30, 2013 4:36 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
On 01/30/2013 09:31 AM, Julia wrote:
We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in "ru" and "tu", because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified "tu" is not included.
I would say your PSTN GW is doing it wrong. No routing should ever be done on To. It is a purely cosmetic commentary on the intended logical destination of the call. Only the RURI should be used for that.
I had the same problem with CANCEL requests for transactions created by an INVITE that was rewritten in a branch_route. I sent a small patch to dev list in October and didn't receive any comment. You can try to find it in sr-dev archive for October 2012.
Yes, we know it's wrong. But if we really need it, is there a way to do it?
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Wednesday, January 30, 2013 4:36 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] How to rewrite "tu" in CANCEL message ?
On 01/30/2013 09:31 AM, Julia wrote:
We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in "ru" and "tu", because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified "tu" is not included.
I would say your PSTN GW is doing it wrong. No routing should ever be done on To. It is a purely cosmetic commentary on the intended logical destination of the call. Only the RURI should be used for that.
On 01/30/2013 07:36 AM, Alex Balashov wrote:
On 01/30/2013 09:31 AM, Julia wrote:
We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in "ru" and "tu", because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified "tu" is not included.
I would say your PSTN GW is doing it wrong. No routing should ever be done on To. It is a purely cosmetic commentary on the intended logical destination of the call. Only the RURI should be used for that.
You're 100% correct, but I've also run into carriers that do it. Trying to convince them to change has so far been as effective as talking to a brick wall.
Corey
I don't understand how this happens, hopefully somebody know why?? When the BYE is sent to Kamailio, it forwards to an incorrect address. This address is only in dispatcher, so I don't understand how it gets to that?
U 192.168.9.130:5060 -> 4.55.10.163:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 4.55.10.163:5060;branch=z9hG4bK0bB4b99383b1a4d3f48..From: <sip :+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..To: <sip:+1<inbound_number>@192.168.9.130 :5060>;tag=as622c3fb5..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 11847 INVITE..Server: FP BX-2.10.0(1.8.9.3)..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, P UBLISH..Supported: replaces, timer..Contact: <sip:+1<inbound_number>@10.1.7.86:5060>..Content-Type: a pplication/sdp..Content-Length: 228....v=0..o=root 338878463 338878463 IN IP4 10.1.7.86..s=Aste risk PBX 1.8.9.3..c=IN IP4 10.1.7.86..t=0 0..m=audio 13212 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000. .a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=ptime:20..a=sendrecv..
U 10.1.7.86:5060 -> 192.168.9.130:5060 BYE sip:+1<dialed_number>@4.55.10.163:5060 SIP/2.0..Via: SIP/2.0/UDP 10.1.7.86:5060;branch=z9hG4bK6e 5d6461;rport..Max-Forwards: 70..From: <sip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4 .55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-HangupCause: Protocol e rror, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 192.168.9.130:5060 -> 205.158.163.150:5060 BYE sip:+1<dialed_number>@<wan_ip>:5060 SIP/2.0..Record-Route: <sip:<wan_ip>:5060;lr=on> ..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6d4b.7269e5c5.0..Via: SIP/2.0/UDP 10.1.7.86:5060 ;branch=z9hG4bK6e5d6461;rport=5060..Max-Forwards: 69..From: <sip:+1<inbound_number>@192.168.9.130:506 0>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-H angupCause: Protocol error, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 205.158.163.150:5060 -> 192.168.9.130:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6 d4b.7269e5c5.0..Via: SIP/2.0/UDP 74.63.151.37:13000;branch=z9hG4bK6e5d6461;rport=5060..From: <s ip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup -oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 102 BYE..Content-Lengt h: 0....
It is very likely your config is executing dispatcher function for the BYE. You can load debugger module and enable execution trace logging, so you see what functions are executed from the configuration file.
I don't see the Record-Route in the reply and Route header in the BYE, typical usage is to do record routing for handling requests within dialog.
Cheers, Daniel
On 2/13/13 9:19 PM, Scott, Matt wrote:
I don't understand how this happens, hopefully somebody know why??
When the BYE is sent to Kamailio, it forwards to an incorrect address.
This address is only in dispatcher, so I don't understand how it gets to that?
U 192.168.9.130:5060 -> 4.55.10.163:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 4.55.10.163:5060;branch=z9hG4bK0bB4b99383b1a4d3f48..From: <sip
:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..To: <sip:+1<inbound_number>@192.168.9.130
:5060>;tag=as622c3fb5..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 11847 INVITE..Server: FP
BX-2.10.0(1.8.9.3)..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, P
UBLISH..Supported: replaces, timer..Contact: <sip:+1<inbound_number>@10.1.7.86:5060>..Content-Type: a
pplication/sdp..Content-Length: 228....v=0..o=root 338878463 338878463 IN IP4 10.1.7.86..s=Aste
risk PBX 1.8.9.3..c=IN IP4 10.1.7.86..t=0 0..m=audio 13212 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000.
.a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=ptime:20..a=sendrecv..
U 10.1.7.86:5060 -> 192.168.9.130:5060
BYE sip:+1<dialed_number>@4.55.10.163:5060 SIP/2.0..Via: SIP/2.0/UDP 10.1.7.86:5060;branch=z9hG4bK6e
5d6461;rport..Max-Forwards: 70..From: <sip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To:
<sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4
.55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-HangupCause: Protocol e
rror, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 192.168.9.130:5060 -> 205.158.163.150:5060
BYE sip:+1<dialed_number>@<wan_ip>:5060 SIP/2.0..Record-Route: <sip:<wan_ip>:5060;lr=on>
..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6d4b.7269e5c5.0..Via: SIP/2.0/UDP 10.1.7.86:5060
;branch=z9hG4bK6e5d6461;rport=5060..Max-Forwards: 69..From: <sip:+1<inbound_number>@192.168.9.130:506
0>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID:
2081157154_72743403@4.55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-H
angupCause: Protocol error, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 205.158.163.150:5060 -> 192.168.9.130:5060
SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6
d4b.7269e5c5.0..Via: SIP/2.0/UDP 74.63.151.37:13000;branch=z9hG4bK6e5d6461;rport=5060..From: <s
ip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup
-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 102 BYE..Content-Lengt
h: 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
-
Alex Balashov -
Carsten Bock -
Corey Edwards -
Daniel-Constantin Mierla -
Julia -
Olle E. Johansson -
Scott, Matt -
Vitaliy Aleksandrov