- sr-users - kamailio.org

ims_auth with AKAv1-MD5
by Oleg Belousov 24 Oct '22

24 Oct '22

Hello, I'm wondering if ims_auth is tested with actual SIM-card/AKAv1-MD5 authentication? Bit concerned with that since as per authorize.c source code can see for AUTH_AKAV1_MD5/AUTH_AKAV2_MD5/AUTH_MD5 response is counted in the same way, though algorithms are different. -- obelousov.tel

2 2

No REGISTER sent to third party AS from scscf
by Anthony Blandin 24 Oct '22

24 Oct '22

Hi Community, I am using scscf from Kamailio and I need that scscf sent a REGISTER to a third party AS during the registration phase. When scscf received a new registration, no REGISTER is sent to the AS. SAR-SAA is well processed but only 200 OK is sent for the REGISTER to the pcscf. REGISTER is well sent to the AS only for Re-Registration or De-registration. Do you have any idea to handle this case? Regards Anthony

2 3

Dialog Module: How to get two different dialogues if a call is looped through kamailo (call forwarding scenario)
by Benoit Panizzon 21 Oct '22

21 Oct '22

Hi Using the dialog module to generate CDR for billing. We have this situation: Kamailio 'routing' instance, where dialog is used and billing happens. Kamailio 'register' instance. IC is connected to the routing instance. Customers register to the register instance. Call originates from 'A' via IC through routing instance to register instance and rings customer 'B'. This times out and 'call forwarding' is engaged by sending the call back to the routing instance with a new RURI containing the call forwarding destination 'C'. An appropriate 'no-answer' Diversion Header is added. Now we need two different CDR for this scenario (add more CDR if the call is forwarded multiple times) One from the A to B leg to bill termination fee to the IC carrier. One from B to C to bill the forwarded call with destination 'C' to customer B. The issue I now face is that I only get the kamailio routing instance to generates one dialogue from B to C despite handling two separate connections. How could that challenge be solved? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

relay sip-tls vs sips-tcp
by beer Ll 21 Oct '22

21 Oct '22

Hi everyone, I'm using Kamailio as TLS gateway/filter for an internal Asterisk server the network schema is : UAC (tls) --- INTERNET --- (tls) KAMAILIO (sip udp) --- LAN --- (sip udp) ASTERISK with kamailio in multi-homed mode WAN network interface for sip tls LAN network interface for sip udp to asterisk server UAC address 80.0.0.1 KAMAILIO Wan address 80.0.0.2 KAMAILIO Lan address 172.16.0.2 ASTERISK Lan address 172.16.0.3 SIP-TLS call example If the UAC use tls(sip) all works good [image: sip-ok-small.jpeg] SIPS call example If the same UAC use his default settings tls(sips) , there are problems with ACK and BYE packet [image: sip-ko-small.jpeg] the SIP OK SDP packet from kamailio to UAC is 2022/10/10 09:28:47.854721 80.0.0.2:5061 -> 80.0.0.1:49992 SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.0.1:49992 ;rport=49992;received=80.0.0.1;branch=z9hG4bKM01j360VrBdH5VSV Record-Route: <sip:172.16.0.1:5060 ;lr;r2=on;ftag=F798336AA08EF9FCFA89D3BDFE0C8C8F> Record-Route: <sip:80.0.0.2:5061 ;transport=tls;lr;r2=on;ftag=F798336AA08EF9FCFA89D3BDFE0C8C8F> Call-ID: 1EC2AB679C1EA1BAB60FD03B09F878020B12D3E7 From: <sips:200@pbx.voip.com>;tag=F798336AA08EF9FCFA89D3BDFE0C8C8F To: <sips:*43@pbx.voip.com>;tag=961d0e22-a4f0-453c-9870-6a41578afc96 CSeq: 2 INVITE Contact: <sip:172.16.0.2:5060> P-Asserted-Identity: "xxxxxxxxx" <sips:*43@pbx.voip.com> Content-Type: application/sdp and the UAC send the ACK and BYE from a different tcp port and to: sips:172.16.0.2:5060;transport=tcp 2022/10/10 09:28:48.495365 80.0.0.1:49996 -> 80.0.0.2:5061 ACK sips:172.16.0.2:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TLS 192.168.0.1:49996;branch=z9hG4bKppftdQze20lnwT41;rport Route: <sip:80.0.0.2:5061 ;transport=tls;lr;r2=on;ftag=F798336AA08EF9FCFA89D3BDFE0C8C8F> Route: <sip:172.16.0.1:5060;lr;r2=on;ftag=F798336AA08EF9FCFA89D3BDFE0C8C8F> Max-Forwards: 70 To: <sips:*43@pbx.voip.com>;tag=961d0e22-a4f0-453c-9870-6a41578afc96 From: <sips:200@pbx.voip.com>;tag=F798336AA08EF9FCFA89D3BDFE0C8C8F Call-ID: 1EC2AB679C1EA1BAB60FD03B09F878020B12D3E7 CSeq: 2 ACK kamailio error log WARNING: <core> [core/forward.c:229]: get_send_socket2(): protocol/port mismatch (forced udp:172.16.0.2:5060, to tls:172.16.0.3:5060) How can I solve this ? Best Regards Leo

3 4

After changing instance type for kamailio server in aws log file is corrupted
by Sammy Dominguez 19 Oct '22

19 Oct '22

Hello guys, after changing instance type from t2 to t3a for kamailio server in aws log(/var/log/kamailio.log) file and some other files are corrupted and I can not touch,delete,create or anything and when kamailio start receiving traffic it crashed. Is there any particular reason for this? Basically on t2, they are under /dev/sda1 and /dev/xvda. Under t3 they are nvme disks (biggest part of the speed increase), so they are under /dev/nvme1n1. Note: once I rollback to t2 everything is working as expected.

1 0

Issue with duplicite SIP messages in traffic loop
by Michal Popovič 19 Oct '22

19 Oct '22

Hello, I am trying to configure kamailio to use external antifraud protection using so called "traffic loop" when call is forwarded to external SIP proxy that would response even with same INVITE back or with error message if number is fraud. schema: PBX -> kamailio -> traffic loop -> kamailio -> carrier Kamailio in second and fourth step is the same. Issue is that if kamailio receives same INVITE back to I would like to forward to next carrier it is possible, but kamailio struggles with transaction handling. If ACK message come from PBX, kamailio will correctly forward it to traffic loop but when it comes back, function t_check_trans is failed and I cant relay it. Only workaround is to use send() message, but that causes deny of BYE message from carrier. My question is following: Is it possible to register two different transactions states for same message? If yes how? If no, would it help to send and receive messages on another network port or not? Thank you, Michal

2 1

Recommended openSSL version
by Igor Olhovskiy 19 Oct '22

19 Oct '22

Hello! Due to I still experience irregular Kamailio 5.4 crashes (like 1/month) related to SSL (using websockets and SIPS) I'm wondering, could openSSL upgrade change the situation? As of now in CentOS 7 I have 1.0.2k version. Does anyone have experience to fix crash-related to TLS problems with openSSL upgrade? Or maye some tuneup of TCP parameters can help here?My current setup is quite simple: children=4 enable_tls=yes tcp_accept_no_cl=yes tcp_connection_lifetime=600 tcp_max_connections=998976 # 1000000 - 1024, so we're leaving 1k for system reserve tls_max_connections=998976 Number of clients ~ 200 constantly connected to websocket. -- Best regards, Igor

5 7

IMC module
by Giovanni Iamonte 19 Oct '22

19 Oct '22

HI, I am facing a problem related to the IMC module. I have installed kamailio 5.2.x and I tried to list the members of a room-qsipchat. In my test environment the kamailio.cfg file it is very basic, the kamailio server listen on tcp=192.168.100.192:15006 the client run on a PC with IP address 192.168.100.156 the imc outbound_proxy is set modparam("imc", "db_url", DBURL) modparam("imc", "imc_cmd_start_char", "#") modparam("imc", "outbound_proxy", "sip:sip-test.quintetto.it:15006;transport=tcp") The client start by sending a #join message to kamailio and looking the log file I can see that the room-qsipchat has been create, and also I received the message 200 OK. By using the tcpdump I can see the join message from the Client to kamailio server and the reply from kamailio to the client. When I send the #list message to the room-qsipchat , I expecting to receive the message relate to room's members and the 200 OK message. When I tcp dumping I saw the following messages ******************************************************************** Request from client to list the members - from client to server ******************************************************************** TX 538 bytes Request msg MESSAGE/cseq=57652 (tdta0x77b26460a8) to TCP 192.168.100.192:15006: MESSAGE sip:room-qsipchat@sip-test.quintetto.it SIP/2.0 Via: SIP/2.0/TCP 192.168.100.156:48129;rport;branch=z9hG4bKPjRzgOBgY6vfKZ8Fh8GA4CWheCO840Xzud;alias Max-Forwards: 70 From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f To: <sip:room-qsipchat@sip-test.quintetto.it> Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY CSeq: 57652 MESSAGE Accept: text/plain, application/im-iscomposing+xml Route: <sip:sip-test.quintetto.it:15006;transport=tcp;lr> Content-Type: text/plain Content-Length: 5 #list ******************************************************************** The server ask for the authentication - from server to client ******************************************************************** 2022-10-17 15:45:25.837 4700-10610/it.quintetto.qsipchat D/pjlib(pjsua_1): RX 574 bytes Response msg 407/MESSAGE/cseq=57652 (rdata0x77b3337330) from TCP 192.168.100.192:15006: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TCP 192.168.100.156:48129;rport=48129;branch=z9hG4bKPjRzgOBgY6vfKZ8Fh8GA4CWheCO840Xzud;alias;received=192.168.100.156 From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f To: <sip:room-qsipchat@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.e417 Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY CSeq: 57652 MESSAGE Proxy-Authenticate: Digest realm="sip-test.quintetto.it", nonce="Y01doWNNXHVEyRtiAyN28xJdMjNIG8Ju" Server: kamailio (5.2.8 (x86_64/linux)) Content-Length: 0 ********************************************************************* The client send the authenticated request - from client to server ******************************************************************** TX 755 bytes Request msg MESSAGE/cseq=57653 (tdta0x77b26460a8) to TCP 192.168.100.192:15006: MESSAGE sip:room-qsipchat@sip-test.quintetto.it SIP/2.0 Via: SIP/2.0/TCP 192.168.100.156:48129;rport;branch=z9hG4bKPjj6uuy25r0kKlnICHKQWEaIweOex-sNyq;alias Max-Forwards: 70 From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f To: <sip:room-qsipchat@sip-test.quintetto.it> Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY CSeq: 57653 MESSAGE Accept: text/plain, application/im-iscomposing+xml Route: <sip:sip-test.quintetto.it:15006;transport=tcp;lr> Proxy-Authorization: Digest username="quintetto00", realm="sip-test.quintetto.it", nonce="Y01doWNNXHVEyRtiAyN28xJdMjNIG8Ju", uri="sip:room-qsipchat@sip-test.quintetto.it", response="d495ec20cb1be8f1b605d4e5b1a4c357" Content-Type: text/plain Content-Length: 5 #list ************************************************************************** The server send the 200 OK message - from server to client ******************************************************************** RX 447 bytes Response msg 200/MESSAGE/cseq=57653 (rdata0x77b3337330) from TCP 192.168.100.192:15006: SIP/2.0 200 ok Via: SIP/2.0/TCP 192.168.100.156:48129;rport=48129;branch=z9hG4bKPjj6uuy25r0kKlnICHKQWEaIweOex-sNyq;alias;received=192.168.100.156 From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f To: <sip:room-qsipchat@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.365f Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY CSeq: 57653 MESSAGE Server: kamailio (5.2.8 (x86_64/linux)) Content-Length: 0 ********************************************************************************* Till here everything is OK. But regarding the members when a TCP dumping I saw a message with the room's members that go from the kamailio server to the kamailio server ********************************************************************************* MESSAGE sip:quintetto00@sip-test.quintetto.it SIP/2.0 Via: SIP/2.0/TCP 192.168.100.192:15006;branch=z9hG4bKf20a.be253b92000000000000000000000000.0 To: <sip:quintetto00@sip-test.quintetto.it> From: <sip:room-qsipchat@sip-test.quintetto.it>;tag=03e4c67b0f95c0aeb1f633479b4aa5cd-72f2 CSeq: 10 MESSAGE Call-ID: 37db44aa523ea24a-6567(a)192.168.100.192 Max-Forwards:.70 Content-Length: 47 User-Agent: kamailio (5.2.8 (x86_64/linux)) Content-Type: text/plain Members: *sip:quintetto00@sip-test.quintetto.it ************************************************************************************** a reply from the kamailio server to the kamailio server, with an authenticated request ************************************************************************************** SIP/2.0.407.Proxy Authentication.Required Via: SIP/2.0/TCP 192.168.100.192:15006;branch=z9hG4bKf20a.be253b92000000000000000000000000.0 To: <sip:quintetto00@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.cfc3 From: <sip:room-qsipchat@sip-test.quintetto.it>;tag=03e4c67b0f95c0aeb1f633479b4aa5cd-72f2 CSeq: 10 MESSAGE Call-ID: 37db44aa523ea24a-6567(a)192.168.100.192 Proxy-Authenticate: Digest realm="sip-test.quintetto.it", nonce="Y01fQmNNXhbsHdM1THmENyJn1MH/VD/8" Server: kamailio (5.2.8 (x86_64/linux)) Content-Length:.0 ************************************************************************************** bottom of line the outbound_proxy request for an authenticated request, but kamailio do not reply to this request. Could you please point me in the right direction? Thanks a lot for any help. Bye -- ------------------------------------------------------------------------ Ing. Giovanni Iamonte Developments and technologies area Quintetto Srl Via Monte Navale, 1 10015 - Ivrea (TO)  mobile: +39 393 9196310  tel: +39 0165 1845290  e-mail: giovanni.iamonte(a)quintetto.it  web: www.quintetto.it

2 4

ClueCon and ... FreeSWITCH 1.10.8/RHEL8 packages!
by Richard Chan 18 Oct '22

18 Oct '22

Hi sr-users, Since ClueCon is going on right now, and some Kamailio community members are involved I hope you will forgive a little promo here: I have a RHEL8 build of the just released 1.10.8 on Copr: https://copr.fedorainfracloud.org/coprs/beaveryoga/FreeSWITCH-1.10.8/ Hope you will find it useful in your kamailio + Class 5 scenarios! Cheers Shih-Ping

1 0

Testing dialog module (and acc with dialog cdrs)
by Daniel-Constantin Mierla 18 Oct '22

18 Oct '22

Hello, as I am not a user of dialog variables, I am turning to community to ask for help testing the current master branch with configurations that make use of dialog variables and acc dialog-based cdr generation. With a few reports of issues related to dialog modules and unexpected crashes, I looked over the code and noticed that the access of the value for dialog variables was not protected, making them vulnerable of invalid memory access in case of the variable was updated by another process or dialog was terminated. I introduced a couple of new functions to try to cover different use cases of getting the dlg variable values, dialog management code was not affected, but given that these commits need to be backported to stable branch (5.6), I want to get proper feedback from community that things work fine. A previous attempt of a simpler fix was not enough, having side effects to acc module for dialog-based cdr generation, because it was keeping referenced to many dlg variables at the same time. In short, it would be appreciated any feedback on testing dialog and acc with dialog-based cdr generation using git master branch. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Nov 7-10, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

3 13

kamailio & rtpengine question
by Gerry Kernan 15 Oct '22

15 Oct '22

Hi Looking for advise if anyone could point out where im going wrong. My setup is Kamailio Ver 5.6.0 running in azure , rtpengine Version: git-master-dc395d5, behind kamailio I have asterisk ver 18.12.1 Kamailio conf I have interface set as below listen=udp:10.3.1.6:5060 advertise WANIP:5060 and rtpengine.conf set as below interface = eth0/10.3.1.5 but when I can make a call I don't get any audio, rtpengine.log extract below shows that rtp is going to the private IP rather that the Public IP of the phone that initiated the call, do I need to set rtpengine_manage() to fix this? Oct 7 09:38:58 kamailio-proxy rtpengine[8127]: INFO: [NmE0MjdhMzA4NjUzYWVjMmRjYzIxNGJjMTY4ZTc2MWE. port 30278]: [core] Confirmed peer address as 10.3.1.5:12890 Oct 7 09:38:58 kamailio-proxy rtpengine[8127]: INFO: [NmE0MjdhMzA4NjUzYWVjMmRjYzIxNGJjMTY4ZTc2MWE. port 30278]: [core] Kernelizing media stream: 10.3.1.5:12890 -> 10.3.1.6:30278 | 10.3.1.6:30298 -> 192.168.0.123:40042 Oct 7 09:39:00 kamailio-proxy rtpengine[8127]: INFO: [NmE0MjdhMzA4NjUzYWVjMmRjYzIxNGJjMTY4ZTc2MWE. port 30279]: [core] Confirmed peer address as 10.3.1.5:12891 Kind regards gerry Gerry Kernan | Technical Director Mobile: +353(0)86-170 9790 [Graphical user interface, website Description automatically generated]<https://www.infinityit.ie/> [A picture containing text, clipart Description automatically generated,Icon Description automatically generated]

3 8

tsilo usage more generally
by Alex Balashov 14 Oct '22

14 Oct '22

Since on the topic of tsilo: 1. I watched Federico’s presentation on it from 2015, and his examples insinuate that it is necessary to store the index and label of a suspended transaction in some external vehicle, e.g. htable, for use with ts_append_to(). Why would one do this when it is possible to call ts_append() based on R-URI alone? 2. The appropriate pattern of interaction between tsilo and http_async_client — which I imagine to be a rather common use-case — is rather unclear. If I use http_async_query() to call out to a PN service, with $http_req(suspend) = 1, what should happen to the current instance of SIP request processing? That is to say: request_route { . . . t_check_trans(); if(is_method(“REGISTER”)) { . . . save(“location”, “0x06”); if(ts_append(“location”, “$tu”)) { xlog(“success”); } return; } else if(is_method(“INVITE”)) { # PN stuff. ts_store(“$var(uri)”); http_async_query(“http://url”, “PUSH_REPLY”); return; # <— ??? } } route[HTTP_PUSH_REPLY] { . . . if(!t_relay()) sl_reply_error(); } I should add that this proxy front-ends a registrar, but is not in itself a registrar. It contains a shadow registrar - hence the save() calls - in order to be able to take advantage of the ’tsilo’ module, given its dependency on registrar/usrloc. This leads to the difference that the gateway receives requests with RURIs that have already been resolved to a contact binding elsewhere, so there are no lookup() calls. How should this play into the http_async_client workflow? Appreciate any help! — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

tsilo logging
by Alex Balashov 13 Oct '22

13 Oct '22

Hi, When there are no stored transactions for an AOR, it logs this error: Oct 13 07:48:18 gw1 /usr/sbin/kamailio[14758]: ERROR: tsilo [ts_append.c:64]: ts_append(): failed to retrieve record for sip:abalashov@sip.evaristesys.com But not having transactions ts_store()’d is a rather normal occurrence, right? It is the expected case the vast majority of the time that someone registers. Does that mean one is simply destined to have this scary-looking error, to the syslog ERROR facility, for a normal runtime condition? Is there not some principle against using attention-grabbing error messages this way? Would a patch to fix be welcome? — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

About kamailio + freeswitch issue on Kamailio v5.6
by SparkleZou 12 Oct '22

12 Oct '22

Hi Sir/Mada, I'm trying to integrate kamailio + freeswitch, according to the manual http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc on Kamailio v5.6 modified the kamailio.cfg file, add WITH_FREESWITCH parts, then kamailio could NOT start up. Could you please help check, what should be modified to fit the version 5.6？ Thanks！ BR， Sparkle Zou

4 9

Re: [SR-Users] play_media sounds interrupted
by Stepan Kislyakov 12 Oct '22

12 Oct '22

> The duration of the media playback is returned from the play_media() > command (see `media_duration` modparam). You could use some sort of > timer to invoke media unblocking after media playback ends. Sadly my > Kamailio-Fu isn't strong enough to be able to tell you how to run this > sort of timer. :) > > Cheers Thank you for the hint. I was thinking about timers, but rtimer cannot be triggered in an event route. I used a "timer" module, it could trigger another route from the event route but when a new route is triggered unblock_media() is not aware of the call-id and if i assign call-id to a variable in the event route, that variable is unavailable at new route. Hope that make sense. here is my peace of code: loadmodule "timer.so" modparam("timer", "declare_timer", "PB_TIMER=START,5000"); route[START]{ xlog("current call id at event route is $ci, but call-id avp is $avp(call_id)"); unblock_media("all"); timer_enable("PB_TIMER",0); #we need to disable timer or it will be triggered over and over again } event_route[dialog:start]{ xlog("L_INFO", "dialog started, received 200OK"); #block_media(); play_media("all file=/usr/local/src/myfile.wav"); $avp(call_id)=$ci; timer_enable("PB_TIMER",1); }

1 0

play_media sounds interrupted
by Stepan Kislyakov 11 Oct '22

11 Oct '22

Hi, I'm using latest kamailio 5.6.2 and rtpengine. I need to play announcement to both parties when call is answered by callee. Now I run play_media in event route but when audio start announcement sounds like we have a 50% packet loss. After it is completed there is no problem with audio both sides. I figured out that if i do block_media() my announcement play perfectly but i dont understand how to do unblock_audio() after announcement ends. Appriciate any help! here is my code: event_route[dialog:start]{ xlog("L_INFO", "dialog started, received 200OK"); block_media(); play_media("all file=/usr/local/src/myfile.mp3"); #unblock_media(); } -- Best Regards Stepan Kislovich

2 1

IPSec problem with P-CSCF
by Ali Akbar Hemmati 11 Oct '22

11 Oct '22

Hi everyone, I am using Kamailio as an IMS server. The UE first sends its SIP REGISTER over TCP and gets a 401 in response. Then the UE starts sending its packets over ESP. These ESP packets reach P-CSCF but are not delivered to its process by the kernel. We can see ESP packets in P-CSCF using wireshark. The ports used are correct (both client and server) based on their prior negotiations. We have also checked xfrm policies using the command `ip xfrm policy list` and seems right regarding prior negotiations. Our Linux kernel version is 5.4 and the OS is Ubuntu 20.04. Has anyone any clue of the root cause of this problem? Any ideas are appreciated. Thanks, Aliakbar

2 6

kamcli folder
by Volker Denneberg 11 Oct '22

11 Oct '22

hello, I'm not very familiar with PHP, so this may be a stupid question. I'm following https://github.com/kamailio/kamcli to install kamcli. Now i am at $ pip3 install -r requirements/requirements.txt which i should "run inside kamcli folder". So far, I don't have a kamcli folder, so i assume i have to create it. Any recommendations where ? Thanks in advance, Volker

3 3

detect tcp connection close using tcpops module
by sthustfo 11 Oct '22

11 Oct '22

I am running latest kamailio 5.6.2 and attempting to detect tcp/tls connection being disconnected or closed using tcpops module. As suggested in tcpops documentation at https://www.kamailio.org/docs/modules/devel/modules/tcpops.html, registered event routes as below. event_route[tcp:closed] { xlog("L_INFO", "$proto connection closed ($conid)\n"); } event_route[tcp:timeout] { xlog("L_INFO", "$proto connection timed out ($conid)\n"); } event_route[tcp:reset] { xlog("L_INFO", "$proto connection reset by peer ($conid)\n"); } Now it is observed that the event route is being called but the $conid is not set. The logs show the below log statements and extra data is (nil). 24(4263) DEBUG: <core> [core/tcp_read.c:284]: tcp_read_data(): EOF on connection 0x7ffff2ff8b90 (state: 0, flags: 4018) - FD 7, bytes 0, rd-flags 10000 ([10.8.137.33]:51069 -> [10.8.137.33]:5060)24(4263) DEBUG: <core> [core/tcp_read.c:1500]: tcp_read_req(): EOF 24(4263) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0x555555ab6960, 7, -1, 0x10) fd_no=2 called 24(4263) DEBUG: <core> [core/tcp_read.c:1870]: handle_io(): removing from list 0x7ffff2ff8b90 id 1 fd 7, state 2, flags 4018, main fd 51, refcnt 2 ([10.8.137.33]:51069 -> [10.8.137.33]:5060) 24(4263) DEBUG: <core> [core/tcp_read.c:1653]: release_tcpconn(): releasing con 0x7ffff2ff8b90, state -1, fd=7, id=1 ([10.8.137.33]:51069 -> [10.8.137.33]:5060) 24(4263) DEBUG: <core> [core/tcp_read.c:1657]: release_tcpconn(): extra_data (nil) 32(4271) DEBUG: <core> [core/tcp_main.c:3651]: handle_tcp_child(): reader response= 7ffff2ff8b90, -1 from 0 32(4271) DEBUG: <core> [core/tcp_main.c:3576]: tcp_emit_closed_event(): TCP closed event creation triggered (reason: 0) 32(4271) DEBUG: tcpops [tcpops.c:295]: tcpops_handle_tcp_closed(): received TCP closed event 32(4271) DEBUG: tcpops [tcpops.c:249]: tcpops_tcp_closed_run_route(): event reason id: 0 rt: 1 32(4271) DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 32(4271) DEBUG: <core> [core/parser/msg_parser.c:679]: parse_msg(): SIP Request: 32(4271) DEBUG: <core> [core/parser/msg_parser.c:681]: parse_msg(): method: <OPTIONS> 32(4271) DEBUG: <core> [core/parser/msg_parser.c:683]: parse_msg(): uri: <sip:you@kamailio.org> 32(4271) DEBUG: <core> [core/parser/msg_parser.c:685]: parse_msg(): version: <SIP/2.0> 32(4271) DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Via] type 1 32(4271) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=2 32(4271) DEBUG: <core> [core/parser/msg_parser.c:555]: parse_headers(): Via found, flags=2 32(4271) DEBUG: <core> [core/parser/msg_parser.c:557]: parse_headers(): this is the first via 32(4271) exec: *** cfgtrace:dbg_cfg_trace(): unknown_route=[tcp:closed] c=[/usr/local/etc/kamailio/kamailio.cfg] l=976 a=26 n=xlog32(4271) INFO: <script> tcp connection closed (<null>) Can anyone provide any pointers on what I am missing? Thanks in advance.

2 3

suppress t1 timer retransmissions?
by Brooks Bridges 10 Oct '22

10 Oct '22

So I have a very odd situation that requires me to suppress retransmissions when using t_reply() to send a response back to a UAC that is horribly broken but I'm stuck with for the time being. In the previous iteration of this platform it was fine since I was using a stateless reply, so even though it wasn't "right" it still worked out. I need to replicate this behavior in the event route for http_async_client(), which prevents me from being able to use t_release(). Anyone have any clever ideas? Brooks Bridges 1200 S. Rogers Circle, Unit 6 Boca Raton, FL 33487 Office: 916-235-2097 Main: 888-444-1111 email: bbridges(a)call48.com | web: www.call48.com Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

2 4

cannot register ACC CDR JSON engine when using acc_json module
by Alexis Prodhomme 10 Oct '22

10 Oct '22

Hi everyone, I have some troubles using acc_json module. I can't load it and I don't understand why it fails. The configuration is quite basic: Debian 10 and Kamailio (fails in 5.5 and 5.6) installed using APT repository. Here is parts of my config: loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "dialog.so" loadmodule "acc.so" loadmodule "acc_json.so" modparam("acc_json", "cdr_enable", 1) I also tried with those 4 additionnal settings with no success: modparam("acc_json", "cdr_output_syslog", 1) modparam("acc_json", "cdr_log_facility", "LOG_LOCAL3") modparam("acc_json", "cdr_enable", 1) modparam("acc_json", "cdr_expired_dlg_enable", 1) As soon as I set cdr_enable to 1, it displays the "*cannot register ACC CDR JSON engine*". Here is logs: 0(2488) DEBUG: <core> [core/sr_module.c:969]: init_mod(): acc_json 0(2488) DEBUG: <core> [core/sr_module.c:722]: find_mod_export_record(): found export of <bind_acc> in module acc [/usr/lib/x86_64-linux-gnu/kamailio/modules/acc.so] 0(2488) INFO: acc_json [acc_json_mod.c:159]: mod_init(): janson version : 2.12 0(2488) DEBUG: <core> [core/mem/q_malloc.c:374]: qm_malloc(): qm_malloc(0x7f0a6b154010, 56) called from acc: acc_mod.c: acc_register_engine(725) 0(2488) DEBUG: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7f0a6b154010, 56) returns address 0x7f0a6b220b40 frag. 0x7f0a6b220b08 (size=56) on 1 -th hit 0(2488) DEBUG: acc_json [acc_json_mod.c:269]: acc_json_init(): init ... 0(2488) DEBUG: acc [acc_mod.c:741]: acc_register_engine(): new acc engine registered: json 0(2488) DEBUG: <core> [core/sr_module.c:722]: find_mod_export_record(): found export of <load_dlg> in module dialog [/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so] 0(2488) ERROR: acc_json [acc_json_mod.c:245]: mod_init(): cannot register ACC CDR JSON engine 0(2488) ERROR: <core> [core/sr_module.c:974]: init_mod(): Error while initializing module acc_json (/usr/lib/x86_64-linux-gnu/kamailio/modules/acc_json.so) ERROR: error while initializing modules May it be related to the Jansson version ? I use the native one from Debian 10, v2.12. Do you have any advice, or some tips to debug my issue ? I don't really want to use acc module and parse CDRs manually from syslog, json is far easiest for this job. Thank you -- Alexis R&D Sewan

2 2

Re: [SR-Users] Mails received twice in my Inbox
by Ginhoux, Patrick 10 Oct '22

10 Oct '22

Apparently, the emails are received on the fr unisys dot com address. So maybe there is a need to clean the sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> and sr-users-bounces(a)lists.kamailio.org <mailto:sr-users-bounces@lists.kamailio.org> list. If this is the case, thanks to keep only the fr unisys dot com. Cordialement. Patrick GINHOUX Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginhoux(a)unisys.com De : Henning Westerholt <hw(a)gilawa.com> Envoyé : lundi 10 octobre 2022 09:32 À : Ginhoux, Patrick <patrick.ginhoux(a)fr.unisys.com> Objet : RE: Mails received twice in my Inbox EXTERNAL EMAIL - Be cautious of all links and attachments. Hello, Ive checked last week directly on the list server. Maybe one subscription is old and and does not send mails anymore, and the mails are doubled from your side? Just guessing obviously, have not checked it yet. You should be able to check the email headers to see which address is actually used and maybe some forwarding is done from your side. If you like I can remove one subscription, let me know which one. Cheers, Henning From: Ginhoux, Patrick <patrick.ginhoux(a)fr.unisys.com <mailto:patrick.ginhoux@fr.unisys.com> > Sent: Monday, October 10, 2022 8:39 AM To: Henning Westerholt <hw(a)gilawa.com <mailto:hw@gilawa.com> > Subject: RE: Mails received twice in my Inbox Im back again. After having removed the address with fr unisys dot com, I received these 2 emails on my last one for approval : And later, still 2 copies of each emails : Same for yesterday : Except you see something wrong for the address, Im going to investigate internally. Cordialement. Patrick GINHOUX De : Ginhoux, Patrick Envoyé : jeudi 6 octobre 2022 14:10 À : Henning Westerholt <hw(a)gilawa.com <mailto:hw@gilawa.com> > Cc : Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > Objet : RE: Mails received twice in my Inbox Thanks for the list. I have now removed the one with fr unisys dot com and will wait for new emails on the other address. But it is still strange this problem happened recently. Cordialement. Patrick GINHOUX Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | <mailto:patrick.ginhoux@unisys.com> patrick.ginhoux(a)unisys.com De : Henning Westerholt <hw(a)gilawa.com <mailto:hw@gilawa.com> > Envoyé : jeudi 6 octobre 2022 13:32 À : Ginhoux, Patrick <patrick.ginhoux(a)fr.unisys.com <mailto:patrick.ginhoux@fr.unisys.com> > Cc : Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > Objet : RE: Mails received twice in my Inbox EXTERNAL EMAIL - Be cautious of all links and attachments. Hello, you are subscribed with two addresses, only list the domains below: at fr unisys dot com at unisys dot com You can change your subscription with the URL: <https://lists.kamailio.org> https://lists.kamailio.org Cheers, Henning From: Ginhoux, Patrick < <mailto:patrick.ginhoux@fr.unisys.com> patrick.ginhoux(a)fr.unisys.com> Sent: Thursday, October 6, 2022 1:25 PM To: Henning Westerholt < <mailto:hw@gilawa.com> hw(a)gilawa.com> Cc: Kamailio (SER) - Users Mailing List < <mailto:sr-users@lists.kamailio.org> sr-users(a)lists.kamailio.org> Subject: RE: Mails received twice in my Inbox Hi, Im sure Im not registered with different account, but who can check that in the mailing list to be sure ? Actually, I registered in 2017 and this issue occurs recently but I cant tell exactly since when. Cordialement. Patrick GINHOUX Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | <mailto:patrick.ginhoux@unisys.com> patrick.ginhoux(a)unisys.com De : Henning Westerholt <hw(a)gilawa.com <mailto:hw@gilawa.com> > Envoyé : jeudi 6 octobre 2022 11:06 À : Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > Cc : Ginhoux, Patrick <patrick.ginhoux(a)fr.unisys.com <mailto:patrick.ginhoux@fr.unisys.com> > Objet : RE: Mails received twice in my Inbox EXTERNAL EMAIL - Be cautious of all links and attachments. Hello, Strange issue. Stupid question, but you are not registered two times to the mailing list, maybe with different accounts? Cheers, Henning -- Henning Westerholt <https://skalatan.de/blog/> https://skalatan.de/blog/ Kamailio services <https://gilawa.com/> https://gilawa.com From: sr-users < <mailto:sr-users-bounces@lists.kamailio.org> sr-users-bounces(a)lists.kamailio.org> On Behalf Of Ginhoux, Patrick Sent: Wednesday, October 5, 2022 10:04 AM To: <mailto:sr-users@lists.kamailio.org> sr-users(a)lists.kamailio.org Subject: [SR-Users] Mails received twice in my Inbox Hi, Since several weeks, I received the same mails twice in my Inbox. Examples : Is there anybody else that has the same thing ? Thanks in advance for your help. Cordialement. Patrick GINHOUX

1 0

Kamailio IMS supports Early IMS Authentication
by PAUL SUN 10 Oct '22

10 Oct '22

Hello I have a question on using Kamailio IMS, does it support Early IMS Authentication?, Thanks RBK

1 0

Kamailio v5.6.2 Released
by Daniel-Constantin Mierla 09 Oct '22

09 Oct '22

Hello, Kamailio SIP Server v5.6.2 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.2. For more details about version 5.6.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2022/10/kamailio-v5-6-2-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

4 6

I am having an error with Kamailio
by Michael Osude 07 Oct '22

07 Oct '22

Please see my output and see if you can help me resolve the error ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/usr/lib/systemd/system/kamailio.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2022-10-06 23:42:33 CDT; 10min ago Process: 9931 ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=255) Main PID: 9931 (code=exited, status=255) Oct 06 23:42:32 s181866.wholesaleinternet.net systemd[1]: Unit kamailio.service entered failed state. Oct 06 23:42:32 s181866.wholesaleinternet.net systemd[1]: kamailio.service failed. Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: kamailio.service holdoff time over, scheduling restart. Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: start request repeated too quickly for kamailio.service Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: Unit kamailio.service entered failed state. Oct 06 23:42:33 s181866.wholesaleinternet.net systemd[1]: kamailio.service failed. Thank you

2 1

Kamailio Developers Meeting, Nov 16-17, 2022, in Dusseldorf
by Daniel-Constantin Mierla 07 Oct '22

07 Oct '22

Hello, Kamailio SIP Server project is organizing another meeting of its developers during November 16-17, 2022, hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join. Please note we have a limited capacity of seats in the meeting room, the main policy for accepting participants being first come first server. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Oct 10-13, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

Mails received twice in my Inbox
by Ginhoux, Patrick 06 Oct '22

06 Oct '22

Hi, Since several weeks, I received the same mails twice in my Inbox. Examples : Is there anybody else that has the same thing ? Thanks in advance for your help. Cordialement. Patrick GINHOUX

2 4

How to use different version of python3 with KEMI
by Lợi Đặng 06 Oct '22

06 Oct '22

Hi all, regarding KEMI with python3, how to specify the python instance we're going to use instead of the system's? i.e: virtual environment or alternative installation of python3. Asking as I'm having existing code running on a version which does not match the system's, and upgrading system's to the specific version is not feasible. I tried specifying the python3 instance in src/modules/app_python3/Makefile but it seems only to help with the build, later the system python is used when kamailio starts. Any help would be appreciated. rgds, Loi Dang Thanh Phone : +84. 774.735.448 Email : loi.dangthanh(a)gmail.com

2 2

Releasing v5.6.2
by Daniel-Constantin Mierla 06 Oct '22

06 Oct '22

Hello, I am considering to release Kamailio v5.6.2 (out of branch 5.6) later this week (likely on Thursday, Nov 6, 2022). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better 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 Nov 7-10, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

xhttp - default reply
by Ilie Soltanici 05 Oct '22

05 Oct '22

Hello, Is there a way to set a default reply message for the xhttp module, or at least drop the TCP connection when 'url_match' parameter is used? For example, if used: modparam("xhttp", "url_match", "^/rpc/") which should handle only HTTP requests to this endpoint: http://127.0.0.1:5060/rpc, now if HTTP requests are sent to another endpoint (http://127.0.0.1:5060/v2) - then the TCP connection just stays established even nobody process it. I know I can ignore this parameter and filter all requests in the event_route, but dropping them before calling event_route will make more sense for me, or at least add another parameter to this module that can control that. Thanks

2 1

Error in RTP engine setup
by palany 04 Oct '22

04 Oct '22

I have installed RTPENGINE on debian 11 and on starting it I am getting the following errors. Oct 04 12:14:39 ip-172-31-26-106 systemd[1]: Starting NGCP RTP/media Proxy Daemon... Oct 04 12:14:39 ip-172-31-26-106 ngcp-rtpengine-iptables-setup[4655]: /usr/sbin/ngcp-rtpengine-iptables-setup: 15: /usr/libexec/rtpengine/rtpengine-get-table: not found Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [crypto] Generating new DTLS certificate Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: ERR: [core] FAILED TO CREATE KERNEL TABLE 0 (No such file or directory), KERNEL FORWARDING DISABLED Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [core] Startup complete, version 11.1.0.0+0~mr11.1.0.0 git-master-c53f213f Oct 04 12:14:39 ip-172-31-26-106 systemd[1]: Started NGCP RTP/media Proxy Daemon. Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [http] Websocket listener thread running How do I solve this. Best Regards, Palany Chakadya

3 6

Kamailio Fail to write logs using syslog
by M Arqum CH 02 Oct '22

02 Oct '22

Dear All, Thanks in advance for your help. kamailio installed on debain 9, sometime kamailio failed to generate any log in syslog files i.e messages/ syslog , not even generate a single line against complete dialog or generate partial logs. It's a random behaviour, as i am using syslog with the acc module, kamailio also failed to write acc logs on file which is a very critical matter for me. In a script using xinfo, xnotice, xerr function, no output from these functions in log file. Please suggest a way to fix this issue. modparam("xlog", "log_facility", "LOG_LOCAL1") version: kamailio 5.5.4 (x86_64/linux) 9d039b 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: 9d039b -- Regards M Arqum

1 0

loose_route() clarification
by Mack Hendricks 30 Sep '22

30 Sep '22

Hey All, I always struggle with loose_route() and I implemented workarounds in the past. But, I want to get a better understanding. I have a SIP Endpoint -> Kamailio -> FreeSWITCH The domain and alias is set to the ip address of the Kamailio server (137.184.130.206) When I get the ACK back from the SIP Endpoint it looks like this ACK sip:18889072085@137.184.72.42:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 10.1.10.140:1052 ;branch=z9hG4bK-524287-1---740db0025fa217ce;rport Max-Forwards: 70 *Route: <sip:137.184.130.206;lr>* Contact: <sip:1000@50.192.97.226:53790;transport=UDP> To: <sip:18889072085@dsiptest.dsiprouter.net>;tag=5gv4etZ8tUUcH From: <sip:1000@dsiptest.dsiprouter.net;transport=UDP>;tag=0af5b751 Call-ID: fWido7VIUKIEI6f6kf4vkQ.. CSeq: 1 ACK User-Agent: Z 5.5.8 v2.10.17.2 Content-Length: 0 Kamailio will then remove the ACK and change the RURI to itself, which causes an ACK loop. This is what is look like *ACK sip:137.184.130.206;lr* SIP/2.0 Via: SIP/2.0/UDP 137.184.130.206;branch=z9hG4bK3fd.0cf34b683f0627ee2455594ea6cb2517.0 Via: SIP/2.0/UDP 10.1.10.140:1052 ;received=50.192.97.226;branch=z9hG4bK-524287-1---740db0025fa217ce;rport=1052 Max-Forwards: 69 Contact: <sip:1000@50.192.97.226:1052;transport=UDP> To: <sip:18889072085@dsiptest.dsiprouter.net>;tag=5gv4etZ8tUUcH From: <sip:1000@dsiptest.dsiprouter.net;transport=UDP>;tag=0af5b751 Call-ID: fWido7VIUKIEI6f6kf4vkQ.. CSeq: 1 ACK User-Agent: Z 5.5.8 v2.10.17.2 Content-Length: 0 *Question:* What am I missing here? We have the alias set and we even set it in the domain module (with the register_myself flag). We have workarounds for this, but I would prefer to figure out how to have Kamailio handle this natively via the loose_route or tm module. Thanks in advance,

3 2

Keepalive dialog with SIP/TLS OPTIONS
by Denys Pozniak 30 Sep '22

30 Sep '22

Hello! In order to keep the SIP/TCP connection alive for some specific clients (more precisely, specific firewalls) in long calls, I use periodic SIP OPTIONS probes through the dialog module. I noticed that when subscribers are using the SIP/TLS protocol, such keepalives are not sent (with SIP/UDP and SIP/TCP working well). I did not detect any obvious errors in the debug mode. Are there any ideas why the messages are not being sent for SIP/TLS leg? ---- loadmodule "dialog.so" modparam("dialog", "db_url", "DBURL") modparam("dialog", "db_mode", 1) modparam("dialog", "ka_timer", 5) modparam("dialog", "ka_interval", 30) modparam("dialog", "ka_failed_limit", 2) modparam("dialog", "send_bye", 1) modparam("dialog", "track_cseq_updates", 1) modparam("dialog", "default_timeout", 7205) ----- dlg_manage(); dlg_set_property("ka-src"); dlg_set_property("ka-dst"); -- BR, Denys Pozniak

3 3

Kamailio stops responding to OPTIONS for some time
by Muhammad Danish Moosa 30 Sep '22

30 Sep '22

Hi, With Kamailio 5.5.3 (with KEMI/Lua) I noticed it apparently had stopped responding to OPTIONS in my test system. It can cause problems if a similar issue appears in production. Only thing i could observe it was apparently responding to INVITE and CANCEL etc randomly , its pretty strange as it was not dead completely. There was no core dump, I restarted and it started functioning again. Any clues please? -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

2 1

http_async_client "route_name" is what type of route?
by Brooks Bridges 30 Sep '22

30 Sep '22

Running into an issue where I can't access certain functions inside the response route or "route_name" for handling the asynchronous reply from an http_async_query() that's being run. Does anyone know what type of route that is considered to be? I know it's not a request route or a failure route based on the errors I'm getting, but I can't find anything that outlines what that route actually is. Thanks! Brooks Bridges 1200 S. Rogers Circle, Unit 6 Boca Raton, FL 33487 Office: 916-235-2097 Main: 888-444-1111 email: bbridges(a)call48.com | web: www.call48.com Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

3 7

Interactions of dmq_usrloc and usrloc w/db_mode > 0
by Alex Balashov 29 Sep '22

29 Sep '22

Hi, Are there any known contraindications for replicating contacts using dmq/dmq_usrloc, and injecting those contacts into a database on one of the nodes using usrloc with `db_mode` 1 or 2? Predictably, this is being done to support the use-case of getting registration status from database. If you think this should be done with JSONRPC, I am in complete agreement with you, but it’s not up to me. :-) I am doing this with `db_mode` 2 now, and finding that, for a small number of AORs, one can find instances where they are consistently stored in memory but not present in the `location` table. The overall proportion of these AORs, out of thousands, seems to be quite small. It was initially somewhat higher, and it went down once I increased usrloc `timer_processes` and increased the sync interval from 30 to 60 seconds. Nevertheless, it is still non-zero, and I am getting intermittent reports. I wonder if there are some prior experiences with this and anything to watch out, or if `db_mode` 1 might be a superior choice. I personally cannot see how that would be; it seems to have all the performance downsides of mode 3. But perhaps if something about it is more “problem-free” vis-a-vis DMQ, it’s worth a shot? — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

5 7

New feature: #defexp -preprocessor define with expression
by Daniel-Constantin Mierla 29 Sep '22

29 Sep '22

Hello, following the recent new feature of #!ifexp based on snexpr (https://www.kamailio.org/w/2022/09/ifexp-conditional-preprocessor-blocks/), another preprocessor directive was added which allows defining IDs with a value computed from the evaluation of an expression, respectively: #!defexp ID EXP The EXP can be any expression supported by snexpr, including the previously defined IDs. For example: #!define IPADDR 1.2.3.4 #!define PORT 5060 #!defexp SIPURI "sip:" + IPADDR + ":" + PORT The result is that SIPURI is defined to sip:1.2.3.4:5060. Another variant is available as #!defexps, which encloses the result of the expression in double quotes, making it suitable to be used further as string value: #!defexps SIPURI "sip:" + IPADDR + ":" + PORT The result is that SIPURI is defined to “sip:1.2.3.4:5060”. More details at: - https://www.kamailio.org/wikidocs/cookbooks/devel/core/#defexp - https://www.kamailio.org/wikidocs/cookbooks/devel/core/#defexps Testing would be appreciated, feedback can be addressed to sr-users mailing list! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Nov 7-10, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

Question about the Secsipid module
by Володимир Іванець 28 Sep '22

28 Sep '22

Hello everyone! I'm testing calls with STIR/SHAKEN with a Secsipid module on a Kamailio version 5.6.1 and ran into a problem. Outbound calls work fine when the function *secsipid_add_identity* with appropriate parameters is called. But as soon as I add function *secsipid_check_identity* to my configuration, Kamilio would not start. Here is an error message I get: *kamailio: CRITICAL: <core> [core/cfg.y:3791]: yyerror_at(): parse error in config file /etc/kamailio/include/registrar.cfg, line 47, column 39: unknown command, missing loadmodule?* *loadmodule "secsipid.so"* is present and is above the function *secsipid_check_identity* call. Both secsipid.so and secsipid_proc.so module files are the correct version and present on the system. Another question is related to the rpm package build. How do you build additional modules? I made adjustment to the pkg/kamailio/Makefile file. In the *cfg* section changed *$(MAKE) -C ../../src cfg* with *$(MAKE) FLAVOUR=kamailio include_modules="secsipid secsipid_proc" -C ../../src cfg*. Required modules appeared in the modules.lst file but their rpm packages were not built. Thank you very much!

2 8

Failed to create a TLS connection when a 'loose' tls_method is configured
by Leonid Fainshtein 28 Sep '22

28 Sep '22

Hi, I have a problem creating a TLS connection when tls_method is configured as one of the "loose" methods: SSLv23, TLSv1+, TLSv1.1+, TLSv1.2+. The problem doesn't happen when the tls_method is defined "strictly": TLSv1, TLSv1.1, or TLSv1.2. The problem is reproducible with the modern Yealink phones and also with sipexer. I have Kamailio v.5.5.4 installed from the Kamailio repo ( http://deb.kamailio.org/kamailio55), on Ubuntu 18.04, OpenSSL ver.1.1.1-1ubuntu2.1~18.04.20 The sipexer output: -------------------------- $ ./sipexer -register -vl 3 -co -com -ex 60 -fuser 2001 -cb -au 2001 -ap "......" -sd -sw 20000 -tk ./id_rsa tls:nnnnnnnnn.com:5061 [debug] [sipexer.go:912] main.main(): parsed socket address argument ({Val:tls:nnnnnnnnn.com:5061 Proto:tls Addr:nnnnnnnnn.com Port:5061 PortNo:5061 AType:8 ProtoId:3}) [debug] [sipexer.go:1800] main.SIPExerSendTLS(): client: 192.168.0.178:41586 connected to: 142.93.233.32:5061 [debug] [sipexer.go:1803] main.SIPExerSendTLS(): [48 130 1 34 48 13 6 9 42 134 72 134 247 13 1 1 1 5 0 3 130 1 15 0 48 130 1 10 2 130 1 1 0 222 21 229 237 77 230 193 157 183 132 186 194 65 98 162 250 243 232 189 223 115 181 41 199 130 221 201 143 254 218 254 201 82 173 233 44 158 103 150 78 210 162 187 138 5 179 11 47 208 0 117 27 186 180 197 229 94 13 63 72 227 27 169 127 197 173 67 52 182 68 140 220 132 20 241 57 24 182 29 234 58 60 214 145 225 29 251 240 190 159 43 233 53 57 121 159 81 4 200 12 193 90 91 158 78 196 25 202 74 111 106 215 164 12 178 120 129 8 81 1 245 181 149 20 47 197 165 74 126 24 249 241 187 197 249 209 192 11 204 254 110 19 248 79 122 11 131 24 101 155 237 110 186 5 214 88 79 255 185 156 52 12 29 222 254 76 71 171 142 28 69 22 34 31 111 105 87 7 108 68 6 23 199 236 134 154 42 208 199 158 190 48 193 192 179 120 189 199 117 71 104 231 127 73 128 91 234 168 175 207 55 6 191 144 209 25 10 182 27 53 182 182 96 248 198 206 220 207 102 236 194 96 67 159 34 112 81 145 2 166 207 86 247 232 117 126 158 214 215 10 226 68 81 235 169 81 2 3 1 0 1] <nil> [debug] [sipexer.go:1804] main.SIPExerSendTLS(): CN=nnnnnnnnn.com [debug] [sipexer.go:1803] main.SIPExerSendTLS(): [48 130 2 34....247 31 2 3 1 0 1] <nil> [debug] [sipexer.go:1804] main.SIPExerSendTLS(): CN=ZeroSSL RSA Domain Secure Site CA,O=ZeroSSL,C=AT [debug] [sipexer.go:1803] main.SIPExerSendTLS(): [48 130 2 34 48 ....130 15 2 3 1 0 1] <nil> [debug] [sipexer.go:1804] main.SIPExerSendTLS(): CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US [debug] [sipexer.go:1806] main.SIPExerSendTLS(): client: handshake: true [debug] [sipexer.go:1807] main.SIPExerSendTLS(): client: mutual: true [info] [sipexer.go:1432] main.SIPExerDialogLoop(): local socket address: 192.168.0.178:41586 (tls) [info] [sipexer.go:1433] main.SIPExerDialogLoop(): local via address: 192.168.0.178:41586 [info] [sipexer.go:1434] main.SIPExerDialogLoop(): sending to tls 142.xx.yy.32:5061: [[--- REGISTER sip:nnnnnnnnn.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.178:41586 ;rport;branch=z9hG4bKSG.f7a247eb-5440-4e7a-8a5a-4f849684f30d From: <sip:2001@nnnnnnnnn.com>;tag=33e66091-193c-4535-b659-d5e562aca5a4 To: <sip:2001@nnnnnnnnn.com> Call-ID: 4556156d-e8da-4632-82f7-f3ab3c4c73a1 CSeq: 621470 REGISTER Date: Sun, 04 Sep 2022 11:21:33 IDT Contact: <sip:192.168.0.178:41586;transport=tls> Expires: 60 User-Agent: SIPExer v1.0.2 Content-Length: 0 [info] [sipexer.go:1436] main.SIPExerDialogLoop(): ---]] [error] [sipexer.go:1312] main.SIPExerDialogReadBytes(): not receiving after 32000ms (bytes 0 - EOF) [debug] [sipexer.go:1009] main.SIPExerExit(): return code: -1154 The Kamailio debug log: --------------------------------- Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/ip_addr.c:577]: print_ip(): tcpconn_new: new tcp connection: 207.232.46.53 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/tcp_main.c:1175]: tcpconn_new(): on port 18566, type 3, socket 72 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/tcp_main.c:1507]: tcpconn_add(): hashes: 1963:2250:2856, 16 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x5648d2a55e40, 72, 2, 0x7f9dcaf01958) - fd_no=63 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0x5648d2a55e40, 72, -1, 0x0) fd_no=64 called Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/tcp_main.c:4471]: handle_tcpconn_ev(): sending to child, events 1 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/tcp_main.c:4141]: send2child(): selected tcp worker idx:7 proc:45 pid:25549 for activity on [tls:142.xx.yy.32:5061], 0x7f9dcaf01958 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7f9dcaf01958, fd=10 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:244]: tls_complete_init(): completing tls connection initialization Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:274]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7f9dc4c17078 ctx 0x7f9dc4c65da0 sn []) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f9dc4c65da0: (nil) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:778]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:979]: tls_server_name_cb(): received server_name (TLS extension): 'tmx.cpbxmt-demo187.xorcom.com' Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:998]: tls_server_name_cb(): TLS cfg domain selected for received server name [tmx.cpbxmt-demo187.xorcom.com]: socket [:0] server name='' - switching SSL CTX to 0x7f9dc4c65da0 dom 0x7f9dc4c17078 (default) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_main.c:2720]: tcpconn_do_send(): sending... Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_main.c:2753]: tcpconn_do_send(): after real write: c= 0x7f9dcaf01958 n=5435 fd=10 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_main.c:2754]: tcpconn_do_send(): buf= Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: #026#003#003 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x5648d29e8c80, 10, 2, 0x7f9dcaf01958) - fd_no=1 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f9dc4c65da0: (nil) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:778]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:782]: sr_ssl_ctx_info_callback(): SSL renegotiation initiated by client Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:778]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:782]: sr_ssl_ctx_info_callback(): SSL renegotiation initiated by client Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:470]: tls_accept(): TLS accept successful Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:477]: tls_accept(): tls_accept: new connection from 207.232.46.53:18566 using TLSv1.3 TLS_AES_256_GCM_SHA384 256 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:480]: tls_accept(): tls_accept: local socket: 142.xx.yy.32:5061 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:491]: tls_accept(): tls_accept: client did not present a certificate Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: tls [tls_server.c:1245]: tls_h_read_f(): Reading on a renegotiation of connection (n:-1) (2) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_read.c:1503]: tcp_read_req(): EOF Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0x5648d29e8c80, 10, -1, 0x10) fd_no=2 called Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_read.c:1872]: handle_io(): removing from list 0x7f9dcaf01958 id 16 fd 10, state 2, flags 4018, main fd 72, refcnt 2 ([207.232.46.53]:18566 -> [207.232.46.53]:5061) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_read.c:1656]: release_tcpconn(): releasing con 0x7f9dcaf01958, state -1, fd=10, id=16 ([207.232.46.53]:18566 -> [207.232.46.53]:5061) Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 45(25549) DEBUG: <core> [core/tcp_read.c:1660]: release_tcpconn(): extra_data 0x7f9dcaefe628 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: <core> [core/tcp_main.c:3573]: handle_tcp_child(): reader response= 7f9dcaf01958, -1 from 7 Sep 4 08:21:33 cpbxmt-demo187 kamailio[23878]: 46(25550) DEBUG: tls [tls_server.c:729]: tls_h_tcpconn_close_f(): Closing SSL connection 0x7f9dcaefe628 As far as I understood the log, the certificate was accepted but something wrong happened later. Any suggestion? Best regards, Leonid Fainshtein

2 3

No CDR is written on failover
by Björn Klasen 28 Sep '22

28 Sep '22

Hi Community, I'm experimenting with dmq to do dialog sync between two instances of Kamailio. This works great so far. When I did my first experiments I even could create a CDR when there was a failover. Since some Versions (we are now on Version 5.6.1) I just get a acc-request in log but no acc-cdr. In former versions this worked. Both server have the same configuration and both server writes cdrs when theres no failover. In case of a failover everything is fine, the dialogs are clean and thanks to dmq all needed variables are replicated between the server. There's just no cdr. I found nothing on the issue-page on github but maybe somebody knows something about it. BR Björn -- Björn Klasen, Senior Specialist (VoIP) TNG Stadtnetz GmbH, TNG-Technik Projensdorfer Str. 324 24106 Kiel・Deutschland T +49 431 7097-10 F +49 431 7097-555 bklasen(a)tng.de www.tng.de <http://www.tng.de> Executive board (Geschäftsführer): Dr. Sven Willert (CEO/Vorsitz), Helmut Gertz, Moritz Meis, Gunnar Peter, Sven Schade, Carsten Tolkmit Amtsgericht Kiel HRB 6002 KI USt-ID: DE225201428 Die Information über die Verarbeitung Ihrer Daten gemäß Artikel 12 DSGVO können Siehier <https://tng.de/privatkunden/datenschutz/>abrufen.

2 2

Kamailio + RTPEngine SIP Proxy...
by David Walsh 24 Sep '22

24 Sep '22

Hi Jerry, I just joined so am unsure if you are good to go now but thought I would post my config as I also have a Freeswitch environment which I have placed Kamailio in front of to act as a load-balancing proxy. I also managed to get RTPEngine proxying through it too. Here is the config, which I have created from Daniel’s default kamailio config. I have omitted the top portions of loading the modules and their settings. My dispatcher list is just a text file. I have two groups. One for registrations and outbound calls, and one for calls inbound coming from the FreeSwitch server. In the NATMANAGE route, I currently have RTP proxying disabled as my free switch servers have external IPs and I let them handle the rtp stream. On Freeswitch, I made the following changes to accomodate user/pass and IPAuth reg: Changes to the Freeswitch servers listed in the dispatcher file Edit /usr/local/freeswitch/conf/autoload_configs/acl.conf <list name="proxy" default="deny"> <node type="allow" cidr=“IP address of Kamailio/32"/> </list> Edit /usr/local/freeswitch/conf/sip-profiles/internal-private.xml (or the sip-profile you need to edit in your instance) <param name="apply-proxy-acl" value="proxy"/> #Add this line above the one below. This tells Freeswitch to look at the X-Auth-IP header which was inserted by Kamailio. <param name="apply-inbound-acl" value="domains"/> Then, restart freeswitch (with no active calls), service freeswitch restart # or rescan the profile / reloadxml I am not proxying RTP, however, I can un-comment out the stanza in the NATMANAGE route to get it to work. The biggest gotcha for me was I was trying to use fix_nated_register when handling NAT for registrations instead of: Fix_nated_contact() or the better set_contact_alias(). Using add_path_received(); in the Dispatcher just before sending to Freeswitch ensured all traffic returned to Kamailio too. I am unsure of the SUBSCRIBE/PRESENCE stuff for you but the route should go out via the Kamailio proxy with this. ---------------------------- # main request routing logic request_route { xlog("L_WARN", "--- Going to <$ru>. src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si\n"); # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); if(ds_is_from_list("33")) { setflag(FLT_FS); #xlog("L_WARN", "This source $si is from the dispatcher list.\n"); } # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle retransmissions if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); } # handle requests within SIP dialogs route(WITHINDLG); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) { xlog("L_WARN", "--- Going to <$ru>. src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si\n"); xlog("L_ALERT", "Marker 1\n"); record_route(); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } if (isflagset(FLT_FS)) { ##t_on_reply("EXTERNAL_REPLY"); route(FROM_FS); exit; } # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # dispatch destinations route(DISPATCH); return; } route[FROM_FS] { #record_route(); #loose_route_preloaded(); route(DLGURI); route(RELAY); exit; } route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } #reply_route { # if(status == 403) { # xlog("L_WARN", "Forbidden from $si:$sp blah...\n"); # xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); # } #} onreply_route[LOGRPL] { if(status == 403) { xlog("L_ALERT", "$rs response. Consider banning AVP \"ipbancandidate\" is $avp(ipbancandidate) "); } } # Per SIP request initial checks route[REQINIT] { # no connect for sending replies # Enable tracing for SNGREP ##sip_trace(); ##setflag(24); # set_reply_no_connect(); # enforce symmetric signaling # - send back replies to the source address of request force_rport(); #!ifdef WITH_ANTIFLOOD # flood detection from same IP and traffic ban for a while # be sure you exclude checking trusted peers, such as pstn gateways # - local host excluded (e.g., loop to self) if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { # ip is already blocked xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } #!endif if($ua =~ "friendly|scanner|sipcli|sipvicious|VaxSIPUserAgent|pplsip|Hello\ SIP\ Automated") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); xlog("User agent is: $ua\n"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("17895", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { xlog("L_INFO", "Routing before DLGURI\n"); route(DLGURI); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("ACK") ) { # ACK is forwarded statelessly route(NATMANAGE); } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); exit; } # Handle SIP registrations route[REGISTRAR] { if(!is_method("REGISTER")) return; xlog("L_WARN", "--- Going to <$ru>. src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si\n"); add_path_received(); $avp(ipbancandidate) = $si; if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); #!ifdef WITH_NATSIPPING # do SIP NAT pinging setbflag(FLB_NATSIPPING); #!endif } route(DISPATCH); if (!save("location")) { sl_reply_error(); } exit; } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT if (nat_uac_test("19")) { if (is_method("REGISTER")) { #fix_nated_register(); Disabled as we proxy registrations #fix_nated_contact(); set_contact_alias(); ##add_contact_alias(); #fix_nated_sdp("3"); xlog("L_ALERT", "Nat Registration nat fixed.\n"); } else { if(is_first_hop()) { set_contact_alias(); xlog("L_ALERT", "Contact NAT fixed\n"); } } setflag(FLT_NATS); xlog("L_ALERT", "FLT_NATS flag set\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")) { setbflag(FLB_NATB); } } } if (nat_uac_test("3")) { #fix_nated_contact(); set_contact_alias(); ##add_contact_alias(); force_rport(); } if (has_body("application/sdp") && nat_uac_test("8")) { fix_nated_sdp("11"); } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; ###!ifdef WITH_RTPENGINE ## xlog("RTPEngine enabled\n"); ## if(nat_uac_test("8")) { ## xlog("RTP 1\n"); ## rtpengine_manage("SIP-source-address replace-origin replace-session-connection"); ## } else { ## rtpengine_manage("replace-origin replace-session-connection"); ## } ###!else ## if(nat_uac_test("8")) { ## rtpproxy_manage("co"); ## } else { ## rtpproxy_manage("cor"); ## } ###!endif if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); xlog("Nat notation added!\n"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) #fix_nated_contact(); set_contact_alias(); #add_contact_alias(); } } if(isbflagset(FLB_NATB)) { # no connect message in a dialog involving NAT traversal if (is_request()) { if(has_totag()) { set_forward_no_connect(); } } } #!endif return; } # URI update for dialog requests route[DLGURI] { #!ifdef WITH_NAT if(!isdsturiset()) { handle_ruri_alias(); xlog("L_INFO", "Routing in-dialog $rm from $fu to $du\n"); } #!endif return; } # Dispatch requests route[DISPATCH] { # round robin dispatching on gateways group '1' remove_hf_re("Subject|P-.*|X-.*"); append_hf("X-Auth-IP: $si\r\n"); #add_rr_param(";nat=yes"); t_on_reply("LOGRPL"); if(!ds_select_dst("1", "0")) { send_reply("404", "No destination"); exit; } #xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); xlog("L_WARN", "--- Going to <$ru>. src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si; $RAi; $Ri;\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); } # Try next destionations in failure route failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { if(ds_next_dst()) { xdbg("--- SCRIPT: retrying to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } # Manage outgoing branches branch_route[MANAGE_BRANCH] { xdbg("new branch [$T_branch_idx] to $ru\n"); xlog("L_ALERT", "Marker 20\n"); route(NATMANAGE); return; } # Manage incoming replies reply_route { if(!sanity_check("17604", "6")) { xlog("Malformed SIP response from $si:$sp\n"); drop; } return; } # Manage incoming replies in transaction context onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); xlog("L_ALERT", "Marker 21\n"); if(status=~"[12][0-9][0-9]") { route(NATMANAGE); } # if (has_body("application/sdp")) { # rtpengine_manage(); # } return; } # Manage failure routing cases failure_route[MANAGE_FAILURE] { xlog("L_ALERT", "Marker 23\n"); route(NATMANAGE); if (t_is_canceled()) exit; #!ifdef WITH_BLOCK3XX # block call redirect based on 3xx replies. if (t_check_status("3[0-9][0-9]")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_BLOCK401407 # block call redirect based on 401, 407 replies. if (t_check_status("401|407")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_VOICEMAIL # serial forking # - route to voicemail on busy or no answer (timeout) if (t_check_status("486|408")) { $du = $null; route(TOVOICEMAIL); exit; } #!endif return; }

1 0

MANAGE_REPLY not getting replies to PRACK?
by Benoît Panizzon 23 Sep '22

23 Sep '22

Hi all On calls with privacy enabled to customers, I want to ensure no information is disclosed. Not even if one would capture packets. A PRACK and the 200 OK to a PRACK therefore may need the To and From Header changed. Unfortunately I seem not to be able to catch the 200 OK REPLY sent to a PRACK with t_on_reply. It looks like they somehow pass completely unprocessed through Kamailio (not completely Via Header are removed accordingly) Am I missing something? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Guide to set up Kamailio as an SBC
by Unai Rodriguez 23 Sep '22

23 Sep '22

Dear List, I’m new to Kamailio and would like to set it up as a standalone general purpose SBC. I’m having a hard time finding a guide specific for this. What can you recommend? Thank you so much With best wishes, Unai Rodriguez

2 1

app_python3 crash woes
by Alex Balashov 22 Sep '22

22 Sep '22

Hi, Some exceptions generated in Python script cause a harmless traceback in the logs, while others cause Kamailio to crash: Sep 22 06:28:34 proxy /usr/sbin/kamailio[3984]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 11 Sep 22 06:28:34 proxy /usr/sbin/kamailio[3957]: ALERT: <core> [main.c:783]: handle_sigs(): child process 3965 exited by a signal 11 Sep 22 06:28:34 proxy /usr/sbin/kamailio[3957]: ALERT: <core> [main.c:786]: handle_sigs(): core was generated (gdb) where #0 0x00007fdaea729079 in vfprintf () from /lib64/libc.so.6 #1 0x00007fdaea754179 in vsnprintf () from /lib64/libc.so.6 #2 0x00007fdac45e9afd in make_message () from /usr/lib64/kamailio/modules/app_python3.so #3 0x00007fdac45e5bc9 in python_handle_exception () from /usr/lib64/kamailio/modules/app_python3.so #4 0x00007fdac45ebfde in apy_exec () from /usr/lib64/kamailio/modules/app_python3.so #5 0x00007fdac45ecef1 in python_exec2 () from /usr/lib64/kamailio/modules/app_python3.so #6 0x0000000000474ee0 in do_action () #7 0x000000000048217d in run_actions () #8 0x0000000000474d39 in do_action () #9 0x000000000048217d in run_actions () #10 0x0000000000474d39 in do_action () #11 0x000000000048217d in run_actions () #12 0x0000000000474d87 in do_action () #13 0x000000000048217d in run_actions () #14 0x00000000004828c1 in run_top_route () #15 0x00000000005e8044 in receive_msg () #16 0x00000000004df772 in udp_rcv_loop () #17 0x0000000000429f5b in main_loop () #18 0x000000000043423e in main () Is there a reasonable way to try to prevent this type of mid-air explosion? — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 2

SIPp uas(SIPp)->client reINVITE late offer
by David Villasmil 20 Sep '22

20 Sep '22

Hello all, Anyone got a SIPp scenario for reINVITE with late offer? I.e.: UAT--->INVITE (sdp)--->SIPp UAT<--- 100 <---SIPp UAT<--- 183 <---SIPp UAT<--- 200 OK <---SIPp UAT----> ACK --->SIPp UAT<--- INVITE (NO sdp) <---SIPp UAT---> 100 --->SIPp UAT---> 183 --->SIPp UAT---> 200 OK (sdp) -->SIPp UAT<--- ACK (sdp) <---SIPp UAT---> BYE -->SIPp UAT<--- ACK <--SIPp I can’t get past UAT<--- INVITE (NO sdp) <---SIPp Kamailio responds with “not here” Appreciate the help! -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 4

Substdef syntax change?
by Fredrik Dahlgren 20 Sep '22

20 Sep '22

Hi, I'm looking at a kamailio config where all substdef have the syntax "!regexp!subst!flags", "!DB_URL!db.example.com!g" but i can't find this syntax in the documentation. It's currently running on a fairly modern 5.x version and as far as i know it has never been on 4.x or older. Does anyone know where this syntax is from and if it's possible/recommended to simply replace it with "/regexp/subst"? *Fredrik* *Dahlgren* | Senior SIP/VoIP Engineer fredrik.dahlgren(a)freespee.com | LinkedIn <https://www.linkedin.com/company/freespee/> | Twitter <https://twitter.com/freespee>

2 1

Kamailio stops processing requests mid script
by Joel Serrano 20 Sep '22

20 Sep '22

Hello, I have a cluster of 2 kamailios v5.5 on debian 9 working flawlessly. We have added a third node, also on v5.5 but debian 11. Kamailio doesn't work correctly for some reason that I'm not seeing. The symptoms are: 1- Kamailio receives INVITEs and starts to process them per routing script. 2- There is a specific place where something happens and the calls are dropped (Kamailio is not even replying to the source). Note that the config is exactly the same on all 3 servers, only one of the three is having the issue. I enabled debug logs and I could see: [...] Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.example.com} *** cfgtrace:dbg_cfg_trace(): request_route=[GET_OUTBOUND_API_DATA] c=[/etc/kamailio/sbc/api.cfg] l=61 a=5 n=route Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.example.com} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=211 a=26 n=xlog Sep 10 12:30:48 sbc03 sbc[956340]: INFO: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <script>: Applying local to toll-free rewrite rules on callee number using dpid '20' Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=212 a=63 n=assign Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=219 a=16 n=if Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=213 a=26 n=dp_translate Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dialplan.c:237]: dp_get_ivalue(): searching 15 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dialplan.c:245]: dp_get_ivalue(): dpid is 20 from pv argument Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dialplan.c:254]: dp_get_svalue(): searching 15 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dialplan.c:350]: dp_translate_f(): input is 67339924 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:605]: dp_translate_helper(): regex operator testing over [67339924] Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dp_repl.c:676]: dp_translate_helper(): no matching rule Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialplan [dialplan.c:354]: dp_translate_f(): could not translate 67339924 with dpid 20 Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=217 a=26 n=xlog Sep 10 12:30:48 sbc03 sbc[956340]: INFO: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <script>: No matching rewrite rules for '67339924' found Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=218 a=2 n=return Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/receive.c:514]: receive_msg(): request-route executed in: 12245 usec Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:785]: dlg_lookup_mode(): ref dlg 0x7ff1b4884b48 with 1 -> 2 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:789]: dlg_lookup_mode(): dialog id=8614 found on entry 343 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_var.c:63]: dlg_cfg_cb(): new dialog with no transaction after config execution Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7ff1b4884b48 with 1 from dlg_hash.c:1109 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7ff1b4884b48 with 1 -> 1 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7ff1b4884b48 with 1 from dlg_hash.c:1109 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7ff1b4884b48 with 1 -> 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): ref <=0 for dialog 0x7ff1b4884b48 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:345]: destroy_dlg(): destroying dialog 0x7ff1b4884b48 (ref 0) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:356]: destroy_dlg(): removed timer for dlg 0x7ff1b4884b48 [343:8614] with clid '5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa' and tags 'as5d31c96b' '' Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_db_handler.c:708]: remove_dialog_from_db(): trying to remove dialog [ 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa], update_flag is 1024 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [db_query.c:72]: db_do_submit_query(): submitted query: delete from `dialog` where `hash_entry`=343 AND `hash_id`=8614, result 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [db_query.c:72]: db_do_submit_query(): submitted query: delete from `dialog_vars` where `hash_entry`=343 AND `hash_id`=8614, result 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_db_handler.c:736]: remove_dialog_from_db(): callid was 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list 0x7ff1b4880370 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/receive.c:606]: receive_msg(): cleaning up If I go to line 61 from route GET_OUTBOUND_API_DATA, I have this: if(route(APPLY_REWRITE_RULE)) { $rU = $var(dp_user); $avp(icx_real_number) = $var(dp_user); } The very next thing is: # Query API $avp(apiUrl) = "{{ call_api_url }}/outbound/" + $avp(icx_src_number) + "/" + $avp(icx_real_number); http_client_query("$avp(apiUrl)", "$avp(apiResponseBody)"); $avp(apiResponseCode) = $rc; I see the GET_OUTBOUND_API_DATA route calling APPLY_REWRITE_RULE, and APPLY_REWRITE_RULE returning correctly then finished: Sep 10 12:30:48 sbc03 sbc[956340]: exec: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} *** cfgtrace:dbg_cfg_trace(): request_route=[APPLY_REWRITE_RULE] c=[/etc/kamailio/sbc/extras.cfg] l=218 a=2 n=return But then Kamailio is apparently just tearing down the call and ending it. Can someone help me understand what this part of the logs means or what can be causing them? Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/receive.c:514]: receive_msg(): request-route executed in: 12245 usec Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:785]: dlg_lookup_mode(): ref dlg 0x7ff1b4884b48 with 1 -> 2 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:789]: dlg_lookup_mode(): dialog id=8614 found on entry 343 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_var.c:63]: dlg_cfg_cb(): new dialog with no transaction after config execution Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7ff1b4884b48 with 1 from dlg_hash.c:1109 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7ff1b4884b48 with 1 -> 1 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7ff1b4884b48 with 1 from dlg_hash.c:1109 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7ff1b4884b48 with 1 -> 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:1095]: dlg_unref_helper(): ref <=0 for dialog 0x7ff1b4884b48 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:345]: destroy_dlg(): destroying dialog 0x7ff1b4884b48 (ref 0) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_hash.c:356]: destroy_dlg(): removed timer for dlg 0x7ff1b4884b48 [343:8614] with clid '5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa' and tags 'as5d31c96b' '' Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_db_handler.c:708]: remove_dialog_from_db(): trying to remove dialog [ 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa], update_flag is 1024 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [db_query.c:72]: db_do_submit_query(): submitted query: delete from `dialog` where `hash_entry`=343 AND `hash_id`=8614, result 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [db_query.c:72]: db_do_submit_query(): submitted query: delete from `dialog_vars` where `hash_entry`=343 AND `hash_id`=8614, result 0 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} dialog [dlg_db_handler.c:736]: remove_dialog_from_db(): callid was 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list 0x7ff1b4880370 Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Sep 10 12:30:48 sbc03 sbc[956340]: DEBUG: {1 102 INVITE 5111a7c71ec485e443099844491ef7d8(a)sip02.vozelia.com.pa} <core> [core/receive.c:606]: receive_msg(): cleaning up I can see it's related to the dialogs, but is this a cause or a consequence? I have checked the API access logs, and Kamailio doesn't get to send the request, I've also noticed that normally Kamailio replies with a 100-Trying almost instantly, in the case of this server I don't see a single 100-Trying from Kamailio. I'm pretty lost here so any tips are more than welcome. NOTE: I tried with debian11 + Kamailio 5.6 and the same issue happens too. Thanks, Joel.

4 12

Kamailio v5.5.5 Released
by Daniel-Constantin Mierla 19 Sep '22

19 Sep '22

Hello, Kamailio SIP Server v5.5.5 stable release is out. This is a maintenance release of the stable branch 5.5 that includes fixes since the release of v5.5.4. 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.5. Note that 5.5 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.6, with v5.6.1 being release out of it. For more details about version 5.5.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2022/09/kamailio-v5-5-5-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 Oct 10-13, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

Database changes required for upgrading from 5.5 to 5.6
by Leonid Fainshtein 19 Sep '22

19 Sep '22

Hi, Instructions for upgrading from 5.5 to 5.6 don't include instructions for the MySQL database schema changes: http://www.kamailio.org/wiki/install/upgrade/5.5.x-to-5.6.0 Where can I get this information? It was always published in the past. Best regards, Leonid Fainshtein

3 3

Releasing Kamailio v5.5.5
by Daniel-Constantin Mierla 19 Sep '22

19 Sep '22

Hello, I am considering to release Kamailio v5.5.5 soon, likely on Monday or Tuesday next week (Sep 19 or 20, 2022). 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 Oct 10-13, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

Log levels severely impacts performance
by Amit 16 Sep '22

16 Sep '22

Hello, We’ve been running Kamailio 5.5.0 for a while now and recently ran into an issue where the application buffer would get full and Kamailio has a lot of difficulty keeping up with REG requests. This severely impacted Kamailio’s ability to perform and resulted in many REG timeouts. Running ‘watch netstat -ulpn’ revealed the buffer issue. We usually run the production system at log level INFO (2) and had not ran into any issues in the past. When the buffer issue occurred and after some testing, we discovered that changing the log level to NOTICE (1) was sufficient to bring the system back into operational status. For example, at log level INFO (2) we seem to achieve ~150-200 REG/s while at log level NOTICE (1) we reach ~500-700 REG/s. I did find this article in the wiki and tried using the “-“ in front of the log path but this didn’t seem to help. http://www.kamailio.org/wiki/tutorials/3.2.x/syslog Even writing the logs directly to our external log server and preventing them from being written to the local disk doesn’t seem to alleviate the issue when the log level is set to INFO (2). Does anyone have any experience with this or have any suggestions? We are finding it difficult to scale as a result of this issue. Thank you in advance. Amit

7 20

TM Module, avp not present during handling of ack, prack and cancel?
by Benoît Panizzon 16 Sep '22

16 Sep '22

Hi List If I'm correctly reading the documentation, all avp variables should exist during a transaction until it's final ACK. ACK, PRACK and CANCEL are part of that transaction. But I seem not to be able to access the content of avp during those messages. Strangely during MANAGE_REPLY of the 487 following a cancel, the avp are present so that 487 clearly is part of the transaction. What am I missing? (Yes, I am still working on mirroring al username (phone number) translations and filtering unwanted header to prevent information leakage, any hints welcome if there is a simpler way to achieve this) -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Modules changes query
by Satyaprakash Chiramchetty 16 Sep '22

16 Sep '22

Hi team, I have added a few lines more in the SCA module, So if I want to compile again only the sca, So what command I need to use? Thanks and Regards, Satyaprakash. -- * <https://www.ecosmob.com/> * *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

2 1

Kamailio v5.4.9 Released
by Daniel-Constantin Mierla 16 Sep '22

16 Sep '22

Hello, Kamailio SIP Server v5.4.9 stable release is out. This is a maintenance release of the old stable branch, 5.4, that includes fixes since the release of v5.4.8. 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.9 or even better to v5.5.x or 5.6.x series. For more details about version 5.4.9 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2022/09/kamailio-v5-4-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.4 is an old stable branch, v5.4.9 being the last planned release out of it, to mark the end of official maintenance. The maintained stable branches are now 5.5 and 5.6, at this time with v5.6.1 being the latest stable release. 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 v.5.4.9
by Daniel-Constantin Mierla 16 Sep '22

16 Sep '22

Hello, I am planning to release a new version from branch 5.4, respectively 5.4.9, sometime soon, maybe on Friday or Monday. Unless a major regression comes out with this release, this is going to be the last official packaged version from branch 5.4. The latest two stable branches 5.5 and 5.6 will be maintained further. As usual, if anyone is aware of issues not yet reported to bug tracker or missing backports, report them in order to try to get the fixes in this release. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

ndb_redis value substitution or escaping spaces
by Brooks Bridges 15 Sep '22

15 Sep '22

I am aware of, and have used sucessfully, the %s substitution option in redis_cmd, however when trying to do 4 values I'm getting a parse error about too many arguments. A review of the module's source appears to indicate that there is a hard limit of 3 substitution values when using this method. Is there a suitable workaround anyone has for this to enable insertion of values with spaces in them that won't get interpreted by Kamailio itself? Escaping the value, even by using $_s to eval a dynamic string, ends up with Kamailio itself apparently trying to parse the escape and breaking things further. Thanks! Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

2 5

New feature: #!ifexp - conditional preprocessor blocks
by Daniel-Constantin Mierla 15 Sep '22

15 Sep '22

Hello, a new feature has landed to Kamailio devel version, bringing in more flexibility for preprocessing of the kamailio.cfg file. It is about #!ifexp, which allows to evaluate an expression created with defined IDs, string and number values. Based on evaluation result, being true or false, parts of the config file can be enabled or disabled. An extensive number of operators can be used in expressions, such as: +, -, *, /, ==, !=, <, >, <=, >=, ||, &&, etc. The evaluation is done using snexpr (https://github.com/miconda/snexpr), which was embedded inside Kamailio code. Here are some simple kamailio.cfg examples: #!ifexp KAMAILIO_VERSION >= 5006000 loadmodule "tlsa.so" #!else loadmodule "tls.so" #!endif #!ifexp MOD_xlog && (OS_NAME == "darwin") xlog("running on MacOS\n"); #!endif Documentation and more examples can be found on the wiki portal at: - https://www.kamailio.org/wikidocs/cookbooks/devel/core/#ifexp Testing would be appreciated, feedback can be addressed to sr-users mailing list! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

kamailio.org short unavailability
by Daniel-Constantin Mierla 15 Sep '22

15 Sep '22

Hello, kamailio.org system needs a reboot and it will become unavailable for a short time frame about 08:00UTC (20 min from now). Website, mailing list, wiki, and a few other web services will be affected. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

evapi_async_relay() and workers
by Alex Balashov 14 Sep '22

14 Sep '22

Hi, When a transaction suspended by evapi_async_relay() is resumed, in which child processes is it resumed? Is it in the dedicated “EVAPI RELAY” workers defined by the ‘workers’ modparam to ‘evapi’? If this is so, just trying to work out the concurrency implications and the optimal size for the worker pool for maximal throughput. It sounds, at first glance, like it should be roughly similar to the sizing considerations for listener children. Thoughts welcome! Cheers, — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 3

Kamailio + RTPEngine SIP Proxy...
by Jerry Kendall 12 Sep '22

12 Sep '22

Hi There, It's been a few years since I joind the group and I have watched and learnt and played but, I am stuck... I have searched hi & low but I can't seem to find what I am looking for. Is is do-able to have SIP Phones proxy through Kamailio/RTPengine and have the connection relayed to a freeswitch system where all the work is done. I need to have Kamailio act as proxy ONLY - no need to do AUTH, and I need Kamilio to have the RTPEngine have the media but only as proxy. I have FreeSWITCH doing all the IVR/VM/CONF/etc.... So: 1) The SIP Phone sends everything to the Kamailio system, the Kamailio system will relay everything to the FreeSWITCH system (requests and replies) 2) The FreeSWITCH system will send everything to the Kamailio system which will relay everything back to the SIP Phone (requests and replies) 3) The SIP phones are behind NAT 4) The Kamailio and FreeSWITCH systems are on the public internet with public IP addresses I have found a few sample kamailio.cfg files but, I can get REG to make it through but no SUBCRIBE wont get NOTIFYs back, etc... I seem to get parts but not all the way. If this is doable, and I assume it is, is there a config file someone can share with me? or point me to? Jerry

3 6

Siremis JSONRPC problem on Bullseye
by Joseph Goettgens 12 Sep '22

12 Sep '22

I am not sure what I have to look for and I didn't change the initial config files (except for the 666 mode for kamailio_rpc.sock). As far as Kamailio is concerned the socket files files do exist: root@deb11srv1-kamailio:/var/www/siremis-5.3.x# ls -l /run/kamailio/ insgesamt 4 srw------- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_ctl -rw-r--r-- 1 kamailio kamailio 5 7. Jun 11:37 kamailio.pid prw-rw---- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_rpc.fifo srw-rw-rw- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_rpc.sock When I look at siremis/log/ERR.log I repeatedly get: '06/07/2022','09:43:29','ERR','ErrorHandler','socket_bind(): unable to bind address [2]: No such file or directory','' This disappears when I put the local file socket in /tmp: <UnixSockLocal name="unixsocklocal" address="/tmp/siremis_rpc.sock" timeout="3.0"/> which was probably done this way in previous versions of Siremis (before systemd private tmp config). In this case I get no error messages, but still no answers (as expected). The next step seems to get UnixSockLocal right.

2 1

MANAGE_REPLY: do_action(): bad uri: How to mirror username changes from the invite to all replies?
by Benoît Panizzon 09 Sep '22

09 Sep '22

Hey there! Kamailio is being used between CPE (customer) and IC. Towards IC we use e164 numbers Towards customers we use 'localized' numbers and also ensure that Privacy is enforced by setting usernames to 'Anonymous' if Privacy is set to id, remove unwanted header etc. I realized, that I have to apply the same translations to replies and re-invites to make sure, they do not leak unwanted information towards the customer. But when I try to set: onreply_route[MANAGE_REPLY] $fU,$rU,$tU within MANAGE_REPLY I get: do_action(): bad uri Just removing unwanted header works fine it looks as it's only changing the usernames that causes this issue. What would be the proper was to change usernames in replies? Is there any module which would apply the same user translations as done with the invite to all replies and re-invites? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

tls_wolfssl talk at KWO: traffic generation scripts are online
by Richard Chan 09 Sep '22

09 Sep '22

Hi sr-users, The TLS traffic generation scripts are online here: * SIP library - fork of sippy/b2bua - use main-async branch https://github.com/space88man/b2bua This branch is an async refactoring of sippy; the master branch of the repo is the regular sync+elperiodic version. * runtime UA generation scripts: https://github.com/space88man/multiuac-tester This repo contains the TLS-client transport (sippy out-of-the-box supports UDP); also gratuitously uses the match/case syntax for fun (so needs Python 3.10) * no documentation: the scripts/t_register.py and scripts/t_phone.py should give you an idea how to create UACs. The script in the talk is scripts/t_register.py - creates SIP UACs that sit in an infinite loop and do REGISTER and keepalive ('\r\n\r\n'). Disclaimer: this is not a SIP-scenario framework like SIPp; SIP messages are programmatically created using sippy; e.g., the test scenario does not need to handle RTP media so the SDP body is a hardcoded string. Regards S-P

1 0

Info: Kamailio World Conference Online 2022 - The Schedule
by Daniel-Constantin Mierla 08 Sep '22

08 Sep '22

The schedule for Kamailio World Conference Online 2022 has been published on the event website: - https://www.kamailioworld.com The event spans over two days, September 7-8, 2022, with presentations and open discussion sessions during 12:50-17:00UTC. With the main target to share the knowledge and connect the community, the conference has presentations covering use of Kamailio for 5G services, NAT traversal and integration with RTPEngine, TLS with WolfSSL, end to end testing testing, controlling SIP message content from KEMI and resources management for scalability. It is a good balance between established and new speakers at this edition of Kamailio World Conference. There is no registration required to join the event, the sessions will be presented in a live video conferencing room streamed to YouTube KamailioWorld Channel. A text chat room will be made available for posting questions and background discussions. Book the dates in your agenda and prepare for another amazing Kamailio World Conference! Keep the eye on the event website for updates! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 5

Re: [SR-Users] SSL Offloading with AWS ELB or Google GSLB and Kamailio
by Mohammed Alarayshi 08 Sep '22

08 Sep '22

Hi Joel Did you manage to offload TLS SSL on the load balancer side ? I tested it before on AWS and the calls were working well. Wondering if this makes any issues like you said with headers ?

1 0

slow timer too slow: overflow
by Denys Pozniak 05 Sep '22

05 Sep '22

Hello! After some time, Kamailio stops processing incoming messages. slow timer too slow: overflow messages appear in the log (I suspect that the problem is related to the rtimer module) Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 2b45547f33f5203f-4091(a)10.10.10.10} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment> Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 2b45547f33f5203f-4091(a)10.10.10.10} <core> [core/rvalue.c:253]: rval_new_empty(): could not allocate private memory from pkg pool Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: <core> [core/timer.c:936]: timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023) Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found! Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment no> Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/rvalue.c:253]: rval_new_empty(): could not allocate private memory from pkg pool Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: <core> [core/timer.c:936]: timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023) Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ 1c18959d07113951-203309(a)10.10.10.30} <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found! Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ 1c18959d07113951-203309(a)10.10.10.30} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment no> Please point me out where the source of the problem could be. version: kamailio 5.6.1 (x86_64/linux) -- BR, Denys Pozniak

2 2

Dynamic rtimer interval, transaction to replace in-memory dispatcher list
by Anton Yabchinskiy 05 Sep '22

05 Sep '22

Hello, I have two slightly related questions, and would appreciate any advice on the matter. The first one is about dynamic `rtimer` (or `timer`) intervals. In the route, called by the timer process there is a request to a neighbor service. In the response there's a set of new destinations for in-memory dispatcher list and some TTL value. And I need to adjust the timer interval based on this TTL (e.g., timer interval may be 10 min, but TTL may suggest to request destinations every 5 min since now). Also, the first call to the timer route should be at T+0, not at T+interval. As far as I can tell from `rtimer` module implementation, that's unfeasible. But maybe I'm missing something? Any suggestion on how one should implement something like this? The second one is about updating in-memory dispatcher list. After receiving and parsing new destinations in the timer route, the previous in-memory destinations must be replaced by these new destinations. The naive way of doing so would look something like: `dispatcher.reload` to clear previous list, then a series of `dispatcher.add` calls to add new destinations. But a failed `add` call may lead to wrong in-memory destinations set. As far as I understand I should start using some transaction-aware database for dispatcher destinations, and literally write a transaction. Are there any other ways to solve this?

1 0

Kamailio 5.6 rpm availability
by Riccardo Villa 03 Sep '22

03 Sep '22

Hello, I can’t find rpm packages of kamailio 5.6.x on rpm.kamailio.org, do you know if it’s planned to build them in the future? I’m available if some help/testing is needed. Thanks, Riccardo Villa -- -- NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

2 1

How to hide Via and Record-Route header to external network and restore them to internal network?
by Anthony Blandin 02 Sep '22

02 Sep '22

Hi Community, I have set up a SBC with Kamailio. I am testing voice call from external network to my network and voice call from my network to external network. When I send SIP messages to external network, I want to hide Via and Record-Route headers but when I receive replies from the external network I want to restore these Via and Record-Route headers to my network. How to store and restore these headers in Kamailio configuration ? Could you help on this? Thanks Anthony Blandin

4 11

remove user param from RURI
by Maarten Ureel 02 Sep '22

02 Sep '22

Hello I have a SIP INVITE with a RURI like this: sip:31427;phone-context=stripped@IP How can I remove the phone-context parameter here? In reality it's a very long string and the next hop (an SBC) is complaining about it, but I don't need it anyway. Regards Maarten

1 0

Dispatcher module and xavp_dst
by Pyry Aaltonen 01 Sep '22

01 Sep '22

Hello, I’m quite new user with kamailio (heard first time about it a year ago and joined the list yesterday) and now wondering how the xavp_dst should work. I had read from the documentation that ”The first XAVP is the current selected destination.” I use ds_select_dst with alg 13. And my kamailio version is kamailio 5.5.3 (x86_64/linux) So when my dispatcher list is like (I have also tried to differ the priority value like 10 and 1, but doesn’t make difference) 10 sip:1.2.3.4;transport=tcp 10 1 type=type1 10 sip:4.3.2.1;transport=tcp 10 1 type=type2 If one of the destinations fails (dx/ip), and it happens to be the one with higher priority or the one that just gets higher position in the dispatcher list if the prio Is equal. My xavp_$xavp(dsdst=>attrs) get null value. And, if I try to seek $(xavp(dsdst[0]=>attrs) or $(xavp(dsdst[1]=>attrs) I also got nothing. If both destinations are up with equal priority, it selects them with round-robin, and the xavp_$xavp(dsdst=>attrs) has the type value of the selected destination as expected, also the $(xavp(dsdst[0]=>attrs) or $(xavp(dsdst[1]=>attrs) contains the destinations so that the selected is 0 and the other is at position 1. The $du is updated as I expect so if one fails the other one is selected always, why the xavp_dst isn’t working same way, or am I missing something? If needed I’ll try to provide more information, Thanks already in advance -Pyry

2 4

HTTP client and HTTP/2 support
by Alex Balashov 01 Sep '22

01 Sep '22

Hi, I wasn’t able to find an answer on the list previously, nor any trail of breadcrumbs in the docs: do any of the existing HTTP client modules support HTTP/2? — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 3

Disabling video rtp proxing
by mayamatakeshi 31 Aug '22

31 Aug '22

Hi, I'm using rtpengine for RTP proxying with kamailio. I use it just for audio. But eventually some terminal reinvites offering video. I don't want to refuse the request but just disable RTP proxying for video as my employer has limited bandwidth and want to reserve it only for audio. So I checked the rtpengine module documentation but it seems there is no way to restrict RTP proxying to be performed only for m=audio. I tried some things like replace_body("^m=video [0-9]+", "m=video 0"); and subst_body('/^m=video [0-9]+ /m=video 0 /'); and msg_apply_changes(); but still the RTP proxying for video is set up. Any hints on how to solve this?

3 4

Intermittent delays relaying BYE (up to 1s)
by Lewis Hutchinson 31 Aug '22

31 Aug '22

Ok so making progress but still a little confused, hopefully this forum can shed some light on this behaviour. Using the hints provided (thanks all so far) and the latency logging from the cookbook I have managed to isolate the issue down to RTPengine introducing the delay. INFO: app_python3 [apy_kemi.c:1820]: sr_apy_kemi_exec_func(): alert - action KSR.rtpengine.rtpengine_manage(...) took too long [1003089 ms] (file:(null) func:(null) line:252) What is confusing is, I don't believe this block should be being called. when the BYE is triggered, it routes to ksr_route_withindlg # handle requests within SIP dialogs if self.ksr_route_withindlg(msg)==-255 : return 1 from within the ksr_route_withindlg a check is done to see if any RTPengine work needs doing # Handle requests within SIP dialogs def ksr_route_withindlg(self, msg): if KSR.siputils.has_totag()<0 : return 1 # RTPEngine handling for UPDATES & reINVITES with sdp if self.ksr_route_rtpengine(msg) == -255: return 1 RTPengine is configured in a way to step in whenever there is an SDP present based on Content-Type: application/sdp # RTPengine handle anything with SDP def ksr_route_rtpengine(self, msg): if KSR.textops.has_body_type("application/sdp"): KSR.rtpengine.rtpengine_manage( "RTP/AVP replace-session-connection replace-origin ICE=remove") return 1 What I can understand is why is this being called and erroring introducing the delay when there is no Content-Type: application/sdp in a BYE ??? As a quick fix I have put this in which stops the problem (I am sure there is better ways to handle this but for now this works in a DEV environment) def ksr_route_rtpengine(self, msg): if KSR.is_BYE(): return 1 if KSR.textops.has_body_type("application/sdp"): KSR.rtpengine.rtpengine_manage( "RTP/AVP replace-session-connection replace-origin ICE=remove") return 1 Can anyone see why this would occur? Why is sr_apy_kemi_exec_func(): alert - action KSR.rtpengine.rtpengine_manage(...) even being called for this BYE ? when there is no Content-Type: application/sdp Lewis

2 3

Manual Siremis
by -Luís Fernando- 31 Aug '22

31 Aug '22

Hello, Is there a Siremis Manual, that explain how to configure a SIP Trunk, a sip route, etc.. Thank you

2 1

Websockets Configuration
by Mahmood Alkhalil 31 Aug '22

31 Aug '22

Hi, I'm trying to configure kamailio to register users over websockets, but i am not able to find any working configuration around, am new to kamailio. as far as i understand now, xhttp will handle the HTTP GET requests, i am not sure how to configure xhttp port number, cannot find parameters in the module manual, i found multiple sample configs but none of them is working, am using JsSip client. if someone can guide me with a link to a working config and that i can start from.

2 4

app_python module load error in 5.6
by Stefan-Cristian Mititelu 30 Aug '22

30 Aug '22

Hello, I am trying to load app_python.so module in kamailio 5.6 and I am getting the following error, under debian bullseye: ERROR: <core> [core/sr_module.c:573]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/app_python.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/app_python.so: undefined symbol: LOG_ The app_python.so file exists, under that path. Same ERROR for app_python3.so. I have tried updating some modules's Makefile LDFLAGS but didn't work so far; still searching. Any ideas? Thank you, Stefan

2 3

Core variable with from userinfo value of sip uri
by Denys Pozniak 30 Aug '22

30 Aug '22

Hello! It was accidentally noticed that the variable $fU gets the user part of userinfo SIP URI (although it is logical and described in the document RFC2543). I got message below and my spam filter based on $fU passed it inside the network, as $fU was test From: <sip:test:test@1.1.1.1>;tag=123456 Sure I can filter it through a regular expression, but maybe it's worth adding another core variable with the userinfo value? SIP-URL = "sip:" [ userinfo "@" ] hostport url-parameters [ headers ] userinfo = user [ ":" password ] -- BR, Denys Pozniak

2 1

Re: [SR-Users] kamailio Trunk authentication
by Keshav Kaushik 29 Aug '22

29 Aug '22

1 0

Re: [SR-Users] kamailio Trunk authentication
by Henning Westerholt 29 Aug '22

29 Aug '22

Hello, For non-commercial support please address our sr-users list (added to CC). Please look at the uac module, there a function uac_auth() for this particular scenario with example cfg. https://kamailio.org/docs/modules/5.5.x/modules/uac.html#uac.f.uac_auth Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Keshav Kaushik <kdkaushik(a)gmail.com> Sent: Sunday, August 28, 2022 1:34 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: kamailio Trunk authentication Respected Sir, I am new to kamailio so not very familiar with config PV’s and transformations etc. I have successfully authenticated the Twilio SIP phone via ACL. But I also willing to authenticate the Twilio SIP via username and password. For doing this I plan to modify the “proxy-authentication” header as blow: if (is_present_hf("Proxy-Authorization")) { $nonc=$sel(proxy-authorization.nonce);// not working $has="kamailio:$ar:SdE-----------ADVpa"; $ha1=$(has{s.md5}); hat="$aa:$adu"; $ha2=$(hat{s.md5}); $resp="$HA1:$nonc:$HA2"; append_hf('Proxy-Authorization: Digest username="kamailio", realm="$ar", nonce="$nonc", uri="sip:+1650ZZZZZZ@XX.YY.7.195", response="$(resp{s.md5})"'); } remove_hf("Proxy-Authorization");// remove original header When I save the config file and restart kamailio, it does not start, may be due to some error in code. Can you please help in authentication of a SIP trunk using user/passowrd. Thanks in advance Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

Intermittent delays relaying BYE (up to 1s)
by Lewis Hutchinson 26 Aug '22

26 Aug '22

Thanks Alex and Kaufman, As you said there is an element of db blocking for accounting, but I don't see the same impact when the INVITE goes through and sets the accounting flags. I will look to disable accounting and see if it improves things. If not, I will have a look at benchmark to try and pin it down. It is not causing any noticeable delay in the clearing down of the call to the end users but I want to try and optimise the cleardown if possible. Once I have tested this I will report back. Thanks for your assistance. Lewis

3 2

Intermittent delays relaying BYE (up to 1s)
by Lewis Hutchinson 25 Aug '22

25 Aug '22

I have a situation where I am seeing intermittently Kamailio having delays when relaying the BYE received from an external party This is only affecting the BYE We have 6 Kamailios stood up 3 linked to the SIP Providers (SBC) 3 for Registration (REG) Language KEMI | Python version: kamailio 5.5.1 (x86_64/linux) 278772-dirty 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: 278772 -dirty compiled with gcc 9.3.0 Simplified Flow PSTN >>>> Kamailio SBC >>>> FREESWITCH >>>> Kamailio REG >>>> SIP DEVICE SIP DEVICE >>>> Kamailio REG >>>> FREESWITCH >>>> Kamailio SBC >>>> PSTN This happens on all of them intermittently when receiving the BYE from either a SIP trunk or a SIP Device Publicly, it can take upto 1s to pass this onto the next hope (Freeswitch) on the local network. All BYEs passed between the local network relay in fractions of a second. All BYEs passed out of the KAMAILIO SBC or KAMAILIO REG to their respective public enpoints relay in fractions of a second but BYEs received from public on advertised address take upto 1s for Kamailio to process and relay. i.e PSTN >>> BYE >>>> KAMAILIO SBC (kamailio will sometimes take upto 1 second to relay this on to other kit on the internal solution. Freeswitch etc) SIP DEVICE >>> BYE >>>> KAMAILIO REG (kamailio will sometimes take upto 1 second to relay this on to other kit on the internal solution. Freeswitch etc) I am basing these timings on SNgrep and PCAP traces from homer. Does anyone have any hints and tips on how I can debug this issue. I have enabled debug logging and replicated the issue but it doesn't show anything from what I can see as to why there is delays. Thanks in advance lewis

3 2

JSON-RPC dgram_socket just part of the output
by Ilie Soltanici 25 Aug '22

25 Aug '22

Hello, I'm trying to get the dispatcher status from kamailio through the UDP datagram but for some reason, it is getting just part of the output. Is there any buffer that I have to increase to get the complete output? command used: ``` echo '{"jsonrpc": "2.0", "method": "dispatcher.list", "reply_name": "kamailio_reply_fifo", "id": 1}' | nc -u 192.168.1.1 8090 ``` kamailio related config: modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_request.fifo") modparam("jsonrpcs", "transport", 6) modparam("jsonrpcs", "fifo_mode", 0600) modparam("jsonrpcs", "fifo_user", "kamailio") modparam("jsonrpcs", "dgram_socket", "udp:MY_INTERNAL_IP_ADDR:8090") modparam("jsonrpcs", "dgram_timeout", 2000) modparam("jsonrpcs", "pretty_format", 1) output: [image: image.png] Thanks

2 4

Kamailio 5.3 call forwarding
by Derek OSS 24 Aug '22

24 Aug '22

Hi, I'm using Kamailio 5.3 and I am interested in doing call forwarding. I am interested in having a user "alice" bypass the SIP REGISTER step and have their SIP INVITE request/call forwarded to another SIP user "bob" (who, let's just say for now is within the same domain, so accessible by the same SCSCF and if it makes things simpler, let's say that bob went through the register step). In the PCSCF configuration, I've tried doing something like this: route { route(TEST) ... } route[TEST] { $ru = "sip:bob@domain.com" if (!t_relay("scscf.domain.com",6060)) { sl_reply_error(); } exit; } Instead of $ru, I've also tried using uac_replace_to, providing both the To and URI fields with Bob's SIP URI. When I try using the $ru, the S-CSCF still seems to use Alice's R-URI instead of Bob's. When I try using uac_replace_to, I get a 403 error saying that I need to register with the S-CSCF first. Am I going about this the correct way? Thank you. Derek

2 1

TLSA module compile errors
by Koray Vatansever 23 Aug '22

23 Aug '22

Hi everyone, I'm trying to build tlsa module on redhat 7.9 server. But I'm encountering the following compile errors. Any ideas on how I can deal with this? CC (gcc) [M tlsa.so] tls_util.o CC (gcc) [M tlsa.so] tls_domain.o CC (gcc) [M tlsa.so] tls_locking.o CC (gcc) [M tlsa.so] tls_rand.o CC (gcc) [M tlsa.so] tls_map.o CC (gcc) [M tlsa.so] tls_cfg.o CC (gcc) [M tlsa.so] tls_select.o CC (gcc) [M tlsa.so] tls_dump_vf.o CC (gcc) [M tlsa.so] tls_init.o CC (gcc) [M tlsa.so] tls_bio.o CC (gcc) [M tlsa.so] tls_config.o CC (gcc) [M tlsa.so] tls_server.o CC (gcc) [M tlsa.so] tls_rpc.o CC (gcc) [M tlsa.so] tls_ct_wrq.o CC (gcc) [M tlsa.so] tlsa_mod.o CC (gcc) [M tlsa.so] tls_verify.o LD (gcc) [M tlsa.so] tlsa.so /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(deflate.o): relocation R_X86_64_32S against hidden symbol `_length_code' can not be used when making a shared object /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(inflate.o): relocation R_X86_64_32S against hidden symbol `zcfree' can not be used when making a shared object /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(inftrees.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(trees.o): relocation R_X86_64_32S against hidden symbol `_length_code' can not be used when making a shared object /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(zutil.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(crc32.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libz.a(inffast.o): relocation R_X86_64_32S against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: tlsa.so: version node not found for symbol SSLeay_version(a)OPENSSL_1.0.1 /usr/bin/ld: failed to set dynamic section sizes: Bad value collect2: error: ld returned 1 exit status make[2]: *** [tlsa.so] Error 1 make[1]: *** [modules] Error 1

2 2

TLS issue
by M Arqum CH 22 Aug '22

22 Aug '22

Dear All, Thank you in advance . Facing issue is setting up tls with kamailio 5.5.4 on ec2 Amazon linux server. Getting this error. Aug 18 20:36:33 abc.domain /usr/local/mykamailio/sbin/kamailio[10772]: ERROR: tls [tls_server.c:1329]: tls_h_read_f(): protocol level error Aug 18 20:36:33 abc.domain /usr/local/mykamailio/sbin/kamailio[10772]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca Aug 18 20:36:33 abc.domain /usr/local/mykamailio/sbin/kamailio[10772]: ERROR: tls [tls_server.c:1333]: tls_h_read_f(): src addr: 143.198.11.1:62033 ///client ip Aug 18 20:36:33 abc.domain /usr/local/mykamailio/sbin/kamailio[10772]: ERROR: tls [tls_server.c:1336]: tls_h_read_f(): dst addr: 172.36.53.1:5061 ///ec2 local ip Aug 18 20:36:33 abc.domain /usr/local/mykamailio/sbin/kamailio[10772]: ERROR: <core> [core/tcp_read.c:1481]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xffff80d78a10 r: 0xffff80d78b38 (-1) TLS Config [server:default] method = TLSv1+ verify_certificate = no require_certificate = nocertificate=/usr/local/ssl/certs/cert.pem private_key=/usr/local/ssl/certs/fullkey.pem server_name = abc.domain Also tried this conf [server:default] method = TLSv1+ ///tries all version options verify_certificate = no require_certificate = no certificate=/usr/local/ssl/certs/ abc.domain.crt private_key=/usr/local/ssl/certs/ abc.domain.key server_name = abc.domain.link openssl version OpenSSL 1.0.2k-fips 26 Jan 2017 please guide. -- Regards Arqum

3 3

remove header from reply?
by Brett Nemeroff 19 Aug '22

19 Aug '22

Hello, I'm receiving calls which I forward to a server I KNOW will reply with a 302. When I get that 302, I parse some information and then t_reply(302) the originator. The 302 I create needs to have it's own contact header which I am adding with append_to_reply(). That works great. BUT the contact header from the original 302 is hanging around. Now I have two contact headers :( How can I get rid of the original 302's contact header? remove_hf() doesn't work in this context since it's a reply. So I need a kind of "remove_header_from_reply()". Thanks, Brett

2 3

Processing Async HTTP Requests in Real-time
by Brett Nemeroff 19 Aug '22

19 Aug '22

Hello Kamailio Team! I've tried following the documentation for http_async_query() with suspend=1 and not getting results I'm expecting. Perhaps I'm misunderstanding the documentation. Basically I'm performing a http_async_query() with suspend set to 1 and a "route_name" set to HTTP_REPLY. When my query executes, it appears that Kamailio stops processing in that route block, suspends, and then when a reply is available, it continues in HTTP_REPLY. That makes sense. I pull the return value and set some $var and $avp. When I get to the end of the HTTP_REPLY block, I'm EXPECTING it to RESUME FROM the suspended location from the original route block, which it does NOT seem to do. Is that expected? For what it's worth, I did test just continuing my route logic in HTTP_REPLY and just forgetting about the original route block (moved all the remaining processing logic into HTTP_REPLY) However, existing $avp and $vars that were already set within the transaction were not set. So that's not possible either. I'm pretty sure there is a right way to do this without getting hacky. Can someone help me out? And yes, I know what I'm trying to do sounds like sync, but I want async to handle high volume and the potential for my external URL to lightly block. I believe the right way to do this is with async+suspending. Thank you, Brett

2 4

packets exceeding MTU size
by Ali Taher 18 Aug '22

18 Aug '22

Hello all, Lately I faced an issue that Kamailio is not responding to some invite packets coming from SBC. When investigating I found that these packets exceeds MTU size. Could this be the issue? Knowing that in Kamailio configuration I have a condition on is_method("INVITE"). Could be that in case of packet exceeding MTU size it's not considered as invite packet by Kamailio? I have Kamailio 5.2.5. Regards, Ali Taher

4 6

How to enforce max_contacts at registration?
by Benoit Panizzon 18 Aug '22

18 Aug '22

Hi List # ----- registrar params ----- modparam("registrar", "method_filtering", 1) # modparam("registrar", "append_branches", 0) modparam("registrar", "max_contacts", 10) modparam("registrar", "max_expires", 3600) modparam("registrar", "gruu_enabled", 0) modparam("registrar", "retry_after", 30) modparam("registrar", "xavp_cfg", "reg") == snipp == # Handle SIP registrations route[REGISTRAR] { # We are authenticated. # Create an AOR based on the auth_username for the location service. $var(saveuri) = "sip:" + $aU + "@" + $rd; # Set max_contacts limit via registration module reg xavp. if ($avp(debug) > 0) { xlog("L_INFO", "$cfg(route): Setting max_contacts to $avp(max_contacts) for $var(saveuri)\n"); } $xavp(reg=>max_contacts) = $avp(max_contacts); # Save Location! $var(result) = save("location","0x00","$var(saveuri)"); if ($var(result) == -2) { xlog("L_ERR", "$cfg(route): Too many contacts for $var(saveuri)\n"); sl_reply_error(); } if ($var(result) == -1) { xlog("L_ERR", "$cfg(route): Error saving location $var(saveuri)\n"); sl_reply_error(); } if ($var(result) == 1) { xlog("L_INFO", "$cfg(route): Contact $var(saveuri) inserted\n"); } if ($var(result) == 2) { xlog("L_INFO", "$cfg(route): Contact $var(saveuri) updated\n"); } if ($var(result) == 3) { xlog("L_INFO", "$cfg(route): Contact $var(saveuri) deleted\n"); } if ($var(result) == 4) { xlog("L_INFO", "$cfg(route): Contact $var(saveuri) returend\n"); } exit; } == snapp == $avp(max_contacts) is set to 1 Still, multiple registrations are possible for the $aU in question. What am I doing wrong? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 8

Re: [SR-Users] TLSv1.3 support
by Henning Westerholt 17 Aug '22

17 Aug '22

Hello, Please keep the list in CC. Regarding opening new TLS 1.3 connection, this should work, but did not tested it right now. If not, open an issue on our tracker. Regarding the option to restrict to only TSLv1.3 connection - I have added support for configuring this to git master version in commit 105600b3. Maybe you can give it a try, the patch should probably apply to 5.6.x branch. Cheers, Henning From: Helio <hok.sh10(a)gmail.com> Sent: Wednesday, August 17, 2022 2:52 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] TLSv1.3 support Regarding the full support, I would like to know if Kamailio can start a TLSv1.3 connection as a client. Another point is if we can restrict to accept only TLS v1.3 and not TLSv1.2 for instance. Thanks, Helio Em ter., 16 de ago. de 2022 às 11:45, Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> escreveu: Hello, not sure about the question about “full support”, maybe you can add details. Kamailio supports connection with TLSv1.3: $ openssl s_client -connect kam04.tst.domain.net:5061<http://kam04.tst.domain.net:5061> -tls1_3 2>&1 | tail -n 10 New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 4096 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) Cheers, Henning From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Helio Sent: Monday, August 15, 2022 8:01 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] TLSv1.3 support Hello, I noticed that Kamailio has option TLSv1.2+. Does the Kamailio support full TLSv1.3? Or does it have any restrictions? BR,

1 1

Kamailio not responding in heavy load
by Ali Taher 17 Aug '22

17 Aug '22

Hello all, I'm using sqlops module to connect to postgres and get the routing of calls from postgresql database. In order to troubleshoot issues in case they happened, I added each call details to Kamailio log. In some cases, when there is heavy traffic load (around 100 cps), I don't find some calls in Kamailio log, knowing that I can find them on the switch log (switch sending the invite packets to Kamailio). When checking the traces on these calls taken by the switch, it's clear that Kamailio is not responding to the invite packets sent by the switch. It could be because there are no available process to handle the call at this moment (I have set fork=14) Is it possible to check if there are calls pending in the queue? Regards,

2 1

Request rpms for 5.6.1
by Richard Chan 17 Aug '22

17 Aug '22

Hi kamailio team, I'd like to request that 5.6.1 be added to rpm.kamailio.org. Thanks! S-P Chan

3 3

TLSv1.3 support
by Helio 16 Aug '22

16 Aug '22

Hello, I noticed that Kamailio has option TLSv1.2+. Does the Kamailio support full TLSv1.3? Or does it have any restrictions? BR,

2 1

proper way for infinite loop in event_route for evrexec module
by Patrick Karton 16 Aug '22

16 Aug '22

Hello i would like to use the evrexec module to execute background jobs over exec module mainly because i want to be able to trigger that route manually via rpc from time to time. in the documentation its is stated we should use tasks that run forever and except using while loop i dont see another way. and i dont to want to disable max_while_loops. but if i disable it i will get error message like runaway while (1091, 9): more then 100 loops. so is there another way to do it properly ? Thanks.

4 5

Remove and Re add FROM in 200 OK sl reply
by Lewis Hutchinson 16 Aug '22

16 Aug '22

Hello All kamailio 5.5.3 KEMI Python Lab environemnt Is there a reason why this does not work? Lines 2 and 3 work but the removal of the initial From is not working on Line 1 1. KSR.hdr.remove("From") 2. KSR.hdr.append_to_reply("From: " +KSR.pv.gete("$fn") + " <"+KSR.pv.gete("$fu") + ">" + ";tag=" +KSR.pv.gete("$ft") + "--1234" + "\r\n") 3. KSR.sl.sl_send_reply(200, "OK") In a SUBSCRIBE/NOTIFY scenario I am trying to control the From Tag returned in the 200OK so I can use the same one in subsequent NOTIFY messages generated outside of Kamailio, my theory is use the From tag in the Subscribe and append it on the reply with -1234 for example (this is only in a Lab at this stage, any other options please let me know) Whenever I do this I end up with 2 From headers (see below) SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.67:5060;branch=z9hG4bK-f710a11a;rport=46404;received=xx.yy.xx.yy From: " testuser" sip:limeant30@sip.viazeta.com;tag=bf8745def06c7b12 To: <sip: testuser(a)sip.viazeta.com>;tag=47969b75f14e6954812863912d1cf21c.b5f3318f Call-ID: b21ba770-9b5836aa(a)192.168.1.67 CSeq: 18137 SUBSCRIBE Contact: "testuser" <sip:testuser@ xx.yy.xx.yy:46404> Expires: 3600 From: "testuser" sip:testuser@testbed.com;tag=bf8745def06c7b12--1234 Content-Length: 0 I have tried many many variations but the original From header always persists I have checked the debug logs and it says it has been removed Anyone know what I am missing? And how to get KSR.hdr.remove("From") to work. Looking in a debug log the header is removed. Lewis

2 3

Need help with multi mtree
by Benoît Panizzon 16 Aug '22

16 Aug '22

Heya I try to use mutli tree mtree to define multiple 'named' prefixes. id(int,auto) tname(string) tprefix(string) tvalue(string) 0:tech:+1:1 0:tech:+9:1 0:cust:+1:1 0:cust:+9:0 Kamailio is not complaining while loading this file, but mtree.summary shows no entries. Any hint on what I may be do wrong? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

Kamailio Configuration Help
by P. White 16 Aug '22

16 Aug '22

Hi All, Really sorry to bother everyone, but if possible, can I ask for a little help? I've been attempting to get Kamailio configured and working for some considerable time now (read: Years of occasional tinkering, and weeks of recent dedicated evening work) -- all without success. I have a sip trunk from sipgate, with two PSTN numbers assigned. My local network has a static external IP, with an internal private network. Currently I have Kamailio running within the intenal network along with two physical sip telephones (gigaset and an old grandstream), although I do have the option to put kamailio within a DMZ if necessary. Would anyone have a working config file that they could share please, permitting incoming and outgoing calls? With grateful thanks, Phil

2 1

Where to find DMQ protocol specification
by Илья Болмосов 15 Aug '22

15 Aug '22

Hello, we use DMQ module and we need to handle some events: 1) when peer joins cluster 2) when peer leaves cluster It will be helpful to know which content will be in KDMQ message in different cases. Tried to find any specification of KDMQ protocol, but didn't find it. Can you, please, help me with this?

2 1

Change reply code reason other than using change_reply_status
by Patrick Karton 12 Aug '22

12 Aug '22

hello is there a way to change reply code reason other than using () function. because the first parameterc of change_reply_status needs to be a constant so i can not use pseudo var for first argument of that function. so i use change_reply_status_code to change to code with a pseudo. but i would also to change the code reason.

3 3

remove_hf() does not remove the complete line
by Bernd Krueger-Knauber 11 Aug '22

11 Aug '22

Hi, I tried to remove a Via header line with: remove_hf("Via"); Original I have this 2 lines: Via: SIP/2.0/TCP xxx.xxx.xxx.xxx;branch=z9hG4bK370b.21720bb33c4f8264fde4e7994d288a57.0;i Via: SIP/2.0/TCP yyy.yyy.yyy.yyy:53967;received=yyy.yyy.yyy.yyy;rport=53967;branch=z9hG4bKPjxb0bdb2c9624076815f12937cc9e51d;alias If I insert remove_hf("Via"); in the cfg, I get: Via: SIP/2.0/TCP xxx.xxx.xxx.xxx;branch=z9hG4bK370b.21720bb33c4f8264fde4e7994d288a57.0;i ;received=yyy.yyy.yyy.yyy;rport=53967;branch=z9hG4bKPjxb0bdb2c9624076815f12937cc9e51d;alias Doesn't mattter if the command make sense or not, the result, in my opinion, is wrong. The INVITE packet has now an invalid header line. Any ideas? version: kamailio 5.6.1 (x86_64/linux) Best regards, Bernd

4 8

Kamailio has unconfined processes
by HimaBindu G 11 Aug '22

11 Aug '22

Hi, Problem Description: Customer security scan returned unconfined services on Kamailio. Unconfined processes run in unconfined domains Rationale: For unconfined processes, SELinux policy rules are applied, but policy rules exist that allow processes running in unconfined domains almost all access. Processes running in unconfined domains fall back to using DAC rules exclusively. If an unconfined process is compromised, SELinux does not prevent an attacker from gaining access to system resources and data, but of course, DAC rules are still used. SELinux is a security enhancement on top of DAC rules - it does not replace them Solution Investigate any unconfined processes found during the audit action. They may need to have an existing security context assigned to them or a policy built for them. Notes: Occasionally certain daemons such as backup or centralized management software may require running unconfined. Any such software should be carefully analyzed and documented before such an exception is made. See Also https://workbench.cisecurity.org/files/2485 For Kamailio ====== The command returned : 00 kamailio 00 kamailio 00 kamailio 00 kamailio 00 kamailio 10 kamailio 10 kamailio 10 kamailio 10 kamailio 00 kamailio 00 kamailio 00 kamailio 00 kamailio 33 kamailio 33 kamailio 33 kamailio 32 kamailio 17 kamailio 16 kamailio 33 kamailio 00 kamailio 00 kamailio 03 kamailio 05 kamailio 18 kamailio 17 kamailio 18 kamailio 18 kamailio 07 kamailio 00 sleep is any security context available to assign kamailio processes ? theses services can be run as confined services ? Please suggest us with resolution, thanks in advance. Thanks & Regards, Hima Bindu.

2 1

Kamailio World Conference - Sep 7-8, 2022 - Online
by Daniel-Constantin Mierla 10 Aug '22

10 Aug '22

For the 3rd year, we are planning an online version of Kamailio World Conference! At the beginning of 2022, the situation was not clear in terms of whether pandemic would decrease enough in intensity and we would be allowed to organize an on-site event late spring/beginner of summer, when the usual Kamailio Conference took place in Berlin, therefore we chose the safety path. But we hope that next year we will return in-person to the beautiful Berlin city center! The event this year, to happen in 4 weeks from now (Sep 7-8, 2022), follows the structure from previous edition, being two afternoons with presentations about Kamailio, sharing technical solutions and open discussions, allowing the community to interact and reconnect. The website of the event: - https://kamailioworld.com/k10-online/ There is no registration required, the event will happen on live video conferencing, also streamed to youtube. A text chatting channel will be made available as well. If you want to present, just send me the title and a short description -- we encourage community members to step forward and share their knowledge. It has to be related to Kamailio and fit within a 30min slot (including the questions). The agenda will be released in the near future. The event will be used also to celebrate 21 years of Kamailio project development, first commit being done on Sep 3, 2001. Two other major celebrations for 2022 to make the party bigger: - 20 years of open source for the project -- after one year of internal development, GPL was added on Sep 19, 2002 and source code was released to public - the 10th edition of Kamailio World Conference Book the dates in your agenda! I am looking forward to a very interesting event and (re-)connecting with many of you! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

set source port of TCP socket in Contact header
by Maarten Ureel 09 Aug '22

09 Aug '22

Hello I want to set the correct source port in an outgoing message over TCP. Is it possible? I can't find a pseudo-variable for this. Currently we have no port number in the contact header, and the other party is sending their BYE to port 5060 instead of to the source port from which the outgoing TCP connection was made. Regards Maarten

2 5

Syncing Registration Database across Kamailio Pairs
by harneet singh 09 Aug '22

09 Aug '22

Hi Experts, We have been using Kamailio in an Active/Standby Pair(with Keepalived under the rugs moving the single Virtual IP to access the Active Kamailio) for sometime now. *Kamailio also acts as a Registrar for our webrtc endpoints. * It has been serving the purpose pretty well and now we have a requirement where we need to be syncing the Registration DB between Two Pairs of Kamailios. Kamailio-Active(*Pair 1*) -------- Kamailio-Standby(*Pair 1*) || Kamailio-Active(*Pair 2*) -------- Kamailio-Standby(*Pair 2*) We generally keep the counterpart in the same Pair as a notifier( *modparam("dmq", "notification_address", "sip:PEER1_IP:5060")* ) so as to sync the dialogs and the userloc data too( *modparam("dmq_usrloc", "enable", 1) * ). In order to achieve the said requirement with the other Pair, we added another "*notification_address*" in the kamailio cfg. At this point, we ran into weird issues. *1. *With Kamailio ver *5.3.2, *the subsequent *notification_address *line in the cfg file, seemed to be overriding the previous one. Hence we see only the latter peer in the dmq list nodes. Example: modparam("dmq", "notification_address", "sip:*172.27.45.77* :5090") modparam("dmq", "notification_address", "sip:*172.27.45.200* :5090") In this case, the "*kamcmd dmq.list_nodes*" would show the local Machine and 172.27.45.200 as the only nodes in the output, ie *172.27.45.77 is not showing up at all,* which is problematic, since the local machine(172.27.45.243 in our case) would not been able to send any dmq sync info to its peer(172.27.45.77) in the same Pair. To see if the above issue might have been addressed in later release, we upgraded to the latest Kamailio ver *5.6.0* *To our respite, the above issue no longer exists in the new version*(though not sure which immediate release after v 5.3.2 it would have been initially fixed.) This is where we have a new issue explained below: *2. *The registration data does get synced to the peer Kamailio in the same Pair, and also to the Kamailio instances in the other Pair. However, the *Socket* Parameter in "*kamctl ul show*" output shows *[not set] *even on the side where the websocket connection actually exists. [root@localhost ~]# *kamctl ul show * { "jsonrpc": "2.0", "result": { "Domains": [{ "Domain": { "Domain": "location", "Size": 1024, "AoRs": [{ "Info": { "AoR": "9008077221", "HashID": 1952082106, "Contacts": [{ "Contact": { "Address": "sip:Harneet_qifir@172.24.58.210", "Expires": 159, "Q": -1, "Call-ID": "vfli2uv8du3ppda73q5ppe", "CSeq": 106, "User-Agent": "EngageDigital", "Received": "sip:172.27.44.252:60070;transport=ws", "Path": "[not set]", "State": "CS_NEW", "Flags": 0, "CFlags": 0, * "Socket": "[not set]", <<<<<<<<<<<<<<<<<<<<<<* "Methods": 7071, "Ruid": "uloc-62f26e3b-2677-1", "Instance": "<urn:uuid:4fbd3e96-b4de-497b-886d-1ca8ffa016a4>", "Reg-Id": 1, "Server-Id": 0, "Tcpconn-Id": -1, "Keepalive": 0, "Last-Keepalive": 1660063892, "KA-Roundtrip": 0, "Last-Modified": 1660063892 } }] } } ], In order to confirm that the socket actually exists on this Kamailio instance, I am pasting the below outputs from the same machine, where ws dump and even the native netstat confirms that. [root@localhost ~]# *netstat -tunelap | grep 60070* tcp 0 0 172.27.45.199:8080 172.27.44.252:*60070* *ESTABLISHED* 994 17322355 16230/kamailio [root@localhost ~]# *kamcmd ws.dump* { connections: { 1: ws:172.27.44.252:*60070* -> ws:172.27.45.199:8080 (state: *OPEN*, last used 24s ago, sub-protocol: sip) } info: { wscounter: 1 truncated: no } } We do need to distinguish the actual Kamailio instance where the websocket connection actually exists, so as to route the call ahead from the same instance, or if it does not exist(and it's merely a sync'ed registration data received over DMQ Channel), then the Kamailio should route the call ahead to the Kamailio instance in the other Pair, which can then route it ahead to the Registered webrtc endpoint. We were hoping to use the Socket Parameter output, but for the said problem, unable to use the same as an indicator. *So what would be the best way to identify which Kamailio has the websocket connection with the Actual endpoint*? Should we rely on the output of netstat or ws.dump to infer that? I mean this needs to be done in kamailio.cfg for each call, so want to know the best way, or if there is completely different approach that can be suggested? Apologies for the long email, but any pointers will be much helpful. Thanks & Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 1

recompute distribution list
by David Villasmil 08 Aug '22

08 Aug '22

Hello guys, Is it possible to have dispatcher recompute the distribution list? i.e. one server goes down, all traffic for that server goes to the next one, doubling traffic on that one. Is there a way of, when a host becomes unreachable, recompute the whole list? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 7

Contact header modification - Kamailio
by Ankit Jayswal 04 Aug '22

04 Aug '22

Hello Team, I am in need to modify the contact header in Kamailio before sending an INVITE request to the SIP trunk provider. Basically the IP address I need to modify in the contact header. Please suggest a better way to do this. Below is an example. *OLD (Existing):* Contact: <sip:009169240xxx@*45.118.162.x:5080*;alias=10.52.26.102~5080~1> *NEW (Needed):* Contact: <sip:00912269240xxx@*10.52.26.98:5060 <http://10.52.26.98:5060>*> I tried various functions from the textops module but no hope. I am looking for a function that can replace the contact header's value. Please help me with this. -- Thanks & Regards, *Ankit Jayswal* | Specialist - Software Development

4 13

Support of ECDHE cipher suites for tls connection in kamailio
by Илья Болмосов 03 Aug '22

03 Aug '22

Hello. I have a question about support of ECDHE cipher suites in kamailio-5.6.0 in centos7 with installed OpenSSL 1.0.2k-fips. We received kamailio with its modules from https://rpm.kamailio.org/. Our client can use only cipher suites: TLS_AES_256_GCM_SHA384 (0x1302) TLS_CHACHA20_POLY1305_SHA256 (0x1303) TLS_AES_128_GCM_SHA256 (0x1301) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) And some of them are supported by our openssl: $ openssl cipher -V ... 0xC0,0x14 - ECDHE-RSA-AES256-SHA SSLv3 Kx=ECDH Au=RSA Enc=AES(256) Mac=SHA1 0xC0,0x0A - ECDHE-ECDSA-AES256-SHA SSLv3 Kx=ECDH Au=ECDSA Enc=AES(256) Mac=SHA1 ... 0xC0,0x13 - ECDHE-RSA-AES128-SHA SSLv3 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA1 0xC0,0x09 - ECDHE-ECDSA-AES128-SHA SSLv3 Kx=ECDH Au=ECDSA Enc=AES(128) Mac=SHA1 ... But when trying to connect with, for example, cipher suite ECDHE-RSA-AES256-SHA (the same with other 3 cipher suites), we receive, that it is not allowed: $ openssl s_client -connect ${kamailio-serper-ip}:${kamailio-server-port} -cipher ECDHE-RSA-AES256-SHA ... SSL handshake has read 7 bytes and written 121 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 ... To exclude the influence of other factors, I installed nginx on the same machine with usage of the same tls certificate and it can use cipher suites ECDHE-RSA-AES256-SHA and ECDHE-RSA-AES128-SHA. $ openssl s_client -connect ${nginx-serper-ip}:${nginx-server-port} -cipher ECDHE-RSA-AES256-SHA ... SSL handshake has read 3271 bytes and written 406 bytes Verification: OK --- New, TLSv1.0, Cipher is ECDHE-RSA-AES256-SHA Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-SHA ... So, the reason of failed handshake is, probably, kamailio. Tried to add cipher_list modparam: modparam("tls", "cipher_list", "ECDHE-RSA-AES256-SHA") but result is the same: $ openssl s_client -connect ${kamailio-serper-ip}:${kamailio-server-port} -cipher ECDHE-RSA-AES256-SHA ... SSL handshake has read 7 bytes and written 121 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 ... Can you, please, help me to add support of cipher suites ECDHE-RSA-AES256-SHA and ECDHE-RSA-AES128-SHA to kamailio?

2 1

Newbie - Installation Issue - ERROR: could not load the script in /usr/lib/kamailio//kamctl/kamdbctl.mysql for database engine MYSQL
by p.t.crossley＠gmail.com 02 Aug '22

02 Aug '22

I suspect this must have been addressed before but I couldn't find a way of searching Archives. I'm using Alpine Linux. Used "apk add kamailio" to install Kamailio 5.5.4-r1 Following the Instructions on https://kamailio.org/docs/tutorials/5.5.x/kamailio-install-guide-git/ At the section for "Creating MySQL database" I modify the file and then run kamdbctl create ERROR: could not load the script in /usr/lib/kamailio//kamctl/kamdbctl.mysql for database engine MYSQL ERROR: database engine not loaded - tried 'MYSQL' I checked the /usr/lib/kamailio//kamctl/ directory and the file wasn't there I suspect I'm missing a module but there aren't any other packages listed for Kamailio at pkgs.alpinelinux.org Thanks for your help P Crossley

3 2

Limit cps per destination gw
by Jon Bonilla (Manwe) 02 Aug '22

02 Aug '22

Hi I'm thinking on having a cps preference for each pstn gw that I can check. I've started thinking in the pike module but it won't allow me to set custom cps per peer. seems that the threshold is global. Ratelimit module needs the queues to be set as modparam, not dynamic AFAICS. Any hints? cheers, Jon -- PekePBX, the multitenant PBX solution https://pekepbx.com

6 8

Sharing Database between three kamailios
by Waqar 40 01 Aug '22

01 Aug '22

I have three Kamailios in three different servers which are dispatching calls to 9 asterisks in three different servers using load balancing. All these Kamailios are using databases installed on that servers. As the entries of the dispatcher table are the same for all the Kamailio, so I want that these Kamailio use a single database installed on one of the servers. All these Kamailios instances should use the same database which is common between them. And also I want these Kamailios to write into the database by creating a table that stores all the active calls in three Kamailios. Is it possible? How can I do it? Please guide me with somewhat explanation as I am not this much expert in Kamailio. Waiting for a quick response. Regards VoIP Engineer Vicky

3 3

Kamailio behind NAT
by Алексей Якимкин 29 Jul '22

29 Jul '22

Hello, I have kamailio in local network behind NAT. Kamailio have one interface eth1 with ip 10.130.0.23 UserAgent - (internet) - (178.0.0.169)router_with_NAT - (LAN) - kamailio+rtpproxy - pbx I made two listeners: listen=udp:10.130.0.23:5070 #to pbx in lan (I don`t want to put via header with 178.0.0.169) listen=udp:10.130.0.23:5060 advertise 178.0.0.169:5060 #to internet (UserAgent need to get via header with 178.0.0.169 ) mhomed = 1 # I think It not useful for my case UserAgent send Register and Invite to 178.0.0.169:5060, Kamailio get it on udp:10.130.0.23:5060 Kamailio Relay it to udp:10.130.0.23:5070 My pbx get requests from udp:10.130.0.23:5070 with via header 10.130.0.23 Responses to UserAgent go from udp:10.130.0.23:5060 with via 178.0.0.169 In RELAY block: if ($Ru == «udp:10.130.0.23:5070») { #set_send_socket(«udp:10.130.0.23:5060»); $fs = «udp:10.130.0.23:5060»; #force_send_socket(«udp:10.130.0.23:5060»); } else { #set_send_socket(«udp:10.130.0.23:5070»); $fs = «udp:10.130.0.23:5070»; } #$fs = «udp:10.130.0.23:5070»; if (!t_relay()) { sl_reply_error(); } route[REGISTRAR] { if ($rd == "mydomain.ru" || $rd == "mydomain2.ru") { set_send_socket("udp:10.130.0.23:5070"); } } It works for requests from UserAgent to PBX. But INVITE from my pbx to UserAgent goes only through udp:10.130.0.23:5070 , Kamailio realy it to internet from udp:10.130.0.23:5070 I get error in syslog: (pv [pv_branch.c:62]: pv_get_branchx_helper(): error accessing branch [0]) I tried set_send_socket(«udp:10.130.0.23:5070»); and $fs = «udp:10.130.0.23:5070»; Why I can`t relay outgoing requests to internet through another socket? -- Best regards, Alex

3 6

[REGISTRAR] Registered. How to match $sut to usrloc received ?
by Richard Edmands 29 Jul '22

29 Jul '22

Hey Kamailio Users, So the scenario is we get the registers. Load them, slightly oddly as we also fill in the received section, not something I usually do. Then when they send an invite, the To and From headers are real phone numbers and for some reason the contact header isn't their username. So to compensate for that I'm trying to match their connection ($sut) using registered, but after a couple of hours I haven't been able to get it to match up. Not sure what I'm missing. ul.dump gets me Received: sip:sipclientpublicip:2353;transport=udp so we know that part is loading $sut correctly into the user location data. modparam("usrloc", "matching_mode", 2) modparam("registrar", "xavp_rcd", "ulrcd") modparam("registrar", "received_avp", "$avp(i:42)") $xavp(regcfg=>match_received) = $sut; if (registered("location","$sut", 2, 1)) { After that block of code $sut is sip: sipclientpublicip:2353;transport=udp which is what's in usrloc for received, but it's not match. There's probably a much smarter way of doing this that I've completely missed, if so then that'd be excellent. But if I'm on the right path somewhat then it would be great to get this working.

2 3

[UAC] How to get the outbound registration status of uac.reg_active?
by Denys Pozniak 28 Jul '22

28 Jul '22

Hello! I have several Kamailio sharing a common uacreg table and use the RPC interface to enable and disable outgoing registration on nodes depending on the cluster status: *kamcmd uac.reg_active 0kamcmd uac.reg_active 1* https://kamailio.org/docs/modules/stable/modules/uac.html#uac.r.uac.reg_act… How can I get the current status of uac outbound registration (to get 0 or 1)? -- BR, Denys Pozniak

2 3

Re: [SR-Users] TLS connection failure. Not sure if system behavior is correct.
by Ahmed Fouad 27 Jul '22

27 Jul '22

Hi, You are currently using TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384 256 Teams stopped TLSv1/ TLSv1.1 and only allowing TLS1.2+ So change your TLS settings to enforce it only method = TLSv1.2+ after restarting kamailio your teams connections should be good.

1 0

ACC CDR accounting
by Oleg Podguyko 27 Jul '22

27 Jul '22

HI I’m trying to get CDR function. I would like to have one CDR for whole call at the syslog. I use: …… loadmodule "db_text.so" loadmodule "dialog.so" loadmodule "acc.so" …….. # -----Dialog module ----- modparam("dialog", "db_mode", 0) # -----ACCounting module ----- modparam("acc", "early_media", 0) modparam("acc", "report_cancels", 1) modparam("acc", "log_facility", "LOG_LOCAL1") modparam("acc", "detect_direction", 0) modparam("acc", "log_level", ACC_LOG_LEVEL) modparam("acc", "log_flag", FLAG_ACC_LOG) modparam("acc", "log_missed_flag", FLAG_ACC_LOG_MISSED) modparam("acc", "failed_transaction_flag", FLAG_ACC_LOG_FAILED) modparam("acc", "log_extra", "ip_src=$si;ip_dst=$avp(ip_dst);sip_from=$fU;sip_to=$tU;ruri_user=$rU;spx_rs=$avp(spx_http_rs)") ## TODO modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_enable_log", 1) modparam("acc", "cdr_facility", "LOG_LOCAL1") request_route { if (is_method("INVITE")) { setflag(FLAG_ACC_LOG); setflag(FLAG_ACC_LOG_MISSED); setflag(FLAG_ACC_LOG_FAILED); } At the kamailio.log I see only transaction for INVITE, but I wait for some CDR for all dialog. Whats wrong in my config? -- -- Олег Подгуйко

3 9

Cannot load usrloc table at startup using DMQ_USRLOC sync feature
by Benedito Marques 25 Jul '22

25 Jul '22

I have an scenario with two kamailios, and no databases. At the first, I authenticate one subscriber successfully and save in memory usrloc: /etc/kamailio # kamailio --version version: kamailio 5.4.4 (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 on 16:13:18 Feb 15 2021 with gcc 9.3.0 /etc/kamailio # /etc/kamailio # --- /etc/kamailio # cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.12.3 PRETTY_NAME="Alpine Linux v3.12" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://bugs.alpinelinux.org/" --- # Handle SIP registrations route[REGISTRAR] { if (!is_method("REGISTER")) return; if (!save("location","0x05")) { sl_reply_error(); } exit; } -- /etc/kamailio # kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 1024 AoRs: { Info: { AoR: 1014(a)my.domain HashID: -1989102610 Contacts: { Contact: { Address: sip:1014@10.0.0.2:7071;ob Expires: 299 Q: -1.000000 Call-ID: d5cf6d5f293647a59ba64ba996a793b0 CSeq: 43689 User-Agent: MicroSIP/3.20.7 Received: sip: 10.0.0.2:7071 Path: [not set] State: CS_NEW Flags: 1 CFlags: 0 Socket: [not set] Methods: 8159 Ruid: uloc-62d95ca2-3c-1 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 0 Last-Keepalive: 1658412252 KA-Roundtrip: 0 Last-Modified: 1658412252 } } } } Stats: { Records: 1 Max-Slots: 1 } } } } /etc/kamailio # *The problem is*: when I start the second kamailio server, the current usrloc users are not replicated to it, so in the second server the usrloc is empty: /etc/kamailio # kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 1024 AoRs: { } Stats: { Records: 0 Max-Slots: 0 } } } } *The modules loaded:* - dmq.so - dmq_usrloc.so *Params (sync enabled):* modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) modparam("dmq_usrloc", "usrloc_domain", "location") modparam("dmq_usrloc", "usrloc_delete", 1) modparam("dmq_usrloc", "replicate_socket_info", 0) *Obs*: The DMQ replication is working perfectly. So, if I register another user in server 1, server 2 receives the KDMQ message and the new user appears on usrloc. The real problem is to load pre registered users at startup. *Log messages from second server at startup:* 0(51) DEBUG: <core> [core/sr_module.c:873]: init_mod(): dmq_usrloc 0(51) INFO: dmq_usrloc [dmq_usrloc.c:81]: mod_init(): dmq usrloc replication mode = 1 0(51) DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <ul_bind_usrloc> in module usrloc [/usr/lib/kamailio/modules/usrloc.so] 0(51) DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <bind_dmq> in module dmq [/usr/lib/kamailio/modules/dmq.so] 0(51) DEBUG: dmq_usrloc [usrloc_sync.c:286]: usrloc_dmq_initialize(): loaded dmq api 0(51) DEBUG: dmq_usrloc [usrloc_sync.c:299]: usrloc_dmq_initialize(): dmq peer registered 0(51) DEBUG: dmq_usrloc [dmq_usrloc.c:111]: mod_init(): dmq_usrloc initialized 0(51) DEBUG: <core> [core/sr_module.c:804]: init_mod_child(): idx 0 rank -127: dmq_usrloc [main] 0(51) DEBUG: dmq_usrloc [dmq_usrloc.c:127]: child_init(): child_init PROC_INIT 7(62) DEBUG: dmq_usrloc [usrloc_sync.c:552]: usrloc_dmq_request_sync(): requesting sync from dmq peers 0(51) DEBUG: <core> [core/sr_module.c:804]: init_mod_child(): idx 0 rank 0: dialog [main] 7(62) DEBUG: dmq_usrloc [usrloc_sync.c:568]: usrloc_dmq_request_sync(): sending serialized data {"action":3} 7(62) DEBUG: dmq_usrloc [usrloc_sync.c:317]: usrloc_dmq_send(): sending dmq broadcast... 7(62) DEBUG: dmq [dmq_funcs.c:166]: bcast_dmq_message1(): skipping node sip:10.0.2.38:5090 7(62) DEBUG: dmq [dmq_funcs.c:166]: bcast_dmq_message1(): skipping node sip:10.0.2.30:5090 7(62) DEBUG: dmq [dmq_funcs.c:166]: bcast_dmq_message1(): skipping node sip:0.0.0.0:5090 *List nodes at SERVER 1:* /etc/kamailio # kamcmd dmq.list_nodes { host: 10.0.1.36 port: 5090 resolved_ip: 10.0.1.36 status: active last_notification: 0 local: 0 } { host: 10.0.1.35 port: 5090 resolved_ip: 10.0.1.35 status: active last_notification: 0 local: 0 } { host: 0.0.0.0 port: 5090 resolved_ip: 0.0.0.0 status: active last_notification: 0 local: 1 } *List nodes at SERVER 2:* /etc/kamailio # kamcmd dmq.list_nodes { host: 10.0.1.35 port: 5090 resolved_ip: 10.0.1.35 status: active last_notification: 0 local: 0 } { host: 10.0.1.36 port: 5090 resolved_ip: 10.0.1.36 status: active last_notification: 0 local: 0 } { host: 0.0.0.0 port: 5090 resolved_ip: 0.0.0.0 status: active last_notification: 0 local: 1 } -- Att, Benedito Marques

2 2

Job oportunitie
by Jaime Gajardo 24 Jul '22

24 Jul '22

Hello, We are seeking Engineers with some experience in open source VoIP solutions like Kamilio, Asterisk, etc. The opportunity is remote in Latin america. We are a Chilean company dedicated to giving different solutions for customer service on cloud. is you are interested please send us an email to alejandro(a)elipse.ai Thank you!!

2 1

db.c can't find dp_postgressql
by Phillip Thern 23 Jul '22

23 Jul '22

so, I don't actually know if my previous message found you, or if you replied, since my syslog suddenly grew to 26 GB and my server couldn't receive any mail because of it... Description I loaded module "db_postgres.so". I expected kamilio to start. It didn't Troubleshooting Reproduction config file |#!KAMAILIO #!define WITH_POSTGRESSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_MSGREBUILD #!define WITH_NAT #!define WITH_NATSIPPING . . . #!ifdef WITH_POSTGRESSQL loadmodule "db_postgres.so" #!endif | Log Messages |Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [db.c:204]: db_bind_mod(): Module db_postgresql not found. Missing loadmodule? Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: usrloc [usrloc_mod.c:361]: mod_init(): failed to bind database module Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so) | output from ls of modules directory: |acc.so call_obj.so dialog.so ipops.so msrp.so presence_conference.so qos.so sipcapture.so statsd.so uid_avp_db.so acc_diameter.so carrierroute.so dialplan.so jsonrpcs.so mtree.so presence_dialoginfo.so ratelimit.so sipdump.so stun.so uid_domain.so alias_db.so cfg_db.so dispatcher.so keepalive.so nat_traversal.so presence_mwi.so regex.so sipjson.so tcpops.so uid_gflags.so app_jsdt.so cfg_rpc.so diversion.so kemix.so nathelper.so presence_profile.so registrar.so sipt.so textops.so uid_uri_db.so app_sqlang.so cfgt.so dmq.so kex.so nosip.so presence_reginfo.so rls.so siptrace.so textopsx.so uri_db.so async.so cfgutils.so dmq_usrloc.so lcr.so outbound.so presence_xml.so rr.so siputils.so timer.so userblocklist.so auth.so corex.so domain.so log_custom.so p_usrloc.so pua.so rtimer.so sl.so tm.so usrloc.so auth_db.so counters.so domainpolicy.so lrkproxy.so path.so pua_bla.so rtjson.so sms.so tmrec.so xcap_client.so auth_diameter.so ctl.so drouting.so mangler.so pdb.so pua_dialoginfo.so rtpengine.so smsops.so tmx.so xcap_server.so auth_xkeys.so db2_ops.so enum.so matrix.so pdt.so pua_reginfo.so rtpproxy.so speeddial.so topoh.so xhttp.so avp.so db_cluster.so evrexec.so maxfwd.so permissions.so pua_rpc.so sanity.so sqlops.so topos.so xhttp_prom.so avpops.so db_flatstore.so exec.so mediaproxy.so pike.so pua_usrloc.so sca.so ss7ops.so tsilo.so xhttp_rpc.so benchmark.so db_postgres.so group.so mohqueue.so pipelimit.so pua_xmpp.so sdpops.so sst.so uac.so xlog.so blst.so db_text.so htable.so mqueue.so prefix_route.so pv.so seas.so statistics.so uac_redirect.so xprint.so call_control.so debugger.so imc.so msilo.so presence.so pv_headers.so secfilter.so statsc.so uid_auth_db.so | Possible Solutions tried renaming db_postgres.so to db_postgresql.so, but that didn't work, so I reversed it Additional Information * *Kamailio Version* - output of |kamailio -v| |version: kamailio 5.5.4 (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_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: unknown compiled with gcc 10.2.1 | * *Operating System*: |Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux opensips 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux |

2 1

uac replace PRACK trouble
by Алексей Якимкин 22 Jul '22

22 Jul '22

Hello, pbx -> kamailio -> provider kamailio registers (uacreg) on provider. When I call through my provider I need to change headers To From and PAI. I tried with uac_replace_from and uac_replace_to. $tU for example 0987656789 if($fU=~"1234567") { uac_replace_from("sip:provider_login@provider.com"); uac_replace_to("sip:$tU@provider.com"); } My provider answers on Invite with 183 progress, so pbx answers with PRACK. Kamailio change To and from like this: To: <sip:0987656789@provider.comsip:0987656789@provider.com>;tag=..... To: <sip:0987656789@provider.comsip:0987656789@provider.com> From: <sip:provider_login@provider.comsip:provider_login@provider.com >;tag=..... From: <sip:provider_login@provider.comsip:provider_login@provider.com> Is it a bug? I tried to disable this modification for PRACK u REQINIT ($csb != "2 PRACK") It haven't worked for me. I solved this issue with this code. remove_hf("From"); if ($ft == $null) { insert_hf("From: <sip:provider_login@provider.com>\r\n", "To"); } else { insert_hf("From: <sip:provider_login@provider.com>;tag=$ft\r\n", "To"); } version: kamailio 5.7.0-dev0 (x86_64/linux) Ubuntu 18 -- Regards, Alex

1 0

Module db_postgresql not found
by Phillip Thern 22 Jul '22

22 Jul '22

Description I loaded module "db_postgres.so". I expected kamilio to start. It didn't Troubleshooting Reproduction config file |#!KAMAILIO #!define WITH_POSTGRESSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_MSGREBUILD #!define WITH_NAT #!define WITH_NATSIPPING . . . #!ifdef WITH_POSTGRESSQL loadmodule "db_postgres.so" #!endif | Log Messages |Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [db.c:204]: db_bind_mod(): Module db_postgresql not found. Missing loadmodule? Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: usrloc [usrloc_mod.c:361]: mod_init(): failed to bind database module Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so) | output from ls of modules directory: |acc.so call_obj.so dialog.so ipops.so msrp.so presence_conference.so qos.so sipcapture.so statsd.so uid_avp_db.so acc_diameter.so carrierroute.so dialplan.so jsonrpcs.so mtree.so presence_dialoginfo.so ratelimit.so sipdump.so stun.so uid_domain.so alias_db.so cfg_db.so dispatcher.so keepalive.so nat_traversal.so presence_mwi.so regex.so sipjson.so tcpops.so uid_gflags.so app_jsdt.so cfg_rpc.so diversion.so kemix.so nathelper.so presence_profile.so registrar.so sipt.so textops.so uid_uri_db.so app_sqlang.so cfgt.so dmq.so kex.so nosip.so presence_reginfo.so rls.so siptrace.so textopsx.so uri_db.so async.so cfgutils.so dmq_usrloc.so lcr.so outbound.so presence_xml.so rr.so siputils.so timer.so userblocklist.so auth.so corex.so domain.so log_custom.so p_usrloc.so pua.so rtimer.so sl.so tm.so usrloc.so auth_db.so counters.so domainpolicy.so lrkproxy.so path.so pua_bla.so rtjson.so sms.so tmrec.so xcap_client.so auth_diameter.so ctl.so drouting.so mangler.so pdb.so pua_dialoginfo.so rtpengine.so smsops.so tmx.so xcap_server.so auth_xkeys.so db2_ops.so enum.so matrix.so pdt.so pua_reginfo.so rtpproxy.so speeddial.so topoh.so xhttp.so avp.so db_cluster.so evrexec.so maxfwd.so permissions.so pua_rpc.so sanity.so sqlops.so topos.so xhttp_prom.so avpops.so db_flatstore.so exec.so mediaproxy.so pike.so pua_usrloc.so sca.so ss7ops.so tsilo.so xhttp_rpc.so benchmark.so db_postgres.so group.so mohqueue.so pipelimit.so pua_xmpp.so sdpops.so sst.so uac.so xlog.so blst.so db_text.so htable.so mqueue.so prefix_route.so pv.so seas.so statistics.so uac_redirect.so xprint.so call_control.so debugger.so imc.so msilo.so presence.so pv_headers.so secfilter.so statsc.so uid_auth_db.so | Possible Solutions tried renaming db_postgres.so to db_postgresql.so, but that didn't work, so I reversed it Additional Information * *Kamailio Version* - output of |kamailio -v| |version: kamailio 5.5.4 (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_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: unknown compiled with gcc 10.2.1 | * *Operating System*: |Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux opensips 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux |

1 0

incomplete values and Wrong Counting for $hfl and $hflc
by Patrick Karton 21 Jul '22

21 Jul '22

the counting and values provided by $hfl and $hflc are wrong and incomplete from my understanding. looking at the source code these pseudo vars count the body values of Via, Record-Route and Route headers. in kamalio 5.6.1 with Record-Route: <sip:1.1.1.1;lr=on;nat=yes> Record-Route: <sip:2.2.2.2:5060;lr;transport=udp>,<sip:3.3.3.3:22506;lr;transport=udp> i get $hflc(Record-Route) == 2 instead of 3 and $(hfl(Record-Route)[0]) == 1.1.1.1 $(hfl(Record-Route)[1]) == 2.2.2.2 $(hfl(Record-Route)[3]) does not exists.

2 2

Using Kamailio with Teams
by Javier González Muñoz 21 Jul '22

21 Jul '22

Hi, I'm using kamailio with Teams like SBC and asterisk. Works perfectly less one thing. When I make a call asterisk to Teams, in my Teams app I see 3 popup notifications, and 3 calls in my history. If I call Teams to Asterisk, perfect.. When I make an asterisk to Teams call, I get the trace from Asterisk and I can see three 180, I don't know if this is the problem, but are there any way to fix it? Limit to 1 notification? Thanks

2 1

iterate trough all Record-Route values via @hf_value.Record_Route
by Patrick Karton 21 Jul '22

21 Jul '22

Hello All, i would to iterate through all ips in Record-Route through @hf_value.Record_Route. if i put static index like @hf_value.Record_Route[0] it works. but $var(i) = 0; @hf_value.Record_Route[$var(i)] does not work. is there a way to get the count of all headers values through @hf_value.Record_Route For example i would like to iterate through all Record-Route Values if i receive it like this Record-Route: <sip:1.1.1.1;lr=on;nat=yes> Record-Route: <sip:2.2.2.2:5060;lr>,<sip:3.3.3.3:22506;lr>

2 2

siremis installation
by Fernando Piana 19 Jul '22

19 Jul '22

hello, My name is Fernando Piana from Colombia. I am writing to you because I am testing Kamailio together with the Siremis graphical environment. I was visiting the siremis.org website and also the siremis wiki, but I couldn't find the administration manual. >From this medium I want to ask you if you can send me a copy of the Siremis administration manual. I await a response. Thank you very much. -- Fernando Piana Ing. Comunicaciones y Bases de Datos Cel: +57 311 641 7558

2 1

Using usrloc db_insert_update in a dmq replicated environment with shared db ?
by Matteo Brancaleoni 19 Jul '22

19 Jul '22

Hi, I was wondering if it is safe from a cache consistency pow to enable usrloc db_insert_update in a dmq replicated environment, where all registrars share the same db. I'm already using the filter option to avoid loading/deletion by server id, but there's no similar option for writing. I know that it is possible to use db mode 4 on all registrars (which get synced by dmq) except one, which will be responsible for writing, but this creates a little unbalanced setup in addition to performing writes only from one proxy. Any hint? Maybe is time to check how to filter writes, too :) ? Thanks, Matteo

1 0

How to externally trigger htable cache flushing?
by Benoit Panizzon 18 Jul '22

18 Jul '22

Hi List We cache stuff like call forwarding information in a htable cache to minimizie SQL lookups and have it available via DMQ on all instances. But of course, if the call forwarding information for a destination changes in the database, we would like to flush either the whole cache, or even better, that single entry. What is the best way to do this? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 3

dialog timeout_avp no longer works?
by Alex Balashov 18 Jul '22

18 Jul '22

Hi, I discovered recently that, on Kamailio 5.5.4 at least, the dialog ’timeout_avp’ no longer appears to have effect. Here are my (seemingly relevant) dialog parameters: modparam("dialog", "enable_stats", 0) modparam("dialog", "hash_size", 4096) modparam("dialog", "rr_param", "dlgcor") # DLG "correlator" modparam("dialog", "dlg_flag", 2) modparam("dialog", "default_timeout", 28800) # 8 hours modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "table_name", "dialog") modparam("dialog", "send_bye", 1) modparam("dialog", "wait_ack", 0) modparam(“dialog”, “timeout_avp”, “$avp(dlg_timeout)”) The flow is roughly like this: request_route { ... t_check_trans(); if(is_method(“INVITE”)) { ... dlg_manage(); $avp(dlg_timeout) = 10; ... if(!t_relay()) sl_reply_error(); return; } I was able to resolve the problem by switching to dlg_set_timeout() instead, but I wonder if there has been a regression. Last version I have on which this positively works is 4.4.7, though, so not sure when it might have broken. One nuance: $avp(dlg_timeout) is not initialised prior to calling dlg_manage(), and the value is only set if certain conditions are true. Not sure if some stricter check appeared in later releases which could cause this to be a problem. Thank you! — Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 3

Nathelper sip ping and Path support ?
by matteo brancaleoni 18 Jul '22

18 Jul '22

Hello, I'm trying to setup the following scenario with sip ping: UAC -> Kamailio Edge -> Kamailio Registrar Edge proxy is a multihomed proxy with public/private ips and the registrar is a kamailio on a private network. The edge acts as a nat proxy and loadbalancer. Edge proxy inserts a Path header (and contact alias) which get correctly saved on registrar usrloc. Registration works as expected. Now, since I need to keep nat open towards the uacs and expire them when they're not reachable anymore, I'm trying to send sip pings from the registrar via the edge proxy. I'm using nathelper sipping in the registrar. What I see is that the registrar sends out a sip options putting in the Route header the Path as expected, but the sip packet gets sent directly to the UAC contact and not via the edge, as the Route header specifies. After looking into the nathelper code, it seems that the sip packet is sent via udp directly without any specific routing. So the question: it should work what I'm trying to achieve? Maybe not? Probably I can work around it setting the ;received in the contact on registrar (it will set to the edge proxy) and since the contact is aliased on the edge when the edge receives an option from the registrar it can process the alias and send it to the correct endpoint, but seems a workaround? Or using the keepalive module maybe, even if that means setting specific timers and manually do what the nathelper module already does? Any hint? Thanks, Matteo

3 2

Does pure outbound RFC5626 work without edge proxies?
by Richard Chan 17 Jul '22

17 Jul '22

Hi sr-users, Does pure RFC5626 outbound work without an edge proxy->internal proxy design? By "pure" I mean no nathelper to rewrite addresses. I tried setting up the following: Configuration: use standard kamailio configuration without WITH_NAT (Ignore RTP-rtpengine/rtpproxy for the moment as I am just testing the control plane) 1. UA1 UA2 each behind NAT, with bogus Contact: headers 2. kamailio loaded with rr/tm (no outbound/path because I am using single proxy/registrar — without edge proxies) 3. no nathelper: no Contact rewriting, set_contact_alias etc 4. Both UA1 and UA2 establish persistent TLS to kamailio 5. INVITE/200 OK/ACK does work. 6. Contact headers show the NAT bogus addresses (as expected). UA1/UA2 are configured to be "dumb"(i.e. don't self-rewrite Contact:/SDP based on rport/received). Problem: 7. In-dialog requests don't work as kamailio tries to route to the bogus addresses per the Contact header. I.e. kamailio doesn't seem to resolve the UAs(bogus Contact addresses) to the persistent TLS connections. Now in the Route header I don't see any flow-token so probably kamailio is doing "normal" routing instead of RFC5626 routing (i.e. because it has no flow-token to match with an existing flow). This leads me to ask: for pure RFC5626 to work (no nathelper stuff at all) is it a must that there is a "edge-proxy--[1]-->internal-proxy" layout? ...and...the flow-tokens in [1] are what make it possible to skip bogus Contact: header and route to an existing flow? Regards Shih-Ping Chan

2 1

KEMI: getting ksr_request_route not found or is not callable after t_relay()
by Nigel Daniels 16 Jul '22

16 Jul '22

``` def ksr_route_relay(self, msg): if KSR.is_method_in("IBSU"): if KSR.tm.t_is_set("branch_route") < 0: KSR.tm.t_on_branch("ksr_branch_manage") if KSR.is_method_in("ISU"): if KSR.tm.t_is_set("onreply_route") < 0: KSR.tm.t_on_reply("ksr_onreply_manage") if KSR.is_INVITE(): KSR.info("try and relay the traffic\n") if KSR.tm.t_is_set("ksr_failure_route") < 0: KSR.tm.t_on_failure("ksr_failure_manage") t_relay_result = KSR.tm.t_relay(["10.0.0.6", "5060"]) KSR.info(f't_relay: {t_relay_result}\n') KSR.info(f'MSG: {msg}') if KSR.tm.t_is_set("ksr_failure_route_one"): KSR.tm.t_on_reply("ksr_on_reply_route_one") ``` ERROR: app_python3 [python_exec.c:91]: apy_exec(): ksr_request_route not found or is not callable Again this only happens after t_replay is called. Any help understanding why this happens would be appreciated. -- - Nigel

2 1

uacreg get error on 2nd 401: error uac_reg_tm_callback(): authentication failed
by Алексей Якимкин 15 Jul '22

15 Jul '22

Hello, I try to register on provider`s pbx version: kamailio 5.7.0-dev0 (x86_64/linux) modparam("uac", "reg_db_url", "mysql://kamailio:123@localhost/kamailio") modparam("uac", "reg_contact_addr", "1.1.1.1:5060") modparam("uac", "reg_retry_interval", 120); # for failed registrations modparam("uac", "reg_keep_callid", 1) modparam("uac","restore_mode","auto") uacreg table: +----+---------+------------+-----------+----------------+-----------------+-------+----------------+------------------+----------+---------------------+---------+-------+-----------+--------------+------------------+ | id | l_uuid | l_username | l_domain | r_username | r_domain | realm | auth_username | auth_password | auth_ha1 | auth_proxy | expires | flags | reg_delay | contact_addr | socket | +----+---------+------------+-----------+----------------+-----------------+-------+----------------+------------------+----------+---------------------+---------+-------+-----------+--------------+------------------+ | 1 | 1234567 | pbx | 127.0.0.1 | login | ip.provider.ru | | login | password| | sip:...com | 120 | 0 | 0 | | 10.130.0.23:5060 | I see this two 401 replies [image: изображение.png] 1st REGISTER Via: SIP/2.0/UDP 1.1.1.1:5060 ;branch=z9hG4bK589d.8183f2e6000000000000000000000000.0 To: <sip:login@ip.provider.com> From: <sip:login@ip.provider.com >;tag=f9cf84029bbf24b61836c3d9fef7b7ae-78a2ffe1 CSeq: 10 REGISTER Call-ID: 6818f1b436befce1-21980(a)10.130.0.23 Max-Forwards: 70 Content-Length: 0 User-Agent: server Contact: <sip:1234567@1.1.1.1:5060> Expires: 120 1st 401 WWW-Authenticate: Digest algorithm=MD5,realm=".......org",nonce=" *56806a6f32c49a3afea043c2fa42381f*",domain="sip:......org",qop="auth", *stale=FALSE* 2nd REGISTER Authorization: Digest username="login", realm=".....", nonce=" *56806a6f32c49a3afea043c2fa42381f*", uri="sip:......com", qop=auth, nc=00000001, cnonce="357420659", response="6e300c9f7f4d81095f29b5408f8d5191", algorithm=MD5 2nd 401 WWW-Authenticate: Digest algorithm=MD5,realm=".....org",nonce=" *3b9586f6d31a76e509eb204d8a030415*",domain="sip:.....org",qop="auth", *stale=TRUE* I think kamailio need to sent 3nd REGISTER with a new nonce, because stale=true. But it interrupts register with error: Jul 14 18:41:00 opensips kamailio[21936]: 10(21949) DEBUG: {2 11 REGISTER 6818f1b436befcf7-21980(a)10.130.0.23} uac [uac_reg.c:852]: uac_reg_tm_callback(): completed with status 401 [uuid: 1234567] Jul 14 18:41:00 opensips kamailio[21936]: 10(21949) ERROR: {2 11 REGISTER 6818f1b436befcf7-21980(a)10.130.0.23} uac [uac_reg.c:933]: uac_reg_tm_callback(): authentication failed for <1234567> Can I get kamailio to send REGISTER after the second 401-reply? Can I intercept this REGISTER and 401 in kamailio.conf? Is there any examples? I know about this instruction https://kamailio.org/docs/modules/5.7.x/modules/uac.html :) Itried in request_route xlog("L_NOTICE", "uac 114411 1 remote fU $fU user [$rU] on [$rd] via [$du] $Ri \n"); if (uac_reg_request_to("$fU", 0)) { xlog("L_NOTICE", "uac 114411 Found remote user [$rU] on [$rd] via [$du]\n"); t_on_failure("REMOTE_AUTH"); #t_relay(); } And failure_route failure_route[REMOTE_AUTH] { if ($T_reply_code == 401 or $T_reply_code == 407) { xlog("L_NOTICE", "uac 114411 Remote asked for authentication\n"); uac_auth(); } } but I haven't got logs on register request, 401 reply. -- Best regards, Alex

1 1

usage of {s.urldecode.param} to convert special chars (why is + removed?)
by Benoit Panizzon 14 Jul '22

14 Jul '22

Hi List Service Numbers, like to activate CFW probably often start with * and end with a # # is a special character that needs to be urlencoded in an SIP URI. So best would be to use a generic kamailio urldecode transormation. I guess {s.urldecode.param} is what I was looking for. So when I get a call to the 'enable CFW' service I get $rU => "*21+419999999%23" So I want to extract the destination number and remove the urlencoded # sign. So I do $var(cfw-dest) = $var(cfw-dest) = $rU; $var(cfw-dest) = $(var(cfw-dest){s.substr,3,0}); # "+419999999%23" $var(cfw-dest) = $(var(cfw-dest){s.urldecode.param}); But now I end up with 419999999# the + sigh disappeared. Is this expected behavior? How would this be done the correct way? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Releasing v5.6.1
by Daniel-Constantin Mierla 14 Jul '22

14 Jul '22

Hello, I am considering to release Kamailio v5.6.1 (out of branch 5.6) on Wednesday, July 6, 2022 -- in about 1 week and a half from now. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better 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 20-23, 2022 * https://www.asipto.com/sw/kamailio-advanced-training-online/

5 6

Need Suggestion/Idea to set call limit on 3 kamailios.
by Waqar 40 13 Jul '22

13 Jul '22

Please Read the Scenario in full and then guide me. In my scenario, I have three Kamailio (KamA, KamB, KamC) running in production. They do load balancing for the asterisks which are about 9. Kamailios randomly receive calls from the SIP trunk. I have set the limit of 750 calls on each kamailios. I want to provide only 1000 Calls to my client but they are enjoying calls more than this since each kamailio can receive 750 calls (I have set this limit for redundancy purpose). And I cannot set the limit like 750 on KamA and the rest on KamB and KamC for redundancy purposes. If one kamailio goes down then they send calls on the other kamailios so that no call drops. So, I want to know if there is a module or a way that my redundancy is not affected and I limit total calls on the three kamailios to not exceed 1000. Waiting for a prompt response. Let me know if you need any further information. Regards, Vicky

3 3

How to disable GRUU?
by Алексей Дырявко 11 Jul '22

11 Jul '22

Hello. kamailio -v version: kamailio 5.4.8 (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 8.3.0 How can I disable GRUU support completely? Sip client Grandstream NT-XXX sends default registration request with "reg-id" and "instance" REGISTER sip:kamailio3.telecom.ru SIP/2.0 Via: SIP/2.0/UDP 172.17.0.252:5060;branch=z9hG4bK1645839794;rport From: "7777" sip:7777@kamailio3.telecom.ru;tag=53756161 To: sip:7777@kamailio3.telecom.ru Call-ID: 308071885-5060-1 CSeq: 2031 REGISTER Contact: sip:7777@172.17.0.252:5060 ;reg-id=1;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB" Authorization: Digest username="7777", realm="kamailio3.telecom.ru", nonce="Ysv842LL+7dABGNcyuYZhl1L2QTPgzFq", uri="sip:kamailio3.telecom.ru", response="0ef43a754a7422dd9d8ed36f91aa546 , algorithm=MD5 Max-Forwards: 70 User-Agent: Grandstream HT-502 V2.0A 1.0.9.1 chip V2.2 Supported: path Expires: 1800 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.17.0.252:5060 ;branch=z9hG4bK1645839794;rport=5060;received=172.17.0.252 From: "7777" sip:7777@kamailio3.telecom.ru;tag=53756161 To: sip:7777@kamailio3.telecom.ru ;tag=5bf75eb19869d3e257cd1fde2cbf92c4.7224507f Call-ID: 308071885-5060-1 CSeq: 2031 REGISTER Contact: sip:7777@172.17.0.252:5060;expires=1800;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB";reg-id=1, sip:07777@172.17.0.250:5060;expires=101, <sip:7777@172.1 0.250:5061>;expires=101, sip:7777@172.17.0.252:5062 ;expires=607;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB";reg-id=2 Server: kamailio (5.4.8 (x86_64/linux)) Content-Length: 0 REGISTER sip:kamailio3.telecom.ru SIP/2.0 Via: SIP/2.0/UDP 172.17.0.252:5062;branch=z9hG4bK212965390;rport From: "7777" sip:7777@kamailio3.telecom.ru;tag=1540711120 To: sip:7777@kamailio3.telecom.ru Call-ID: 1127299103-5062-1 CSeq: 2031 REGISTER Contact: sip:7777@172.17.0.252:5062 ;reg-id=2;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB" Authorization: Digest username="7777", realm="kamailio3.telecom.ru", nonce="Ysv862LL+78cGZE/vXJnQfemhCMiBilm", uri="sip:kamailio3.telecom.ru", response="6c3333159d41ae0fcaabfbbd8c5026e , algorithm=MD5 Max-Forwards: 70 User-Agent: Grandstream HT-502 V2.0A 1.0.9.1 chip V2.2 Supported: path Expires: 1800 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.17.0.252:5062 ;branch=z9hG4bK212965390;rport=5062;received=172.17.0.252 From: "7777" sip:7777@kamailio3.telecom.ru;tag=1540711120 To: sip:7777@kamailio3.telecom.ru ;tag=5bf75eb19869d3e257cd1fde2cbf92c4.451b5a53 Call-ID: 1127299103-5062-1 CSeq: 2031 REGISTER Contact: sip:7777@172.17.0.252:5060;expires=1792;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB";reg-id=1, sip:7777@172.17.0.250:5060;expires=93, <sip:7777@172.17 .250:5061>;expires=93, sip:7777@172.17.0.252:5062 ;expires=1800;+sip.instance="urn:uuid:00000000-0000-1000-8000-000B82566BBB";reg-id=2 Server: kamailio (5.4.8 (x86_64/linux)) Content-Length: 0 Later, when I use branching (with q=-1.0), the kamailio sends an Invite to only one Contact from 7777@172.17.0.252:5062 If I use another Sip client without "instance" , such as Linksys-PAP2T, branching works fine. GRUU is always disabled modparam("registrar", "gruu_enabled", 0)

1 0

(Off-topic) Vienna, meeting
by Henning Westerholt 09 Jul '22

09 Jul '22

(Off-topic) Hello, In about two weeks I will be a few days in Vienna (12h - 14th July). If you want to meet for a drink to chat about Kamailio and other topics, just contact me off-list. Thanks, and regards, Henning

1 1

Client behind nat without stun and kamailio behind NAT
by Алексей Якимкин 08 Jul '22

08 Jul '22

Hello, I hope somebody could help me. This is my scheme. User-agent is behind NAT1. Kamailio and pbx are behind NAT2 [Client ip-phone 192.168.89.213 without stun] - LAN1 - NAT1(46.0.0.30) - (internet) - (51.0.0.60)NAT2 - Local2 - (10.130.0.23:5060)kamailio( 10.130.0.23:5070) - pbx *Questions*: *1*. The VIA header (with 10.130.0.23 and 51.0.0.60) wasn't included in SIP packets. Why? For example 200OK reply. It came from pbx through kamailio. Which setting could break it? Session Initiation Protocol (200) Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 192.168.89.213:5060 ;rport=9570;received=46.0.0.30;branch=z9hG4bK2480172053 Record-Route: <sip:c172.19.19.111.8348.call.cgatepro;lr> Record-Route: <sip:172.19.19.111:5060;lr> Record-Route: <sip:10.130.0.23:5070 ;r2=on;lr;ftag=4268683942;nat=yes>,<sip:51.0.0.60;r2=on;lr;ftag=4268683942;nat=yes> From: "Aleksey" <sip:a.yakimkin@mail.domain.ru:5060>;tag=4268683942 To: <sip:2961@mail.domain.ru:5060 >;tag=A03E2397-404246-FA7543E4_jizmelr-582D Call-ID: 6_1903330087(a)192.168.89.213 [Generated Call-ID: 6_1903330087(a)192.168.89.213] CSeq: 2 INVITE Contact: <sip:signode-404246-FA7543E4_jizmelr-582D@172.19.19.111 ;alias=51.0.0.60~5060~1> Supported: 100rel,timer,replaces,histinfo,precondition Allow: INVITE,BYE,CANCEL,ACK,OPTIONS,INFO,MESSAGE,PRACK,UPDATE,REFER Session-Expires: 1800;refresher=uas Content-Type: application/sdp Content-Length: 1170 Message Body *2*. About Registrar, Path and $du. Phone set Register with headers: Via: SIP/2.0/UDP 192.168.89.213:5060;branch=z9hG4bK2691182696 From: "Aleksey" <sip:a.yakimkin@mail.domain.ru:5060>;tag=3926879477 To: "Aleksey" <sip:a.yakimkin@mail.domain.ru:5060> Contact: <sip:a.yakimkin@192.168.89.213:5060> Kamailio respond Via: SIP/2.0/UDP 192.168.89.213:5060 ;rport=9570;received=46.0.0.30;branch=z9hG4bK617463686 Path: <sip:10.130.0.23:5070 ;lr;received=46.0.0.30~9570~1;r2=on>,<sip:51.0.0.60;lr;received=46.0.0.30~9570~1;r2=on> From: "Aleksey" <sip:a.yakimkin@mail.domain.ru:5060>;tag=3926879477 To: "Aleksey" <sip:a.yakimkin@mail.domain.ru:5060>;tag=194ED16D Contact: <sip:a.yakimkin@192.168.89.213:5060>;expires=360 Contact: <sip:2447@192.168.89.221:5060>;expires=247 Contact: <sip:2447@192.168.9.16:5060>;expires=2116 I try to make a call from pbx to ip phone. pbx inserts in Invite header Route: <sip:10.130.0.23:5070 ;lr;received=46.0.0.30~9570~1;r2=on> But kamailio relayed Invite direct to 192.168.89.213. (There is network connectivity between ip-phone and kamailio through vpn). The code below helps me to solve my issue. I saw mail-list with similar trouble. But no setting could get kamailio to relay Invite to "Route-received" ip. $var(the_route) = $hdr(Route); $var(route0) = $(var(the_route){s.select,0,,}); $var(new_host) = $(var(route0){param.value,received}{s.select,0,~}); $var(new_port) = $(var(route0){param.value,received}{s.select,1,~}); if (!strempty($var(new_host)) && !strempty($var(new_port)) ) { $du = "sip:" + $var(new_host) + ":" + $var(new_port); } *Kamailio settings:* I have such listeners listen=udp:10.130.0.23:5070 # to local network listen=udp:10.130.0.23:5060 advertise 51.0.0.60:5060 # to internet #MODULE SETTING #--- # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ # modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ # modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") modparam("path", "use_received", 1) modparam("path", "enable_r2", 1) modparam("path", "received_format", 1) # ----- ctl params ----- /* set the path to RPC unix socket control file */ # modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) modparam("tm", "auto_inv_100_reason", "Trying") # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 1) modparam("rr", "enable_double_rr", 2) modparam("rr", "force_send_socket", 1) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) /* uncomment the next line to disable parallel forking via location */ # modparam("registrar", "append_branches", 0) /* uncomment the next line not to allow more than 10 contacts per AOR */ # modparam("registrar", "max_contacts", 10) /* max value for expires of registrations */ modparam("registrar", "max_expires", 3600) /* set it to 1 to enable GRUU */ modparam("registrar", "gruu_enabled", 0) modparam("registrar", "use_path", 1) modparam("registrar", "path_use_received", 1) modparam("registrar", "path_mode", 0) #--- For register I use this code route[REGISTRAR] { ... add_path_received(); set_send_socket("udp:10.130.0.23:5070"); route(DISPATCH); ... } route[RELAY] { ... if ($Ru eq "sip:10.130.0.23:5070") { $fs = "udp:10.130.0.23:5060"; } else { $fs = "udp:10.130.0.23:5070"; } ... } route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; #send INVITE to IP:PROT from Route:...;received= $var(the_route) = $hdr(Route); $var(route0) = $(var(the_route){s.select,0,,}); $var(new_host) = $(var(route0){param.value,received}{s.select,0,~}); $var(new_port) = $(var(route0){param.value,received}{s.select,1,~}); if (!strempty($var(new_host)) && !strempty($var(new_port)) ) { $du = "sip:" + $var(new_host) + ":" + $var(new_port); } if (client_nat_test("3")) { if(nat_uac_test("18")) { if ($Ru == "sip:10.130.0.23:5070") { rtpproxy_manage("co", "51.0.0.60"); # fix_nated_sdp } else { rtpproxy_manage("co"); } if (is_method("REGISTER")) { #if ($Ru == "sip:10.130.0.23:5070") { # fix_nated_contact(); #} else { # set_contact_alias(); #} set_contact_alias(); } else { if(is_first_hop()) { set_contact_alias(); } else { add_contact_alias("51.0.0.60", "5060", "udp"); #fix_nated_contact(); } } } else { if ($Ru == "sip:10.130.0.23:5070") { rtpproxy_manage("cor", "51.0.0.60"); # fix_nated_sdp } else { rtpproxy_manage("cor"); } } } else { rtpproxy_manage("co"); } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); #fix_contact(); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); #} else { #fix_contact(); #} } } #!endif return; } Thank you. -- Best regards, Alex

2 1

log any rpc command
by Patrick Karton 08 Jul '22

08 Jul '22

hello is there a way to log in kamailio any kamcmd entered ? Thanks.

1 0

Multiple rtpengine servers
by David Cunningham 07 Jul '22

07 Jul '22

Hello, We are looking to implement a system with one Kamailio server and multiple rtpengine servers. I see that the rtpengine module allows the server configuration to be stored in a database table with multiple entries, which is perfect. My question is - how does Kamailio distribute load between multiple rtpengine servers in the same set? If one of the rtpengine servers goes offline then will Kamailio note this and not send calls to that server until it comes back online? If not then presumably calls could be delayed by whatever the timeout for accessing a server is? Thank you very much, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 3

kamailio 5.6.1 minor release
by Patrick Karton 06 Jul '22

06 Jul '22

Hello Daniel, you said a couple weeks ago that you plan to release a minor release 5.6.1 for this week. its still on plan ? Thanks.

2 2

Kamailio v5.6.1 Released
by Daniel-Constantin Mierla 06 Jul '22

06 Jul '22

Hello, Kamailio SIP Server v5.6.1 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.1. For more details about version 5.6.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2022/07/kamailio-v5-6-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Adding a short note that the dates of next Kamailio World Conference - Online have been set for September 7-8, 2022. Event website and more details will be published soon! 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

branch_route not called on DNS failover
by Patrick Karton 06 Jul '22

06 Jul '22

im using dns failover with tm module. i set parameter reparse_on_dns_failover to 0 so that branch_route is called . but when trying next peer of dns failover initial transaction branch_route is not called. do i missing something ? for the first peer branch_route is called and the peer timeout so kamailio tries next peer but branch_route is not called !. do i need again to set branch_route in failure_route ? Thanks for help.

3 4

Changing the From User in Failure Route
by Mack Hendricks 06 Jul '22

06 Jul '22

Hey All, I'm just trying to change the From user before I do a 301 Redirect within a Failure Route. Here's the code snippet: $fu = "+15555555555"; append_to_reply("Contact: sip:+1$var(redirect_did)@$si:$sp\r\n"); t_reply("302", "Redirect"); The From user is not changed and msg_apply_changes() isn't allowed. What am I doing wrong? Thanks

2 1

Kamailio 5.5 STIR SHAKEN private key buffer size error
by Maharaja Azhagiah 05 Jul '22

05 Jul '22

Hi, I am trying STIR/SHAKEN using libstirshaken in Kamailio 5.5. I used a self signed certificate as this is just a test in the local docker environment. However, when I try to add identity with private key (stirshaken_add_identity_with_key), I get "[error_code: 447] Buffer for key from file /tmp/cert/private.pem too short (2000 <= 3247)" I have tried using 2048 and 4096 size root@5907e44bd056:/tmp/cert# openssl rsa -in private.pem -text -noout | grep "Private-Key" RSA Private-Key: (4096 bit, 2 primes) Could you tell me what is wrong with the certificate? Kamailio version: root@5907e44bd056:/usr/local/kamailio/etc/kamailio# kamailio -v version: kamailio 5.5.4 (x86_64/linux) 469465 Error: 0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:761]: ki_stirshaken_add_identity_with_key(): Failed to load private key 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:117]: stirshaken_print_error_details(): failure details: 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:118]: stirshaken_print_error_details(): failure reason is: src/stir_shaken_ssl.c:2112: [error_code: 447] Buffer for key from file /tmp/cert/private.pem too short (2000 <= 3247) 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:119]: stirshaken_print_error_details(): failure error code is: 447 0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} <script>: Failed Regards *Maharaja Azhagiah*

3 6

How to call RPC functions from script
by Marat Gareev 05 Jul '22

05 Jul '22

Hello! Is it possible to call RPC functions from script? In particular, I'm interested in the ability to add new groups to the dispatcher. https://kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.…

4 4

Re: [SR-Users] mhomed not working for tls destination
by Aidar Kamalov 05 Jul '22

05 Jul '22

Hi, thank you for your reply, I have tried it at kamailio 5.5 and 5.6 versions, and there are two network interfaces. Actually, I have created a testing vm for this, with a simple almost default kamailio configuration. And yes, with forcing socket everything is working fine, but I just want to know maybe there is a kamailio params that allow "mhomed" params to work with tcp/tls destinations, or is it impossible by TCP design, or is it a kamailio bug. I wonder if anyone uses kamailio with 2+ network interfaces and uses tls and don't use $fs? -- Aidar

1 0

return 0 is not equivalent to exit
by Patrick Karton 04 Jul '22

04 Jul '22

on 5.5 kamailio wiki for core it is stated that return (0) is the same as exit. but that's not true request_route { if (route(POS)){ xlog("POS PASS\r\n"); } if (!route(NEG)){ xlog("NEG PASS\r\n"); } if (!route(ZERO)) { xlog("ZERO PASS\r\n"); } xlog("AFTER ZERO\r\n"); send_reply("400","Error"); return; } route[POS]{ return 1; } route[NEG]{ return -1; } route[ZERO] { return 0; } for example from the config above not only ZERO PASS will be printed but also all the actions after route(ZERO) are still executed. instead if i replace return 0 with exit in route[ZERO]. this work as expected.

2 2

compare pseudo var ip to one of kamailio ips
by Patrick Karton 04 Jul '22

04 Jul '22

is there a function or way to compare an ip store in pseudo variable to one kamailio ips ? i would for example if ( $nh(d) == myself )

1 0

log_facility is not always 'LOCAL0' when loadmodule log_custom.so
by hanxiaofang 04 Jul '22

04 Jul '22

Hello Kamailio community kamailio v5.5.4 debian10 log_facility is not always 'LOCAL0' when loadmodule log_custom.so cat /etc/kamailio/kamailio.cfg ``` debug=3 log_stderror=no log_facility=LOG_LOCAL0 children=1 listen=udp:0.0.0.0:5060 log_engine_type="udp" log_engine_data="127.0.0.1:514" loadmodule "pv.so" alias="test.com" loadmodule "sl.so" loadmodule "corex.so" loadmodule "kex.so" loadmodule "log_custom.so" request_route { if (uri != myself) { sl_send_reply("403", "Not relaying"); exit; } sl_send_reply("200", "OK"); exit; } ``` cat /etc/rsyslog.conf ``` # /etc/rsyslog.conf configuration file for rsyslog # # For more information install rsyslog-doc and see # /usr/share/doc/rsyslog-doc/html/configuration/index.html ################# #### MODULES #### ################# module(load="imuxsock") # provides support for local system logging module(load="imklog") # provides kernel logging support #module(load="immark") # provides --MARK-- message capability # provides UDP syslog reception module(load="imudp") input(type="imudp" port="514") # provides TCP syslog reception module(load="imtcp") input(type="imtcp" port="514") ########################### #### GLOBAL DIRECTIVES #### ########################### # # Use traditional timestamp format. # To enable high precision timestamps, comment out the following line. # #$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat $ActionFileDefaultTemplate RSYSLOG_DebugFormat # # Set the default permissions for all log files. # $FileOwner root $FileGroup adm $FileCreateMode 0640 $DirCreateMode 0755 $Umask 0022 # # Where to place spool and state files # $WorkDirectory /var/spool/rsyslog # # Include all config files in /etc/rsyslog.d/ # $IncludeConfig /etc/rsyslog.d/*.conf ############### #### RULES #### ############### # # First some standard log files. Log by facility. # auth,authpriv.* /var/log/auth.log *.*;auth,authpriv.none -/var/log/syslog #cron.* /var/log/cron.log daemon.* -/var/log/daemon.log kern.* -/var/log/kern.log lpr.* -/var/log/lpr.log mail.* -/var/log/mail.log user.* -/var/log/user.log # # Logging for the mail system. Split it up so that # it is easy to write scripts to parse these files. # mail.info -/var/log/mail.info mail.warn -/var/log/mail.warn mail.err /var/log/mail.err # # Some "catch-all" log files. # *.=debug;\ auth,authpriv.none;\ news.none;mail.none -/var/log/debug *.=info;*.=notice;*.=warn;\ auth,authpriv.none;\ cron,daemon.none;\ mail,news.none -/var/log/messages # # Emergencies are sent to everybody logged in. # *.emerg :omusrmsg:* ``` cat /var/log/messages ``` Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module' escaped msg: ' INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio: INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 132, syslogtag 'kamailio:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' WARNING: <core> [core/socket_info.c:1480]: fix_hostname(): could not rev. resolve 0.0.0.0' escaped msg: ' WARNING: <core> [core/socket_info.c:1480]: fix_hostname(): could not rev. resolve 0.0.0.0' inputname: imuxsock rawmsg: '<132>Jul 4 10:25:07 kamailio: WARNING: <core> [core/socket_info.c:1480]: fix_hostname(): could not rev. resolve 0.0.0.0' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: <core> [core/tcp_main.c:4997]: init_tcp(): using epoll_lt as the io watch method (auto detected)' escaped msg: ' INFO: <core> [core/tcp_main.c:4997]: init_tcp(): using epoll_lt as the io watch method (auto detected)' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio: INFO: <core> [core/tcp_main.c:4997]: init_tcp(): using epoll_lt as the io watch method (auto detected)' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 132, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' escaped msg: ' WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' inputname: imuxsock rawmsg: '<132>Jul 4 10:25:07 kamailio[660]: WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: sl [sl.c:180]: mod_init(): could not bind tm module - only stateless mode available during modules initialization' escaped msg: ' INFO: sl [sl.c:180]: mod_init(): could not bind tm module - only stateless mode available during modules initialization' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio[660]: INFO: sl [sl.c:180]: mod_init(): could not bind tm module - only stateless mode available during modules initialization' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: <core> [main.c:3030]: main(): processes (at least): 6 - shm size: 67108864 - pkg size: 8388608' escaped msg: ' INFO: <core> [main.c:3030]: main(): processes (at least): 6 - shm size: 67108864 - pkg size: 8388608' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio[660]: INFO: <core> [main.c:3030]: main(): processes (at least): 6 - shm size: 67108864 - pkg size: 8388608' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992' escaped msg: ' INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio[660]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984' escaped msg: ' INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio[660]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 132, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' escaped msg: ' WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' inputname: imuxsock rawmsg: '<132>Jul 4 10:25:07 kamailio[660]: WARNING: sl [../../modules/tm/tm_load.h:142]: load_tm_api(): Cannot import load_tm function from tm module' $!: $.: $/: Debug line with all properties: FROMHOST: 'kam', fromhost-ip: '127.0.0.1', HOSTNAME: 'kam', PRI: 134, syslogtag 'kamailio[660]:', programname: 'kamailio', APP-NAME: 'kamailio', PROCID: '660', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' INFO: sl [sl.c:199]: child_init(): could not bind tm module - only stateless mode available during runtime' escaped msg: ' INFO: sl [sl.c:199]: child_init(): could not bind tm module - only stateless mode available during runtime' inputname: imuxsock rawmsg: '<134>Jul 4 10:25:07 kamailio[660]: INFO: sl [sl.c:199]: child_init(): could not bind tm module - only stateless mode available during runtime' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_MAIN with rank 0' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_MAIN with rank 0' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_MAIN with rank 0' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: sl [main]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: sl [main]' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: sl [main]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: corex [main]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: corex [main]' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: corex [main]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: kex [main]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: kex [main]' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: kex [main]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (0)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (0)' inputname: imudp rawmsg: '(660) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (0)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-294-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-294-] (0 / 18)' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-294-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: log_custom [main]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: log_custom [main]' inputname: imudp rawmsg: '(660) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 0 rank 0: log_custom [main]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(660)', programname: '(660)', APP-NAME: '(660)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [main.c:1893]: main_loop(): Expect maximum 2080 open fds' escaped msg: ' DEBUG: <core> [main.c:1893]: main_loop(): Expect maximum 2080 open fds' inputname: imudp rawmsg: '(660) DEBUG: <core> [main.c:1893]: main_loop(): Expect maximum 2080 open fds' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1395651006' escaped msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1395651006' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1395651006' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1395651006' escaped msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1395651006' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1395651006' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1706875772' escaped msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1706875772' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1706875772' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' escaped msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1907030787 1472551529 366291743 1443005452' escaped msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1907030787 1472551529 366291743 1443005452' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1907030787 1472551529 366291743 1443005452' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1706875772' escaped msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1706875772' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1706875772' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 997893165' escaped msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 997893165' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 997893165' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' escaped msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: sl [timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: sl [timer]' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: sl [timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1339236272 1961881452 3510136093 136723668' escaped msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1339236272 1961881452 3510136093 136723668' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1339236272 1961881452 3510136093 136723668' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: corex [timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: corex [timer]' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: corex [timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 997893165' escaped msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 997893165' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 997893165' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: kex [timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: kex [timer]' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: kex [timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' inputname: imudp rawmsg: '(663) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' escaped msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: sl [slow timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: sl [slow timer]' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: sl [slow timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 3710294115' escaped msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 3710294115' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 3710294115' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-297-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-297-] (0 / 18)' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-297-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1640811744 313033881 1910478272 3953138690' escaped msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1640811744 313033881 1910478272 3953138690' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1640811744 313033881 1910478272 3953138690' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: corex [slow timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: corex [slow timer]' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: corex [slow timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 2804346838' escaped msg: ' DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 2804346838' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 2804346838' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(663)', programname: '(663)', APP-NAME: '(663)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: log_custom [timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: log_custom [timer]' inputname: imudp rawmsg: '(663) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 3 rank -1: log_custom [timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TIMER with rank -1' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: sl [secondary timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: sl [secondary timer]' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: sl [secondary timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: kex [slow timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: kex [slow timer]' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: kex [slow timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: corex [secondary timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: corex [secondary timer]' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: corex [secondary timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 3710294115' escaped msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 3710294115' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 3710294115' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 2804346838' escaped msg: ' DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 2804346838' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 2804346838' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' escaped msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: kex [secondary timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: kex [secondary timer]' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: kex [secondary timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' escaped msg: ' DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' inputname: imudp rawmsg: '(662) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 768215415 2130568241 786907391 1147444666' escaped msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 768215415 2130568241 786907391 1147444666' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 768215415 2130568241 786907391 1147444666' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' inputname: imudp rawmsg: '(664) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-1)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1440943297 556268029 2006317306 707883259' escaped msg: ' DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1440943297 556268029 2006317306 707883259' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 1440943297 556268029 2006317306 707883259' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-298-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-298-] (0 / 18)' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-298-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-296-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-296-] (0 / 18)' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-296-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(664)', programname: '(664)', APP-NAME: '(664)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: log_custom [secondary timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: log_custom [secondary timer]' inputname: imudp rawmsg: '(664) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 4 rank -1: log_custom [secondary timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(662)', programname: '(662)', APP-NAME: '(662)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: log_custom [slow timer]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: log_custom [slow timer]' inputname: imudp rawmsg: '(662) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 2 rank -1: log_custom [slow timer]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_SIPINIT with rank 1' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_SIPINIT with rank 1' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_SIPINIT with rank 1' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: sl [udp receiver child=0 sock=0.0.0.0:5060]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: sl [udp receiver child=0 sock=0.0.0.0:5060]' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: sl [udp receiver child=0 sock=0.0.0.0:5060]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TCP_MAIN with rank -4' escaped msg: ' DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TCP_MAIN with rank -4' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/sr_module.c:913]: init_child(): initializing PROC_TCP_MAIN with rank -4' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: sl [tcp main process]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: sl [tcp main process]' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: sl [tcp main process]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: corex [udp receiver child=0 sock=0.0.0.0:5060]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: corex [udp receiver child=0 sock=0.0.0.0:5060]' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: corex [udp receiver child=0 sock=0.0.0.0:5060]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: kex [udp receiver child=0 sock=0.0.0.0:5060]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: kex [udp receiver child=0 sock=0.0.0.0:5060]' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: kex [udp receiver child=0 sock=0.0.0.0:5060]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: corex [tcp main process]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: corex [tcp main process]' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: corex [tcp main process]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (1)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (1)' inputname: imudp rawmsg: '(661) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (1)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: kex [tcp main process]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: kex [tcp main process]' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: kex [tcp main process]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-295-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-295-] (0 / 18)' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-295-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-4)' escaped msg: ' DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-4)' inputname: imudp rawmsg: '(665) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-4)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-299-] (0 / 18)' escaped msg: ' DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-299-] (0 / 18)' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/utils/sruid.c:116]: sruid_init(): root for sruid is [srid-62c24f83-299-] (0 / 18)' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: log_custom [udp receiver child=0 sock=0.0.0.0:5060]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: log_custom [udp receiver child=0 sock=0.0.0.0:5060]' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 1 rank 1: log_custom [udp receiver child=0 sock=0.0.0.0:5060]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/action.c:1687]: run_child_one_init_route(): attempting to run event_route[core:worker-one-init]' escaped msg: ' DEBUG: <core> [core/action.c:1687]: run_child_one_init_route(): attempting to run event_route[core:worker-one-init]' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/action.c:1687]: run_child_one_init_route(): attempting to run event_route[core:worker-one-init]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: log_custom [tcp main process]' escaped msg: ' DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: log_custom [tcp main process]' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/sr_module.c:871]: init_mod_child(): idx 5 rank -4: log_custom [tcp main process]' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/local_timer.c:60]: init_local_timer(): timer_list between 0x55e7029f85e8 and 0x55e702a3c5e8' escaped msg: ' DEBUG: <core> [core/local_timer.c:60]: init_local_timer(): timer_list between 0x55e7029f85e8 and 0x55e702a3c5e8' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/local_timer.c:60]: init_local_timer(): timer_list between 0x55e7029f85e8 and 0x55e702a3c5e8' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(661)', programname: '(661)', APP-NAME: '(661)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0x55e702a5f880)[core:worker-one-init] to 2' escaped msg: ' DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0x55e702a5f880)[core:worker-one-init] to 2' inputname: imudp rawmsg: '(661) DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0x55e702a5f880)[core:worker-one-init] to 2' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 7, 4, 0x7fda8a625884) - fd_no=0' escaped msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 7, 4, 0x7fda8a625884) - fd_no=0' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 7, 4, 0x7fda8a625884) - fd_no=0' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 8, 4, 0x7fda8a625918) - fd_no=1' escaped msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 8, 4, 0x7fda8a625918) - fd_no=1' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 8, 4, 0x7fda8a625918) - fd_no=1' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 9, 4, 0x7fda8a6259ac) - fd_no=2' escaped msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 9, 4, 0x7fda8a6259ac) - fd_no=2' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 9, 4, 0x7fda8a6259ac) - fd_no=2' $!: $.: $/: Debug line with all properties: FROMHOST: 'localhost', fromhost-ip: '127.0.0.1', HOSTNAME: 'localhost', PRI: 13, syslogtag '(665)', programname: '(665)', APP-NAME: '(665)', PROCID: '-', MSGID: '-', TIMESTAMP: 'Jul 4 10:25:07', STRUCTURED-DATA: '-', msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 10, 4, 0x7fda8a625a40) - fd_no=3' escaped msg: ' DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 10, 4, 0x7fda8a625a40) - fd_no=3' inputname: imudp rawmsg: '(665) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0x55e7029f8420, 10, 4, 0x7fda8a625a40) - fd_no=3' $!: $.: $/: ``` fac is 'LOCAL0' first, then change to 'USER' (PRI = 13, 1 * 8 + 5) hanxiaofang

2 1

mhomed not working for tls destination
by Aidar Kamalov 04 Jul '22

04 Jul '22

Hello, I have faced an issue when mhomed parameter working well only for udp destinations in systems with multiple network interfaces. If kamailio forward call to the UDP destination, mhomed option chooses the correct Via and the correct network interface for sending. But if the destination is tls, mhomed chooses first described in configuration file "listen=" interface and use this IP in Via header Network routes in the system are correct and "ip r get IP" returns the correct route and interface. Should mhomed work with tcp/tls or is this impossible with TCP design? -- Aidar

2 1

Question about SIP registration
by Cheng Tang 01 Jul '22

01 Jul '22

Hi, everyone! In one sentence, I want to know how to how to add the shared key (aka. K, Ki) used by AKA algorithm to Kamailio. I’m using Kamailio as an IMS server to test my own 5G Core. As you know, UE would send its first SIP Registration message to Kamailio with its IMPI and IMPU, then Kamailio should use the shared key to proceed AKA algorithm to generate the authentication vector, then respond UE with 401 unauthorized message to challenge the UE. I’ve done my research and I still can’t figure out how to let Kamailio know this shared key. And when I was doing my test, it seems like Kamailio used some default key to generate the auth vector. Could anybody help me? I’ve been stuck here for days.

1 0

Run PCSCF without IPSec
by Weiqi Yao 30 Jun '22

30 Jun '22

Hello Community, We are running Kamailio with 3 instances as PCSCF/ICSCF/SCSCF, and we don't want IPsec to be used in between PCSCF and UE and we confirmed the initial Register UE send do not have the Security-Client header. However, seems the IPsec is enabled by default in current PCSCF cfg, we tried to comment WITH_IPSEC as well as couple ipsec_forward function out in the cfg, but when the 401 Challenging message send to PCSCF and PCSCF failed to forward it to UE due to (Create ipsec failed) reason. So I want to reach out and see if anyone have experience not using IPsec with currently Kamailio PCSCF? Any clue or comment will be appreciated! BR, Weiqi

1 0

Makefile.rules:191: recipe for target 'tlsa.so' failed
by Abdoul Osséni 30 Jun '22

30 Jun '22

Hello, Cannot compile tlsa module. I get the following error message: LD (gcc) [M tlsa.so] tlsa.so /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libssl.a(ssl_lib.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libssl.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status ../../Makefile.rules:191: recipe for target 'tlsa.so' failed make[2]: *** [tlsa.so] Error 1 Makefile:511: recipe for target 'modules' failed make[1]: *** [modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.6/kamailio/src' Makefile:34: recipe for target 'all' failed make: *** [all] Error 2 Please find below some information about my environment system: root@sbc:/usr/local/src/kamailio-5.6/kamailio# cat /etc/debian_version 8.6 root@sbc:/usr/local/src/kamailio-5.6/kamailio# openssl version OpenSSL 3.0.4 21 Jun 2022 (Library: OpenSSL 3.0.4 21 Jun 2022) Regards Abdoul

2 1

Install Kamailio in captive network
by Rahul mm 30 Jun '22

30 Jun '22

Hello guys, Ab initio, I'm loving Kamailio and the endless horizons it opens-up. Is there any document somewhere to get Kamailio installed in a captive network that runs w/o internet? I know this seems bizarre but in the mining industry most of the locations do not have internet facilities but they still want to use VoIP. I do not have the privilege to pull a blade system and put it on the internet to install Kamailio, FS etc. Any suggestions? -- Warm Regds. MathuRahul

4 5

Forward reply in onreply_route
by Carsten Bock 29 Jun '22

29 Jun '22

Hi, Question: Is there a way to forward a reply from the reply route and do other stuff afterward? We are currently doing operations on a 183 reply and it would be useful if we could forward the reply before continuing to process other stuff. High-Level example: *route { t_on_reply("REPLY"); t_relay();}onreply_route[REPLY] { // Forward the reply to the Caller t_relay(); // Does not work, as t_relay is only allowed in request and failure-routes // Do other fancy stuff, e.g. a DB Update or anything else}* Any ideas? Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock

6 5

SIP Proxy Challange
by Mihai 27 Jun '22

27 Jun '22

Hello ! I have this issue with the telco provider they give the sip trunk on a private connection with private ips, the problem is that i am trying to relocate the sip trunk in remote server and I've tried though basic networking/tunnels/vpn and no go; their sbc is dropping requests and rejects if they are more via headers, they force me to use that connection and the ip allocated. The challenge is how to do this in kamailio, basically I just want to transport the trunk (similar to a reverse proxy for web) to its new destination and from there handle everything. Any hints on how to achieve this?

3 2

Phones are not getting registered. Is my setup correct?
by Farhan Sahariar (CSSD) 27 Jun '22

27 Jun '22

Hi, I have just installed Goautodial v4. I have followed all the guide to register a phone but this does not work. Is kamailio the reason. I am new to linux need help. [root@vaglxc01 ~]# systemctl status kamailio ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/usr/lib/systemd/system/kamailio.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sun 2022-06-26 16:11:41 +06; 10min ago Process: 1545 ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=255) Main PID: 1545 (code=exited, status=255) Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Unit kamailio.service entered failed state. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service holdoff time over, scheduling restart. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: start request repeated too quickly for kamailio.service Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Unit kamailio.service entered failed state. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: start request repeated too quickly for kamailio.service Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. [root@vaglxc01 ~]# kamailio -version version: kamailio 5.0.7 (x86_64/linux) 743c2d flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 743c2d compiled on 03:02:32 Aug 26 2018 with gcc 4.8.5 Best regards, Farhan Sahariar Assistant Manager Customer Support Services Division LEADS Corporation Limited [Description: Description: Green Living Slogan_Email]

3 6

How to handle a 301 redirect request from a client?
by Benoît Panizzon 27 Jun '22

27 Jun '22

Hi Gang We want to allow customers to send a 301 to forward calls to mimik ISDN PARE. The new destination is in the contact user HF. So I guess I could handle this on the t_on_failure route to catch that error, extract the contact user HF, craft an appropriate Diversion header and send the call on. But I wonder, is there maybe a module which handles all of this out of the box? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 11

kamailio + sems for early media
by mohsen khashei 25 Jun '22

25 Jun '22

2 2

update PAI Header User part
by Patrick Karton 24 Jun '22

24 Jun '22

hello is there a cleaner/fastest way to update PAI header user part other than using subst i come up with subst('/^P-Asserted-Identity:(.*)(sip|sips|tel|tels):([^@]*)@([a-zA-Z0-9.]+)(.*)$/P-Asserted-Identity:\1\2:$var(newPAIUser)@\4\5/ig'); Thanks.

2 1

Append (not replace) line to SDP body
by Benoît Panizzon 24 Jun '22

24 Jun '22

Hi Gang Next question. I have some broken CPE which do not set a=ptime despite using 20ms which then causes the call to get rejected in certain destinations, because ptime header is missing. So I would like to match the user-agents in question and add back a=ptime:20 Google searches found an user with the exact same problem almost 10 years ago and Daniel replying that indeed a function to add a body line would be handy. https://www.kamailio.org/docs/modules/devel/modules/textops.html How could this be accomplished? I don't see a add_body_line or other function which does not 'replace' a body line. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 3

Finding advertised address of socket
by Tor Petterson 24 Jun '22

24 Jun '22

Hi I have a setup where Kamailio is connected to several telephony providers using different IP addresses to communicate with them. So I have a socket per provider. I am using the dispatcher module to route calls to the different providers. My question is if there is a way to get the advertised address of the socket chosen by dispatcher? I have a socket pointer in the XAVP, but I can't figure out if it is possible to get the advertised address from it somehow. Thanks in advance. Tor

3 5

Testers wanted for new TLS transport based on wolfSSL
by Richard Chan 24 Jun '22

24 Jun '22

Hello Kamailio users, I would like testers to try out a new module tls_wolfssl, an alternate TLS transport based on wolfSSL. Why another TLS transport implementation? The travails of using OpenSSL >= 1.1.1 in Kamailio’s multi-process paradigm has been documented by OpenSIPS (and that sister project has implemented tls_wolfssl). Essentially, OpenSSL makes no concessions to the multi-process use case and in fact has implementation details that work against global shared memory structures. As a result Kamailio contains some tricky code * a pthread polyfill in core * duplicated SSL_CTX per worker * atexit workaround How to test? The code is currently in master and can be built in the usual way. Debian has 5.2.0 libwolfssl-dev needed; for some RPM distros (el8, el9, fc36) I have created a Copr repository https://copr.fedorainfracloud.org/coprs/beaveryoga/wolfSSL/ Known limitations The current state can be considered as identical to tls+OpenSSL 1.1.1/3.0.x. Old TLS protocols < 1.2 and cipher list configuration don’t work, i.e., only TLS 1.2 and 1.3 work with the default cipher list. In your configuration just replace loadmodule “tls.so” with loadmodule “tls_wolfssl.so” The rest of the TLS configuration can remain unchanged unless you are using a funky protocol version/cipher list combination. Thanks! S-P

3 3

Kamailio Procedure
by Suporte 24 Jun '22

24 Jun '22

Hi Does anyone have the procedure model for Kamailio_cdrs, I'm trying to implement the model from the book, but the syntax error always appears. Thanks for the support. Adriano Vieira

3 2

problem getting the rtp packet source port
by hamed r 23 Jun '22

23 Jun '22

hello i have problem on receive source port rtp packet client-ip = 5.202.105.250 server-ip = 194.5.205.33 client2-ip = 188.212.241.46 In the 200 ok packet from client2 ,The value 4002 is set in the audio port [image: photo_2022-06-12_17-44-37.jpg] I expect rtp packets to be sent to me from source port 4002, but these packets are sent to me from another source , which is port 55755 in the image below, and I just opened this port(4002) in the firewall. If I turn on my firewall service, all packets will be dropped. I have to have this firewall [image: photo_2022-06-12_17-44-48.jpg] thanks for help me

3 2

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

What is the alignment of shm_malloc and friends?
by Richard Chan 22 Jun '22

22 Jun '22

Hi Daniel and kamailio users, In my integration adventure of wolfSSL and kamailio I have encountered an alignment issue sometime causing segfaults. May I enquire what is the alignment of shm_malloc and friends? The wolfSSL library integration requires that ser_malloc and ser_realloc return values aligned on alignof(_max_align_t) which in the case of x86_64 is 16. Thank you Shih-Ping

2 3

5.6 Package for Ubuntu 22.04 LTS?
by Mark Boyce 21 Jun '22

21 Jun '22

Hi all Any chance of Ubuntu 22.04 LTS "Jammy Jellyfish” being added to the Jenkins package builder for kamailio 5.6? Ubuntu native repo seems to have 5.5 in it. Thanks Mark

1 0

Finding advertised address of socket
by Tor Petterson 21 Jun '22

21 Jun '22

Hi I have a setup where Kamailio is connected to several telephony providers using different IP addresses to communicate with them. I am using the dispatcher module to route calls to the different providers. My question is if there is a way to get the advertised address of the socket chosen by dispatcher? I have a socket pointer in the XAVP but I can't figure out if it is possible to get the advertised address from it somehow. Thanks in advance. Tor

2 1

Record-Route advertised per branch
by Ilie Soltanici 17 Jun '22

17 Jun '22

Hello, Is there any way to advertise a different IP Address in the Record-Route header individually per branch? I have a setup here - where Kamailio is listening on 2 different interfaces: Local IP and External IP. At the moment if the packet is coming through the internal interface - I'm checking where is it going to and based on that I'm setting the Record-Route header accordingly - and everything works well, except when I have multiple branches: one going through the internal interface and another one through the external one, so in this case, I have to add a different record-route header per branch, by doing this in the branch_route - it's not working and getting the error: w_record_route_advertised_address(): Double attempt to record-route. What would be another way to accomplish this?

4 7

RTPengine in Debian
by Richard Fuchs 17 Jun '22

17 Jun '22

HI all, Just a quick heads up that RTPengine is now available in Debian sid/unstable mainline repositories. Big thanks to our own Victor Seva and Guillem Jover for making this possible. Cheers

4 4

set/add_contact_alias() difference
by ZZ Wave 17 Jun '22

17 Jun '22

Playing around with WSS support: if (nat_uac_test(64)) { force_rport(); ...... if (!add_contact_alias()) { xinfo("Error aliasing contact <$ct>\n"); sl_send_reply("400", "Bad Request"); exit; } set_contact_alias() throws this error on ACK without Contact, add_contact_alias() doesn't (and thats OK). Is this the expected behavior?

2 1

Re: [SR-Users] Callback for TM?s "fr_inv_timer" ?
by Antonio Couto 15 Jun '22

15 Jun '22

I will try this, thanks a lot for your help. regards. On Wed, Jun 15, 2022 at 5:43 PM Alex Balashov <abalashov(a)evaristesys.com> wrote: > Setting t_on_failure("FAILURE_ROUTE") before t_relay(), given a route > block failure_route[FAILURE_ROUTE], as you are doing, should work. > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > On Wed, Jun 15, 2022 at 8:34 AM Antonio Couto <couto.a(a)gmail.com> wrote: > >> Thanks for your support, I am trying to do this but to be honest I don't >> know >> how to arm the failure route for this case of "fr_inv_timer". >> >> When I received reply 183 I use t_set_fr() function to set the new value >> for "fr_inv_timer", >> do far so good, but I never received failure_route[0] when Kamailio >> terminate the call sending 408, >> even calling like this: >> >> t_on_failure("0"); >> t_relay(); >> >> I can't find on documentation how to do this. >> Thanks a lot >> >> >> >>

1 0

terminate a call on 183 state
by Antonio Couto 15 Jun '22

15 Jun '22

Someone know how to terminate a call on TM module from a external application, http, websocket, udp or using other modules when the call on 183 state? I am making a answering machine detection analising audio from RTPEngine recording daemon , but i need to disconnect the call before is anwered byt remote side. Kamailio INVITE >> Destination << 100 trying << 183 session progress I need to comand Kamailio to drop this call from a external application in this point. I searched on each module but I can not find any solution. Thanks in advance

2 2

Re: [SR-Users] Callback for TM?s "fr_inv_timer" ?
by Antonio Couto 15 Jun '22

15 Jun '22

Thanks for your support, I am trying to do this but to be honest I don't know how to arm the failure route for this case of "fr_inv_timer". When I received reply 183 I use t_set_fr() function to set the new value for "fr_inv_timer", do far so good, but I never received failure_route[0] when Kamailio terminate the call sending 408, even calling like this: t_on_failure("0"); t_relay(); I can't find on documentation how to do this. Thanks a lot

1 0

Callback for TM´s "fr_inv_timer" ?
by Antonio Couto 14 Jun '22

14 Jun '22

There some way to set a callback route for TM´s "fr_inv_timer" ? I want to receive this callback when its fires and before Kamailio send 408 Request Timeout to the caller ? I tryed every callback available but I think I missing something or I will need to implement on TM module. Thanks in advance

2 1

jsonrpc with many methods not found
by Joseph Goettgens 14 Jun '22

14 Jun '22

Hi, I think I have not yet understood how jsonrpc needs to be configured. In kamcli I can issue the cmd "ul show" and I get a valid reply. When I print "domain list" I get error: code: 500 message: Method Not Found id: 6897 jsonrpc: '2.0' The same applies to JSONRPC Commands with Siremis. Some commands work, others are not found. Do I need some special configuration?

1 0

Kamailio eats pkg mem, but where?
by Sebastian Damm 14 Jun '22

14 Jun '22

Hi, we have some Kamailio instances running (currently latest 5.4 release), and we need to restart it from time to time. We have a grafana graph showing the pkg memory usage of one random tcp listener, and it increases slowly over time. Config is pure python KEMI. A mem dump directly after restarting Kamailio says this: SipSeppBook22:tmp sdamm$ grep alloc pkgmem_before.log | awk '{ print substr( $0, 16, length($0) ) }' | sort | uniq -c | sort -k1n | tail -10 16 sipproxy qm_status(): alloc'd from core: core/re.c: subst_parser(301) 31 sipproxy qm_status(): alloc'd from core: core/sr_module.c: load_module(436) 31 sipproxy qm_status(): alloc'd from core: core/sr_module.c: register_module(236) 31 sipproxy qm_status(): alloc'd from core: core/sr_module.c: register_module(253) 40 sipproxy qm_status(): alloc'd from core: core/pvapi.c: pv_init_buffer(2139) 58 sipproxy qm_status(): alloc'd from core: core/cfg.lex: pp_define(1827) 133 sipproxy qm_status(): alloc'd from core: core/rpc_lookup.c: rpc_hash_add(101) 162 sipproxy qm_status(): alloc'd from core: core/counters.c: cnt_hash_add(339) 211 sipproxy qm_status(): alloc'd from core: core/cfg.lex: addstr(1448) 265 sipproxy qm_status(): alloc'd from core: core/pvapi.c: pv_table_add(236) And after running for some weeks, the same dump looks like this: SipSeppBook22:tmp sdamm$ grep alloc prod_pkgmem.log | awk '{ print substr( $0, 16, length($0) ) }' | sort | uniq -c | sort -k1n | tail -10 31 ifens5 qm_status(): alloc'd from core: core/sr_module.c: register_module(253) 40 ifens5 qm_status(): alloc'd from core: core/pvapi.c: pv_init_buffer(2139) 59 ifens5 qm_status(): alloc'd from core: core/cfg.lex: pp_define(1827) 133 ifens5 qm_status(): alloc'd from core: core/rpc_lookup.c: rpc_hash_add(101) 161 ifens5 qm_status(): alloc'd from core: core/counters.c: cnt_hash_add(339) 203 ifens5 qm_status(): alloc'd from core: core/cfg.lex: addstr(1448) 265 ifens5 qm_status(): alloc'd from core: core/pvapi.c: pv_table_add(236) 686 ifens5 qm_status(): alloc'd from core: core/pvapi.c: pv_parse_format(1173) 694 ifens5 qm_status(): alloc'd from htable: ht_var.c: pv_parse_ht_name(158) 707 ifens5 qm_status(): alloc'd from core: core/pvapi.c: pv_cache_add(349) I know, currently there are a few lines in the code which look like this: self.instance_name = KSR.pv.get("$sht(pbxdata=>ip.%s)" % (ip,)) This has been an issue in the past and I have replaced the code with something like this: KSR.pv.sets("$var(tmpInstanceIp)", ip) self.instance_name = KSR.pv.get("$sht(pbxdata=>ip.$var(tmpInstanceIp))") However, even after changing this, the memory still grows slowly but steadily. The usage scenario is TLS-only on one side (clients) and TCP-only on the other side (pbxes). Does anybody have a hint for me how to debug this? Looks like there's a lot of pv stuff in the memory, but I don't really know where. Thanks for any hints, Sebastian

2 1

Re: [SR-Users] Hangup a call after a certain time from 183
by Antonio Couto 14 Jun '22

14 Jun '22

Thanks a lot I will try this options, sorry, I am new on Users Mailing List, I think that´s is not right way to make a response. regards.

1 0

Hangup a call after a certain time from 183
by Antonio Couto 14 Jun '22

14 Jun '22

I need to hang up a call after some seconds after received 183 provisional response but before any other SIP message. I am using "rtimer" module to set a callback on time, but how can I search for a call on transaction module in order to terminate the call? I think I am missing something to prepare the transaction data before I can use this data to terminate the call. I am thinking of storing the call-Id of all transactions to use on timeout callback, I don't know if it's possible. Thanks in advance. Antonio

2 1

issue using phonenum module
by David Escartín 13 Jun '22

13 Jun '22

Hello all we are using the phonenum_match_cn function to detect valid phone numbers, but seems there are some numbers like 576015145834 which are no detected as valid ones, $phn(ani=>valid) --> 0 $phn(ani=>ccname) --> <null> $phn(ani=>cctel) --> 0 $phn(ani=>error) --> Invalid number but using https://libphonenumber.appspot.com/phonenumberparser?number=576015145834&co… seems it gives a valid result Validation Results Result from isPossibleNumber() true Result from isValidNumber() true Result from isValidNumberForRegion() true Phone Number region CO Result from getNumberType() FIXED_LINE we are using kamailio 5.4 and libphonenumber tag v8.12.30 (also tested v8.9) the command is used with 'ZZ' cnc and passing the number with + maybe we are missing something in the configuration/setup? thanks 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>

4 4

KAZOO module on quorum queues
by David VILLAUME 13 Jun '22

13 Jun '22

Hello, Did any of you had any success with Kazoo module with RabbitMq quorum queues ? Regards, David

1 0

Get all contacts by domain
by Jose Fco. Irles Durá 13 Jun '22

13 Jun '22

Hi, I'm running a cloud infrastructure with multiple sip domains and I have some kamailio's as registrars with dmq for usrloc replication. The kamailio registrars are configured without db, so the aors are in ram. For some gui's I need to get all aors for one sip domain, If I execute ul.dump I get all aors, but I want only a few. In my situation it would be perfect to get all registrations for one sip domain in one request (memory, performance, cache at gui...) I thought I could save the registers with save("$rd") but ul.dump doesn't allow any parameter that restricts the "location" domain. Is there any solution for this? Best regards -- Jose Fco. Irles Durá

3 4

problem getting the rtp packet source port
by hamed r 12 Jun '22

12 Jun '22

hello i have problem on receive source port rtp packet client-ip = 5.202.105.250 server-ip = 194.5.205.33 client2-ip = 188.212.241.46 In the 200 ok packet from client2 ,The value 4002 is set in the audio port [image: invite.jpg] I expect rtp packets to be sent to me from source port 4002, but these packets are sent to me from another source , which is port 55755 in the image below, and I just opened this port(4002) in the firewall. If I turn on my firewall service, all packets will be dropped. I have to have this firewall [image: rtp.jpg] thanks for help me

1 0

Use of interface name or listening socket name as DMQ server_socket
by Ben Kaufman 10 Jun '22

10 Jun '22

Kamailio allows the use of an interface name (eth0 for example), as the identifier for the listen directive. Additionally it allows assignment of a name to be used as an identifier. This can be used, as indicated in the documentation: A unique name can be set for sockets to simplify the selection of the socket for sending out. For example, the rr and path modules can use the socket name to advertise it in header URI parameter and use it as a shortcut to select the corresponding socket for routing subsequent requests. I'm wondering if there is a way to get allow either of these parameters to be used to define DMQ's server_socket parameter. This would be useful in containerization situations where the local IP address is assigned dynamically. Here's what I'm attempting: #!KAMAILIO loadmodule "tm" loadmodule "sl" loadmodule "dmq" loadmodule "textops" listen=udp:eth0:5060 name "sip5060" listen=udp:eth0:5090 name "sip5090" modparam("dmq", "server_address", "sip:dmq_quicktest:5090") modparam("dmq", "notification_address", "sip:dmq-bus:5090") modparam("dmq", "server_socket", "sip5090" ) ## Above line doesn't work, neither does the line below: #modparam("dmq", "server_socket", "udp:eth0:5090" ) modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 3) modparam("dmq", "ping_interval", 30) request_route { exit; } I get the following error during startup: 0(1) ERROR: dmq [dmq.c:241]: mod_init(): server_uri is not a socket the proxy is listening on Thoughts? I realize that I can configure and pass static networking with the containers, but I'm looking for a way to have this set on the fly - especially when testing, etc. Ben Kaufman

2 1

SIP trunk challange
by Mihai 10 Jun '22

10 Jun '22

Hello ! I have this issue with the telco provider they give the sip trunk on a private conection with private ips, the problem is that i am trying to relocate the sip trunk in remote server and I've tried though basic networking/tunnels/vpn and no go; their sbc is dropping requests and rejects if they are more via headers, they force me to use that conection and the ip allocated. The challenge is how to this is in kamailio, basically i just want to transport the trunk (similiar to a reverse proxy for web) to its new destination and from there handle everything. Any hints on how to achieve this?

2 1

Kamailio vs FreeSWITCH as SBC
by Unai Rodriguez 09 Jun '22

09 Jun '22

Dear List, I’m looking at using Kamailio as SBC. This would replace our current FreeSWITCH-based SBCs. What are your thoughts on this move? Would there be any known reasons why Kamailio would be superior to FreeSWITCH as an SBC? Thank you so much Unai Rodriguez

3 3

t_drop_replies can't be used on a route?
by David Villasmil 09 Jun '22

09 Jun '22

Hello guys, I have a failure route which calls another route, and on this route I need to t_drop_replies(); But i'm getting: [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/kamailio/include/relay_routes.cfg, line 143, column 20: Command cannot be used in the block Any way to fix this without me having to use it in the failure_route? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 0

remove header in async processing (e.g. by http_async_client)
by Henning Westerholt 09 Jun '22

09 Jun '22

Hello, I'd like to remove headers during async processing e.g. in a route called from http_async_client(..). The usual textops functions are not working here. Adding headers could be done using something like rtjson, but it do not offer a remove header function. I could of course loop the request locally, but this is not that "nice". Any other suggestions for this case? Or just the rtjson module needs some extensions? Thank you, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

Siremis startup helper service for systemd
by Joseph Goettgens 09 Jun '22

09 Jun '22

Hi, I had some difficulties getting Siremis 5.3 to run under Debian 11 Bullseye. It turned out that the problem was the creation of the Siremis socket: <UnixSockLocal name="unixsocklocal" address="/run/siremis/siremis_rpc.sock" timeout="3.0"/> There is a warning in siremisJRCommands.xml that points out that systemd has to be reconfigured as sockets in /tmp are no longer shared (PrivateTmp setting). By the same token, /run/siremis/siremis_rpc.sock cannot be created as the httpd server is not allowed to write to /run, i.e. it can neither create the socket nor the siremis directory. The permanent creation of the siremis directory with suitable access rights is also not possible, since /run is mounted as tmpfs in the default configuration. At least the directory has to be created at boot time, which can be done with a small helper service. This is working for me (siremis-helper.service): [Unit] Description=Siremis Helper Service After=network.target [Service] Type=oneshot ExecStartPre=/usr/bin/mkdir /var/run/siremis ExecStart=/usr/bin/chown www-data:www-data /var/run/siremis [Install] WantedBy=multi-user.target It is enabled the usual way with systemctl "systemctl start --now siremis-helper". Siremis now works with jsonrpc commands and the procedure would mean that installing Siremis on a newer Debian system would definitely require some attention. Does anyone have any objections to the above procedure?

1 0

Re-establishment of a closed TCP connection
by Vitalii Krutsitskyi 09 Jun '22

09 Jun '22

Hello General overview of the infrastructure: Client (Cisco Hardware) ---> AWS NLB ---> Kamailio Instances The client has a time limit for the opened TCP connections - 10 minutes. This is a hardcoded value that can't not be changed. Regardless of the traffic that flows through the connection, it is closed after 10 minutes. Problem: in case of long-running calls above 10 minutes it is not possible for Kamailio to send back SIP traffic back to the client using the original TCP connection. The client has been asked to either increase the time limit or send SIP reinvites - none of that is possible due to some client's infrastructure limitations. Question: is it possible to force Kamailio to open a new TCP connection and associate it with the call? Client has a 5060 port always opened which can accept incoming connections.

3 2

ipops dns_query not working using Kemi
by Thomas de Rooij | CM.com 09 Jun '22

09 Jun '22

Hi all, We are trying to do a DNS query using Kemi: KSR.ipops.dns_query(domain, "xyz") The result is always -3. This is returned here: https://github.com/kamailio/kamailio/blob/5.5.4/src/modules/ipops/ipops_pv.… It seems weird to me that the error code is returned because the same non-Kemi code works just fine. Could it be related to this issue: https://github.com/kamailio/kamailio/issues/2052 Thanks. Kind regards, Thomas

3 2

remove headers with less than 5 characters with textops
by Patrick Karton 07 Jun '22

07 Jun '22

Hello im trying to textops module to remove headers with name length less than 5 characters with regular expression but it seems impossible or the module does not handle $ char remove_hf_re("^.{1,5}$")

3 3

Siremis JSONRPC problem on Bullseye
by Joseph Goettgens 07 Jun '22

07 Jun '22

Hi, I seem to have a problem setting up Siremis 5.3 on a Debian 11 box using the Kamailio 5.6.0 release (installed from repo). When I enter something like core.uptime into the JSONRPC Command Panel, I get a "System Internal Error" alert. The Apache error log then says: [Mon Jun 06 10:48:41.459377 2022] [php7:notice] [pid 22322] [client 192.168.xxx.xxx:45030] socket bind failed: No such file or directory, referer: http://deb11srv1-kamailio/siremis/sipadmin/jrcmds The path siremis/sipadmin/jrcmds obviously does not seem to exist and I assume that one needs some internal adjustments for some paths. As far as the socket is concerned, siremis/modules/sipadmin/service/siremisJRCommands.xml has the definition: UnixSockRemote name="unixsockremote" address="/var/run/kamailio/kamailio_rpc.sock" timeout="3.0"/> and the corresponding definition in /etc/kamailio/kamailio.cfg is: modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") modparam("jsonrpcs", "dgram_mode", 0666) which looks fine to me. I also checked for the existence of the socket and its access rights. Any suggestions?

2 1

t_cancel_callid - doesn't insert Reason header, if called from branch 0
by Pavel Veselovsky 07 Jun '22

07 Jun '22

Hallo all, I defined branch_failure routing block via t_on_branch_failure() In the branch_failure route, in case of "408 Request timeout" I am sending CANCEL with reason "t_cancel_callid("$ci", "$cs", "22", "408")". If the t_cancel_callid("$ci", "$cs", "22", "408") is called in branch_failure for branch idx 0, the CANCEL is sent, but Reason header is missing there. Why? (I expect that t_cancel_callid() should insert Reason header regardless of branch it is called from) If the t_cancel_callid is called in branch idx !=0, the CANCEL contains Reason header with cause as expected. Thanks for clarification of this behavior, Pavel. P.S. code snipset: event_route[tm:branch-failure:primary] { if ($T(reply_code) == "408") { if ($avp(branch_idx) == $T_branch_idx) { if (t_cancel_callid("$ci", "$cs", "22", "408")) { xlog("L_INFO", "CANCEL sent ci:$ci, cs:$cs 408"); } else { xlog("L_INFO", "CANCEL not sent ... ci:$ci, cs:$cs 408"); } $var(_palotmp_) = "sip:" + $avp(replaced_cfnry_target_number) + "@" + $dd + ":" + $dp + ";user=phone"; append_branch($var(_palotmp_),"1.0"); t_relay(); return; } } }

3 3

Fatal Python error: failed releasing import lock after fork
by Nigel Daniels 06 Jun '22

06 Jun '22

The logs appear as follows: Fatal Python error: failed releasing import lock after fork Current thread 0x 7(13) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [srid-62930e67-d-] (0 / 16) kamailio | 00007fe8fb8a4180 (most recent call first): kamailio | <no Python frame> kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tm [ctl handler] kamailio | 7(13) DEBUG: tm [callid.c:136]: child_init_callid(): callid: '06d932e436730fa0-13(a)10.10.0.4' kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tmx [ctl handler] kamailio | 7(13) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: sl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: ctl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: debugger [ctl handler] kamailio | 7(13) DEBUG: debugger [debugger_mod.c:224]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: app_python3 [ctl handler] kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:234]: sr_apy_kemi_exec_func_ex(): execution of method: .info kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:266]: sr_apy_kemi_exec_func_ex(): param[1] for: info is str: ===== kamailio.child_init(-2) kamailio | kamailio | 7(13) INFO: <core> [core/kemi.c:106]: sr_kemi_core_info(): ===== kamailio.child_init(-2) kamailio | 7(13) DEBUG: ctl [ctl.c:329]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x556774893180 kamailio | 7(13) DEBUG: ctl [ctl.c:336]: mod_child(): ctl: 0 io_listen_loop(1, 0x556774893180) kamailio | 7(13) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) kamailio | 7(13) DEBUG: ctl [io_listener.c:245]: io_listen_loop(): io_listen_loop: adding socket 8, type 2, transport 3 (/var/run/kamailio//kamailio_ctl) kamailio | 7(13) DEBUG: ctl [../../core/io_wait.h:374]: io_watch_add(): processing io_watch_add(0x7fe8f9aef380, 8, 2, 0x556774893180) - fd_no=0 Running python 3.8.10 using the suggested. # ----------------- setting module-specific parameters --------------- # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) ####### Routing Logic ######## modparam("app_python3", "load", "/opt/kamailio/etc/kamailio.py") cfgengine "python"a import sys import KSR as KSR def dumpObj(obj): for attr in dir(obj): KSR.info("obj.%s = %s\n" % (attr, getattr(obj, attr))) def mod_init(): KSR.info("===== from Python mod init\n") dumpObj(KSR) return kamailio() class kamailio: def __init__(self): KSR.info('===== kamailio.__init__\n') def child_init(self, rank): KSR.info('===== kamailio.child_init(%d)\n' % rank) return 0 def ksr_request_route(self, msg): KSR.info("===== request - from kamailio python script\n") KSR.setdsturi("sip:alice@127.0.0.1:5080") KSR.tm.t_on_branch("ksr_branch_route_one") KSR.tm.t_on_reply("ksr_onreply_route_one") KSR.tm.t_on_failure("ksr_failure_route_one") KSR.sl.send_reply(100, "Trying") if KSR.tm.t_relay() < 0 : KSR.sl.send_reply(500, "Server error") return 1 def ksr_reply_route(self, msg): KSR.info("===== response - from kamailio python script\n") return 1 def ksr_onsend_route(self, msg): KSR.info("===== onsend route - from kamailio python script\n") return 1 def ksr_branch_route_one(self, msg): KSR.info("===== branch route - from kamailio python script\n") return 1 def ksr_onreply_route_one(self, msg): KSR.info("===== onreply route - from kamailio python script\n") return 1 def ksr_failure_route_one(self, msg): KSR.info("===== failure route - from kamailio python script\n") return 1 Any help is appreciated, thanks. -- - Nigel

2 3

SNMP, export concurrent calls count
by ZZ Wave 30 May '22

30 May '22

Hello. Debian 10, Kamailio 5.2.1 I want to monitor concurrent calls in/out per every trunk connected to this proxy (it's done with dialog profiles), and export this to Zabbix. But I can't find in snmpstats documentation how to export user-defined variables. Help me please. Maybe SNMP isn't the best solution for that...

2 1

Centos kamailio.repo file is not updated
by Patrick Wakano 30 May '22

30 May '22

Hello ist, I've noticed some of the latest releases do not have their repo mentioned in the https://rpm.kamailio.org/centos/kamailio.repo The repos are there, it is just the kamailio.repo file missing some of the newer versions like 5.4.7, 4.5.8, 5.5.4, 5.6.0... Cheers, Patrick

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