Hello all,
I'm new to Kamailio, so bear with me as I stumble through this. First, I'll describe what I'm trying to achieve at a high level and then perhaps somebody can advise me on whether Kamailio is a good fit for this solution or not. I'd like to be able to deploy a small appliance type server to our customer's sites that just runs Kamailio and a VPN connection back to our datacenter. At our datacenter, we run virtualized instances of Asterisk for each of our customers. The idea is that Kamailio would act as a transparent proxy through to the Asterisk instance under nominal conditions and as a basic SIP router in the case that the Asterisk instance is unavailable. This degraded functionality would then at least allow extension to extension calling even if the Internet or Asterisk instance is down.
I'm currently using dispatcher with a single entry in preparation for a time when we might want to failover to another Asterisk instance. I'm forwarding all REGISTER and INVITE messages to the server chosen from ds_select_dst. Initially this all seems to work as I can register with a softphone and pjsip show endpoints shows my softphone connected. However, when I attempt to call any extension (my own or another) Asterisk responds to the INVITE message with a "401 Unauthorized" message and the typical "The person at extension XXXX is unavailable...".
I know that more details might be necessary to troubleshoot this, but I didn't want to include everything in one post and risk cluttering it up with unnecessary information. If anyone can confirm that this is a reasonable way to approach the problem, I can then provide whatever relevant data is necessary to get deeper into it. (I've used sngrep, logging, asterisk cli, etc.)
Thanks in advance for any help.
Hi,
Sorry if I missed any developments on this, but:
Kamailio does keep a runtime association of Call-ID+Ftag => RTPEngine instance, which is significant if an RTPEngine set with multiple members is used, or if a non-default set is used for a given call.
When Kamailio is restarted, this runtime association goes away, so any subsequent offer/answer cycles or any other commands will (maybe) go to the wrong RTPEngine and/or the wrong set.
Last time I checked a few years ago, there was no way to persist this association across restarts. Has this changed?
Thanks!
— Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Hello guys,
I know SEMS can provide conference, voicemail, and other services.
In theory it’s also a B2BUA. Could I use a python script to provide a
simple routing service? I.e.: receive an invite and send it somewhere else
based on some routing logic?
Thanks all
David
--
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
Hi,
I am searching for a setup where phones register at a central kamailio and kamailio shares these contact infos with multiple asterisks.
So they all need to share a database. For redundancy reasons, the database should work across 2 datacenters.
As far as 1 understood there are some options
* use mysql - good chances to find example code, Siremis API, seems to be the standard solution
* use redis - more performant than mysql
* use ldap - good chances to integrate with existing IT management but most difficult to configure
Maybe I missed a better approach?
Kamailio's ldap driver (http://www.kamailio.net/docs/modules/5.3.x/modules/db2_ldap.html) seems to be from 2008 - is it still recommended ?
Kind regards,
Volker
Hi,
We are using kamailio 5.3 latest version with the topos module. We have
added Homer 7 latest version to consolidate traces from all kamailios and
we have enabled siptrace module on kamailio to send data to homer. What we
have seen up today is that traces on homer have sip headers before topos
changes. So if I look at the same call on sngrep on the kamailio machine, I
see the correct topos changed headers. If I check the same call on Homer I
see headers without topos changes. Also we get duplicate headers on ACKs on
homer.
I was wondering what we have done wrong in the config and we have these
results on homer. Any help will be much appreciated!
Our config has:
===========-
#!substdef "!MY_HOMER_CAPTURE!sip:MY_HOMER_IP_ADDR:MY_HOMER_PORT!g"
#!substdef "!MY_LOCAL_SENDSOCK!sip:MY_KAMAILIO_IP:MY_LOCAL_SEND_PORT!g"
loadmodule "topos.so"
loadmodule "siptrace.so"
modparam("siptrace", "force_send_sock", "MY_LOCAL_SENDSOCK")
modparam("siptrace", "duplicate_uri", "MY_HOMER_CAPTURE")
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_version", 3)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_mode", 0)
modparam("siptrace", "hep_capture_id", NODE_ID)
modparam("topos", "db_url", DBURL)
modparam("topos", "mask_callid", 0)
modparam("topos", "sanity_checks", 0)
modparam("topos", "branch_expire", 130) # 3 Min
modparam("topos", "dialog_expire", 10800) # 3 Hours
modparam("topos", "clean_interval", 60)
modparam("topos", "event_mode", 3)
request_route {
sip_trace_mode("t");
........
}
onsend_route {
if (is_method("ACK")) {
sip_trace();
}
}
==============
Thank you!
Kind regards,
Angelo
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
listen=tcp: 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 50.50.50.182:5060
50.50.50.182:32818 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 -> 50.50.50.182:5060
INVITE 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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>
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 -> 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 200.200.200.209:5060
INVITE 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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>
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 -> 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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>
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 -> 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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>
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 -> 50.50.50.182:5060
PRACK 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 200.200.200.209:5060
PRACK sip:123456789transport=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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 50.50.50.182:5060
PRACK 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 200.200.200.209:5060
PRACK sip:123456789transport=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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 50.50.50.182:5060
PRACK 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 200.200.200.209:5060
PRACK sip:123456789transport=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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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 -> 50.50.50.182:5060
PRACK 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
>;tag=73622588a6084d8ba1bca54781e5094d
To: <sip:123456789@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
Hello,
I am planning to release in two weeks (likely on Wednesday 7th October) the next minor version out of branch 5.3, version 5.3.9.
Backports of fixed issues from other stable branches will be integrated as usual.
If you are aware of new issues which were not yet reported on the issue tracker or are missing back-ports, report them.
Please note that this will be the last minor release created from the 5.3.x stable branch.
The stable branches are usually maintained from the Kamailio development team for a period of two years. The other two stable branches of Kamailio will still be maintained (5.4.x and 5.5.x).
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
