24 Sep
2021
24 Sep
'21
6:08 a.m.
Hello,
good it was sorted out and that you wrote what the solution, so people reading the discussion in the archive know what was the case about.
Cheers, Daniel
On 23.09.21 19:32, Angelo Sipper wrote:
Hi Daniel,
I got a response today from the provider escalation team and they actually confirmed that it was a firewall issue from their side. They were blocking their own BYE to us.... They were expecting traffic from us from one only port (as UDP behavior) and since we were sending from different ports, as TCP does, their SBC was not able to respond to us as their firewall was blocking all other ports. What can I say.... Anyway we now have this provider in operation. Thank you very much and sorry for the big message for no actual reason regarding the Kamailio.
Kind Regards, Angelo
Στις Τετ, 22 Σεπ 2021 στις 7:00 μ.μ., ο/η Angelo Sipper <sippro97@gmail.com mailto:sippro97@gmail.com> έγραψε:
Hi Daniel, Provider managed to add the transport=tcp in the contact as you suggested and call flow was fine but, another issue came up and I believe it is again TCP that causes this issue. If our side terminates the call, our Kamailio2 sends the BYE and it is accepted from the provider side terminating the call correctly. When the far end terminates the call, providers send a BYE that we never receive from the provider and our UAC remains on call. If our UAC terminates the call after the far end terminates the call we receive a 481 from the provider as the call actually does not exist any more on his side and this makes sense. Even this is not the case, to be 100% sure we have even completely disabled our firewall on the tests but we have the same results. Below I am sending you the provider trace that he sends 2 BYE to us without any response from us. These two BYE never reached our side. For testing we even changed the TCP listen port of kamailio to 5080 to be separate ports from the UDP which remains on 5060 Provider engineers cannot respond to this problem with a resolution. Can you please check if you can see something in the trace that can identify the cause of this behavior? Is it something I can change on our Kamailio2 config to avoid this? TRACE ====== INVITE sip:123456789@sip.mydomain.com:5060 <http://sip:123456789@sip.mydomain.com:5060> SIP/2.0 Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK4e1.3a5eafdb0c6cb4f6b4fbaf7faface967.0 Max-Forwards: 68 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>> Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11769 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 Content-Type: application/sdp Content-Length: 324 P-Asserted-Identity: <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>> Contact: <sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp> v=0 o=- 3841298833 3841298833 IN IP4 50.50.50.184 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 27892 RTP/AVP 8 0 101 c=IN IP4 50.50.50.184 b=TIAS:64000 a=ssrc:83234588 cname:6b760b5029f225e8 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:27893 >--- SEND ----------->-------------> [Message: 2 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:16.00120 SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK4e1.3a5eafdb0c6cb4f6b4fbaf7faface967.0 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11769 INVITE Contact: <sip:123456789@200.200.200.209:5060;transport=tcp> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Require: 100rel RSeq: 6618 Content-Length: 242 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 21561 25962 IN IP4 200.200.200.209 s=SIP Media Capabilities c=IN IP4 200.200.200.211 t=0 0 m=audio 27992 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 <--- RECV -----------<-------------< [Message: 3 of 12 ] <------------<------------< Date: 09-22-2021 Time: 08:27:17.00047 PRACK sip:123456789@200.200.200.209:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bKdd1.b4a7f8fbbf8027cc1b0a457f9e5963f7.0 Max-Forwards: 68 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11770 PRACK RAck: 6618 11769 INVITE Content-Length: 0 Contact: <sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp> >--- SEND ----------->-------------> [Message: 4 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:17.00050 SIP/2.0 200 OK Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bKdd1.b4a7f8fbbf8027cc1b0a457f9e5963f7.0 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11770 PRACK Content-Length: 0 >--- SEND ----------->-------------> [Message: 5 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:17.00053 SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK4e1.3a5eafdb0c6cb4f6b4fbaf7faface967.0 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11769 INVITE Require: 100rel RSeq: 6619 Contact: <sip:123456789@200.200.200.209:5060;transport=tcp> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Content-Length: 242 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 21561 25962 IN IP4 200.200.200.209 s=SIP Media Capabilities c=IN IP4 200.200.200.211 t=0 0 m=audio 27992 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 <--- RECV -----------<-------------< [Message: 6 of 12 ] <------------<------------< Date: 09-22-2021 Time: 08:27:17.00059 PRACK sip:123456789@200.200.200.209:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bKed1.fd8ecce909458a05324665afccdde954.0 Max-Forwards: 68 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11771 PRACK RAck: 6619 11769 INVITE Content-Length: 0 Contact: <sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp> >--- SEND ----------->-------------> [Message: 7 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:17.00062 SIP/2.0 200 OK Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bKed1.fd8ecce909458a05324665afccdde954.0 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11771 PRACK Content-Length: 0 >--- SEND ----------->-------------> [Message: 8 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:20.00083 SIP/2.0 200 OK Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK4e1.3a5eafdb0c6cb4f6b4fbaf7faface967.0 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11769 INVITE Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed Contact: <sip:123456789@200.200.200.209:5060;transport=tcp> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS P-Asserted-Identity: <sip:6932489919@MOBILE.PROVIDER.COM <mailto:sip%3A6932489919@MOBILE.PROVIDER.COM>;user=phone> Require: timer Supported: timer Session-Expires: 1800;refresher=uas Content-Length: 242 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 21561 25962 IN IP4 200.200.200.209 s=SIP Media Capabilities c=IN IP4 200.200.200.211 t=0 0 m=audio 27992 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 <--- RECV -----------<-------------< [Message: 9 of 12 ] <------------<------------< Date: 09-22-2021 Time: 08:27:20.00102 ACK sip:123456789@200.200.200.209:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK4e1.d06307f54416ad3db79569f704d8658e.0 Max-Forwards: 68 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11769 ACK Content-Length: 0 Contact: <sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp> >--- SEND ----------->-------------> [Message: 10 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:26.00061 BYE sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 200.200.200.209:5060;branch=z9hG4bK0dB7cb270586eb0337b From: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 To: "987654321" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 9423 BYE Max-Forwards: 70 Supported: 100rel Content-Length: 0 >--- SEND ----------->-------------> [Message: 11 of 12 ] >------------>------------> Date: 09-22-2021 Time: 08:27:32.00010 BYE sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 200.200.200.209:5060;branch=z9hG4bK0dB7cb270586eb0337b From: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 To: "987654321" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 9423 BYE Max-Forwards: 70 Supported: 100rel Content-Length: 0 <--- RECV -----------<-------------< [Message: 12 of 12 ] <------------<------------< Date: 09-22-2021 Time: 08:27:33.00021 BYE sip:123456789@200.200.200.209:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bKbd1.38c5755274f4163db0542d5ec9549053.0 Max-Forwards: 68 From: "MyUserName" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=b695280bab3644b78ac5e09a5dba5ac4 To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0df944e5 Call-ID: d7ecb3b2408a466ea3074d1b48499bfa CSeq: 11772 BYE User-Agent: MicroSIP/3.20.5 Content-Length: 0 Contact: <sip:btpsh-b6-614ae8ae-21085-1@50.50.50.182:5080;transport=tcp> Kind regards, Angelo Στις Τετ, 22 Σεπ 2021 στις 9:12 π.μ., ο/η Daniel-Constantin Mierla <miconda@gmail.com <mailto:miconda@gmail.com>> έγραψε: Hello, On 21.09.21 16:55, Angelo Sipper wrote:Hi Daniel, Thank you for your prompt response! I sent the wrong trace with the added transport=tcp test. Yes we tried to add the transport=tcp on config to overcome this issue but it was not resolved. I will contact the provider to ask them to add the transport on their 183 and I believe it will resolve the issue. In case they cannot do this is there an alternative to bypass this?you have the flexibility to set the transport to $du or $ru and then relay. Or look at tm module, there are functions that can enforce a specific transport layer. Solutions can be made in config, but the best would be that the provider fixes it, otherwise you have to make a more complex config file to figure out if you have to enforce the transport manually or not, assuming you route calls to other endpoints that set the proper transport value. Cheers, DanielAs per now we have the save issue also on our ACK and BYE replies we send to the provider which is logical. Kind regards, Angelo Στις Τρί, 21 Σεπ 2021 στις 5:03 μ.μ., ο/η Daniel-Constantin Mierla <miconda@gmail.com <mailto:miconda@gmail.com>> έγραψε: Hello, the contact of the 183 has no transport parameter, which means it is the default one, respectively UDP. If the Provider wants traffic over TCP, the contact has to be with that transport parameter. I see that incoming PRACK has R-URI without transport parameter, but the one to be forwarded has a malformed version where transport=tcp is misplaced, probably due to a wrong config operation. If you do it in kamailio.cfg, you have to append ";transport=tcp" to $ru (whole r-uri), not to $rU (only user part of r-uri). Cheers, Daniel On 21.09.21 15:29, Angelo Sipper wrote:Correction UAC (OverTLS) ->(TLS)Kamailio1(UDP)-> (UDP)Kamailio2(TCP)-> (TCP)Provider Στις Τρί, 21 Σεπ 2021 στις 4:28 μ.μ., ο/η Angelo Sipper <sippro97@gmail.com <mailto:sippro97@gmail.com>> έγραψε: Hello, We have the following setup and I am having trouble passing the PRACK with correct protocol to the provider. UAC (OverTLS) ->(UDP)Kamailio1 (UDP)-> (UDP)Kamailio2 (TCP)-> (TCP)Provider UAC : 10.2.1.160 NATED to 100.100.100.61 <http://50.50.50.50:5065/> (TLS) Kamailio1 Sockets: 50.50.50.210:5061 <http://170.170.170.210:5061/> (TLS),50.50.50.210:5060 <http://170.170.170.210:5060/> (UDP) Kamailio2 Sockets: 50.50.50.182:5060 <http://170.170.170.170:5060/> (UDP) 50.50.50.182:5080 <http://170.170.170.170:5060/> (TCP) Provider: 200.200.200.209:5060 <http://200.200.200.193:5060/> (TCP) We use dispatcher on Kamailio1 & Kamailio2 The invite goes fine from UCA up to the provider and the provider responses arrive to UAC fine. The PRACK from UAC to kamailio1 goes fine to Kamaili02 but, Kamailio2 uses the UDP socket to send to the provider so the PRACK does not arrive to the provider and the call is canceled. If the provider is on UDP everything works fine. Below I have the trace. What should I look for in the config to resolve this wrong protocol/socket on the PRACK? Kamailio2 Details: Sockets ====== listen=udp:50.50.50.182:5060 <http://50.50.50.182:5060> listen=tcp: 50.50.50.182:5080 <http://50.50.50.182:5080> On the rr module I have ================== modparam("rr", "enable_double_rr", 1) modparam("rr", "append_fromtag", 1) modparam("rr", "enable_full_lr", 1) CONFIG REQINIT & WITHINDLG PARTS ================================ route[REQINIT] { set_reply_no_connect(); force_rport(); if (!mf_process_maxfwd_header("10")) { xlog("L_ERROR","Too Many Hops Rejecting!"); sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp sanity 1511\n"); exit; } if(!sanity_check("17895", "7")) { xlog("Malformed SIP request from $si:$sp sanity 17895\n"); exit; } } route[WITHINDLG] { if (!has_totag()) return; if (loose_route()) { if (is_method("BYE")) { rtpengine_query(); rtpengine_delete(); } route(RELAY_OUT); } if ( is_method("ACK") ) { #if (t_lookup_request()) { if (t_check_trans()) { route(RELAY_OUT); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not Allowed"); exit; } TRACE ====== 50.50.50.210:5060 <http://50.50.50.210:5060> 50.50.50.182:5060 <http://50.50.50.182:5060> 50.50.50.182:32818 <http://50.50.50.182:32818> 200.200.200.209:5060 <http://200.200.200.209:5060> qqqqqqqqqqwqqqqqqq qqqqqqqqqqwqqqqqqq qqqqqqqqqqwqqqqqqqq qqqqqqqqqqqwqqqqqqqqq a 15:31:11.787490 x INVITE (SDP) x x x a +0.003099 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:11.790589 x 100 trying -- your call is x x x a +0.002220 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:11.792809 x x x INVITE (SDP) x a +0.020725 x x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:11.813534 x x x 100 Trying x a +2.628884 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:14.442418 x x x 183 Session Progress (SDP) x a +0.001572 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:14.443990 x 183 Session Progress (SDP) x x x a +0.299221 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:14.743211 x PRACK x x x a +0.043114 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:14.786325 x x PRACK x a +0.448104 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:15.234429 x PRACK x x x a +0.045697 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:15.280126 x x PRACK x a +0.954153 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:16.234279 x PRACK x x x a +0.045832 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:16.280111 x x PRACK x a +1.954170 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:18.234281 x PRACK x x x a +0.045839 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:18.280120 x x PRACK x a +1.829676 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:20.109796 x x x 183 Session Progress (SDP) x a +0.001460 x x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:20.111256 x 183 Session Progress (SDP) x x x a +2.123075 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:22.234331 x PRACK x x x a +0.045825 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:22.280156 x x PRACK x a +2.239640 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:24.519796 x x x 486 Busy Here x a +0.000555 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:24.520351 x x x ACK x a +0.008965 x x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:24.529316 x 486 Busy Here x x x a +0.000835 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:24.530151 x ACK x x x a +1.704184 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:26.234335 x PRACK x x x a +0.045856 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:26.280191 x x PRACK x a +3.954734 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:30.234925 x PRACK x x x x +0.045279 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x x 15:31:30.280204 x x PRACK x x +3.954116 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x x 15:31:34.234320 x PRACK x x x 2021/09/21 15:31:11.787490 50.50.50.210:5060 <http://50.50.50.210:5060> -> 50.50.50.182:5060 <http://50.50.50.182:5060> INVITE sip:123456789@sip.mydomain.com:5060 <http://sip:123456789@sip.mydomain.com:5060> SIP/2.0 Record-Route: <sip:50.50.50.210;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias Max-Forwards: 69 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>> Contact: "MyUserNAme" <sip:mycustomerid@10.2.1.160:58568;transport=TLS;ob;alias=100.100.100.61~48572~3> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.20.5 Content-Type: application/sdp Content-Length: 326 P-Asserted-Identity: <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>> v=0 o=- 3841227071 3841227071 IN IP4 50.50.50.215 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 36448 RTP/AVP 8 0 101 c=IN IP4 50.50.50.215 b=TIAS:64000 a=ssrc:2024148033 cname:4f2468fd611910fa a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:36449 2021/09/21 15:31:11.790589 50.50.50.182:5060 <http://50.50.50.182:5060> -> 50.50.50.210:5060 <http://50.50.50.210:5060> SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3;rport=5060 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Server: myserver Content-Length: 0 2021/09/21 15:31:11.792809 50.50.50.182:32818 <http://50.50.50.182:32818> -> 200.200.200.209:5060 <http://200.200.200.209:5060> INVITE sip:123456789@sip.mydomain.com:5060 <http://sip:123456789@sip.mydomain.com:5060> SIP/2.0 Record-Route: <sip:50.50.50.182:5080;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias Max-Forwards: 68 From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>> Contact: "MyUserNAme" <sip:mycustomerid@10.2.1.160:58568;transport=TLS;ob;alias=100.100.100.61~48572~3> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 Content-Type: application/sdp Content-Length: 326 P-Asserted-Identity: <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>> v=0 o=- 3841227071 3841227071 IN IP4 50.50.50.183 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 29308 RTP/AVP 8 0 101 c=IN IP4 50.50.50.183 b=TIAS:64000 a=ssrc:2024148033 cname:4f2468fd611910fa a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:29309 2021/09/21 15:31:11.813534 200.200.200.209:5060 <http://200.200.200.209:5060> -> 50.50.50.182:32818 <http://50.50.50.182:32818> SIP/2.0 100 Trying Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Content-Length: 0 2021/09/21 15:31:14.442418 200.200.200.209:5060 <http://200.200.200.209:5060> -> 50.50.50.182:32818 <http://50.50.50.182:32818> SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 50.50.50.182:5080;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Record-Route: <sip:50.50.50.182:5080;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182:5060;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210:5060;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Contact: <sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060>> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Require: 100rel RSeq: 1509 Content-Length: 241 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 12038 7929 IN IP4 200.200.200.209 s=SIP Media Capabilities c=IN IP4 200.200.200.212 t=0 0 m=audio 17366 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 2021/09/21 15:31:14.443990 50.50.50.182:5060 <http://50.50.50.182:5060> -> 50.50.50.210:5060 <http://50.50.50.210:5060> SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Record-Route: <sip:50.50.50.182:5080;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182:5060;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210:5060;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Contact: <sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060>> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Require: 100rel RSeq: 1509 Content-Length: 253 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 12038 7929 IN IP4 50.50.50.183 s=SIP Media Capabilities c=IN IP4 50.50.50.183 t=0 0 m=audio 29320 RTP/AVP 8 101 a=maxptime:20 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:29321 2021/09/21 15:31:14.743211 50.50.50.210:5060 <http://50.50.50.210:5060> -> 50.50.50.182:5060 <http://50.50.50.182:5060> PRACK sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:14.786325 50.50.50.182:5060 <http://50.50.50.182:5060> -> 200.200.200.209:5060 <http://200.200.200.209:5060> PRACK sip:123456789transport=tcp@200.200.200.209:5060 <http://tcp@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:15.234429 50.50.50.210:5060 <http://50.50.50.210:5060> -> 50.50.50.182:5060 <http://50.50.50.182:5060> PRACK sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:15.280126 50.50.50.182:5060 <http://50.50.50.182:5060> -> 200.200.200.209:5060 <http://200.200.200.209:5060> PRACK sip:123456789transport=tcp@200.200.200.209:5060 <http://tcp@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:16.234279 50.50.50.210:5060 <http://50.50.50.210:5060> -> 50.50.50.182:5060 <http://50.50.50.182:5060> PRACK sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:16.280111 50.50.50.182:5060 <http://50.50.50.182:5060> -> 200.200.200.209:5060 <http://200.200.200.209:5060> PRACK sip:123456789transport=tcp@200.200.200.209:5060 <http://tcp@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:18.234281 50.50.50.210:5060 <http://50.50.50.210:5060> -> 50.50.50.182:5060 <http://50.50.50.182:5060> PRACK sip:123456789@200.200.200.209:5060 <http://sip:123456789@200.200.200.209:5060> SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com <mailto:sip%3A987654321@sip.mydomain.com>>;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com <mailto:sip%3A123456789@sip.mydomain.com>>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 Any help will be much appreciated. Kind regards, Angelo __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>-- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio Advanced Training - Online Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/ <https://www.asipto.com/sw/kamailio-advanced-training-online/>-- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio Advanced Training - Online Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/ <https://www.asipto.com/sw/kamailio-advanced-training-online/>
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/