[SR-Users] Re: CANCEL first, then INVITE.

Also, since a picture is worth a thousand words, it can be seen here that the INVITE for the new branch is sent before the CANCEL of the earlier branch. Again, I'm not sure why this would make any difference, but it does seem to be the current behavior. [A screenshot of a computer screen Description automatically generated] -----Original Message----- From: Ben Kaufman via sr-users &lt;sr-users(a)lists.kamailio.orgSent: Thursday, September 28, 2023 5:05 PM To: Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.orgCc: James Lipski &lt;jameslipski(a)protonmail.com&gt;om>; Ben Kaufman &lt;bkaufman(a)bcmone.comSubject: [SR-Users] Re: CANCEL first, then INVITE. CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I can reproduce this behavior easily with the config below, but I'm not quite sure how/why it matters. request_route { xinfo("[$ru] recieved\n"); $rd = "target2"; append_branch("sip:$rU@target1", "1.0"); t_load_contacts(); t_next_contacts(); t_on_failure("MANAGE_FAILURE"); t_on_branch("MANAGE_BRANCH"); t_set_fr(5000); t_relay(); exit; } branch_route[MANAGE_BRANCH] { xinfo("Sending [$ru]\n"); } failure_route[MANAGE_FAILURE] { if ( t_branch_timeout() ) { xinfo("Branch timed out.\n"); } if ( !t_next_contacts() ) { send_reply("503", "Server Error"); exit; } t_on_failure("MANAGE_FAILURE"); t_relay(); } -----Original Message----- From: James Lipski via sr-users <sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Sent: Thursday, September 28, 2023 3:08 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Cc: James Lipski <jameslipski@protonmail.com<mailto:jameslipski@protonmail.com> Subject: [SR-Users] Re: CANCEL first, then INVITE. CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, As with my previous update, I'm using the skeleton configurations (with minor changes, such as defining an external voicemail destination) just for testing purposes. With the skeleton configurations, I'm still seeing that the INVITE packet to the voicemail server sent first, and then the CANCEL to the second endpoint (please see SIP trace below). In this call example the second endpoint is a PBX, and is configured to route unanswered calls towards it's own local voicemail system. Is there a way to switch the behaviour so that the CANCEL packet towards endpoint 2 is sent FIRST; and then the INVITE to the voicemail system second? Thank you. 10.0.0.117 --- snom (endpoint 1) 10.0.0.177 --- kamailio 10.0.0.188 --- PBX (endpoint 2) 10.0.0.26 --- external voicemail system. 2023/09/28 15:41:39.122897 10.0.0.117:40274 -> 10.0.0.177:5060 INVITE sip:10000010@10.0.0.177 SIP/2.0 v: SIP/2.0/UDP 10.0.0.117:40274;branch=z9hG4bK-30wsteb4v1cl;rport f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE Max-Forwards: 70 User-Agent: snomD785/10.1.159.12 m: <sip:10000006@10.0.0.117:40274;line=y3jwlgtb>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 Proxy-Authorization: Digest username="10000006",realm="10.0.0.177",nonce="ZRXYH2UV1vNTJ01Zmy97xZsd43iZmRNW",uri="sip:10000010@10.0.0.177",response="4a1d80ae375ae8d56d7b7c602e5bbcd4 ",algorithm=MD5 c: application/sdp l: 315 v=0 o=root 1457342879 1457342879 IN IP4 10.0.0.117 s=call c=IN IP4 10.0.0.117 t=0 0 m=audio 61370 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv 2023/09/28 15:41:39.124438 10.0.0.177:5060 -> 10.0.0.117:40274 SIP/2.0 100 trying -- your call is important to us v: SIP/2.0/UDP 10.0.0.117:40274;branch=z9hG4bK-30wsteb4v1cl;rport=40274;received=10.0.0.117 f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE Content-Length: 0 2023/09/28 15:41:39.125338 10.0.0.177:5060 -> 10.0.0.188:5678 INVITE sip:10000010@10.0.0.188:5678;transport=udp;line=aab32389;alias=10.0.0.188~5678~1 SIP/2.0 Record-Route: <sip:10.0.0.177;lr;nat=yes Via: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE Max-Forwards: 69 User-Agent: snomD785/10.1.159.12 m: <sip:10000006@10.0.0.117:40274;line=y3jwlgtb;alias=10.0.0.117~40274~1>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 315 v=0 o=root 1457342879 1457342879 IN IP4 10.0.0.117 s=call c=IN IP4 10.0.0.117 t=0 0 m=audio 61370 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv 2023/09/28 15:41:39.126941 10.0.0.188:5678 -> 10.0.0.177:5060 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 Record-Route: <sip:10.0.0.177;lr;nat=yes f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177>;tag=c3579c1a01 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE l: 0 2023/09/28 15:41:39.171314 10.0.0.188:5678 -> 10.0.0.177:5060 SIP/2.0 183 Session Progress v: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 Record-Route: <sip:10.0.0.177;lr;nat=yes f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177>;tag=c3579c1a01 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE m: <sip:10000010@10.0.0.188:5678;transport=udp Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp c: application/sdp l: 247 v=0 o=- 1982229263 1982229263 IN IP4 10.0.0.188 s=- c=IN IP4 10.0.0.188 t=0 0 m=audio 59112 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv 2023/09/28 15:41:39.172272 10.0.0.177:5060 -> 10.0.0.117:40274 SIP/2.0 183 Session Progress v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 Record-Route: <sip:10.0.0.177;lr;nat=yes f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177>;tag=c3579c1a01 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE m: <sip:10000010@10.0.0.188:5678;transport=udp;alias=10.0.0.188~5678~1 Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp c: application/sdp l: 247 v=0 o=- 1982229263 1982229263 IN IP4 10.0.0.188 s=- c=IN IP4 10.0.0.188 t=0 0 m=audio 59112 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv 2023/09/28 15:41:59.129391 10.0.0.177:5060 -> 10.0.0.26:7066 INVITE sip:10000010@10.0.0.26:7066 SIP/2.0 Record-Route: <sip:10.0.0.177;lr;nat=yes Via: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.1 v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE Max-Forwards: 69 User-Agent: snomD785/10.1.159.12 m: <sip:10000006@10.0.0.117:40274;line=y3jwlgtb;alias=10.0.0.117~40274~1>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 315 v=0 o=root 1457342879 1457342879 IN IP4 10.0.0.117 s=call c=IN IP4 10.0.0.117 t=0 0 m=audio 61370 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv 2023/09/28 15:41:59.129633 10.0.0.177:5060 -> 10.0.0.188:5678 CANCEL sip:10000010@10.0.0.188:5678;transport=udp;line=aab32389;alias=10.0.0.188~5678~1 SIP/2.0 Via: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 CANCEL Max-Forwards: 69 l: 0 2023/09/28 15:41:59.130509 10.0.0.188:5678 -> 10.0.0.177:5060 SIP/2.0 200 Ok v: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 v: SIP/2.0/UDP 10.0.0.117:40274;received=10.0.0.117;branch=z9hG4bK-30wsteb4v1cl;rport=40274 Record-Route: <sip:10.0.0.177;lr;nat=yes f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177>;tag=c3579c1a01 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 INVITE m: <sip:10000010@10.0.0.188:5678;transport=udp Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp c: application/sdp l: 247 v=0 o=- 1982229263 1982229263 IN IP4 10.0.0.188 s=- c=IN IP4 10.0.0.188 t=0 0 m=audio 59112 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv 2023/09/28 15:41:59.130543 10.0.0.188:5678 -> 10.0.0.177:5060 SIP/2.0 200 Ok v: SIP/2.0/UDP 10.0.0.177;branch=z9hG4bK87d3.36c49e4bbd41f8c5625007842e35ce3a.0 f: <sip:10000006@10.0.0.177>;tag=pqxa29jt8v t: <sip:10000010@10.0.0.177>;tag=c3579c1a01 i: f1d61565275f-tqgd64ng8qmq CSeq: 2 CANCEL m: <sip:10000010@10.0.0.188:5678;transport=udp l: 0 ------- Original Message ------- On Wednesday, September 27th, 2023 at 9:43 AM, James Lipski <jameslipski@protonmail.com<mailto:jameslipski@protonmail.com>> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%<https:/… > > > > > unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org > > > > unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: