June 2021 - sr-users - kamailio.org

[Serusers] Digest Authentication with Tenor DX
by Ashutosh Kumar 29 Apr '25

29 Apr '25

Hi, Does someone have any idea/experience with Quintum DX radius server's support for digest mode authentication. The Access-Request packets sent by SER are getting an error back. Guide. Regards, Ashutosh Kumar Chetu, Inc. Ph : 1(305) 402 6724 - Witin US Ph : 91 120 5323340 - Outside US Fax:1 (305) 832 5987 For more information, please visit http://www.chetu.com

2 1

Via header force change protocol to TLS?
by Anthony Alba 30 May '24

30 May '24

I have kamailio behind a TLS termination proxy so the sockets are correctly deduced to be TCP. However the clients only talk TLS to the proxy and are confused when the top Via header added by Kamailio is TCP. Is there a way for Kamailio to forcibly pretend its protocol is TLS? Like advertised_address but "advertised_protocol" instead. (With pjsip testing: it has a flag use_tls which ignores TCP from Kamailio and continues to use the persistent TLS transport to proxy. Linphone fails because it tries to honor TCP in Via and is unable to establish TCP transport). BTW I am using t_relay_to_tcp so Kamailio will return traffic to the proxy as TCP even though the contact addresses specify transport=TLS.

4 10

Dialog and DMQ on restart
by Björn Klasen 25 Mar '24

25 Mar '24

Hi everybody, I'm just testing Kamailio 5.4.1 with dialog replication over DMQ. This seems to work very good. Dialogs are replicated without problems. When I'm restarting one node I would have expected, that all dialogs are synced again, just like in dmq_usrloc. But this does not happen. After a restart the nodes dialog-list is empty. Did I miss somethin? Is there a special parameter that I have to set? BR, Björn -- Björn Klasen, Specialist TNG Stadtnetz GmbH, Network Management (VoIP) Projensdorfer Straße 324 24106 Kiel Germany T +49 431/ 530530 F +49 431/ 7097-555 mailto: bklasen(a)tng.de http://www.tng.de Register: Amtsgericht Kiel HRB 6002 KI Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg, Sven Schade, Carsten Tolkmit, Dr. Sven Willert Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428

4 9

Is Min-SE check broken?
by harneet singh 31 May '23

31 May '23

Hi All, I am facing an issue in understanding how the min_se should be working in kamailio. As per the SST documentation, it seems like if the min_se is configured as 500, then any value of Session-Expires OR MIN-SE if lower than 500, can be responded to by a 422. However, I strangely see the reverse happening. To investigate further, I looked in to the ki_sst_check_min() code in the master, and these seems like a potential issue. Ref Code: Inside ki_sst_check_min(), there is an if condition like below: if (sst_min_se < MIN(minse, se.interval)) { However, shouldn't it be the other way around? ie if (sst_min_se > MIN(minse, se.interval)) { because we need to send 422 if the received value(in INVITE etc) is smaller than the sst configure min_se value? I also found a different documentation, at https://git.sgu.ru/oldssu/ex-opensips/blob/cb9df8d59dbb254a9d862569fd5d11f6… where the check is as below? if (sst_min_se > MIN(minse, se.interval)) { Can someone confirm if this is broken, or my understanding is incorrect? Regards, Harneet -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
by Daniel Tryba 02 May '23

02 May '23

On Mon, May 07, 2018 at 04:44:14PM +0200, Daniel Tryba wrote: > Sure. Attached. Problem appears to be that the topos query can't find > callid-totag (from the response). > > I'll try the same scenario with the mysql backend to see if it behaves > different. Config works fine with mysql as topos backend. So the bug is restricted to topos-redis.

5 19

Possibility of mirroring the rpm/deb.kamailio.org repos efficiently via rsync?
by Malte Schmidt 23 Jun '22

23 Jun '22

Hello, is there an rsync endpoint available or is there a possiblity of setting this up? Creating a mirror via HTTP is a rather quick and dirty solution and while the deb-repo can be mirrored using debmirror, the rpm repo is hard to sync to a non-CentOS-based machine due to missing dependencies such as yum and reposync in latest Debian-based systems. Would be great to get some input in regards to this topic. Cheers

3 3

Fwd: Possible memory leak on 5.5.x (new)?
by George Diamantopoulos 19 Jan '22

19 Jan '22

Forwarding my reply to the list, using gmail's reply button set Henning as the sole recipient :-\ ---------- Forwarded message --------- From: George Diamantopoulos <georgediam(a)gmail.com> Date: Sat, 26 Jun 2021 at 02:25 Subject: Re: [SR-Users] Possible memory leak on 5.5.x (new)? To: Henning Westerholt <hw(a)skalatan.de> Hello Henning, Thanks for your reply. Here's what has come up after a few hours: shm55: https://pastebin.com/h9JCePmc shm54: https://pastebin.com/Nx5xEEnA It seems to me htable is the culprit? Are you seeing anything different? 54 has been running for 77020 seconds, 55 for 28521 (significantly less). I'm going to turn it off until we figure something out... BR, George On Fri, 25 Jun 2021 at 18:17, Henning Westerholt <hw(a)skalatan.de> wrote: > Hello, > > > > Good observation. Please run the memory statistics CLI commands to get > more hints about the module that might cause it (as per below link). Then > please report more details. If you can point to a particular module, you > can also open an issue on our tracker. > > > > https://www.kamailio.org/wiki/tutorials/troubleshooting/memory > > > > Cheers, > > > > Henning > > > > *From:* sr-users <sr-users-bounces(a)lists.kamailio.org> *On Behalf Of *George > Diamantopoulos > *Sent:* Friday, June 25, 2021 4:53 PM > *To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > *Subject:* [SR-Users] Possible memory leak on 5.5.x (new)? > > > > Hello all, > > > > I'm still investigating the (most likely non-kamailio-related) memory leak > of my previous message to the list, there have been no developments so far. > I'll update if anything changes. > > > > This concerns a new finding which seems to affect kamailio 5.5.x. I have > two kamailio instances receiving the same traffic via round-robin. I > upgraded only one of them to 5.5.1 and left the other to 5.4.6 as I feared > of any issues arising. I was lucky to do so, because with identical > configuration, 5.5.x seems to run out of SHM very quickly. Here are links > to graphs produced by our monitoring system: > > > > Old kamailio (no memory leak): https://pasteboard.co/K8fVBiD.png > > New kamailio (possible leak): https://pasteboard.co/K8fVS9N.png > > > > The configuration uses mtree, htable, vars and vns extensively. Has anyone > come across anything similar? Let me know if I can provide any further > information to help disect this. Thanks! > > > > BR, > > George >

2 8

ENV Values in cfg
by H Yavari 06 Dec '21

06 Dec '21

Hi to all, Is it possible to set modules parameters with env values? I know that in routes we can use $env(NAME), but what about for other parameters? for example setting DB address in K8s cluster ENV values. Regards,Hossein

2 1

update max_while_loops in config
by Juha Heinanen 08 Oct '21

08 Oct '21

It is possible to update value of max_while_loops dynamically in config file? For example, there could be a need to increase the max in some while loop, but after the loop is done, decrease it again for other loops. There exists an rpc command to do that, but I haven't found how to do it in config file. I tried @cfg_seti.core.max_while_loops = 200; but got syntax error. -- Juha

3 6

manually append_branch to lookup result
by David Villasmil 07 Sep '21

07 Sep '21

Hello guys, I'm trying to dynamically add a branch after doing lookup. The user is found, but in some cases I need to add a branch and do parallel forking. So i'm basically doing: route[LOCATION] { if (!lookup("location")) { .... } if (something) { route(BRANCH_TO_EXTRA); } route(RELAY); } route[BRANCH_TO_EXTRA] { $fs = MY_SOCKET; append_branch("sip:$tU@" + $sel(cfg_get.pstn.gw_ip) + ":" + $sel(cfg_get.pstn.gw_port)); return; } For some reason only the branch appended is being used (I have append_branches=1) Ideas? David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 5

Re: [SR-Users] t_drop_replies not working with t_suspend in failure route
by Huber Andreas 03 Sep '21

03 Sep '21

Hi, We’re still using kamailio 4.4 but we’ll be migrating to 5.0 soon. Cool so it will be fixed when we migrate ! Thanks, Andreas From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Federico Cabiddu Sent: vendredi 12 mai 2017 11:56 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] t_drop_replies not working with t_suspend in failure route Hi, which version are you using? A similar case had been reported some months ago and it should be fixed in 5.0. Regards, Federico On Fri, May 12, 2017 at 11:44 AM, Huber Andreas <andreas.huber(a)nagra.com<mailto:andreas.huber@nagra.com>> wrote: Hello, We have a use case where we suspend a transaction in a failure_route to give UEs that might be woken by a push notification more time to REGISTER and join the INVITE. We’d like to drop the previous branches in this case. I tried using t_drop_replies() but it has no effect. The doc states that t_drop_replies() is only working if a new branch is added. And from my understanding t_suspend() adds a new branch. But is it possible that t_drop_replies() cannot be used with t_suspend()? Or am I missing something? Kind Regards, Andreas _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

2 1

Kamailio v5.4.6 Released
by Daniel-Constantin Mierla 13 Jul '21

13 Jul '21

Hello, Kamailio SIP Server v5.4.6 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.6. Note that 5.4 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.5, with v5.5.0 being release out of it. For more details about version 5.4.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/06/kamailio-v5-4-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

3 2

SECSIPID Identity Decode
by Daniel W. Graham 06 Jul '21

06 Jul '21

I am unable to base64url decode the json payload in identity header generated by secsipid. (Using python for test) decoded_payload = url64.decode(‘payload’) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 27: invalid continuation byte Header decodes fine this way but not payload. Is this an issue with the payload encoding? Kamailio 5.5 Daniel W. Graham, CTO CMSInter.net LLC DIRECT (989) 400-4230 INTERNET | TELEPHONE | MANAGED IT

5 28

Kamailio BSD license
by stevecarellccie＠yahoo.com 01 Jul '21

01 Jul '21

Hello, I am trying to use Kamailio in our application which would be deployed in certain environment in addition to a cloud infrastructure. As I understand it, parts of the Kamailio code are covered under the BSD license - are you able to share what those are? I am trying to determine if Kamailio can be used in a customer environment or should it be strictly restricted to cloud environments due to the GPL v2 licenses Thanks,Steve

2 1

install stirshaken module by apt at Debian 10
by Yuriy Nasida 30 Jun '21

30 Jun '21

Hi, I know that it's possible to compile manually but what about apt method to install stirshaken module? I am checking the list of modules using: apt search kamailio But... Nothing looks like stirshaken. Thus, only several modules available and for others we should compile manually ? Please advise Thanks

2 1

Websocket In-dialoge SIP routing failed post network loss due to aliases
by Shahid Hussain 30 Jun '21

30 Jun '21

Hi, Websocket module documentation has a code reference to use aliases for SIP routing. However, aliases will not work in the following setup and situation. 1. Kamailio is configured with active and standby node 2. Ping is implemented from webclient and kamailio responds with pong. 3. Two clients ClinetA and ClientB registered themselves to Kamailio. 4. After SIP negotiation (INVITE-200OK) each client learnt about below aliases. Alias of ClientA: alias=172.27.6.98~58336 Alias of ClientB: alias=172.27.6.98~58342 So normally if ClientB wants to send SIP message to ClientA, SIP URI from ClientB looks like below ACK sip:v9d0gtl6@q0lrdlj63pik.invalid;alias=172.27.6.98~58336~5;transport=ws SIP/2.0 4. Call is in a connected state. Following is the issue. i. Switchover (or network lost or reboot) at Kamailio happened ii. Due to ping pong both the clients detected network loss individually and re-registered themselves. iii. Aliases of both the clients got changed. New Alias of ClientA: alias=172.27.6.98~ 58346 New Alias of ClientB: alias=172.27.6.98~ 58348 iv. But ClientB doesn’t know that ClientA also re-registered and ClientA’s alias got changed and vice-versa v. Because of this ClientB still sends BYE with Initial alias BYE sip:v9d0gtl6@q0lrdlj63pik.invalid;alias=172.27.6.98~58336~5;transport=ws SIP/2.0 Would like to know what is the recommended solution for this problem using alias or is it a limitation of using alias? Thanks & Regards, Shahid

4 11

Re: [SR-Users] Guidance building a WebRTC to Asterisk Intermediate Proxy
by Peter Manley 29 Jun '21

29 Jun '21

Thanks Muhammad, That seems to have done the trick. I am now able to bridge WebRTC to UDP. Regards, Peter Manley M S shaheryarkh at gmail.com<mailto:sr-users%40lists.kamailio.org?Subject=Re%3A%20%5BSR-Users%5D%20Guidance%20building%20a%20WebRTC%20to%20Asterisk%20Intermediate%0A%20Proxy&In-Reply-To=%3CCAFZQphyZE_tGB9%3D5tFQBtXAv5twMh%3D9aCNFAvveGf0-L%3Dy_qwQ%40mail.gmail.com%3E> Sat Jun 26 03:57:27 CEST 2021 * Previous message (by thread): [SR-Users] Guidance building a WebRTC to Asterisk Intermediate Proxy<https://lists.kamailio.org/pipermail/sr-users/2021-June/112799.html> * Messages sorted by: [ date ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/date.html#112800> [ thread ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/thread.html#112800> [ subject ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/subject.html#112800> [ author ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/author.html#112800> ________________________________ The problem seems to that the kamailio is trying to route it over UDP port using WSS transport, which will never work. You are creating a transport bridge (UDP <-> WSS i.e. stateless transport <-> stateful transport) as well media bridge (RTP <-> SRTP), so it is going to be tricky. I strongly discourage it since things get messy for sequential requests. But you can try the following, Here are some PATH module parameters and functions, you will need to setup. 1. You will need to enable "use_received" parameter to ensure connection tracking. 2. It seems you may have enabled "received_format", so you make sure you do NAT detection and use "handle_ruri_alias" for initial requests. 3. You must also enabled "enable_r2", but with caution, since both ends (i.e. UAC and UAS) can be using same kamailio (proxy) socket for in/out. 4. Make sure to use "add_path_received" instead of "add_path". 5. If using OUTBOUND module then make sure it is loaded BEFORE the PATH module. Thank you. -- Muhammad Shahzad Shafi Burraq Technologies Tel: +49 176 99 83 10 85 On Sat, Jun 26, 2021 at 12:47 AM Peter Manley <peter.manley at kombea.com<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote: > Hello, > > > > I'm working on building an RTP Proxy which will allow both regular SIP to > SIP transactions and WebRTC to SIP transactions to an Asterisk Server. > > > > SIP UAC < ---UDP/SIP --- > Kamailio/RTPEngine Proxy < ---UDP/SIP----- > > Asterisk Server > > > > AND > > > > WebRTC UAC < ---WSS--- > Kamailio/RTPEngine Proxy < ---UDP/SIP----- > > Asterisk Server > > > > The Kamailio/RTPEngine Proxy is stateless (does not use the tm or > registerer modules), and uses the Path module to replace the Route header > with a Path header. > > > > It works grep for SIP/UDP to SIP/UDP transactions. > > > > HOWEVER... It only partially works for WSS to SIP/UDP transactions. The > REGISTER/401(Unauthorized), REGISTER/200(OK) transaction works well. > > > > When the Asterisk server sends a SIP Options message, I get the following > error: > > Jun 25 15:47:03 VRTPENGINE kamailio[4953]: INFO: <script>: => OPTIONS < > sip:l4umfumh at 192.0.2.97<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>;transport=ws;alias=209.141.117.212~59751~6 -> > <null> (IP:172.16.0.48:sp) > > Jun 25 15:47:03 VRTPENGINE kamailio[4953]: WARNING: <core> > [core/msg_translator.c:2815]: via_builder(): TCP/TLS connection (id: 0) for > WebSocket could not be found > > Jun 25 15:47:03 VRTPENGINE kamailio[4953]: ERROR: <core> > [core/msg_translator.c:2003]: build_req_buf_from_sip_req(): could not > create Via header > > Jun 25 15:47:03 VRTPENGINE kamailio[4953]: ERROR: <core> > [core/forward.c:550]: forward_request(): building failed > > Jun 25 15:47:03 VRTPENGINE kamailio[4953]: WARNING: <core> > [core/receive.c:425]: receive_msg(): error while trying script > > > > It appears that the WebSocket corresponding to the WSS leg cannot be > located when the request is initiated from the Asterisk Server. > > > > Any thoughts on how I can get this to work in the other direction > (Asterisk to Kamailio)? I've been looking at the WebRTC to SIP Client and > Server (https://github.com/havfo/WEBRTC-to-SIP), but that doesn't quite > do what I want it to do (i.e. it appears to act as a registrar server and > doesn't forward REGISTER requests on to another registrar). > > > > > > Thanks and regards, > > > > *Peter H. Manley, Ph.D.* > > Chief Software Architect > > KomBea Corporation > > 3400 North Ashton Blvd, Suite 470 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > Lehi, Utah 84043 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > www.kombea.com<http://www.kombea.com> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> > > > > Office:+1.801.610.5808 > > Mobile +1.801.243.7773 > > Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

1 0

Kamailio + RTPEngine - Destinations Behind NAT
by Edward Romanenco 29 Jun '21

29 Jun '21

Hi everyone, I'm using Kamailio (Ver 5.5.1, Public IP X.X.X.11, Private IP 172.18.0.20) + RTPEngine (Ver 9.4.1.1, Public IP X.X.X.7, Private IP 172.18.0.50) alongside Freeswitch (Private IP 172.18.0.40) in my backend and delivering calls to a mobile application (call flow is Freeswitch -> Kamailio + RTPEngine -> Applicaiton). While calls made to NATted destination generally works fine - from time to time, we've experiencing one-sided audio due to the rtpengine sending the media stream to the remote end's private IP instead of his public one. For instance, in the attached logs - media was sent towards 192.168.1.93 instead of 79.179.1.2, which is the expected destination. Problem appears almost randomly; I can make 20 fine calls in a row for the same destination until experiencing it, and I didn't find any difference as it comes to the SIP invite exchange between the two. Has anyone ever experienced the same behavior and can share some general instructions on how to troubleshoot it? Relevant Kamailio config section is attached. Invite Kamailio->Device INVITE sip:972587102881@79.179.1.2:56308;transport=TLS;ob SIP/2.0 Record-Route: <sip:X.X.X.11:443;transport=tls;r2=on;lr=on;ftag=cvcHy5UcS9pjj> Record-Route: <sip:172.18.0.20:5099;r2=on;lr=on;ftag=cvcHy5UcS9pjj> Via: SIP/2.0/TLS X.X.X.11:443;branch=z9hG4bK24bf.52b1dd68e26010ba103bd8d6fdb53cf4.0 Via: SIP/2.0/UDP 172.18.0.40;received=172.18.0.40;rport=5060;branch=z9hG4bKH234Q58HpHNKK Max-Forwards: 66 From: "972522149596" <sip:FreeSWITCH@172.18.0.20:5099>;tag=cvcHy5UcS9pjj To: <sip:972587102881@172.18.0.20:5099> Call-ID: be55bd1e-537d-123a-65a9-0242ac120028 CSeq: 37932220 INVITE Contact: <sip:gw+kam-in@172.18.0.40:5060;transport=udp;gw=kam-in;alias=172.18.0.40~5060~1> User-Agent: FreeSWITCH-mod_sofia/1.10.6-release+git~20210325T131609Z~1ff9d0a60e~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 567 X-SESSION-ID: 721533765 X-INCOMING: PSTN X-from-freeswitch: +972522149596 X-FS-Support: update_display,send_info Remote-Party-ID: "972522149596" <sip:972522149596@172.18.0.20:5099>;party=calling;screen=yes;privacy=off v=0 o=FreeSWITCH 1624937621 1624937622 IN IP4 X.X.X.7 s=FreeSWITCH c=IN IP4 X.X.X.7 t=0 0 m=audio 30018 RTP/AVP 102 101 a=rtpmap:102 opus/48000/2 a=fmtp:102 useinbandfec=1; maxaveragebitrate=30000; maxplaybackrate=48000; ptime=20; minptime=10; maxptime=40 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=sendrecv a=rtcp:30019 a=ptime:20 a=ice-ufrag:bKPZt0dW a=ice-pwd:H4qyL7mPUOvoiAjosiLasXAdzj a=candidate:41sXGEsTafxHi8ms 1 UDP 2130706431 X.X.X.7 30018 typ host a=candidate:41sXGEsTafxHi8ms 2 UDP 2130706430 X.X.X.7 30019 typ host Response Device->Kamailio SIP/2.0 200 OK Via: SIP/2.0/TLS X.X.X.11:443;received=X.X.X.11;branch=z9hG4bK24bf.52b1dd68e26010ba103bd8d6fdb53cf4.0 Via: SIP/2.0/UDP 172.18.0.40;rport=5060;received=172.18.0.40;branch=z9hG4bKH234Q58HpHNKK Record-Route: <sip:X.X.X.11:443;transport=tls;lr;r2=on;ftag=cvcHy5UcS9pjj> Record-Route: <sip:172.18.0.20:5099;lr;r2=on;ftag=cvcHy5UcS9pjj> Call-ID: be55bd1e-537d-123a-65a9-0242ac120028 From: "972522149596" <sip:FreeSWITCH@172.18.0.20>;tag=cvcHy5UcS9pjj To: <sip:972587102881@172.18.0.20>;tag=5f75877e-58c2-44f3-a5b3-43f8786c42a1 CSeq: 37932220 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Contact: <sip:972587102881@79.179.1.2:56308;transport=TLS;ob> Supported: replaces, 100rel, timer, norefersub Content-Type: application/sdp Content-Length: 348 v=0 o=- 3833960833 3833960834 IN IP4 192.168.1.93 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 4002 RTP/AVP 96 120 c=IN IP4 192.168.1.93 b=TIAS:96000 a=rtcp:4003 IN IP4 192.168.1.93 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:120 telephone-event/48000 a=fmtp:120 0-16 a=ssrc:816694098 cname:72cdb5f53fc2e8fb Kamailio NAT Detect/Manage Routes # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT xinfo("NATDETECT: Adding the rport parameter to the first Via header of the received message\n"); force_rport(); xinfo("NATDETECT: Trying to guess if client's request originated behind a nat. Testing 19.\n"); if (nat_uac_test("19")) { if (is_method("REGISTER")) { xinfo("NATDETECT: REGISTER request. Creating a URI consisting of the source IP, port, and protocol and storing the URI in an Attribute-Value-Pair.\n"); fix_nated_register(); } else { if(is_first_hop()) { xinfo("NATDETECT: Adding an ;alias=ip~port~transport parameter to the contact URI containing the received ip, port, and transport protocol.\n"); set_contact_alias(); } } xinfo("NATDETECT: Setting flag FLT_NATS.\n"); setflag(FLT_NATS); } else { xinfo("NATDETECT: Didn't detect natted request by any of the given heuristics\n"); } #!endif return; } # RTPProxy control and signaling updates for NAT traversal route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { xinfo("NATMANAGE: This is a request with to-tag that has 'nat=yes', setting branch flag FLB_NATB.\n"); setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) { xinfo("NATMANAGE: No NAT flag detected for this request\n"); return; } else { xinfo("NATMANAGE: NAT flag detected for this request\n"); } if(!is_present_hf("x-purpose")) { xinfo("NATMANAGE: x-purpose header does not appear in this request, SDP is searched for occurrence of RFC1918 or RFC6598 addresses.\n"); if(nat_uac_test("8")) { xinfo("NATMANAGE: Found occurrence of RFC1918 or RFC6598 addresses. Checking if there is a match of source address or uri with an address in the group of the dispatcher-list.\n"); if(ds_is_from_list()) { xinfo("NATMANAGE: There is a match with an address in the group of the dispatcher-list.\n"); rtpengine_manage("ICE=force replace-session-connection replace-origin direction=priv direction=pub"); } else { xinfo("NATMANAGE: No match with an address in the group of the dispatcher-list.\n"); rtpengine_manage("ICE=force replace-session-connection replace-origin direction=pub direction=priv"); } } else { xinfo("NATMANAGE: No occurrence of RFC1918 or RFC6598 addresses. Checking if there is a match of source address or uri with an address in the group of the dispatcher-list.\n"); if(ds_is_from_list()) { xinfo("NATMANAGE: There is a match with an address in the group of the dispatcher-list.\n"); rtpengine_manage("ICE=force replace-session-connection replace-origin trust-address direction=priv direction=pub"); } else { xinfo("NATMANAGE: No match with an address in the group of the dispatcher-list.\n"); rtpengine_manage("ICE=force replace-session-connection replace-origin trust-address direction=pub direction=priv"); } } } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { xinfo("NATMANAGE: This is a request without to-tag and top-executed route block is branch_route, adding record route param ;nat=yes.\n"); add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) { xinfo("NATMANAGE: Adding an ;alias=ip~port~transport parameter to the contact URI containing the received ip, port, and transport protocol.\n"); set_contact_alias(); } } } #!endif return; } RTPEngine Logs 2021-06-29T13:07:05.440658779Z [1624972025.439547] INFO: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Received command 'offer' from 172.18.0.20:53880 2021-06-29T13:07:05.440690853Z [1624972025.439641] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Dump for 'offer' from 172.18.0.20:53880: { "supports": [ "load limit" ], "sdp": "v=0 2021-06-29T13:07:05.440695330Z o=FreeSWITCH 1624937621 1624937622 IN IP4 172.18.0.40 2021-06-29T13:07:05.440698353Z s=FreeSWITCH 2021-06-29T13:07:05.440700926Z c=IN IP4 172.18.0.40 2021-06-29T13:07:05.440703539Z t=0 0 2021-06-29T13:07:05.440706179Z m=audio 34404 RTP/AVP 102 101 2021-06-29T13:07:05.440708722Z a=rtpmap:102 opus/48000/2 2021-06-29T13:07:05.440711294Z a=fmtp:102 useinbandfec=1; maxaveragebitrate=30000; maxplaybackrate=48000; ptime=20; minptime=10; maxptime=40 2021-06-29T13:07:05.440714053Z a=rtpmap:101 telephone-event/48000 2021-06-29T13:07:05.440716746Z a=fmtp:101 0-16 2021-06-29T13:07:05.440719258Z a=ptime:20 2021-06-29T13:07:05.440721823Z ", "ICE": "force", "direction": [ "priv", "pub" ], "replace": [ "session-connection", "origin" ], "call-id": "be55bd1e-537d-123a-65a9-0242ac120028", "received-from": [ "IP4", "172.18.0.40" ], "from-tag": "cvcHy5UcS9pjj", "command": "offer" } 2021-06-29T13:07:05.441069790Z [1624972025.439694] NOTICE: [be55bd1e-537d-123a-65a9-0242ac120028]: [core] Creating new call 2021-06-29T13:07:05.441088698Z [1624972025.439809] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Default sink codec is opus/48000/2 2021-06-29T13:07:05.441091829Z [1624972025.439815] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Output DTMF payload type is 101 2021-06-29T13:07:05.441094966Z [1624972025.439821] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Creating codec handler for opus/48000/2 2021-06-29T13:07:05.441097777Z [1624972025.439828] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Sink supports codec opus/48000/2 2021-06-29T13:07:05.441100540Z [1624972025.439833] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Using passthrough handler for opus/48000/2 2021-06-29T13:07:05.441103390Z [1624972025.439839] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Creating codec handler for telephone-event/48000 2021-06-29T13:07:05.441106153Z [1624972025.439844] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Sink supports codec telephone-event/48000 2021-06-29T13:07:05.441108913Z [1624972025.439849] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Using passthrough handler for telephone-event/48000 2021-06-29T13:07:05.441111679Z [1624972025.440116] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [core] set FILLED flag for stream 172.18.0.40:34404 2021-06-29T13:07:05.441124990Z [1624972025.440124] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [core] set FILLED flag for stream 172.18.0.40:34405 2021-06-29T13:07:05.441663481Z [1624972025.441074] INFO: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Replying to 'offer' from 172.18.0.20:53880 (elapsed time 0.001414 sec) 2021-06-29T13:07:05.441694377Z [1624972025.441103] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Response dump for 'offer' to 172.18.0.20:53880: { "sdp": "v=0 2021-06-29T13:07:05.441701068Z o=FreeSWITCH 1624937621 1624937622 IN IP4 X.X.X.7 2021-06-29T13:07:05.441706421Z s=FreeSWITCH 2021-06-29T13:07:05.441711414Z c=IN IP4 X.X.X.7 2021-06-29T13:07:05.441716274Z t=0 0 2021-06-29T13:07:05.441721177Z m=audio 30018 RTP/AVP 102 101 2021-06-29T13:07:05.441726204Z a=rtpmap:102 opus/48000/2 2021-06-29T13:07:05.441731246Z a=fmtp:102 useinbandfec=1; maxaveragebitrate=30000; maxplaybackrate=48000; ptime=20; minptime=10; maxptime=40 2021-06-29T13:07:05.441736873Z a=rtpmap:101 telephone-event/48000 2021-06-29T13:07:05.441742017Z a=fmtp:101 0-16 2021-06-29T13:07:05.441827012Z a=sendrecv 2021-06-29T13:07:05.441844744Z a=rtcp:30019 2021-06-29T13:07:05.441848881Z a=ptime:20 2021-06-29T13:07:05.441852444Z a=ice-ufrag:bKPZt0dW 2021-06-29T13:07:05.441856394Z a=ice-pwd:H4qyL7mPUOvoiAjosiLasXAdzj 2021-06-29T13:07:05.441860642Z a=candidate:41sXGEsTafxHi8ms 1 UDP 2130706431 X.X.X.7 30018 typ host 2021-06-29T13:07:05.441864955Z a=candidate:41sXGEsTafxHi8ms 2 UDP 2130706430 X.X.X.7 30019 typ host 2021-06-29T13:07:05.441868967Z ", "result": "ok" } 2021-06-29T13:07:07.001082810Z [1624972027.000176] DEBUG: [core] timer run time = 0.000029 sec 2021-06-29T13:07:07.817899628Z [1624972027.816949] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] >>> in_ssrc changed for: :0 new: 30adc352 2021-06-29T13:07:07.817932021Z [1624972027.816987] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] >>> out_ssrc changed for 172.18.0.40:34405 new: 30adc352 2021-06-29T13:07:07.817936388Z [1624972027.816998] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [rtcp] Calling handler for RTCP packet type 201 2021-06-29T13:07:07.817939853Z [1624972027.817025] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] RR from 30adc352 about 0: FL 0 TL 0 HSR 0 J 0 LSR 0 DLSR 0 2021-06-29T13:07:07.817942689Z [1624972027.817030] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] No payload type known for RTCP RR, discarding 2021-06-29T13:07:07.817945696Z [1624972027.817036] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [rtcp] Calling handler for RTCP packet type 202 2021-06-29T13:07:07.817948500Z [1624972027.817124] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] Forward to sink endpoint: 172.18.0.40:34405 2021-06-29T13:07:07.818762433Z [1624972027.817995] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [rtcp] Calling handler for RTCP packet type 201 2021-06-29T13:07:07.818790347Z [1624972027.818031] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] RR from 30adc352 about 0: FL 0 TL 0 HSR 0 J 0 LSR 0 DLSR 0 2021-06-29T13:07:07.818794422Z [1624972027.818035] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] No payload type known for RTCP RR, discarding 2021-06-29T13:07:07.818797834Z [1624972027.818042] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [rtcp] Calling handler for RTCP packet type 202 2021-06-29T13:07:07.818801095Z [1624972027.818122] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30019]: [core] Forward to sink endpoint: 172.18.0.40:34405 2021-06-29T13:07:07.847992398Z [1624972027.846284] INFO: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Received command 'answer' from 172.18.0.20:47817 2021-06-29T13:07:07.848048472Z [1624972027.846325] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Dump for 'answer' from 172.18.0.20:47817: { "supports": [ "load limit" ], "sdp": "v=0 2021-06-29T13:07:07.848058346Z o=- 3833960833 3833960834 IN IP4 192.168.1.93 2021-06-29T13:07:07.848063378Z s=pjmedia 2021-06-29T13:07:07.848067785Z b=AS:117 2021-06-29T13:07:07.848071736Z t=0 0 2021-06-29T13:07:07.848075782Z a=X-nat:0 2021-06-29T13:07:07.848079588Z m=audio 4002 RTP/AVP 96 120 2021-06-29T13:07:07.848084210Z c=IN IP4 192.168.1.93 2021-06-29T13:07:07.848089110Z b=TIAS:96000 2021-06-29T13:07:07.848092756Z a=rtcp:4003 IN IP4 192.168.1.93 2021-06-29T13:07:07.848096578Z a=sendrecv 2021-06-29T13:07:07.848100173Z a=rtpmap:96 opus/48000/2 2021-06-29T13:07:07.848104153Z a=fmtp:96 useinbandfec=1 2021-06-29T13:07:07.848108660Z a=rtpmap:120 telephone-event/48000 2021-06-29T13:07:07.848112776Z a=fmtp:120 0-16 2021-06-29T13:07:07.848116856Z a=ssrc:816694098 cname:72cdb5f53fc2e8fb 2021-06-29T13:07:07.848120776Z ", "ICE": "force", "direction": [ "pub", "priv" ], "replace": [ "session-connection", "origin" ], "call-id": "be55bd1e-537d-123a-65a9-0242ac120028", "received-from": [ "IP4", "79.179.1.2" ], "from-tag": "cvcHy5UcS9pjj", "to-tag": "5f75877e-58c2-44f3-a5b3-43f8786c42a1", "command": "answer" } 2021-06-29T13:07:07.848128079Z [1624972027.846411] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Default sink codec is opus/48000/2 2021-06-29T13:07:07.848132255Z [1624972027.846418] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Output DTMF payload type is 120 2021-06-29T13:07:07.848136164Z [1624972027.846424] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Creating codec handler for opus/48000/2 2021-06-29T13:07:07.848139819Z [1624972027.846429] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Sink supports codec opus/48000/2 2021-06-29T13:07:07.848143930Z [1624972027.846434] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Using passthrough handler for opus/48000/2 2021-06-29T13:07:07.848169208Z [1624972027.846441] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Creating codec handler for telephone-event/48000 2021-06-29T13:07:07.848174300Z [1624972027.846445] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Sink supports codec telephone-event/48000 2021-06-29T13:07:07.848178752Z [1624972027.846449] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [codec] Using passthrough handler for telephone-event/48000 2021-06-29T13:07:07.848183460Z [1624972027.846586] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [core] set FILLED flag for stream 192.168.1.93:4002 2021-06-29T13:07:07.848188805Z [1624972027.846593] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [core] set FILLED flag for stream 192.168.1.93:4003 2021-06-29T13:07:07.848193111Z [1624972027.846597] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [ice] Shutting down ICE agent (nothing to do) 2021-06-29T13:07:07.848197042Z [1624972027.847228] INFO: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Replying to 'answer' from 172.18.0.20:47817 (elapsed time 0.000890 sec) 2021-06-29T13:07:07.848201623Z [1624972027.847243] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028]: [control] Response dump for 'answer' to 172.18.0.20:47817: { "sdp": "v=0 2021-06-29T13:07:07.848205754Z o=- 3833960833 3833960834 IN IP4 172.18.0.50 2021-06-29T13:07:07.848209696Z s=pjmedia 2021-06-29T13:07:07.848213446Z b=AS:117 2021-06-29T13:07:07.848217361Z t=0 0 2021-06-29T13:07:07.848220816Z a=X-nat:0 2021-06-29T13:07:07.848224363Z m=audio 30018 RTP/AVP 96 120 2021-06-29T13:07:07.848228432Z c=IN IP4 172.18.0.50 2021-06-29T13:07:07.848232603Z b=TIAS:96000 2021-06-29T13:07:07.848235992Z a=ssrc:816694098 cname:72cdb5f53fc2e8fb 2021-06-29T13:07:07.848240381Z a=rtpmap:96 opus/48000/2 2021-06-29T13:07:07.848243923Z a=fmtp:96 useinbandfec=1 2021-06-29T13:07:07.848247725Z a=rtpmap:120 telephone-event/48000 2021-06-29T13:07:07.848386453Z a=fmtp:120 0-16 2021-06-29T13:07:07.848395759Z a=sendrecv 2021-06-29T13:07:07.848399822Z a=rtcp:30019 2021-06-29T13:07:07.848403748Z a=ptime:20 2021-06-29T13:07:07.848407203Z a=ice-ufrag:4Q9H38CE 2021-06-29T13:07:07.848410827Z a=ice-pwd:OR8EfUn5dCLbhZqyiwsTUOyUdW 2021-06-29T13:07:07.848414680Z a=candidate:f75EKiqnFiVfQdoZ 1 UDP 2130706431 172.18.0.50 30018 typ host 2021-06-29T13:07:07.848419247Z a=candidate:f75EKiqnFiVfQdoZ 2 UDP 2130706430 172.18.0.50 30019 typ host 2021-06-29T13:07:07.848432370Z ", "result": "ok" } 2021-06-29T13:07:07.872251466Z [1624972027.871342] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [ice] Created candidate pair f75EKiqnFiVfQdoZ:33d9f4832b3cc9a0:1 between 172.18.0.50 and 172.18.0.40:34404, type prflx 2021-06-29T13:07:07.872276197Z [1624972027.871381] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [ice] Triggering check for f75EKiqnFiVfQdoZ:33d9f4832b3cc9a0:1 2021-06-29T13:07:07.872286600Z [1624972027.871396] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [ice] ICE pair f75EKiqnFiVfQdoZ:33d9f4832b3cc9a0:1 has been nominated by peer 2021-06-29T13:07:07.872289762Z [1624972027.871401] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [ice] ICE not completed yet and no usable candidates 2021-06-29T13:07:07.872292668Z [1624972027.871407] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Successful STUN binding request from 172.18.0.40:34404 2021-06-29T13:07:07.919668940Z [1624972027.918862] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] >>> in_ssrc changed for: 172.18.0.40:34404 new: 70f328c1 2021-06-29T13:07:07.919698433Z [1624972027.918897] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] >>> out_ssrc changed for 192.168.1.93:4002 new: 70f328c1 2021-06-29T13:07:07.919703321Z [1624972027.918911] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64423 TS 2880) 2021-06-29T13:07:07.939554198Z [1624972027.938733] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64424 TS 3840) 2021-06-29T13:07:07.959769679Z [1624972027.959017] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64425 TS 4800) 2021-06-29T13:07:07.979861917Z [1624972027.979067] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64426 TS 5760) 2021-06-29T13:07:07.999566603Z [1624972027.998777] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64427 TS 6720) 2021-06-29T13:07:08.019668998Z [1624972028.018802] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64428 TS 7680) 2021-06-29T13:07:08.040856248Z [1624972028.039663] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64429 TS 8640) 2021-06-29T13:07:08.061133612Z [1624972028.059847] DEBUG: [be55bd1e-537d-123a-65a9-0242ac120028 port 30018]: [core] Forward to sink endpoint: 192.168.1.93:4002 (RTP seq 64430 TS 9600) Edward

1 1

Guidance building a WebRTC to Asterisk Intermediate Proxy
by Peter Manley 26 Jun '21

26 Jun '21

Hello, I'm working on building an RTP Proxy which will allow both regular SIP to SIP transactions and WebRTC to SIP transactions to an Asterisk Server. SIP UAC < ---UDP/SIP --- > Kamailio/RTPEngine Proxy < ---UDP/SIP----- > Asterisk Server AND WebRTC UAC < ---WSS--- > Kamailio/RTPEngine Proxy < ---UDP/SIP----- > Asterisk Server The Kamailio/RTPEngine Proxy is stateless (does not use the tm or registerer modules), and uses the Path module to replace the Route header with a Path header. It works grep for SIP/UDP to SIP/UDP transactions. HOWEVER... It only partially works for WSS to SIP/UDP transactions. The REGISTER/401(Unauthorized), REGISTER/200(OK) transaction works well. When the Asterisk server sends a SIP Options message, I get the following error: Jun 25 15:47:03 VRTPENGINE kamailio[4953]: INFO: <script>: => OPTIONS < sip:l4umfumh@192.0.2.97;transport=ws;alias=209.141.117.212~59751~6 -> <null> (IP:172.16.0.48:sp) Jun 25 15:47:03 VRTPENGINE kamailio[4953]: WARNING: <core> [core/msg_translator.c:2815]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jun 25 15:47:03 VRTPENGINE kamailio[4953]: ERROR: <core> [core/msg_translator.c:2003]: build_req_buf_from_sip_req(): could not create Via header Jun 25 15:47:03 VRTPENGINE kamailio[4953]: ERROR: <core> [core/forward.c:550]: forward_request(): building failed Jun 25 15:47:03 VRTPENGINE kamailio[4953]: WARNING: <core> [core/receive.c:425]: receive_msg(): error while trying script It appears that the WebSocket corresponding to the WSS leg cannot be located when the request is initiated from the Asterisk Server. Any thoughts on how I can get this to work in the other direction (Asterisk to Kamailio)? I've been looking at the WebRTC to SIP Client and Server (https://github.com/havfo/WEBRTC-to-SIP), but that doesn't quite do what I want it to do (i.e. it appears to act as a registrar server and doesn't forward REGISTER requests on to another registrar). Thanks and regards, Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

2 1

using both ldap and local authenticate
by Thành Trần Duy 25 Jun '21

25 Jun '21

Hi all, I am using kamailio as PBX with some softphones and hard phones. I want user on a pc to login with LDAP and users using a hard phone login normally (username/password). Can I use 2 types of authentication at the same time? Many thanks, Tran Duy Thanh

2 2

Possible memory leak on 5.5.x (new)?
by George Diamantopoulos 25 Jun '21

25 Jun '21

Hello all, I'm still investigating the (most likely non-kamailio-related) memory leak of my previous message to the list, there have been no developments so far. I'll update if anything changes. This concerns a new finding which seems to affect kamailio 5.5.x. I have two kamailio instances receiving the same traffic via round-robin. I upgraded only one of them to 5.5.1 and left the other to 5.4.6 as I feared of any issues arising. I was lucky to do so, because with identical configuration, 5.5.x seems to run out of SHM very quickly. Here are links to graphs produced by our monitoring system: Old kamailio (no memory leak): https://pasteboard.co/K8fVBiD.png New kamailio (possible leak): https://pasteboard.co/K8fVS9N.png The configuration uses mtree, htable, vars and vns extensively. Has anyone come across anything similar? Let me know if I can provide any further information to help disect this. Thanks! BR, George

2 1

rr module: record_route_advertised_address()/record_route_preset() do ignore custom user AVP
by Valentin Christoph 25 Jun '21

25 Jun '21

Hi, Maybe a discussion for the DEV mailing list???? Want to overwrite the FQDN by a NATed IP address in the topmost Record-Route of an outgoing INVITE request. Cannot set the advertise parameter (this must tell the FQDN for all other situations), only in some special situations I want to overwrite the FQDN in Record-Route. My solution would be to implement in the Kamailio source code (rr module) that not only record_route() uses the get_custom_user() function, but the other both functions uses it, too. Any better proposals? All the best Christoph

2 3

Kamailio $Rp variable showing wrong port
by Shahid Hussain 25 Jun '21

25 Jun '21

Hi, I have configured the dispatcher default socket as below IP , the expectation here is that kamailio should send all traffic from this IP (port will be ephemeral) over TCP. modparam("dispatcher", "ds_default_socket", "tcp:172.27.45.219:5060") This system also listens on port 8080 which is meant for websocket communication (dispatcher communication is over non websocket). Kamailio is sending an OPTION message to dispatcher IP over TCP on 5060 and getting 200 OK response but Kamailio considering the response is on websocket port 8080 ,$Rp value is 8080. onreply_route { if (($Rp == 8080 ) && !(proto == WS)) { xlog("L_WARN", "SIP response received on $Rp protocol:proto RIP:$Ri SIP:$si method:$rm cid:$ci replystatus:$rs len:$ml\n"); xlog("L_WARN", "SIP message received: $mb\n"); drop; } ..... .... } Following is the output of above logs: Jun 24 15:10:08 localhost /usr/sbin/kamailio[6223]: WARNING: {2 10 OPTIONS 1ab6573a4640823b-6209(a)172.27.45.198} <script>: SIP response received on 8080 protocol:tcp RIP:172.27.45.219 SIP:172.27.44.125 method:OPTIONS cid:1ab6573a4640823b-6209@172.27.45.198 replystatus:200 len:416 Jun 24 15:10:08 localhost /usr/sbin/kamailio[6223]: WARNING: {2 10 OPTIONS 1ab6573a4640823b-6209(a)172.27.45.198} <script>: SIP message received: SIP/2.0 200 OK#015#012Via: SIP/2.0/TCP 172.27.45.198:5060;branch=z9hG4bK4526.92b79f34000000000000000000000000.0;received=172.27.45.219#015#012From: <sip:dispatcher@localhost>;tag=1ae6c95d92f9ea9ce927f715de5c48c8-eb141029#015#012To: <sip:172.27.44.125:5060;transport=tcp>;tag=a9d542e0#015#012Call-ID: 1ab6573a4640823b-6209(a)172.27.45.198#015#012CSeq: 10 OPTIONS#015#012Allow: INVITE, ACK, BYE, OPTIONS, CANCEL, INFO, UPDATE, NOTIFY#015#012Content-Length: 0 Also I have attached a pcap. Dispatcher.list configuration: 1 sip:172.27.44.125:5060;transport=tcp 0 0 duid=sample-cas;maxload=1000 Thanks, Shahid

3 10

S-CSCF and I-CSCF
by Jayanth Acharya 24 Jun '21

24 Jun '21

Hi, Have found example configuration for S-CSCF, I-CSCF and P-CSCF in Kamailio repository, and a S-CSCF module for the registered user data, but no recent updates. Wondering if anyone can share insights into how widely it has been used, or interops done in say telco networks with it ? Does it handle third-party registrations, is it actually able to do a Cx interaction with HSS ? Finally, how have these components that make up the IMS-core from SIP signaling standpoint, been tested ? Are there any signaling only test harnesses ? cheers, Jay

2 1

Errors after upgrade to 5.5
by Daniel W. Graham 23 Jun '21

23 Jun '21

Receiving constant errors for all functions after upgrade to 5.5, any change that could have caused this? ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:968] took too long [1251 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:988] took too long [1309 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:1038] took too long [1321 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (5)] cfg [/usr/local/etc/kamailio/kamailio.cfg:452] took too long [1342 us] ERROR: <core> [db_query.c:68]: db_do_submit_query(): alert - query execution too long [1493 us] for [select `password`,`id` from `subscriber` where `username`='x'] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [www_authenticate (26)] cfg [/usr/local/etc/kamailio/kamailio.cfg:951] took too long [1667 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:968] took too long [1694 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:988] took too long [1817 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (16)] cfg [/usr/local/etc/kamailio/kamailio.cfg:1038] took too long [1835 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [corefunc (5)] cfg [/usr/local/etc/kamailio/kamailio.cfg:452] took too long [1869 us] ERROR: <core> [core/action.c:1598]: run_actions(): alert - action [www_authenticate (26)] cfg [/usr/local/etc/kamailio/kamailio.cfg:951] took too long [1405 us] ……. -dan

2 4

AVPs in Switch/Case
by Joel Serrano 22 Jun '21

22 Jun '21

Hi guys, Quick question, are AVPs valid in "switch" as "case"'s? Example: $avp(var1) = "101"; $avp(var2) = "201"; switch($rU) { case "$avp(var1)": ... break; case "$avp(var2)": ... break; default: send_reply("403", "Forbidden"); exit; } For some reason I can't get the case to match, and I'm thinking it's not using the actual value of $avp(var1) and instead it's using literally "$avp(var1)" as a string. NOTE: I also tried without putting the AVPs in quotes, but Kamailio complains and doesn't start. Is this doable or do I need to use if..else if..else if..else for this? Thanks, Joel.

3 3

Web Sockets connection error: bad request, state=7, error=4
by Peter Manley 22 Jun '21

22 Jun '21

Hello, I'm using Kamailio 5.3.2 and am trying to establish a WebRTC connection for using SIP through Kamailio on port 8089. I am getting the following error in the Syslog: Jun 22 09:20:38 VRTPENGINE kamailio[43050]: ERROR: <core> [core/tcp_read.c:1535]: tcp_read_req(): bad request, state=7, error=4 buf:#012GET /ws HTTP/1.1#015#012Host: rtpengine.kombea.io:8089#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://vicidev.kombea.io#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9#015#012Sec-WebSocket-Key: 1Pda50NxHxMenZaMW7cUkA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012#012parsed:#012GET /ws HTTP/1.1#015#012Host: rtpengine.kombea.io:8089#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://vicidev.kombea.io#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9#015#012Sec-WebSocket-Key: 1Pda50NxHxMenZaMW7cUkA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012 Any idea on what would cause this? Thanks Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

2 2

execute callback every X minutes mid call
by Avremy Cohen 22 Jun '21

22 Jun '21

Hi I am trying to execute code every X min in active calls and I cant seem to find any way to do this. I basically have a function that checks if the user has balance and permission to carry on the call and the callback should trigger it every X mins. The call_control module doesnt work for me since A. It doesn't trigger a function it just ends the callback B. it uses an external application to calculate it any advice is appreciated Avi

3 3

Re: [SR-Users] Unable to establish TCP connection with Kamailio
by Peter Manley 17 Jun '21

17 Jun '21

Hello Ovidiu, Interestingly, that fixed the problem. I can now continue to make progress. Why does not forking and/or logging to stderr cause this to happen? Thank you! Regards, Peter Manley Ovidiu Sas osas at voipembedded.com<mailto:sr-users%40lists.kamailio.org?Subject=Re%3A%20%5BSR-Users%5D%20Unable%20to%20establish%20TCP%20connection%20with%20Kamailio&In-Reply-To=%3CCAND0LkvxyxE%3D5CPxZTe-Em43X6E5nep6z9n7a8f1zo3YbKksMw%40mail.gmail.com%3E> Thu Jun 17 23:05:14 CEST 2021 * Previous message (by thread): [SR-Users] Unable to establish TCP connection with Kamailio<https://lists.kamailio.org/pipermail/sr-users/2021-June/112759.html> * Messages sorted by: [ date ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/date.html#112760> [ thread ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/thread.html#112760> [ subject ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/subject.html#112760> [ author ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/author.html#112760> ________________________________ It seems that you have fork set to no, Let kamailio fork and collect logs via syslog (not via stderror). -ovidiu On Thu, Jun 17, 2021 at 16:26 Peter Manley <peter.manley at kombea.com<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote: > Hello, > > > > I'm running Kamailio Version 5.3.2 on Ubuntu 20.04. Here my build > information: > > > > version: kamailio 5.3.2 (x86_64/linux) > > flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, > F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, > USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, > HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED > > ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, > BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB > > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > > id: unknown > > compiled with gcc 9.2.1 > > > > I have the following configuration set in my kamalio.cfg file: > > > > ##!define WITH_MYSQL > > ##!define WITH_AUTH > > ##!define WITH_USRLOCDB > > ##!define WITH_TLS > > ##!define WITH_HOMER > > ##!define WITH_WEBSOCKETS > > ##!define WITH_ANTIFLOOD > > ##!define WITH_IPV6 > > ##!define WITH_BRIDGE_ON_FAIL > > ##!define WITH_LOCALHOST_WS > > ##!define WITH_LOCALHOST_SIP > > > > #!substdef "!MY_SIP_PORT!5060!g" > > #!substdef "!MY_SIPS_PORT!5061!g" > > #!substdef "!MY_WS_PORT!8088!g" > > #!substdef "!MY_WSS_PORT!8089!g" > > > > #!substdef "!MY_LOG_FACILITY!LOG_DAEMON!g" > > > > #!substdef "!MY_IP4_ADDR!172.16.0.57!g" > > #!substdef "!IP4_LOCALHOST!127.0.0.1!g" > > #!substdef "!MY_WS4_ADDR!tcp:MY_IP4_ADDR:MY_WS_PORT!g" > > #!substdef "!MY_WSS4_ADDR!tls:MY_IP4_ADDR:MY_WSS_PORT!g" > > #!substdef "!LOCALHOST_WS4_ADDR!tcp:IP4_LOCALHOST:MY_WS_PORT!g" > > #!substdef "!LOCALHOST_WSS4_ADDR!tls:IP4_LOCALHOST:MY_WSS_PORT!g" > > > > #!ifdef WITH_IPV6 > > #!substdef "!MY_IP6_ADDR![fe80::d6e4:2f5f:e5b7:7dff]!g" > > #!substdef "!IP6_LOCALHOST![::1]!g" > > #!substdef "!MY_WS6_ADDR!tcp:MY_IP6_ADDR:MY_WS_PORT!g" > > #!substdef "!MY_WSS6_ADDR!tls:MY_IP6_ADDR:MY_WSS_PORT!g" > > #!substdef "!LOCALHOST_WS6_ADDR!tcp:IP6_LOCALHOST:MY_WS_PORT!g" > > #!substdef "!LOCALHOST_WSS6_ADDR!tls:IP6_LOCALHOST:MY_WSS_PORT!g" > > #!endif > > > > #!substdef "!MY_DOMAIN!rtpengine.kombea.io!g" > > debug=10 // debug level (cmd line: -dddddddddd) > > children=4 > > #fork=yes > > force_rport=yes // Add recieved port to VIA > > #log_stderror=no // (cmd line: -E) > > > > // Uncomment these lines to enter debugging mode > > fork=no > > log_stderror=yes > > > > check_via=no // (cmd. line: -v) > > dns=no // (cmd. line: -r) > > rev_dns=no // (cmd. line: -R) > > > > log_facility=MY_LOG_FACILITY > > > > // Define the listening ports and addresses > > port=MY_SIP_PORT > > tls_port_no=MY_SIPS_PORT > > > > > > // Define TCP parameters > > tcp_children=4 > > tcp_no_connect=no > > tcp_rd_buf_size=16384 > > tcp_max_connections=2048 > > tcp_connection_lifetime=3605 > > disable_tcp=no > > #!ifdef WITH_TLS > > enable_tls=yes > > #!endif > > > > > > listen=MY_IP4_ADDR > > #!ifdef WITH_LOCALHOST_SIP > > listen=IP4_LOCALHOST > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_IP6_ADDR > > #!ifdef WITH_LOCALHOST_SIP > > listen=IP6_LOCALHOST > > #!endif > > #!endif > > > > #!ifdef WITH_WEBSOCKETS > > listen=MY_WS4_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WS4_ADDR > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_WS6_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WS6_ADDR > > #!endif > > #!endif > > #!ifdef WITH_TLS > > listen=MY_WSS4_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WSS4_ADDR > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_WSS6_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WSS6_ADDR > > #!endif > > #!endif > > #!endif > > #!endif > > > > force_rport=yes // Add received port to VIA > > > > loadmodule "pv.so" // Pseudo-Variable support > > loadmodule "xlog.so" // Formatted logging support > > loadmodule "sl.so" // Stateless request handling > > loadmodule "siputils.so" // SIP utility helpers > > loadmodule "sanity.so" // Sanity check > > loadmodule "maxfwd.so" // Support for Max-Forward header > > loadmodule "textops.so" // Text operations on SIP messages > > loadmodule "textopsx.so" // Extended Text operations on SIP messages > > loadmodule "sdpops.so" // SDP operations > > loadmodule "nathelper.so" // NAT traversal helpers > > loadmodule "rr.so" // Record Route handling > > loadmodule "outbound.so" // Outbound support > > loadmodule "path.so" // Path handling > > > > #!ifdef WITH_TLS > > loadmodule "tls.so" // TLS Support > > #!endif > > > > #!ifdef WITH_WEBSOCKETS > > loadmodule "xhttp.so" // XHTTP support > > loadmodule "websocket.so" // WebSocket support > > #!endif > > loadmodule "rtpengine.so" // RTPEngine control > > > > #!ifdef WITH_DEBUG > > loadmodule "debugger.so" > > #!endif > > > > When I start Kamailio, I see the following in the output to stderr: > > > > Listening on > > udp: 172.16.0.57:5060 > > tcp: 172.16.0.57:5060 > > Aliases: > > tcp: VRTPENGINE:5060 > > udp: VRTPENGINE:5060 > > > > WARNING: no fork mode > > 0(6299) INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt > as the io watch method (auto detected) > > > > Here's the problem: > > > > When I connect via UDP, everything works fine. I can connect and see all > SIP traffic. > > > > However, if I try to connect via TCP, I see the initial SYN packet in > attempting to establish a connection. > > > > Kamailio responds with an [RST,ACK] message and the TCP connection is > never established. No further TCP traffic is sent. > > > > Any ideas on what I'm doing wrong? > > <https://www.google.com/maps/search/3400%0D%0A+North+Ashton+Blvd,+Suite+470+…> > > > > *Peter H. Manley, Ph.D.* > > Chief Software Architect > > KomBea Corporation > > 3400 North Ashton Blvd, Suite 470 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > Lehi, Utah 84043 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > www.kombea.com<http://www.kombea.com> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> > > > > Office:+1.801.610.5808 > > Mobile +1.801.243.7773 > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users at lists.kamailio.org<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > 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 > -- VoIP Embedded, Inc. http://www.voipembedded.com<http://www.voipembedded.com/>

2 1

Unable to establish TCP connection with Kamailio
by Peter Manley 17 Jun '21

17 Jun '21

Hello, I'm running Kamailio Version 5.3.2 on Ubuntu 20.04. Here my build information: version: kamailio 5.3.2 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 9.2.1 I have the following configuration set in my kamalio.cfg file: ##!define WITH_MYSQL ##!define WITH_AUTH ##!define WITH_USRLOCDB ##!define WITH_TLS ##!define WITH_HOMER ##!define WITH_WEBSOCKETS ##!define WITH_ANTIFLOOD ##!define WITH_IPV6 ##!define WITH_BRIDGE_ON_FAIL ##!define WITH_LOCALHOST_WS ##!define WITH_LOCALHOST_SIP #!substdef "!MY_SIP_PORT!5060!g" #!substdef "!MY_SIPS_PORT!5061!g" #!substdef "!MY_WS_PORT!8088!g" #!substdef "!MY_WSS_PORT!8089!g" #!substdef "!MY_LOG_FACILITY!LOG_DAEMON!g" #!substdef "!MY_IP4_ADDR!172.16.0.57!g" #!substdef "!IP4_LOCALHOST!127.0.0.1!g" #!substdef "!MY_WS4_ADDR!tcp:MY_IP4_ADDR:MY_WS_PORT!g" #!substdef "!MY_WSS4_ADDR!tls:MY_IP4_ADDR:MY_WSS_PORT!g" #!substdef "!LOCALHOST_WS4_ADDR!tcp:IP4_LOCALHOST:MY_WS_PORT!g" #!substdef "!LOCALHOST_WSS4_ADDR!tls:IP4_LOCALHOST:MY_WSS_PORT!g" #!ifdef WITH_IPV6 #!substdef "!MY_IP6_ADDR![fe80::d6e4:2f5f:e5b7:7dff]!g" #!substdef "!IP6_LOCALHOST![::1]!g" #!substdef "!MY_WS6_ADDR!tcp:MY_IP6_ADDR:MY_WS_PORT!g" #!substdef "!MY_WSS6_ADDR!tls:MY_IP6_ADDR:MY_WSS_PORT!g" #!substdef "!LOCALHOST_WS6_ADDR!tcp:IP6_LOCALHOST:MY_WS_PORT!g" #!substdef "!LOCALHOST_WSS6_ADDR!tls:IP6_LOCALHOST:MY_WSS_PORT!g" #!endif #!substdef "!MY_DOMAIN!rtpengine.kombea.io!g" debug=10 // debug level (cmd line: -dddddddddd) children=4 #fork=yes force_rport=yes // Add recieved port to VIA #log_stderror=no // (cmd line: -E) // Uncomment these lines to enter debugging mode fork=no log_stderror=yes check_via=no // (cmd. line: -v) dns=no // (cmd. line: -r) rev_dns=no // (cmd. line: -R) log_facility=MY_LOG_FACILITY // Define the listening ports and addresses port=MY_SIP_PORT tls_port_no=MY_SIPS_PORT // Define TCP parameters tcp_children=4 tcp_no_connect=no tcp_rd_buf_size=16384 tcp_max_connections=2048 tcp_connection_lifetime=3605 disable_tcp=no #!ifdef WITH_TLS enable_tls=yes #!endif listen=MY_IP4_ADDR #!ifdef WITH_LOCALHOST_SIP listen=IP4_LOCALHOST #!endif #!ifdef WITH_IPV6 listen=MY_IP6_ADDR #!ifdef WITH_LOCALHOST_SIP listen=IP6_LOCALHOST #!endif #!endif #!ifdef WITH_WEBSOCKETS listen=MY_WS4_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WS4_ADDR #!endif #!ifdef WITH_IPV6 listen=MY_WS6_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WS6_ADDR #!endif #!endif #!ifdef WITH_TLS listen=MY_WSS4_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WSS4_ADDR #!endif #!ifdef WITH_IPV6 listen=MY_WSS6_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WSS6_ADDR #!endif #!endif #!endif #!endif force_rport=yes // Add received port to VIA loadmodule "pv.so" // Pseudo-Variable support loadmodule "xlog.so" // Formatted logging support loadmodule "sl.so" // Stateless request handling loadmodule "siputils.so" // SIP utility helpers loadmodule "sanity.so" // Sanity check loadmodule "maxfwd.so" // Support for Max-Forward header loadmodule "textops.so" // Text operations on SIP messages loadmodule "textopsx.so" // Extended Text operations on SIP messages loadmodule "sdpops.so" // SDP operations loadmodule "nathelper.so" // NAT traversal helpers loadmodule "rr.so" // Record Route handling loadmodule "outbound.so" // Outbound support loadmodule "path.so" // Path handling #!ifdef WITH_TLS loadmodule "tls.so" // TLS Support #!endif #!ifdef WITH_WEBSOCKETS loadmodule "xhttp.so" // XHTTP support loadmodule "websocket.so" // WebSocket support #!endif loadmodule "rtpengine.so" // RTPEngine control #!ifdef WITH_DEBUG loadmodule "debugger.so" #!endif When I start Kamailio, I see the following in the output to stderr: Listening on udp: 172.16.0.57:5060 tcp: 172.16.0.57:5060 Aliases: tcp: VRTPENGINE:5060 udp: VRTPENGINE:5060 WARNING: no fork mode 0(6299) INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt as the io watch method (auto detected) Here's the problem: When I connect via UDP, everything works fine. I can connect and see all SIP traffic. However, if I try to connect via TCP, I see the initial SYN packet in attempting to establish a connection. Kamailio responds with an [RST,ACK] message and the TCP connection is never established. No further TCP traffic is sent. Any ideas on what I'm doing wrong? Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

2 1

ATIS-1000085 STIR/SHAKEN DIV PASSporT
by Steven Wheeler 17 Jun '21

17 Jun '21

My Google searches aren't turning up any results, probably because this standard isn't finalized yet, but is anyone aware of a module which implements DIV PASSporTs for diverted calls? More details on the standard here: https://transnexus.com/blog/2020/shaken-div-std-letter-ballot/ Steven Wheeler

3 5

Re: [SR-Users] Roadmap to the next major release - v5.5.0
by Henning Westerholt 16 Jun '21

16 Jun '21

Hello, If I remember correctly then in Debian Buster, the necessary library is not included and therefore the package cannot be build. You could use bullseye, the upcoming version, of compile by yourself. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: David Villasmil <david.villasmil.work(a)gmail.com> Sent: Wednesday, June 16, 2021 8:54 PM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] Roadmap to the next major release - v5.5.0 I don't see the module in deb http://deb.kamailio.org/kamailio55 buster main Regards, David Villasmil email: david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337 On Wed, Jun 16, 2021 at 9:12 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello, if you are referring to the module, its available in this release: https://kamailio.org/docs/modules/5.5.x/modules/secsipid.html Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of David Villasmil Sent: Wednesday, June 16, 2021 10:03 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>; miconda(a)gmail.com<mailto:miconda@gmail.com> Subject: Re: [SR-Users] Roadmap to the next major release - v5.5.0 Hello Daniel, Is it possible at all to get secsipid in? Thanks David On Thu, 25 Feb 2021 at 15:21, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> wrote: Hello, it is the time to plan a bit the road to the next major release, to be versioned 5.5.0. The 5.4.0 was release by end of July 2020, therefore we are approaching the end of our usual development cycle, also during the last online devel meeting we considered the 2nd part of spring 2021 as a target time frame for 5.5. To narrow it down, I would propose to freeze the development at the end of March 2021, test during April and maybe beginning of May, then release v5.5.0. So far we have a lot of development to existing components, by the freeze date I expect 3-5 new modules to be in the repo as well. If anyone wants a different time line towards 5.5.0, let's discuss and choose the one that suits most of the developers. Cheers, Daniel -- 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> Funding: https://www.paypal.me/dcmierla _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337

2 1

Roadmap to the next major release - v5.5.0
by Daniel-Constantin Mierla 16 Jun '21

16 Jun '21

Hello, it is the time to plan a bit the road to the next major release, to be versioned 5.5.0. The 5.4.0 was release by end of July 2020, therefore we are approaching the end of our usual development cycle, also during the last online devel meeting we considered the 2nd part of spring 2021 as a target time frame for 5.5. To narrow it down, I would propose to freeze the development at the end of March 2021, test during April and maybe beginning of May, then release v5.5.0. So far we have a lot of development to existing components, by the freeze date I expect 3-5 new modules to be in the repo as well. If anyone wants a different time line towards 5.5.0, let's discuss and choose the one that suits most of the developers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

3 3

Using Kamailio with Asterisk/pjsip outbound_publish - early state is not notified
by Barry Flanagan 15 Jun '21

15 Jun '21

Hi Using Kamailio 5.4 with Asterisk 18 and using the pjsip outbound-publish to allow Kamailio to handle BLF for phones. BLF sort of works, in that when a line is on a call, the BLF reflects that. However the early/ringing state does not generate a NOTIFY to the phone, although Asterisk is sending the Publish and is receiving a 200OK reply from Kamailio. I would presume that since basic BLF is working that this early state PUBLISH should generate a NOTIFY but it doesn't Module params are as follows: # ----- presence params ----- modparam("presence", "db_url", DBURL) modparam("presence", "server_address", "sip:192.168.245.250:5060") modparam("presence", "local_log_level", 3) modparam("presence", "publ_cache", 0) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "sip_uri_match", 1) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_dialoginfo", "force_single_dialog", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) Any help appreciated! -Barry

1 0

Kamailio v5.5.1 Released
by Daniel-Constantin Mierla 15 Jun '21

15 Jun '21

Hello, Kamailio SIP Server v5.5.1 stable release is out. This is a maintenance release of the latest stable branch, 5.5, that includes fixes since the release of v5.5.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.1. For more details about version 5.5.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/06/kamailio-v5-5-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Releasing Kamailio v5.5.1
by Daniel-Constantin Mierla 15 Jun '21

15 Jun '21

Hello, I am considering to release Kamailio v5.5.1 sometime next week, likely on Tuesday or Wednesday (June 15 or 16, 2021). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

Is Kamailio GPL or GPLv2
by Yan Gao 15 Jun '21

15 Jun '21

Hello, I have a question about the license of Kamailio. It is said to be GPL in https://www.kamailio.org/w/: "Kamailio® (successor of former OpenSER and SER) is an Open Source SIP Server released under GPL, able to handle thousands of call setups per second...." But GPLv2 in https://www.kamailio.org/w/info/ : "Kamailio is released under GNU Public License v2 (GPLv2). Beginning with 3.0.0, the application includes parts of code under BSD license that can be used such as individual components." Which one is the correct description? Thanks & Regards, Yan

2 2

vsf/vst question
by David Escartín 15 Jun '21

15 Jun '21

Hello all! as we knew vsf/vst were added to the RR header when using uac_replace for From/To headers. BUt we observed that some versions ago (we are using now 5.4) that stop happening with this setup modparam("uac", "restore_mode", "auto") modparam("uac", "restore_dlg", 1) modparam("rr", "enable_full_lr", 0) modparam("rr", "enable_double_rr", 1) modparam("rr", "append_fromtag", 1) and only ftag, did are added as param to RR However we have seen that when using multihomed kamailio instance and doing uac_replace, vsf/vst are included also with ftag and did params. Is that behaviour known or expected? thanks a lot and regards david -- <http://www.sonoc.io/> David Escartín NOC engineer *www.sonoc.io* <http://www.sonoc.io/> [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Facebook] <https://www.facebook.com/SONOCio/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: *dataprotection(a)sonoc.io* <dataprotection(a)sonoc.io>*.* <dataprotection(a)sonoc.io>

2 2

using path in Subscriber table
by Thành Trần Duy 14 Jun '21

14 Jun '21

Hi all, First of all, I would like to present the system model we are applying: - dSIPRouter : Sip relay for all users connected from the internet (installed with RTPEngine to handle media data). - kamailio 5.3.5: core system, registration server. - Asterisk 17: SBC. Sorry if our model seems a bit backwards but we have so many users (>12k configured users, > 3k concurrent registered users, > 500 concurrent users at cps 10), I don't know of any solution that can work with such a large load. With call outbound (from user to PSTN via SBC), everything is fine. But with internal or inbound calls, it wasn't successful. I showed that: - After dSIPRouter, the register message has Path parameter in SIP Header, - Kamailio store sip:user@domain in column contact at location table. - Using modparam registrar with use_path=1, path_mode=0, path_use_received=1, I stored this parameter in DB. - When calling internal or inbound, for the search destination of a phone, I am using sip_trace() function. But the result is always column contact. - With this uri, kamailio wasn't known and sent the invite to proxy. - Final error message: 404. I need one of these solutions: - get path column when result of sip_trace() like sip:user@domain (with phone in internal network, it like sip:user@ipaddress). - write path value to column contact when the register message has it. - sip_trace can get a path instead of contact if it has. Or you can have other solutions, pls help me. We can talk and test via my Webex PMR. Many thanks, Thanh Duy Tran

3 3

set empty custom global variable
by Sergey Safarov 14 Jun '21

14 Jun '21

In Kamailio config I use empty global string variable local.trace_troubleshooting_net = "" descr "trace all SIP messages from given network" When I check variable value I get blank string kamcmd cfg.get local trace_troubleshooting_net I can set new value [root@host]# kamcmd cfg.sets local trace_troubleshooting_net "2600::/48" [root@host]# kamcmd cfg.get local trace_troubleshooting_net 2600::/48 Now I want to set the empty custom global variable using a command kamcmd cfg.sets group trace_troubleshooting_net "" But get error error: 400 - error at parameter 2: expected string type but record doesn't match type How to properly set empty values?

3 4

Kamailio 5.5.0 | CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26
by Laurent Schweizer 11 Jun '21

11 Jun '21

Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it's a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -m 5000 -M 128 -P /run/kamailio/kamailio.pid -f /confi'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (gdb) bt #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x00007f5d209a3a5b in X509_STORE_CTX_get_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x00007f5d209a418d in X509_STORE_CTX_get1_issuer () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #3 0x00007f5d209a9207 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x00007f5d209a9f96 in X509_verify_cert () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x00007f5d20caf337 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #6 0x00007f5d20cd037b in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #7 0x00007f5d20cd2995 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #8 0x00007f5d20ccc48c in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #9 0x00007f5d20cb84e4 in SSL_do_handshake () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #10 0x00007f5d215cbdb1 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #11 0x00007f5d2159f4de in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #12 0x00007f5d21b410b1 in db_mysql_new_connection (id=0x7f5d21ee2b30) at km_my_con.c:157 #13 0x00007f5d211456dc in db_do_init2 (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>, pooling=DB_POOLING_PERMITTED) at db.c:317 #14 0x00007f5d211443f9 in db_do_init (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>) at db.c:270 #15 0x00007f5d21b3459e in db_mysql_init (_url=0x7f5d1e9dd4e0 <ul_db_url>) at km_dbase.c:202 #16 0x00007f5d1e7a1987 in child_init (_rank=-1) at usrloc_mod.c:471 #17 0x000055ddd6c45602 in init_mod_child (m=0x7f5d21e03818, rank=-1) at core/sr_module.c:864 #18 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e03bb8, rank=-1) at core/sr_module.c:860 #19 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e04498, rank=-1) at core/sr_module.c:860 #20 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e056a8, rank=-1) at core/sr_module.c:860 #21 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06390, rank=-1) at core/sr_module.c:860 #22 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06b38, rank=-1) at core/sr_module.c:860 #23 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06fb8, rank=-1) at core/sr_module.c:860 #24 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e075f0, rank=-1) at core/sr_module.c:860 #25 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e090c0, rank=-1) at core/sr_module.c:860 #26 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e09500, rank=-1) at core/sr_module.c:860 #27 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0a400, rank=-1) at core/sr_module.c:860 #28 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0aa70, rank=-1) at core/sr_module.c:860 #29 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b0b0, rank=-1) at core/sr_module.c:860 #30 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b5d8, rank=-1) at core/sr_module.c:860 #31 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0bdd0, rank=-1) at core/sr_module.c:860 #32 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0c968, rank=-1) at core/sr_module.c:860 #33 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0f7f8, rank=-1) at core/sr_module.c:860 #34 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e105d8, rank=-1) at core/sr_module.c:860 #35 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e109b0, rank=-1) at core/sr_module.c:860 #36 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e10ea0, rank=-1) at core/sr_module.c:860 #37 0x000055ddd6c45ef9 in init_child (rank=-1) at core/sr_module.c:909 #38 0x000055ddd6b9eebe in fork_process (child_id=-1, desc=0x55ddd6ee7847 "slow timer", make_sock=1) at core/pt.c:337 #39 0x000055ddd6abaa62 in main_loop () at main.c:1814 #40 0x000055ddd6ac6095 in main (argc=9, argv=0x7ffe6ae5d298) at main.c:3053

1 0

Kamailio SBC+ Freeswitch as media server
by John Tuxies 09 Jun '21

09 Jun '21

in a Debian system i am running Kamailio 5.5 installed from repo and with the basic setup i have 2 users 101 & 102 to be able to call each other. So far so good. i added Freeswitch in the same system and tried to follow this guide http://kb.asipto.com/freeswitch:kamailio-3.1.x-freeswitch-1.0.6d-sbc even though it is old and there are many changes. Freeswitch is installed from deb repo as well. after following the guide i tried to adapt to newer versions of kamailio and freeswitch, but i am getting errors. The problem is that the users now are able to register to Kamailio, but unable to call each other. I can see users being registered in Kamailio: *root@kamfs: ~ $ kamctl online101102root@kamfs: ~ $* while when 101 calls 102 i am getting: *2021-06-08 10:35:19.015670 [NOTICE] switch_channel.c:1118 New Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [f3b8f5a0-652a-4640-b2d3-9b7cc21d7f91]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_NEW (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [INFO] sofia.c:10362 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> receiving invite from 192.168.1.15:5060 <http://192.168.1.15:5060> version: 1.10.6 -release-18-1ff9d0a60e 64bit call-id: ZDFiZWFkZmVmYjgxZDEwOTgyYTYxZjkxNzkwMzlmYmQ.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:10456 verifying acl "domains" for ip/port 192.168.1.15:0 <http://192.168.1.15:0>.2021-06-08 10:35:19.015670 [WARNING] sofia.c:10569 IP 192.168.1.15 Rejected by acl "domains"2021-06-08 10:35:19.015670 [NOTICE] sofia.c:2445 Hangup sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_NEW] [CALL_REJECTED]2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:604 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State NEW2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_HANGUP (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:848 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Callstate Change DOWN -> HANGUP2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:453 Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> hanging up, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:60 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard HANGUP, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:620 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_HANGUP -> CS_REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_REPORTING (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:174 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard REPORTING, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:611 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_REPORTING -> CS_DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_session.c:1736 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Locked, Waiting on external entities2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1754 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Ended2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1758 Close Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_DESTROY]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:739 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_DESTROY (Cur 0 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:364 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> SOFIA DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:181 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY going to sleepfreeswitch@kamfs>* i am attaching the kamailio.cfg file and the whole /etc/freeswitch folder, if someone could help me to solve this issue, please. Kind regards, John

3 2

Any way to force socket used to reach databases ?
by David VILLAUME 08 Jun '21

08 Jun '21

Hello, I’m trying to initiate a redis connection in ndb_redis for topos_redis on a keepalived slave host, but host tries to use the VIP instead of the second socket I defined. Is there a way to influence the ‘database source socket’ so the server can connect with a secondary address even if it does not own the keepalived VIP (tried mhomed options without improvment) ? Regards, David

2 1

List of Header Names
by Evan Verma 07 Jun '21

07 Jun '21

hello! new to working with sip/kamailio. I am currently trying to get a list of all of the header names on the invite the SBC receives. I am having trouble finding a way to do this. Does anyone know of a good solution?

5 4

Problem NOTIFY in Presence module
by hamed r 07 Jun '21

07 Jun '21

hello dears ,i am using presence module and NOTIFY message are working properly. but when i put the database on another server , NOTIFY message will not be sent to subscribers. what is problem?

2 2

List of Header Names
by Evan Verma 05 Jun '21

05 Jun '21

hello! new to working with sip/kamailio. I am currently trying to get a list of all of the header names on the invite the SBC receives. I am having trouble finding a way to do this. Does anyone know of a good solution? -- Evan

2 1

STIR/SHAKEN
by David Villasmil 04 Jun '21

04 Jun '21

Hello guys, So I'm testing secsipid with made up certificates, basically: [image: Untitled.png] The verification _always_ comes back OK, event if I create the Identity with different From numbers, should that fail? Thanks all, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Info: ClueCon Weekly about Kamailio 5.5 series - Jun 4, 2021, 10:00am CT
by Daniel-Constantin Mierla 04 Jun '21

04 Jun '21

Hello, short announcement to let everyone know that next Friday, Jun 4, 2021, at 10:00am CT (17:00 Berlin), I will join ClueCon Weekly to discuss about latest Kamailio 5.5 series. If you have questions about or just want to be part of the discussions, consider to join the live video conference session, more details at: * https://www.cluecon.com/cclive-6-4/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

About Kamailio ass authentication service
by Nael Silega 04 Jun '21

04 Jun '21

hi, i have a question, can i use Kamailio as a authentication service? i´m traing to set up STIR/SHAKEN framework and im looking for a server that work as authentication service

3 2

Questions on http_async_query() in event_route[xhttp:request] and async best practices for Kamailio
by James Aylett 04 Jun '21

04 Jun '21

Hi, I am using Kamailio v5.2 as a WebRTC proxy for SIP clients, as part of my setup I call a REST API before calling ws_handle_handshake() in event_route[xhttp:request] using http_client_query() to authenticate and retrieve some user details (routing etc) for the user connected via WebSockets. This worked fine until increased load on the system meant API responses were slow, this caused a knock-on effect to existing connected users. Specifically, we saw mass WebSocket disconnects for existing connected users - believed to be due to using too aggressive proxy timeout settings on our reverse proxy in front of Kamailio. My understanding is that event_route[xhttp:request] uses the shared SIP TCP worker threads, so potentially could slow API requests over the network block all the handlers? Could this potentially impact the keepalive processes used by the WebSocket module to check existing WebSocket connections? We were using ping keepalives, again with pretty aggressive timers... To resolve this issue, I am looking at whether I can call API requests asynchronously so that TCP workers are not blocked, my first thought was to use http_async_query() in event_route[xhttp:request] and call ws_handle_handshake() in the HTTP_REPLY route when the API call had completed, but I get "ERROR: websocket [ws_handshake.c:143]: ws_handle_handshake(): retrieving connection". I presume then this approach is a deadend, looking at newer kamailio versions 5.5, there doesn't seem to be any way to do this, correct? Instead of using http_async_query() in event_route[xhttp:request], I presume I could set a short timeout in http_client_query(), but my concern is new WebSocket connections could still impact and block existing ones in this case... My other thought was to move my API call out from the event_route[xhttp:request] into my route handler for REGISTER requests, thinking I could offload new register requests to async workers and move the API call there so as to not block existing connections. Does this seem like a reasonable approach to the problem? Given my current script does not use any async workers, how would one go about optimising the number of plain SIP TCP workers to async workers, are there any guides for this? In general, for any potentially blocking "APIs" or calls over the network, is it best practice to offload them into async workers. For example, we run RTPEngine on separate hosts to Kamailio so should I be wrapping rtpengine_offer/answer calls into async workers in case of a slow network? Apologies for the long text, but I would really appreciate any help to understand these problems. Thank you

2 1

Need help analyze crash
by Andrew Chen 03 Jun '21

03 Jun '21

Hi all, Today I upgraded Kamailio to 5.4.5 and a random crash was just reported in our crash monitoring script. Below is the output of the crash: #3 0x00007fa149ebe58d in ?? () from /usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so #4 0x00007fa14989e277 in ERR_clear_error () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x00007fa149933d81 in X509_STORE_set_default_paths () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #6 0x00007fa10310d374 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #7 0x00007fa10310d9f3 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #8 0x00007fa1030e0427 in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #9 0x00007fa10368428c in db_mysql_new_connection () from /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so #10 0x00007fa1501f96dc in db_do_init2 () from /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 #11 0x00007fa1501f83f9 in db_do_init () from /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 #12 0x00007fa103689710 in db_mysql_init () from /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so #13 0x00007fa15062d35f in carrierroute_db_open () from /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so #14 0x00007fa1506719c6 in ?? () from /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so Is this crash due to libcrypto or mysql client? Currently I have the following mysql client installed on the kamailio instance: ii lib*mysql*client20:amd64 5.7.34-0ubuntu0.18.04.1 amd64 MySQL database client library ii *mysql*-client 5.7.34-0ubuntu0.18.04.1 all MySQL database client (metapackage depending on the latest version) ii *mysql*-client-5.7 5.7.34-0ubuntu0.18.04.1 amd64 MySQL database client binaries ii *mysql*-client-core-5.7 5.7.34-0ubuntu0.18.04.1 amd64 MySQL database core client binaries ii *mysql*-common 5.8+1.0.4 all MySQL database common files, e.g. /etc/*mysql*/my.cnf root@ashintgtpsg51:/var/lib/cores # apt-cache madison mysql-client mysql-client | 5.7.34-0ubuntu0.18.04.1 | http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages mysql-client | 5.7.34-0ubuntu0.18.04.1 | http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages mysql-client | 5.7.21-1ubuntu1 | http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ashintgtpsg51:/var/lib/cores # Any suggestions would be greatly appreciated. Thanks in advance. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 10

handle_ruri_alias() and multiple aliases
by Denys Pozniak 02 Jun '21

02 Jun '21

Hello! I need help understanding how the *handle_ruri_alias()* function works. *Call-flow:* Upstream operator -> Kamailio Proxy -> Edpoint. The upstream operator in the initial SIP INVITE in the Contact field sends us an alias parameter, in turn, our Kamailio Proxy adds its own too. The Contact after the Proxy looks something like this: *Contact: <sip:10.0.0.115:5060;alias=10.0.0.115~5060~1;alias=3.3.3.3~5060~1>* When the Endpoint sends us a SIP BYE, then the *handle_ruri_alias()* absorbs not the last alias, but the first one, and this leads to the incorrect formation of a $du. The RURI after the Proxy looks something like this: *Request-Line: BYE sip:10.0.0.115:5060;alias=3.3.3.3~5060~1 SIP/2.0* The first thing that comes to mind is a modification of the original Contact field with storing it's within a dialogue ... Is it possible to elegantly solve this problem? -- BR, Denys Pozniak

4 7

kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg
by Trevor Hemsley 02 Jun '21

02 Jun '21

Hi We've seen a few occurrences of this crash since we implemented kamailio 5.4.5 for our inbound call traffic. Preceding the crash we always get a message in the logs about "dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg" and whenever we see that message, we get the crash. Jun 1 10:12:14 thissystem /usr/sbin/kamailio[20001]: CRITICAL: {2 1 INVITE 6787142-3831531134-1330894187(a)some.telco.domain} dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg 0x7fae153d3cf0 [3973:6059] with clid '82608924-3831089984-1833452161(a)some.telco.domain' and tags '3831089984-684203260' '' The crash happens on line 879 of https://github.com/kamailio/kamailio/blob/master/src/modules/dialog/dlg_db_… SET_STR_VALUE(values+7, cell->bind_addr[DLG_CALLER_LEG]->sock_str); Looking at gdb, I see that cell->bind_addr[DLG_CALLER_LEG] == 0 so trying to use it results in the segfault. I have thought about patching that to check for bind_addr being set and bypassing that line if not but I do not think it's the right fix though it probably would avoid the current crash (and do odd things later instead!). I did check that everything else in that function that uses DLG_CALLER_LEG is set correctly and it appears that it is - or at least if not correctly then they are at least set! The "bogus event 2 in state 5" message is coming out from line 1143 in src/modules/ims_dialog/dlg_hash.c case DLG_EVENT_RPL1xx: switch (dlg->state) { case DLG_STATE_UNCONFIRMED: case DLG_STATE_EARLY: dlg->state = DLG_STATE_EARLY; break; default: log_next_state_dlg(event, dlg); } break; (I didn't really understand why it would set dlg->state = DLG_STATE_EARLY if it's already DLG_STATE_EARLY but...) I have a couple of core dumps of this from the last day or two - usually seems to crash at least once a week on our pair of kamailio inbound servers. If there's any more info I can provide to help fix this properly rather than my proposed bodge then feel free to ask. Trevor Hemsley Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

2 2

UAC module register originating from private interface on server
by Jonathan Hunter 02 Jun '21

02 Jun '21

Hi, I am working with the UAC module and trying to register with providers, and can see that kamailio keeps sending the REGISTER from the private IP address socket on the server (eth0). Is it possible to set the default socket or send socket for the REGISTER message that gets sent out via kamailio? I am running version 4.4.7. I notice SIP OPTIONS are being sent out from the public IP address (eth1) on the server (as I have set socket in dispatcher) and was hoping for same behaviour with uac module. Please can anyone advise? Many thanks Jon Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

2 4

STIR/SHAKEN tests
by David Villasmil 02 Jun '21

02 Jun '21

Hello guys, I want to test secsipid, but i don't yet have the certificate. So i thought i'd create a cert like: openssl req -new -newkey rsa:4096 -nodes -keyout snakeoil.key -out snakeoil.csr openssl x509 -req -sha256 -days 365 -in snakeoil.csr -signkey snakeoil.key -out snakeoil.pem Then i'm simply doing: $var(rc) = secsipid_add_identity("$fU", "$rU", "A", "", " https://somedomain.com/stir/$rd/cert.pem <https://kamailio.org/stir/$rd/cert.pem>", "/etc/kamailio/snakeoil.pem"); if ( $var(rc) ) { xlog("L_ERR", "[STIR/SHAKEN][$ci] Shaken authentication added (SIP Identity Header created)\n"); } else { xlog("L_ERR", "[STIR/SHAKEN][$ci] Failed\n"); } But no matter what i do it silently fails: INVITE d54c2919-39b6-123a-95a7-0e29a5289b8d} <script>: [STIR/SHAKEN][d54c2919-39b6-123a-95a7-0e29a5289b8d] Failed I have debug on 6, but i don't get more info regarding the error. Any ideas? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 11

Possible memory leak?
by George Diamantopoulos 02 Jun '21

02 Jun '21

Hello all, I've been experiencing memory exhaustion (all 8GiB of it) on hosts running kamailio for quite some time now while on the 5.4.x train. I can't really say about previous versions, because the setup was quite different back when I was using those. After about 2 days of operation, RAM is exhausted and kamailio is killed by the kernel OOM which frees up memory again. Restarting kamailio via systemd will also free up most memory. I can't seem to find what is using it up, so I'm guessing there might be a memory leak, but I'm not 100% sure so I thought I'd ask the list for opinions. I'm including the output of kamcmd pkg and shm stats and kamctl stats here. My take on those is that there's nothing to show where all this RAM is going. Kamailio version is 5.4.5+bpo10 on debian buster and is started with '-P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 2048 -M 16' (51 processes total). Thanks! kamctl stats { "jsonrpc": "2.0", "result": [ "core:bad_URIs_rcvd = 6470677", "core:bad_msg_hdr = 25370", "core:drop_replies = 0", "core:drop_requests = 342064", "core:err_replies = 0", "core:err_requests = 0", "core:fwd_replies = 24367", "core:fwd_requests = 375703", "core:rcv_replies = 45021597", "core:rcv_replies_18x = 834856", "core:rcv_replies_1xx = 1505425", "core:rcv_replies_1xx_bye = 17", "core:rcv_replies_1xx_cancel = 7", "core:rcv_replies_1xx_invite = 1497313", "core:rcv_replies_1xx_message = 0", "core:rcv_replies_1xx_prack = 0", "core:rcv_replies_1xx_refer = 0", "core:rcv_replies_1xx_reg = 0", "core:rcv_replies_1xx_update = 0", "core:rcv_replies_2xx = 41764997", "core:rcv_replies_2xx_bye = 328464", "core:rcv_replies_2xx_cancel = 223572", "core:rcv_replies_2xx_invite = 371129", "core:rcv_replies_2xx_message = 190", "core:rcv_replies_2xx_prack = 0", "core:rcv_replies_2xx_refer = 3205", "core:rcv_replies_2xx_reg = 12783948", "core:rcv_replies_2xx_update = 0", "core:rcv_replies_3xx = 1052", "core:rcv_replies_3xx_bye = 0", "core:rcv_replies_3xx_cancel = 0", "core:rcv_replies_3xx_invite = 1052", "core:rcv_replies_3xx_message = 0", "core:rcv_replies_3xx_prack = 0", "core:rcv_replies_3xx_refer = 0", "core:rcv_replies_3xx_reg = 0", "core:rcv_replies_3xx_update = 0", "core:rcv_replies_401 = 17120", "core:rcv_replies_404 = 525917", "core:rcv_replies_407 = 553", "core:rcv_replies_480 = 23138", "core:rcv_replies_486 = 74201", "core:rcv_replies_4xx = 1715492", "core:rcv_replies_4xx_bye = 2146", "core:rcv_replies_4xx_cancel = 594", "core:rcv_replies_4xx_invite = 317850", "core:rcv_replies_4xx_message = 208", "core:rcv_replies_4xx_prack = 0", "core:rcv_replies_4xx_refer = 1", "core:rcv_replies_4xx_reg = 2382", "core:rcv_replies_4xx_update = 0", "core:rcv_replies_5xx = 29462", "core:rcv_replies_5xx_bye = 15", "core:rcv_replies_5xx_cancel = 10", "core:rcv_replies_5xx_invite = 3501", "core:rcv_replies_5xx_message = 0", "core:rcv_replies_5xx_prack = 0", "core:rcv_replies_5xx_refer = 0", "core:rcv_replies_5xx_reg = 25157", "core:rcv_replies_5xx_update = 0", "core:rcv_replies_6xx = 5169", "core:rcv_replies_6xx_bye = 0", "core:rcv_replies_6xx_cancel = 0", "core:rcv_replies_6xx_invite = 5169", "core:rcv_replies_6xx_message = 0", "core:rcv_replies_6xx_prack = 0", "core:rcv_replies_6xx_refer = 0", "core:rcv_replies_6xx_reg = 0", "core:rcv_replies_6xx_update = 0", "core:rcv_requests = 67620661", "core:rcv_requests_ack = 707431", "core:rcv_requests_bye = 336874", "core:rcv_requests_cancel = 226878", "core:rcv_requests_info = 70", "core:rcv_requests_invite = 1038320", "core:rcv_requests_message = 796", "core:rcv_requests_notify = 6027113", "core:rcv_requests_options = 29079952", "core:rcv_requests_prack = 0", "core:rcv_requests_publish = 40344", "core:rcv_requests_refer = 3217", "core:rcv_requests_register = 20919429", "core:rcv_requests_subscribe = 5296608", "core:rcv_requests_update = 0", "core:unsupported_methods = 0", "dialog:active_dialogs = 458", "dialog:early_dialogs = 123", "dialog:expired_dialogs = 105", "dialog:failed_dialogs = 321224", "dialog:processed_dialogs = 645092", "dns:failed_dns_request = 534", "dns:slow_dns_request = 0", "mysql:driver_errors = 18", "shmem:fragments = 8836", "shmem:free_size = 1955034032", "shmem:max_used_size = 250791392", "shmem:real_used_size = 192449616", "shmem:total_size = 2147483648", "shmem:used_size = 105997528", "siptrace:traced_replies = 0", "siptrace:traced_requests = 0", "sl:1xx_replies = 0", "sl:200_replies = 14330540", "sl:202_replies = 0", "sl:2xx_replies = 0", "sl:300_replies = 0", "sl:301_replies = 0", "sl:302_replies = 0", "sl:3xx_replies = 0", "sl:400_replies = 3", "sl:401_replies = 7979168", "sl:403_replies = 14845", "sl:404_replies = 1159237", "sl:407_replies = 2445205", "sl:408_replies = 0", "sl:483_replies = 79336", "sl:4xx_replies = 28", "sl:500_replies = 0", "sl:5xx_replies = 0", "sl:6xx_replies = 0", "sl:failures = 1", "sl:received_ACKs = 342064", "sl:sent_err_replies = 0", "sl:sent_replies = 26008362", "sl:xxx_replies = 0", "sst:expired_sst = 0", "tcp:con_reset = 0", "tcp:con_timeout = 0", "tcp:connect_failed = 0", "tcp:connect_success = 0", "tcp:current_opened_connections = 0", "tcp:current_write_queue_size = 0", "tcp:established = 24562", "tcp:local_reject = 0", "tcp:passive_open = 24562", "tcp:send_timeout = 0", "tcp:sendq_full = 0", "tmx:2xx_transactions = 41122607", "tmx:3xx_transactions = 1049", "tmx:4xx_transactions = 1904640", "tmx:5xx_transactions = 8025", "tmx:6xx_transactions = 5165", "tmx:UAC_transactions = 2602132", "tmx:UAS_transactions = 43036902", "tmx:active_transactions = 145", "tmx:inuse_transactions = 888", "tmx:rpl_absorbed = 1541413", "tmx:rpl_generated = 1111996", "tmx:rpl_received = 44996889", "tmx:rpl_relayed = 43455476", "tmx:rpl_sent = 44567472" ], "id": 15546 } kamcmd mod.stats all pkg Module: core { init_io_wait(469): 8040 init_modules(911): 16 get_hdr_field(116): 464 parse_headers(325): 128 rpc_hash_add(151): 2048 cnt_hash_add(394): 2048 register_select_table(458): 48 sr_wtimer_add(373): 80 add_callback(59): 312 sr_wtimer_init(351): 136 cfg_declare(50): 3168 fix_sock_str(500): 480 fix_hostname(1466): 96 grp_hash_add(241): 728 init_dst_set(89): 32296 cfg_script_fixup(303): 8 cfg_script_fixup(247): 288 cfg_script_fixup(241): 120 new_db_id(318): 304 fix_expr(554): 192 parse_pvname_list(1599): 480 mk_switch_jmp_table(73): 448 fix_param(1140): 672 pv_parse_index(776): 1232 subst_parser(291): 144 subst_parser(274): 64 subst_parser(301): 8 route_new_list(199): 1152 init_io_wait(516): 7256 db_do_init2(299): 280 parse_select(204): 2496 fix_param(1079): 704 mk_match_cond_table(100): 944 mk_name_lst(3754): 72 mk_listen_id(3771): 96 yyparse(2853): 19728 fix_param(1045): 11792 fixup_regexp_null(213): 368 tr_new(1730): 12352 fix_match(490): 384 fixup_pvar_all(279): 14512 mk_rval_expr2(2703): 845408 mk_elem(90): 528 fix_match_rve(3059): 1464 pv_cache_add(349): 63872 mk_rval_expr1(2643): 522656 mk_case_stm(3879): 3432 mk_rval_expr_v(2562): 2513784 mk_action(118): 493240 parse_params2(593): 6496 set_mod_param_regex(145): 1248 set_mod_param_regex(134): 2520 tr_table_add(1959): 360 register_module(253): 39928 register_module(236): 4784 load_module(437): 2624 new_cfg_script_var(134): 88 dupl_string_name(74): 56 dupl_string(49): 184 new_cfg_script_var(126): 104 pv_parse_format(1173): 30744 cfg_new_group(79): 864 new_sock_info(304): 96 new_sock_info(299): 2400 yyparse(659): 352 yyparse(1879): 216 add_alias(103): 256 add_alias(99): 320 yyparse(2388): 408 yyparse(678): 368 sr_push_yy_state(1695): 208 sr_push_yy_state(1634): 584 addstr(1448): 572072 rpc_hash_add(105): 28128 str_hash_alloc(59): 512 pv_table_add(236): 19448 pv_init_buffer(2139): 327680 pv_init_buffer(2129): 320 init_nonsip_hooks(43): 24 rval_get_str(1281): 54920 init_rlist(146): 24 fix_socket_list(1675): 56 route_add(124): 5312 str_hash_alloc(59): 768 mk_rval_expr_v(2575): 3304 pp_define(1827): 1344 init_counters(125): 128 cnt_hash_add(341): 27856 str_hash_alloc(59): 1280 Total: 5708952 } Module: permissions { get_pathname(243): 64 Total: 64 } Module: auth { generate_random_secret(240): 32 generate_random_secret(239): 32 Total: 64 } Module: dialog { dlg_bridge_init_hdrs(66): 80 Total: 80 } Module: acc { parse_acc_extra(116): 6384 Total: 6384 } Module: xlog { mod_init(212): 8200 xdbg_fixup_helper(498): 7736 xlog_fixup_helper(533): 36280 Total: 52216 } Module: dmq { make_socket_str_from_uri(143): 24 Total: 24 } Module: rr { register_rrcb(61): 96 Total: 96 } Module: jsonrpcs { jsonrpc_dgram_mod_init(182): 40 jsonrpc_init_fifo_server(123): 128 jsonrpc_fifo_mod_init(525): 40 Total: 208 } Module: sqlops { sqlops_tr_buffer_init(46): 2048 sql_init_con(83): 480 Total: 2528 } Module: db_mysql { db_mysql_new_connection(78): 3560 db_mysql_new_connection(68): 96 Total: 3656 } Module: phonenum { sr_phonenum_add_item(99): 16 sr_phonenum_add_item(93): 608 pv_parse_phonenum_name(131): 224 Total: 848 } Module: pv { tr_parse_string(2717): 96 tr_parse_uri(2806): 64 tr_parse_string(2639): 336 tr_parse_string(2628): 424 tr_parse_paramlist(2978): 288 tr_parse_paramlist(2906): 192 tr_parse_string(2569): 120 pv_parse_xavp_name(541): 2664 pv_parse_xavp_name(515): 3720 tr_parse_string(2484): 864 tr_parse_string(2473): 904 add_var(58): 4384 tr_parse_string(2519): 2144 tr_parse_string(2509): 5184 add_var(65): 1544 Total: 22928 } Module: textops { tr_txt_parse_re(212): 32 hname_fixup(3528): 1960 fixup_method(3598): 1648 Total: 3640 } Module: tmx { pv_parse_t_var_name(390): 176 Total: 176 } Module: rtpengine { build_rtpp_socks(1801): 24 child_init(1987): 240 Total: 264 } Module: htable { fixup_ht_key(352): 352 pv_parse_ht_name(158): 2240 Total: 2592 } Module: textopsx { fixup_hname_param(593): 320 Total: 320 } Module: avpops { avpops_parse_pvar(57): 64 Total: 64 } Module: ndb_redis { redisc_add_server(348): 216648 Total: 216648 } Module: sl { sl_register_callback(514): 64 Total: 64 } Module: siptrace { mod_init(341): 384 Total: 384 } Module: tm { Total: 0 } Module: kex { Total: 0 } Module: topos { Total: 0 } Module: mtree { Total: 0 } Module: cfgutils { Total: 0 } Module: dispatcher { Total: 0 } Module: outbound { Total: 0 } kamcmd mod.stats all shm Module: core { dns_cache_mk_rd_entry(1110): 1288 counters_prefork_init(212): 65280 cfg_clone_str(130): 136 cfg_shmize(217): 824 main_loop(1341): 8 init_pt(107): 8 init_pt(106): 8 init_pt(105): 7552 build_req_buf_from_sip_req(2218): 791408 xavp_new_value(116): 186472 sip_msg_shm_clone(496): 4101904 msg_lump_cloner(986): 755320 create_avp(175): 145064 register_timer(995): 216 cfg_register_ctx(47): 64 init_tcp(4962): 8192 init_tcp(4956): 32768 init_tcp(4947): 8 init_tcp(4940): 8 init_tcp(4933): 8 init_tcp(4927): 8 init_tcp(4915): 8 init_avps(90): 8 init_avps(89): 8 init_dst_blacklist(438): 16384 init_dst_blacklist(430): 8 timer_alloc(498): 96 init_dns_cache(361): 8 init_dns_cache(352): 16384 init_dns_cache(344): 16 init_dns_cache(336): 8 init_timer(267): 8 init_timer(266): 16384 init_timer(265): 8 init_timer(264): 8 init_timer(253): 8 init_timer(221): 8 init_timer(210): 278544 init_timer(209): 8 init_timer(197): 8 cfg_child_cb_new(829): 64 sr_cfg_init(361): 8 sr_cfg_init(354): 8 sr_cfg_init(347): 8 sr_cfg_init(335): 8 sr_cfg_init(323): 8 ksr_shutdown_phase_init(120): 8 qm_shm_lock_init(1202): 8 Total: 6424576 } Module: permissions { domain_name_table_insert(978): 96 addr_hash_table_insert(458): 2776 subnet_table_insert(670): 336 init_addresses(526): 8 new_domain_name_table(865): 2048 init_addresses(512): 8 new_subnet_table(635): 57456 init_addresses(498): 8 new_addr_hash_table(418): 2048 init_trusted(220): 8 new_hash_table(98): 2048 Total: 66840 } Module: auth { Total: 0 } Module: dialog { dlg_update_cseq(636): 456 dlg_get_iuid_shm_clone(308): 4688 set_dlg_profile(580): 139680 dlg_set_leg_info(553): 64608 dlg_set_leg_info(544): 16296 build_new_dlg(469): 356616 dlg_set_leg_info(536): 29176 new_dlg_var(127): 624976 new_dlg_var(108): 1675696 init_dlg_table(297): 131088 init_dlg_table(289): 8 init_dlg_table(282): 8 init_dlg_table(277): 8 init_dlg_timer(57): 8 init_dlg_timer(48): 32 new_dlg_profile(188): 2272 new_dlg_var(117): 642216 dlg_set_leg_info(562): 18208 init_dlg_callback(55): 32 register_dlgcb(124): 189728 Total: 3895800 } Module: acc { Total: 0 } Module: xlog { Total: 0 } Module: dmq { alloc_job_queue(255): 64 shm_str_dup(802): 280 build_dmq_node(164): 3616 add_peer(68): 168 mod_init(236): 8 mod_init(229): 48 init_dmq_node_list(70): 24 init_peer_list(33): 24 Total: 4232 } Module: rr { Total: 0 } Module: jsonrpcs { Total: 0 } Module: sqlops { Total: 0 } Module: db_mysql { Total: 0 } Module: phonenum { Total: 0 } Module: pv { add_shvar(177): 8 add_shvar(170): 64 lock_set_alloc(66): 80 Total: 152 } Module: textops { Total: 0 } Module: tmx { tmx_check_pretran(271): 6280 tmx_check_pretran(250): 3320 tmx_init_pretran_table(90): 512 Total: 10112 } Module: rtpengine { rtpengine_hash_table_init(111): 14336 rtpengine_hash_table_init(96): 2048 rtpengine_hash_table_init(85): 1024 rtpengine_hash_table_init(76): 2048 rtpengine_hash_table_init(67): 2048 rtpengine_hash_table_init(58): 32 add_rtpengine_socks(978): 96 add_rtpengine_socks(959): 256 get_rtpp_set(873): 8 get_rtpp_set(864): 56 mod_init(1606): 8 mod_init(1599): 24 mod_init(1586): 8 mod_init(1579): 8 mod_init(1565): 16 rtpp_function_call(2657): 1367600 shm_str_dup(802): 2205800 Total: 3595416 } Module: htable { ht_init_tables(394): 2574336 ht_cell_new(186): 68875496 ht_add_table(315): 256 ht_add_table(289): 8424 Total: 71458512 } Module: textopsx { Total: 0 } Module: avpops { Total: 0 } Module: ndb_redis { Total: 0 } Module: sl { init_sl_stats_child(125): 9792 sl_startup(90): 8 init_sl_stats(110): 8 Total: 9808 } Module: siptrace { mod_init(320): 8 Total: 8 } Module: tm { cancel_reason_pack(1224): 104 update_totag_set(321): 656 build_local_reparse(328): 28384 update_totag_set(320): 864 _reply_light(500): 21480 init_tm_stats_child(56): 13056 build_cell(334): 8250680 relay_reply(2064): 439848 build_uac_req(1597): 118672 insert_tmcb(135): 49272 init_tmcb_lists(72): 16 init_tmcb_lists(70): 16 init_hash_table(482): 2097152 tm_rpc_response_list_init(77): 16 Total: 11020216 } Module: kex { pkg_proc_stats_init(79): 2448 Total: 2448 } Module: topos { lock_set_alloc(66): 2064 Total: 2064 } Module: mtree { mt_add_to_tree(229): 2656 mod_init(247): 8 mt_add_to_tree(255): 9559984 mt_add_to_tree(291): 811224 mt_add_to_tree(301): 269848 mt_init_tree(149): 152 mt_init_tree(136): 256 mt_init_tree(125): 176 mt_init_tree(114): 2376 mt_table_spec(840): 8 Total: 10646688 } Module: cfgutils { mod_init(898): 32 mod_init(892): 8 mod_init(884): 8 Total: 48 } Module: dispatcher { mod_init(484): 80 reindex_dests(723): 7680 ds_avl_insert(3621): 11984 ds_set_attrs(301): 960 pack_dest(411): 1456 ds_init_data(262): 16 ds_init_data(254): 16 ds_parse_reply_codes(1112): 808 mod_init(339): 8 mod_init(337): 8 ds_ping_active_init(138): 8 Total: 23024 } Module: outbound { mod_init(99): 24 Total: 24 }

2 1

Kamailio v5.4.5 Released
by Daniel-Constantin Mierla 02 Jun '21

02 Jun '21

Hello, Kamailio SIP Server v5.4.6 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.6. Note that 5.4 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.5, with v5.5.0 being release out of it. For more details about version 5.4.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/06/kamailio-v5-4-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

Releasing Kamailio v5.4.6
by Daniel-Constantin Mierla 02 Jun '21

02 Jun '21

Hello, I am considering to release Kamailio v5.4.6 sometime next week, likely on Wednesday or Thursday (June 2 or 3, 2021). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

IMS IPSec does use UDP socket?
by H Yavari 01 Jun '21

01 Jun '21

Hi to all, I am interested in the implementation of IPsec module. When I run Kamailio, it is creating processes based on the below formulate: UDP children * IPSEC_MAX_CONN * interfaces (v4 and v6) + (TCP+UD) processes for each interface. For example: children = 16tcp_children=16 IPSEC_MAX_CONN = 25and two interface : IPv6 and V4 Kamailio process count = (16 * 25 * 2 ) + 16 + 16 = 832 But why IPsec module is listening to UDP not TCP? this is an internal connection? Thank you. Regards,Hossein

2 2

SDP body, add maxptime attribut
by Victor Velo 01 Jun '21

01 Jun '21

Hello, I would like to add the maxptime attribut to the sdp body. How and where should I do insertion? This kamailio is also using RTPEngine, so is it better to do the insertion using RTPEngine? And the source of the SDP is actually FreeSwitch :), maybe there to tweak? Of course, I don't know either way of doing it so please advise. Thanks, Victor

2 2

New MariaDB server "limiting" Kamailio CPS
by Stephen Lokker 01 Jun '21

01 Jun '21

Good afternoon All, Im hoping for some advise or direction with the below. We are running a Kamailio SBC used for high call volumes and recently decided to upgrade the Database servers as the existing servers were struggling. Both the old and new databases are using MariaDB(version details all below), the problem we face is that since migrating to the new database there appears to a limitation to the amount of DB connections that can be processed or accepted. The SBC functions normally until the CPS starts to exceed around 100cps at which point the SBC stops responding to invites(in bursts which resembles flood prevention). We have checked both the Kamailio logs and the MySQL logs on the DB, both log files have no indication of errors that would cause the problem experienced(the logs attached are seen when the SBC is cut back to use the old DB, not sure they are related to the fault), the connections/processes in mysql do not drastically increase or get stuck either. The fault points to a db connection limit of some kind but all users have no limitations set. If anyone has experienced a similar problem or has any advise it would be greatly appreciated. Some info on the Kamialio and DB versions New DB root@voice-jhb-db01:~# mysql --version mysql Ver 15.1 Distrib 10.3.27-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Old DB [root@isadb01 ~]# mysql --version mysql Ver 15.1 Distrib 10.0.36-MariaDB, for Linux (x86_64) using readline 5.1 Kamailio SBC [root@sbc01 ~]# kamailio -v version: kamailio 5.1.4 (x86_64/linux) Kind regards, Stephen Voice Engineer Tel: 2404 Fax: 3468 Email:

3 3

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