sr-users September 2021

sr-users@lists.kamailio.org

46 participants
61 discussions

Kamailio/RTPengine as a proxy for FreePBX/Asterisk...
by Micah Quinn 03 Oct '21

03 Oct '21

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 … [View More]

6 22

Fail call from Webrct to PSTN SIP trunk
by Abdul Rahman Reza 01 Oct '21

01 Oct '21

Hi, good morning there is something I want to ask, I'm really stuck looking for a solution, haven't found it yet, So I want to make Webrct able to call SIP and PSTN numbers via SIP trunk, but it keeps failing For testing as follows: webrct => SIP OK webrct => PSTN NOK webrct => webrct OK SIP => webrct OK SIP => PSTN OK SIP => SIP OK Thank you very much in advance this is error log from kamailio webrct => PSTN gagal dan error muncul seperti ini : Aug 16 11:25:16 … [View More]

2 2

ACK not accepted
by Angelo Sipper 01 Oct '21

01 Oct '21

Hi, I am having a problem with some inbound calls that all have the below behavior. My setup has: Carrier(UDP) -> (UDP)Kamailio1(UDP) -> (UDP)Kamailio2(TLS) -> (TLS)UAC Kamailio1 has Topos Module. UAC is behind NAT with LAN IP 192.168.1.105 and Public 200.200.200.30 Carrier IP 50.50.50.19, Kamailio1 IP 100.100.100.243, Kamailio2 IP 100.100.100.210 The Carrier sends in a new call and the call is answered from the UAC with 200 OK SDP. Carrier sends ACK and it looks like it reaches the … [View More]UAC but, UAC still resends several times 200 OK and carrier sends server ACK that arrives or not ??? to UAC until finally UAC sends a BYE. On the SIP flow you can see that Kamailio2 sends the ACK to 192.168.1.105 and not to 200.200.200.30. Is this ok?? Another thing to mention is that Kamailio2 that has the UAC connected via TLS, can be used fine from the UAC to make an outbound call following the reverse path, but on the inbound we have the below. Any help will be much appreciated, ACK from Kamailio2 100.100.100.210 to UAC Session Initiation Protocol (ACK) Request-Line: ACK sip:btpsh-f3-6153392a-5fa-5@192.168.1.105:5061;transport=TLS SIP/2.0 Message Header Via: SIP/2.0/TLS 100.100.100.210:5061 ;branch=z9hG4bKfc5f.67a77810bcdafe811ea3672a027450d8.0 Via: SIP/2.0/UDP 100.100.100.243;rport=5060;branch=z9hG4bKfc5f.e2b515e9c8c33d2bd05682f26df24e39.0 Call-ID: isbcaqhye0rozjgeghorzav1vtytoqztkheq(a)B.5.108.ims.forthnet.gr [Generated Call-ID: isbcaqhye0rozjgeghorzav1vtytoqztkheq(a)B.5.108.ims.incarrier.com] From: <sip:987654321@ims.carrier.com ;user=phone>;tag=ZZ58CDf_CZ.Yj2U5 To: <sip:23456789@ims.carrier.com ;user=phone>;tag=0120779a-edf4-464a-9c43-2ddf54459083 CSeq: 1 ACK Max-Forwards: 64 Request-Disposition: no-fork Content-Length: 0 Contact: <sip:btpsh-f3-6153392a-5fa-5@100.100.100.243> |Time | 50.50.50.19 | 100.100.100.210 | 192.168.1.105 | | | | 100.100.100.243 | | 200.200.200.30 | |0.000000 | INVITE SDP (g711A te | | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> Call-ID:isbcaqhye0rozjgeghorzav1vtytoqztkheq@B.5.108.ims.incarrier.gr CSeq:1 | |(5060) ------------------> (5060) | | | | |0.001737 | 100 trying -- your c | | | |SIP Status 100 trying -- your call is important to us | |(5060) <------------------ (5060) | | | | |0.074622 | | INVITE SDP (g711A te | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |0.074797 | | INVITE SDP (g711A te | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |0.081110 | | 100 trying -- your c | | |SIP Status 100 trying -- your call is important to us | | |(5060) <------------------ (5060) | | | |0.082070 | | 100 trying -- your c | | |SIP Status 100 trying -- your call is important to us | | |(5060) <------------------ (5060) | | | |0.082833 | | | INVITE SDP (g711A te | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) ------------------> (37275) | | |0.163871 | | | 100 Trying| | |SIP Status 100 Trying | | | |(5061) <------------------ (37275) | | |0.447621 | | | 180 Ringing | |SIP Status 180 Ringing | | | |(5061) <------------------ (37275) | | |0.448004 | | 180 Ringing | | |SIP Status 180 Ringing | | |(5060) <------------------ (5060) | | | |0.448765 | | 180 Ringing | | |SIP Status 180 Ringing | | |(5060) <------------------ (5060) | | | |0.465033 | 180 Ringing | | | |SIP Status 180 Ringing | |(5060) <------------------ (5060) | | | | |2.529599 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |2.733556 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |2.734596 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |2.864311 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |3.024789 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |3.025005 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |3.025854 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |3.034979 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |3.106784 | ACK | | | | |SIP Request INVITE ACK 200 CSeq:1 | |(5060) ------------------> (5060) | | | | |3.126287 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |3.126542 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |3.145821 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |4.025449 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |4.025743 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |4.026548 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |4.033198 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |4.094832 | ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |4.102992 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |4.103316 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |4.106301 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |6.025167 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |6.025543 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |6.026377 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |6.034778 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |6.096896 | ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |6.104675 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |6.104910 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |6.108907 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |10.024538| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |10.024866| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |10.025750| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |10.033461| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |10.095387| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |10.102265| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |10.102449| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |10.105760| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |14.025310| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |14.025585| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |14.026528| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |14.037027| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |14.099479| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |14.111540| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |14.111708| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |14.116089| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |18.025311| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |18.025659| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |18.026572| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |18.034736| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |18.096101| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |18.106560| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |18.106687| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |18.111007| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |22.024673| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |22.024953| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |22.026120| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |22.033514| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |22.095104| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |22.105921| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |22.106043| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |22.110298| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |26.031501| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |26.031903| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |26.033136| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |26.040343| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |26.101967| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |26.111938| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |26.112432| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |26.118306| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |30.035446| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |30.035693| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |30.036501| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |30.044170| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |30.106395| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |30.116960| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |30.117412| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |30.129913| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |34.026492| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |34.026807| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |34.027775| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |34.035453| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |34.097385| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |34.106319| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |34.106681| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |34.110714| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |34.526688| | | BYE | | |SIP Request BYE CSeq:15322 | | | |(5061) <------------------ (37275) | | |34.528722| | BYE | | | |SIP Request BYE CSeq:15322 | | |(5060) <------------------ (5060) | | | |34.529704| | BYE | | | |SIP Request BYE CSeq:15322 | | |(5060) <------------------ (5060) | | | |34.668418| BYE | | | | |SIP Request BYE CSeq:15322 | |(5060) <------------------ (5060) | | | | |34.788963| 200 OK | | | | |SIP Status 200 OK | |(5060) ------------------> (5060) | | | | |34.796051| | 200 OK | | | |SIP Status 200 OK | | |(5060) ------------------> (5060) | | | |34.796205| | 200 OK | | | |SIP Status 200 OK | | |(5060) ------------------> (5060) | | | |34.796604| | | 200 OK | | |SIP Status 200 OK | | | |(5061) ------------------> (37275) | | Kind regards, Angelo [View Less]

1 3

RTPEngine + Kamailio state question
by Alex Balashov 30 Sep '21

30 Sep '21

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 … [View More]

3 6

Sipwise SEMS
by David Villasmil 30 Sep '21

30 Sep '21

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

10 22

using LDAP as database ?
by Volker Denneberg 28 Sep '21

28 Sep '21

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 … [View More]

2 1

siptrace & topos modules on 5.3
by Angelo Sipper 24 Sep '21

24 Sep '21

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 … [View More]

3 5

Info: APT Debian/Ubuntu Packages Archive
by Daniel-Constantin Mierla 24 Sep '21

24 Sep '21

Hello, a new server is available to offer APT repositories for each released version of Kamailio: * https://deb-archive.kamailio.org/ It aims to offer a way to downgrade to an older version, if someone wants it for various reasons. At this moment it offers dedicated APT repositories for Kamailio 5.3.8, 5.4.6, 5.4.7, 5.5.1 and 5.5.2. More details were posted in a news article at: * https://www.kamailio.org/w/2021/09/apt-debian-packages-archive/ Cheers, Daniel -- Daniel-… [View More]

1 0

PRACK with UDP to TCP translation send over wrong protocol
by Angelo Sipper 24 Sep '21

24 Sep '21

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/> … [View More](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 [View Less]

2 7

Releasing Kamailio 5.3.9
by Henning Westerholt 23 Sep '21

23 Sep '21

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 … [View More]

1 0

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 September 2021