sr-users

sr-users@lists.kamailio.org

39 participants
37513 discussions

Periodic keepalive for WebRTC clients
by Xuo Guoto 22 Mar '22

22 Mar '22

Hello all, I have a [SIP client] <-> Kamailio <-> Asterisk installation. Sip clients are both WebRTC and Android app. WebRTC connects via 443 while Android app connects VIA TLS at port 5061. WebRTC client uses jsSIP library. My Kamailio version is 5.5.3 (x86_64/linux) I had been using asterisk directly to terminate WebRTC clients previously and was using the qualify feature to periodically send OPTIONS packet to all connected clients as a keep alive mechanism. This allowed the client to detect any loss of connectivity and reconnect back to server if there is any loss of connectivity. After moving to Kamailio I am looking for a similar feature, where Kamailio sends OPTIONS (or any other packets) periodically to the WebRTC clients. My attempts so far hasn't been a success. I am aware of couple of options for keepliave in kamailio: 1. nat_keeplaive() I have some what naively copied the example from nat_keepalive() documentation into route[NATDETECT] but that is not working. route[NATDETECT] { force_rport(); #!ifdef WITH_WEBSOCKETS if (nat_uac_test(64)) { if (is_method("REGISTER")) { fix_nated_register(); } else { if (!add_contact_alias()) { sl_send_reply("400", "Bad Request"); exit; } } setflag(FLT_NATS); return; } #!endif if (nat_uac_test(19)) { if (is_method("REGISTER")) { fix_nated_register(); } fix_contact(); } setflag(FLT_NATS); if ((method=="REGISTER" || method=="SUBSCRIBE" || (method=="INVITE" && !has_totag())) && client_nat_test("3")) { nat_keepalive(); } return; } 2. keepalive module This looks like what I want, but I am not sure how to add a new WebRTC connection to the list of endpoints for pinging. This is the handler for xhttp:request, should the ka_add_destination be added here? event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); if ($Rp != MY_WS_PORT #!ifdef WITH_TLS && $Rp != MY_WSS_PORT #!endif ) { xlog("L_WARN", "HTTP request received on $Rp\n"); xhttp_reply("403", "Forbidden", "", ""); exit; } if ($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm=~"GET") { if ($hdr(Host) == $null || !is_myself("sip:" + $hdr(Host))) { xhttp_reply("403", "Forbidden", "", ""); exit; } if (ws_handle_handshake()) { exit; } } xhttp_reply("404", "Not Found", "", ""); } My search so far has not returned any other means to send options packets to WebRTC clients. Been banging my head around this for couple of days, and any help will be much appreciated. X.

1 0

Dialog module errors with dmq
by Olli Attila 22 Mar '22

22 Mar '22

Hello, I have two Kamailio nodes. Couple of days of ago I enabled dmq to replicate dialogs between these two Kamailio nodes. Now that the dmq is enabled, we are seeing lot of warning and notice messages on kamailio logs related to the dialog module. Is there something I have missed when configuring dlg_manage & dmq replication that might cause this? No calls have been affected negatively by this though. Kamailio 1 node prints lot of this: Mar 4 08:20:25 /usr/sbin/kamailio[14316]: WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK with route param 'a5d.ebf1' [3418:8126] and call-id 'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020' Mar 4 08:20:28 /usr/sbin/kamailio[14313]: WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for BYE with route param 'a5d.ebf1' [3418:8126] and call-id 'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020' Mar 4 08:21:56 /usr/sbin/kamailio[14315]: WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK with route param '689.f2f1' [2438:7983] and call-id 'SD8o63c01-47972a87ee1fd8791ddf27b650badcba-v300g00010' Kamailio 2 node prints lot of this: Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog [dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old (0x7fe07b84e980 ref 1) Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog [dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old (0x7fe07bb03360 ref 1) Mar 4 08:21:59 /usr/sbin/kamailio[8005]: NOTICE: dialog [dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old (0x7fe07b528300 ref 1) (Version: kamailio 5.5.3 (x86_64/linux) 473cef on both kamailio nodes) [root@kamailio-1]# kamcmd dmq.list_nodes { host: 172.19.194.140 port: 5060 proto: * resolved_ip: 172.19.194.140 status: active last_notification: 0 local: 0 } { host: 172.19.194.132 port: 5060 proto: * resolved_ip: 172.19.194.132 status: active last_notification: 0 local: 1 } [root@kamailio-2]# kamcmd dmq.list_nodes { host: 172.19.194.132 port: 5060 proto: * resolved_ip: 172.19.194.132 status: active last_notification: 0 local: 0 } { host: 172.19.194.140 port: 5060 proto: * resolved_ip: 172.19.194.140 status: active last_notification: 0 local: 1 } ### On Kamailio 1: ### #!define DMQ_LOCAL_ADDR "sip:172.19.194.132:5060" #!define DMQ_PEER_ADDR "sip:172.19.194.140:5060" ### On Kamailio 2: ### #!define DMQ_LOCAL_ADDR "sip:172.19.194.140:5060" #!define DMQ_PEER_ADDR "sip:172.19.194.132:5060" ### On Kamailio 1 & 2:### modparam("dmq", "server_address", DMQ_LOCAL_ADDR) modparam("dmq", "notification_address", DMQ_PEER_ADDR) modparam("dialog", "profiles_with_value", "total_dialogs") modparam("dialog", "enable_dmq", 1) route[INITIAL] { ...located at the bottom of the initial route... if(is_method("INVITE") && !has_totag()) { dlg_manage(); } } Cheers, Olli

2 2

About SMSC multi-byte support
by shigeru ishida 22 Mar '22

22 Mar '22

Hi all, I have a little question. I tried SMS over IMS on my smartphones with docker_open5gs (using Kamailio and Open5GS), and the multibyte message (Japanese) was garbled at the recipient smartphone. docker_open5gs URL: https://github.com/herlesupreeth/docker_open5gs Also, docker_open5gs uses Kamailio v5.3. I would be very glad if you could tell me about Kamailio's support for multi-byte SMS. Best regards, --Shigeru

2 2

Kamailio : Parallel Forking
by Paclinio 21 Mar '22

21 Mar '22

I've been trying to do parallel forking but i've a problem. It's when the conversation ends that the user that is in a private network can't send a bye to kamailio and i don't know why. But the on in public network (4G) can. I think it's related to record_route() or Via but I'm not sure. I'm also trying to use lookup on users that are in my domain but the problem is that I don't know how to go through all my append_branch() and then t_relay. My Audio with RTPENGINE works correctly, the only problem is really this SIP method that doesn't go to kamailio. Config : request_route { route(INVITE); exit; } route[INVITE]{ route(RECORD_ROUTE); route(GROUP_RELAY_SER); switch($tU) { case "112": xlog("MY_SEVERITY"," -- Calling Group Serial"); route(GROUP_RELAY_SER); break; case "113": // This number does not exist (It's not a subscriber). xlog("MY_SEVERITY"," -- Calling Group Parallel"); route(GROUP_RELAY_PAR); break; default: xlog("MY_SEVERITY"," -- Calling Someone"); route(LOCATION); route(RELAY); } exit; } route[RECORD_ROUTE]{ # - remove preloaded route headers remove_hf("Route"); if(is_method("INVITE|SUBSCRIBE")) { # record routing for dialog forming requests (in case they are routed) record_route(); } } route[GROUP_RELAY_PAR]{ t_on_reply("MANAGE_REPLY"); #!ifndef WITH_BRIDGE_ON_FAIL setbflag(FLB_BRIDGE); #!endif route(IPV4V6); route(NATMANAGE); append_branch("sip:9919995@192.168.1.24:5066"); append_branch("sip:9919992@192.168.1.26:5066"); append_branch("sip:9919991@192.168.1.10:5067"); // I Would like to do an IP in my domain and then do a lookup but I don't know how to do it. t_on_failure("GroupFailureRoute"); #Relay (aka Forward) the request t_relay(); break; } # User location service route[GROUP_LOCATION] { $avp(oexten) = $rU; if (lookup_branches("location")){ return (1); } else { return (-1); } } failure_route[GroupFailureRoute]{ t_next_contacts(); while(!route(GROUP_LOCATION)){ // Check if the next user (in serial) is logged in) if (!t_next_contacts()) { send_reply("408","Nobody available"); exit; } } t_on_failure("GroupFailureRoute"); t_relay(); } # Manage incoming replies in transaction context onreply_route[MANAGE_REPLY] { if(status=~"[12][0-9][0-9]") { if(has_body("application/sdp")){ setbflag(FLB_BRIDGE); } route(NATMANAGE); } } ----------------- Sip Trace : 2022/03/21 18:36:46.469257 149.154.195.121:9665 -> 192.168.1.41:5060 INVITE sip:113@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---4108e717927214fd;rport Max-Forwards: 70 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 226 v=0 o=Zoiper 53798437 1 IN IP4 100.79.133.159 s=Z c=IN IP4 100.79.133.159 t=0 0 m=audio 8000 RTP/AVP 0 101 8 3 97 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv 2022/03/21 18:36:46.470066 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---4108e717927214fd;rport=9665;received=149.154.195.121 To: <sip:113@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.6dfd9117 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 1 INVITE Proxy-Authenticate: Digest realm="192.168.1.41", nonce="Yji42mI4t64hHbET9W5/8CcWSWEhiKD/" Server: kamailio (5.5.4 (x86_64/linux)) Content-Length: 0 2022/03/21 18:36:46.500471 149.154.195.121:9665 -> 192.168.1.41:5060 ACK sip:113@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---4108e717927214fd;rport Max-Forwards: 70 To: <sip:113@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.6dfd9117 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 1 ACK Content-Length: 0 2022/03/21 18:36:46.549993 149.154.195.121:9665 -> 192.168.1.41:5060 INVITE sip:113@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---75020835629f7238;rport Max-Forwards: 70 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Proxy-Authorization: Digest username="9919993",realm="192.168.1.41",nonce="Yji42mI4t64hHbET9W5/8CcWSWEhiKD/",uri="sip:113@Public_IP ;transport=TCP",response="c8654099b37ca083ace2b245f22ebc71",algorithm=MD5 User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 226 v=0 o=Zoiper 53798437 1 IN IP4 100.79.133.159 s=Z c=IN IP4 100.79.133.159 t=0 0 m=audio 8000 RTP/AVP 0 101 8 3 97 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv 2022/03/21 18:36:46.556454 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665;received=149.154.195.121 To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Server: kamailio (5.5.4 (x86_64/linux)) Content-Length: 0 2022/03/21 18:36:46.558035 192.168.1.41:55008 -> 192.168.1.41:5060 INVITE sip:113@192.168.1.41:5060;transport=TCP SIP/2.0 Record-Route: <sip:Public_IP;transport=tcp;lr> Via: SIP/2.0/TCP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53798437 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36564 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36565 2022/03/21 18:36:46.558616 192.168.1.41:5060 -> 192.168.1.41:55008 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TCP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.0;i=6;rport=55008;received=192.168.1.41 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 To: <sip:113@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.4ecd297d From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Proxy-Authenticate: Digest realm="192.168.1.41", nonce="Yji42mI4t64hHbET9W5/8CcWSWEhiKD/" Server: kamailio (5.5.4 (x86_64/linux)) Content-Length: 0 2022/03/21 18:36:46.559281 192.168.1.41:55008 -> 192.168.1.41:5060 ACK sip:113@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.0;i=6 Max-Forwards: 69 To: <sip:113@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.4ecd297d From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 ACK Content-Length: 0 2022/03/21 18:36:46.559660 192.168.1.41:5060 -> 192.168.1.24:5066 INVITE sip:9919995@192.168.1.24:5066 SIP/2.0 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53798437 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36564 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36565 2022/03/21 18:36:46.559717 192.168.1.41:5060 -> 192.168.1.26:5066 INVITE sip:9919992@192.168.1.26:5066 SIP/2.0 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.2;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53798437 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36564 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36565 2022/03/21 18:36:46.559744 192.168.1.41:5060 -> 192.168.1.10:5067 INVITE sip:9919991@192.168.1.10:5067 SIP/2.0 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53798437 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36564 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36565 2022/03/21 18:36:46.566320 192.168.1.24:5066 -> 192.168.1.41:5060 SIP/2.0 100 Trying To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:36:46.580166 192.168.1.24:5066 -> 192.168.1.41:5060 SIP/2.0 180 Ringing To: <sip:113@192.168.1.41:5060>;tag=57af61cc7a9aaed7i0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: "codec5-private" <sip:9919995@192.168.1.24:5066> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:36:46.580487 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing To: <sip:113@192.168.1.41:5060>;tag=57af61cc7a9aaed7i0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: "codec5-private" <sip:9919995@192.168.1.24:5066> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:36:46.640281 192.168.1.26:5066 -> 192.168.1.41:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.2;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Content-Length: 0 2022/03/21 18:36:46.658312 192.168.1.10:5067 -> 192.168.1.41:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Content-Length: 0 2022/03/21 18:36:46.740855 192.168.1.26:5066 -> 192.168.1.41:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.2;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:36:46.741955 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:36:46.769015 192.168.1.10:5067 -> 192.168.1.41:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919991@192.168.1.10:50561;transport=TCP> To: <sip:113@192.168.1.41:5060>;tag=be610079 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.10 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:36:46.769313 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919991@192.168.1.10:50561;transport=TCP> To: <sip:113@192.168.1.41:5060>;tag=be610079 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.10 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:36:48.945301 192.168.1.26:5066 -> 192.168.1.41:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.2;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 165 v=0 o=Z 0 1 IN IP4 192.168.1.26 s=Z c=IN IP4 192.168.1.26 t=0 0 m=audio 8000 RTP/AVP 0 8 3 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv 2022/03/21 18:36:48.947154 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 200 OK Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 245 v=0 o=Z 0 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36572 RTP/AVP 0 8 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:36573 2022/03/21 18:36:48.953782 192.168.1.41:5060 -> 192.168.1.24:5066 CANCEL sip:9919995@192.168.1.24:5066 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Max-Forwards: 69 To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 CANCEL Content-Length: 0 Reason: SIP;cause=200;text="Call completed elsewhere" 2022/03/21 18:36:48.953817 192.168.1.41:5060 -> 192.168.1.10:5067 CANCEL sip:9919991@192.168.1.10:5067 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;i=6 Max-Forwards: 69 To: <sip:113@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 CANCEL Content-Length: 0 Reason: SIP;cause=200;text="Call completed elsewhere" 2022/03/21 18:36:48.964605 192.168.1.24:5066 -> 192.168.1.41:5060 SIP/2.0 487 Request Terminated To: <sip:113@192.168.1.41:5060>;tag=57af61cc7a9aaed7i0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 Record-Route: <sip:Public_IP:5060;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:36:48.964766 192.168.1.41:5060 -> 192.168.1.24:5066 ACK sip:9919995@192.168.1.24:5066 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Max-Forwards: 69 To: <sip:113@192.168.1.41:5060>;tag=57af61cc7a9aaed7i0 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 ACK Content-Length: 0 2022/03/21 18:36:48.966945 192.168.1.24:5066 -> 192.168.1.41:5060 SIP/2.0 200 OK To: <sip:113@192.168.1.41:5060>;tag=57af61cc7a9aaed7i0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 CANCEL Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.1;i=6 Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:36:48.989036 192.168.1.10:5067 -> 192.168.1.41:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;received=192.168.1.41;i=6 Contact: <sip:9919991@192.168.1.10:50561;transport=TCP> To: <sip:113@192.168.1.41:5060>;tag=be610079 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 CANCEL User-Agent: Z 5.5.10 v2.10.17.3 Content-Length: 0 2022/03/21 18:36:48.989036 192.168.1.10:5067 -> 192.168.1.41:5060 SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---75020835629f7238;rport=9665 To: <sip:113@192.168.1.41:5060>;tag=be610079 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 INVITE User-Agent: Z 5.5.10 v2.10.17.3 Content-Length: 0 2022/03/21 18:36:48.989268 192.168.1.41:5060 -> 192.168.1.10:5067 ACK sip:9919991@192.168.1.10:5067 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.08911f0196683c93f4519bca6c923da6.3;i=6 Max-Forwards: 69 To: <sip:113@192.168.1.41:5060>;tag=be610079 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 ACK Content-Length: 0 2022/03/21 18:36:49.021133 149.154.195.121:9665 -> 192.168.1.41:5060 ACK sip:9919992@192.168.1.26:5066 SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---28ec75a236e47eb1;rport Max-Forwards: 70 Route: <sip:Public_IP;transport=tcp;r2=on;lr> Route: <sip:Public_IP:5060;r2=on;lr> Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 ACK User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:36:49.021618 192.168.1.41:5060 -> 192.168.1.26:5066 ACK sip:9919992@192.168.1.26:5066 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK04b4.064a5839a4d237786d792a9b52b0a37c.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---28ec75a236e47eb1;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 2 ACK User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:37:23.350203 149.154.195.121:9665 -> 192.168.1.41:5060 BYE sip:9919992@192.168.1.26:5066 SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---e5232f6b2a0b88d6;rport Max-Forwards: 70 Route: <sip:Public_IP;transport=tcp;r2=on;lr> Route: <sip:Public_IP:5060;r2=on;lr> Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 3 BYE Proxy-Authorization: Digest username="9919993",realm="192.168.1.41",nonce="Yji42mI4t64hHbET9W5/8CcWSWEhiKD/",uri=" sip:9919992@192.168.1.26:5066 ",response="a7440eb01dfb200b92cc1320808251da",algorithm=MD5 User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:37:23.357139 192.168.1.41:5060 -> 192.168.1.26:5066 BYE sip:9919992@192.168.1.26:5066 SIP/2.0 Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK14b4.ece7c52456dd1d2ba5e46ca9a10b6cee.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---e5232f6b2a0b88d6;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 3 BYE Proxy-Authorization: Digest username="9919993",realm="192.168.1.41",nonce="Yji42mI4t64hHbET9W5/8CcWSWEhiKD/",uri=" sip:9919992@192.168.1.26:5066 ",response="a7440eb01dfb200b92cc1320808251da",algorithm=MD5 User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:37:23.359207 192.168.1.26:5066 -> 192.168.1.41:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP Public_IP:5060;branch=z9hG4bK14b4.ece7c52456dd1d2ba5e46ca9a10b6cee.0;received=192.168.1.41;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---e5232f6b2a0b88d6;rport=9665 Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 3 BYE User-Agent: Z 5.5.9 v2.10.17.3 Content-Length: 0 2022/03/21 18:37:23.359668 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 200 OK Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---e5232f6b2a0b88d6;rport=9665 Contact: <sip:9919992@192.168.1.26:5066> To: <sip:113@192.168.1.41:5060>;tag=28e56d08 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=ed51991c Call-ID: GlECSiXh3tJ37DqYLLvm_g.. CSeq: 3 BYE User-Agent: Z 5.5.9 v2.10.17.3 Content-Length: 0 Thank you. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

Kamailio : Serial forking
by Paclinio 21 Mar '22

21 Mar '22

I've been trying to do serial forking, I've configured something that is working but when I'm looking on github and other sources it seems like my code is a little too complicated and I would like to know if there is a simpler config that I can use. To have more precision, I'm using RTPENGINE and I need to be able to go through NAT. My Config : request_route { route(INVITE); exit; } route[INVITE]{ route(RECORD_ROUTE); route(GROUP_RELAY_SER); switch($tU) { case "112": // This number does not exist (It's not a subscriber). xlog("MY_SEVERITY"," -- Calling Group Serial"); route(GROUP_RELAY_SER); break; case "113": xlog("MY_SEVERITY"," -- Calling Group Parralelle"); route(GROUP_RELAY_PAR); break; default: xlog("MY_SEVERITY"," -- Calling Someone"); route(LOCATION); route(RELAY); } exit; } route[RECORD_ROUTE]{ # - remove preloaded route headers remove_hf("Route"); if(is_method("INVITE|SUBSCRIBE")) { # record routing for dialog forming requests (in case they are routed) record_route(); } } route[GROUP_RELAY_SER]{ t_on_reply("MANAGE_REPLY"); route(IPV4V6); route(NATMANAGE); (RTP Routing is working correctly) append_branch("sip:9919995@192.168.1.41","1"); append_branch("sip:9919992@192.168.1.41", "0.2"); append_branch("sip:75575757@192.168.1.41", "0.4"); append_branch("sip:9919991@192.168.1.41", "0.5"); t_load_contacts(); t_next_contacts(); while(!route(GROUP_LOCATION)) { if (!t_next_contacts()) { send_reply("408","Timeout or nobody available"); exit; } } t_on_failure("GroupFailureRoute"); #Relay (aka Forward) the request t_relay(); break; } # User location service route[GROUP_LOCATION] { $avp(oexten) = $rU; if (lookup_branches("location")){ return (1); } else { return (-1); } } failure_route[GroupFailureRoute]{ t_next_contacts(); while(!route(GROUP_LOCATION)){ if (!t_next_contacts()) { send_reply("408","Nobody available"); exit; } } t_on_failure("GroupFailureRoute"); t_relay(); } # Manage incoming replies in transaction context onreply_route[MANAGE_REPLY] { if(status=~"[12][0-9][0-9]") { if(has_body("application/sdp")){ setbflag(FLB_BRIDGE); } route(NATMANAGE); } } --------------------------------- Here's The SIP Trace : 2022/03/21 18:28:45.265009 149.154.195.121:9665 -> 192.168.1.41:5060 INVITE sip:112@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---75083bb7c6ed8a35;rport Max-Forwards: 70 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 226 v=0 o=Zoiper 53721112 1 IN IP4 100.79.133.159 s=Z c=IN IP4 100.79.133.159 t=0 0 m=audio 8000 RTP/AVP 0 101 8 3 97 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv 2022/03/21 18:28:45.274652 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---75083bb7c6ed8a35;rport=9665;received=149.154.195.121 To: <sip:112@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.064b0d7d From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 1 INVITE Proxy-Authenticate: Digest realm="192.168.1.41", nonce="Yji2+WI4tc0uQkJ6GbQ4I9VeSUQmR6Gk" Server: kamailio (5.5.4 (x86_64/linux)) Content-Length: 0 2022/03/21 18:28:45.335876 149.154.195.121:9665 -> 192.168.1.41:5060 ACK sip:112@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---75083bb7c6ed8a35;rport Max-Forwards: 70 To: <sip:112@192.168.1.41:5060 >;tag=cbfe6543b9079987bce3b5b9a0d1195a.064b0d7d From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 1 ACK Content-Length: 0 2022/03/21 18:28:45.385686 149.154.195.121:9665 -> 192.168.1.41:5060 INVITE sip:112@192.168.1.41:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport Max-Forwards: 70 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Proxy-Authorization: Digest username="9919993",realm="192.168.1.41",nonce="Yji2+WI4tc0uQkJ6GbQ4I9VeSUQmR6Gk",uri="sip:112@Public_IP ;transport=TCP",response="54837810a66298e4542486bb6ab8ca04",algorithm=MD5 User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 226 v=0 o=Zoiper 53721112 1 IN IP4 100.79.133.159 s=Z c=IN IP4 100.79.133.159 t=0 0 m=audio 8000 RTP/AVP 0 101 8 3 97 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv 2022/03/21 18:28:45.418871 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665;received=149.154.195.121 To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Server: kamailio (5.5.4 (x86_64/linux)) Content-Length: 0 2022/03/21 18:28:45.421797 192.168.1.41:5066 -> 192.168.1.24:5066 INVITE sip:9919995@192.168.1.24:5066 SIP/2.0 Record-Route: <sip:192.168.1.41:5066;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53721112 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36502 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36503 2022/03/21 18:28:45.435659 192.168.1.24:5066 -> 192.168.1.41:5066 SIP/2.0 100 Trying To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:28:45.449138 192.168.1.24:5066 -> 192.168.1.41:5066 SIP/2.0 180 Ringing To: <sip:112@192.168.1.41:5060>;tag=694833b3bcc5722bi0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: "codec5-private" <sip:9919995@192.168.1.24:5066> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:28:45.455211 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing To: <sip:112@192.168.1.41:5060>;tag=694833b3bcc5722bi0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: "codec5-private" <sip:9919995@192.168.1.24:5066 ;alias=192.168.1.24~5066~1> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:28:55.445916 192.168.1.41:5066 -> 192.168.1.10:50561 INVITE sip:9919991@192.168.1.10:50561;transport=TCP;rinstance=034d5c22d5466df2 SIP/2.0 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53721112 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36502 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36503 2022/03/21 18:28:55.446096 192.168.1.41:5066 -> 192.168.1.24:5066 CANCEL sip:9919995@192.168.1.24:5066 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Max-Forwards: 69 To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 CANCEL Content-Length: 0 2022/03/21 18:28:55.457941 192.168.1.24:5066 -> 192.168.1.41:5066 SIP/2.0 487 Request Terminated To: <sip:112@192.168.1.41:5060>;tag=694833b3bcc5722bi0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:28:55.458874 192.168.1.41:5066 -> 192.168.1.24:5066 ACK sip:9919995@192.168.1.24:5066 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Max-Forwards: 69 To: <sip:112@192.168.1.41:5060>;tag=694833b3bcc5722bi0 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 ACK Content-Length: 0 2022/03/21 18:28:55.459394 192.168.1.24:5066 -> 192.168.1.41:5066 SIP/2.0 200 OK To: <sip:112@192.168.1.41:5060>;tag=694833b3bcc5722bi0 From: "codec3-public"<sip:9919993@192.168.1.41:5060>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 CANCEL Via: SIP/2.0/UDP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.0;i=6 Server: Cisco/SPA508G-7.6.2c Content-Length: 0 2022/03/21 18:28:55.536475 192.168.1.10:50561 -> 192.168.1.41:5066 SIP/2.0 100 Trying Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Content-Length: 0 2022/03/21 18:28:55.758738 192.168.1.10:50561 -> 192.168.1.41:5066 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919991@192.168.1.10:50561;transport=TCP> To: <sip:112@192.168.1.41:5060>;tag=575a7d2e From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.10 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:28:55.763664 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919991@192.168.1.10:50561 ;transport=TCP;alias=192.168.1.10~50561~2> To: <sip:112@192.168.1.41:5060>;tag=575a7d2e From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.10 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:29:05.761477 192.168.1.41:5066 -> 192.168.1.26:32821 INVITE sip:9919992@192.168.1.26:5066;rinstance=791ce762698e7422;transport=tcp SIP/2.0 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.2;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Zoiper v2.10.17.3-mod Allow-Events: presence, kpml, talk Content-Length: 302 v=0 o=Zoiper 53721112 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36502 RTP/AVP 0 101 8 3 97 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=sendrecv a=rtcp:36503 2022/03/21 18:29:05.761547 192.168.1.41:5066 -> 192.168.1.10:50561 CANCEL sip:9919991@192.168.1.10:50561;transport=TCP;rinstance=034d5c22d5466df2 SIP/2.0 Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Max-Forwards: 69 To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 CANCEL Content-Length: 0 2022/03/21 18:29:05.799795 192.168.1.10:50561 -> 192.168.1.41:5066 SIP/2.0 200 OK Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Contact: <sip:9919991@192.168.1.10:50561;transport=TCP> To: <sip:112@192.168.1.41:5060>;tag=575a7d2e From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 CANCEL User-Agent: Z 5.5.10 v2.10.17.3 Content-Length: 0 2022/03/21 18:29:05.800776 192.168.1.10:50561 -> 192.168.1.41:5066 SIP/2.0 487 Request Terminated Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 To: <sip:112@192.168.1.41:5060>;tag=575a7d2e From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE User-Agent: Z 5.5.10 v2.10.17.3 Content-Length: 0 2022/03/21 18:29:05.801104 192.168.1.41:5066 -> 192.168.1.10:50561 ACK sip:9919991@192.168.1.10:50561;transport=TCP;rinstance=034d5c22d5466df2 SIP/2.0 Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.1;i=6 Max-Forwards: 69 To: <sip:112@192.168.1.41:5060>;tag=575a7d2e From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 ACK Content-Length: 0 2022/03/21 18:29:05.844860 192.168.1.26:32821 -> 192.168.1.41:5066 SIP/2.0 100 Trying Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.2;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 To: <sip:112@192.168.1.41:5060> From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Content-Length: 0 2022/03/21 18:29:06.045373 192.168.1.26:32821 -> 192.168.1.41:5066 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.2;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066;transport=tcp> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:29:06.046528 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 180 Ringing Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066 ;transport=tcp;alias=192.168.1.26~32821~2> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 0 2022/03/21 18:29:11.055497 192.168.1.26:32821 -> 192.168.1.41:5066 SIP/2.0 200 OK Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.6cdc4420824fc17383578fd933a4963b.2;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066;transport=tcp> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 165 v=0 o=Z 0 1 IN IP4 192.168.1.26 s=Z c=IN IP4 192.168.1.26 t=0 0 m=audio 8000 RTP/AVP 0 8 3 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv 2022/03/21 18:29:11.061482 192.168.1.41:5060 -> 149.154.195.121:9665 SIP/2.0 200 OK Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---ba46a700c4dfa090;rport=9665 Record-Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Record-Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066 ;transport=tcp;alias=192.168.1.26~32821~2> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp User-Agent: Z 5.5.9 v2.10.17.3 Allow-Events: presence, kpml, talk Content-Length: 245 v=0 o=Z 0 1 IN IP4 192.168.1.41 s=Z c=IN IP4 192.168.1.41 t=0 0 m=audio 36518 RTP/AVP 0 8 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:36519 2022/03/21 18:29:11.144532 149.154.195.121:9665 -> 192.168.1.41:5060 ACK sip:9919992@192.168.1.26:5066;transport=tcp;alias=192.168.1.26~32821~2 SIP/2.0 Via: SIP/2.0/TCP 100.79.133.159:5060 ;branch=z9hG4bK-524287-1---f49bbd15731e8f8d;rport Max-Forwards: 70 Route: <sip:Public_IP;transport=tcp;r2=on;lr> Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 ACK User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:29:11.152633 192.168.1.41:5066 -> 192.168.1.26:32821 ACK sip:9919992@192.168.1.26:5066;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 192.168.1.41:5066 ;branch=z9hG4bKf831.422a25f74a8ad6c743d75a28764bc8b7.0;i=6 Via: SIP/2.0/TCP 100.79.133.159:5060 ;received=149.154.195.121;branch=z9hG4bK-524287-1---f49bbd15731e8f8d;rport=9665 Max-Forwards: 69 Contact: <sip:9919993@100.79.133.159:5060 ;transport=tcp;alias=149.154.195.121~9665~2> To: <sip:112@192.168.1.41:5060>;tag=dd58ff56 From: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 ACK User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:29:20.514914 192.168.1.26:32821 -> 192.168.1.41:5066 BYE sip:9919993@100.79.133.159:5060;transport=tcp;alias=149.154.195.121~9665~2 SIP/2.0 Via: SIP/2.0/TCP 192.168.1.26:5066 ;branch=z9hG4bK-524287-1---404c84aa134e2a04 Max-Forwards: 70 Route: <sip:192.168.1.41:5066;transport=tcp;r2=on;lr> Route: <sip:Public_IP;transport=tcp;r2=on;lr> Contact: <sip:9919992@192.168.1.26:5066;transport=tcp> To: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 From: <sip:112@192.168.1.41:5060>;tag=dd58ff56 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 BYE User-Agent: Z 5.5.9 v2.10.17.3 Content-Length: 0 2022/03/21 18:29:20.517617 192.168.1.41:5060 -> 149.154.195.121:9665 BYE sip:9919993@100.79.133.159:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP Public_IP:5060;branch=z9hG4bKf831.2578b48bc3463ab1aed37eba97036001.0;i=5 Via: SIP/2.0/TCP 192.168.1.26:5066 ;rport=32821;branch=z9hG4bK-524287-1---404c84aa134e2a04 Max-Forwards: 69 Contact: <sip:9919992@192.168.1.26:5066 ;transport=tcp;alias=192.168.1.26~32821~2> To: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 From: <sip:112@192.168.1.41:5060>;tag=dd58ff56 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 BYE User-Agent: Z 5.5.9 v2.10.17.3 Content-Length: 0 2022/03/21 18:29:20.584230 149.154.195.121:9665 -> 192.168.1.41:5060 SIP/2.0 200 OK Via: SIP/2.0/TCP 192.168.1.41:5060 ;branch=z9hG4bKf831.2578b48bc3463ab1aed37eba97036001.0;i=5 Via: SIP/2.0/TCP 192.168.1.26:5066 ;rport=32821;branch=z9hG4bK-524287-1---404c84aa134e2a04 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 From: <sip:112@192.168.1.41:5060>;tag=dd58ff56 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 BYE User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 2022/03/21 18:29:20.584431 192.168.1.41:5066 -> 192.168.1.26:32821 SIP/2.0 200 OK Via: SIP/2.0/TCP 192.168.1.26:5066 ;rport=32821;branch=z9hG4bK-524287-1---404c84aa134e2a04 Contact: <sip:9919993@100.79.133.159:5060;transport=tcp> To: "codec3-public"<sip:9919993@192.168.1.41:5060 ;transport=TCP>;tag=35ce2334 From: <sip:112@192.168.1.41:5060>;tag=dd58ff56 Call-ID: RtH8fBIrIgUYPAkxlxjI4Q.. CSeq: 2 BYE User-Agent: Zoiper v2.10.17.3-mod Content-Length: 0 Thank you. Thomas <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

Can Kamailio send an ACK to a final response?
by Marrold 21 Mar '22

21 Mar '22

Hello, I'm exploring using Kamailio as a dumb edge proxy, and as such I want to keep things as lean as possible. In some scenarios I would like the "core" proxies to signal to the edge that a request should be dropped without a response. This could be with a custom header in the reply or perhaps a 444 response ( nginx uses this internally to drop a request without responding ) I have discovered that if I drop the response in the reply_route, the edge proxy doesn't send an ACK and keeps retransmitting the request until it times out, at which point it sends a 408 back to the UA. Is there any way to ACK the response from the core and destroy the transaction? Thanks Matthew

3 2

Kamailio WebRTC Call Not Working
by Ankit Jayswal 21 Mar '22

21 Mar '22

Hi, I have configured Kamailio to register a SIP user over websocket. SIP users are getting registered over webphone like JSSIP fine but not able to establish the call scenario below. >From Twilio Trunk - INVITE - KAMAILIO - ASTERISK - play hello world - Dial SIP user 101@Kamailio_IP - Rings 101 and Answer - Hangup. Here, 101 is registered with Kamailio IP, and I am sending a call from Twilio SIP trunk to Kamailio server IP. Asterisk is on port 5080 and Kamailio is on port 5090 both are on the same host 45.118.163.244. This above call scenario is NOT working with Webphones registered via JSSIP. I think the second call leg from Asterisk -> Kamailio is not getting set up properly and ACK is not getting confirmed here, call connects for some time and no voice transmits and then disconnects. The same call scenario is working with users registered at Softphone like Zoiper perfectly fine. No idea why it is not working with a webphone. I have attached kamailio.cfg, Kamailio log and Asterisk's pjsip logs here. So, please guide me on this as soon as possible. -- Thanks & Regards, *Ankit Jayswal* | Specialist - Software Development

1 0

pseudo var for From and To sip uri port
by Patrick Karton 20 Mar '22

20 Mar '22

Hello, is there a pseudo variable for setting only sip uri port for From and To Headers like $rp for R-URI ?

1 0

dialog module issues (BYE Request issued) when topos is enabled
by Patrick Karton 19 Mar '22

19 Mar '22

i am using dialog and topos module. but i have an issue i think with topos module. When topos module is disabled all the call flow works well but when i enable topos module i have this weird behaviour : after Caller sends BYE and complete the call , i receive later a BYE Request issued by the dialog module towards Caller and Callee. Does anyone already had that issue ? modparam("dialog", "enable_stats", 1) modparam("dialog", "hash_size", 1024) modparam("dialog", "rr_param", "oovdlg") modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_mode", 0) modparam("dialog", "db_update_period", 30) modparam("dialog", "wait_ack", 1) modparam("dialog", "ka_timer", 10) modparam("dialog", "ka_interval", 30) modparam("dialog", "profiles_with_value", "concurrent_calls") modparam("dialog", "end_timeout", 180) modparam("dialog", "default_timeout", 3600) modparam("dialog", "noack_timeout", 90) modparam("dialog", "early_timeout", 300) modparam("dialog", "dlg_extra_hdrs", "X-OOV-Hint: Dlg-hit\r\n") modparam("db_text", "db_mode", 0) modparam("db_text", "emptystring", 0) modparam("db_text", "file_buffer_size", 8192) modparam("db_text", "max_result_rows", 1000) modparam("topos", "storage", "db") modparam("topos", "db_url", "text:///home/sbc/database") modparam("topos", "mask_callid", 0) modparam("topos", "sanity_checks", 0) modparam("topos", "contact_mode", 0)

1 0

DMQ version compatability
by Ben Kaufman 19 Mar '22

19 Mar '22

Daniel, In a recent thread you stated the following regarding DMQ compatibility between versions: "if you do dmq replication between kamailio systems running different major versions, then it is likely to get memory leaks due to replication of data and most probably cannot be fixed. This is because internal structures of modules (also dmq commands) can change, practically what an instance does is not ensured to happen on the other instance. Just for example, from my mind, htable got some changes during past releases, dmq also has significant enhancements by getting support for more transport protocols." Is it possible to get a bit more clarification on this, particularly as it relates to DMQ_USRLOC? I'm hoping to do rolling updates, but don't want to end up in a situation where I've caused myself more problems than I've solved. Ben Kaufman

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users