sr-users July 2025

sr-users@lists.kamailio.org

47 participants
37 discussions

Dispatcher failover to the next least loaded destination
by i.ribakov＠zaleos.net 25 Jul '25

25 Jul '25

Hi all, I'm wondering if it is currently supported to perform failover while respecting the call load distribution algorithm. What makes me doubt this is possible is the following wording in the documentation: > The rest of the destination list is taken in order of the entries in set - anyhow, until a re-route to next destination happens, the load on each address can change. From it it's not clear if ds_next_dst() will simplify use next entry from the AVP list or if it will attempt to intelligently choose next entry from the AVP list taking into the account updated call load of the remaining entries.

1 0

Error: receive_fd(): EOF on 18
by Fernando Lopes 25 Jul '25

25 Jul '25

Hello everyone, I'm getting this during start up error and I can't figure out what it means. I've searched for a solution but haven't found anything relevant. Also I don't see any useful debug messages during to complement this error. 19(61) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 18 0(2) ALERT: <core> [main.c:792]: handle_sigs(): child process 49 exited by a signal 11 0(2) ALERT: <core> [main.c:796]: handle_sigs(): core was generated 0(2) INFO: <core> [main.c:819]: handle_sigs(): terminating due to SIGCHLD Any tips for debugging or finding the problem. Thank you.

3 4

Re: [sr-dev] git:master:79f6439f: tls: added support for tls keys log
by Sergei Safarov 24 Jul '25

24 Jul '25

I think exist is more elegant way to export encyptions keys to the file Need to start Kamailio with defined SSLKEYLOGFIL=/path/here/to/file environment variable This I have tested for TLS 1.2 and TLS 1.3. All works perfectly More details you can find at https://www.youtube.com/watch?v=Cq6yj9se9M4&t=1850s Probable this change do not required because allow secret keys to logs. On Thu, 2025-07-24 at 12:42 +0200, Daniel-Constantin Mierla via sr-dev wrote: > Module: kamailio > Branch: master > Commit: 79f6439f16f6b715858414689c7c04cf22164ace > URL: > https://github.com/kamailio/kamailio/commit/79f6439f16f6b715858414689c7c04c… > > Author: Daniel-Constantin Mierla <miconda(a)gmail.com> > Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> > Date: 2025-07-24T12:28:13+02:00 > > tls: added support for tls keys log > > - they can be printed to syslog (NOTICE level) or file > > --- > > Modified: src/modules/tls/tls_domain.c > Modified: src/modules/tls/tls_mod.c > Modified: src/modules/tls/tls_util.c > Modified: src/modules/tls/tls_util.h > > --- > > Diff: > https://github.com/kamailio/kamailio/commit/79f6439f16f6b715858414689c7c04c… > Patch: > https://github.com/kamailio/kamailio/commit/79f6439f16f6b715858414689c7c04c… > > _______________________________________________ > Kamailio - Development Mailing List -- sr-dev(a)lists.kamailio.org > To unsubscribe send an email to sr-dev-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only > to the sender!

1 0

Error: different number of preprocessor directives
by Fernando Lopes 24 Jul '25

24 Jul '25

Hello everyone, I'm having an issue with my Kamailio config where I'm getting the following error: ERROR: bad config file (0 errors) (parsing code: 0) 0(2) ERROR: <core> [core/ppcfg.c:276]: pp_ifdef_level_error(): different number of preprocessor directives: 1 more #!if[n]def as #!endif I've gone through the config up and down so many times and can't seem to find the problem. I have a definitions.cfg file where I define all the variables, and I’ve made sure that every #!ifdef WITH_SOMETHING has a corresponding definition. I also ran this command (recommended by GPT): grep -E '#!ifn?def|#!endif' /usr/local/etc/kamailio/kamailio.cfg It shows matching numbers of #!ifdef and #!endif, and I’ve checked it manually several times — everything looks fine. Any tips for debuging or finding the problem. #!ifdef WITH_CDRS #!endif #!ifdef WITH_DEBUG #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_FAIL2BAN #!ifdef WITH_ANTIFLOOD #!endif #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_RESPONSE_STATS #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_CDRS #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_HTTP #!endif #!ifdef WITH_WEBSOCKETS #!endif #!ifdef WITH_NAT #!ifdef WITH_RTPENGINE #!endif #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_ANTIFLOOD #!endif #!ifdef WITH_FAIL2BAN #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_CDRS #!endif #!ifdef WITH_FAIL2BAN #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_ANTIFLOOD #!endif #!ifdef WITH_NATSIPPING #!endif #!ifdef WITH_NOAUTH_PRIVATE_NET #!endif #!ifdef WITH_AUTH #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_WEBSOCKETS #!endif #!ifdef WITH_HTTP #!ifdef WITH_WEBSOCKETS #!endif #!endif #!ifdef WITH_RTPENGINE #!endif Thank you.

7 7

rtpengine error: no rtpp_set_list->rset_first
by disa_369＠msn.com 24 Jul '25

24 Jul '25

Hello to everyone. I deployed Kamailio on Debian system. Install was successfull. I have the task to use Kamailio as proxy between Avaya PBX and Videoconference System. Outgoing calls only from IPPhone ----- Avaya PBX ---sip----> Kamailio -----sip----> Video System-IVR Now Im trying setup rtpengine for proxy media . Kamailio has some errors by starting service. ERROR: rtpengine [rtpengine.c:3131]: select_rtpp_set(): no rtpp_set_list->rset_first Jun 06 12:07:00 zaks-sbc01-op /usr/sbin/kamailio[635658]: NOTICE: rtpengine [rtpengine.c:1815]: mod_init(): Default rtpp set 0 NOT found Missed out on something in config?

3 7

kamailio 5.8.6 sanity problem
by ale Gural 24 Jul '25

24 Jul '25

Hello, when kamailio 5.8.6 got the follow SIP message. INVITE sip:026774800@kamnet:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.25.206.73:5060;branch=z9hG4bK6204h710copg0h2s34a0.1 From: <sip:506555021@kamnet :5060;transport=UDP;user=phone>;tag=BN-1778920881-1-1752995491-343935404 To: <urn:service:sos.police@kamnet> Call-ID: 5f6d530-13f3cbf9-fb215-7f1546651f58-4d0f660a-13c4-764 CSeq: 1 INVITE X-SessionId: -1778920881 User-Agent: BN4000-3.9.2-706 Max-Forwards: 60 Supported: norefersub,timer,100rel,199 P-Asserted-Identity: <sip:506555021@hotmobile.co.il:5060 ;transport=UDP;user=phone> P-Asserted-Identity: <tel:506555021;phone-context=+972> Contact: <sip:10.25.206.73:5060;yop=00.00.84CE62D9.0000.7009;transport=udp> P-Early-Media: supported P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=425074efe02c6a01 Content-Disposition: session;handling=required Allow: INVITE,CANCEL,ACK,BYE,OPTIONS,INFO,PRACK,UPDATE,REFER,NOTIFY Content-Type: application/sdp Content-Length: 207 v=0 o=BN4000 0 0 IN IP4 10.9.21.56 s=- c=IN IP4 10.9.21.56 t=0 0 m=audio 54732 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=maxptime:20 a=ptime:20 the TO To: <urn:service:sos.police@kamnet>, the problem is kamailio 5.8.6 response with 400 bad to header but kamailio 5.7.5 continue with normal call. here you can see the sanity log for both kamailio: kamailio 5.8.6 Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:254]: check_ruri_sip_version(): check_ruri_sip_version entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:278]: check_ruri_sip_version(): check_ruri_sip_version passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:286]: check_ruri_scheme(): check_ruri_scheme entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:305]: check_ruri_scheme(): check_ruri_scheme passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:327]: check_required_headers(): check_required_headers entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:350]: check_required_headers(): check_required_headers passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:519]: check_cseq_method(): check_cseq_method entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:553]: check_cseq_method(): check_cseq_method passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:563]: check_cseq_value(): check_cseq_value entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:591]: check_cseq_value(): check_cseq_value passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:601]: check_cl(): check_cl entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:626]: check_cl(): check_cl passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:643]: check_expires_value(): check_expires_value entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:679]: check_expires_value(): no expires header found Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:776]: check_parse_uris(): check_parse_uris entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:780]: check_parse_uris(): parsing ruri Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:793]: check_parse_uris(): looking up From header Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:808]: check_parse_uris(): looking up To header Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: <core> [core/parser/parse_uri.c:1369]: parse_uri(): bad char '@' in state 5 parsed: <urn:service:sos.police> (22) / <urn:service:sos.police@kamnet> (29) Jul 20 17:08:15 vm-tkamprov-n 671587 ERROR: <core> [core/parser/parse_to.c:81]: parse_to_uri(): failed to parse To uri Jul 20 17:08:15 vm-tkamprov-n 671587 WARNING: sanity [sanity.c:810]: check_parse_uris(): invalid To header or uri kamailio 5.7.5 Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:253]: check_ruri_sip_version(): check_ruri_sip_version entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:277]: check_ruri_sip_version(): check_ruri_sip_version passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:285]: check_ruri_scheme(): check_ruri_scheme entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:304]: check_ruri_scheme(): check_ruri_scheme passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:326]: check_required_headers(): check_required_headers entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:349]: check_required_headers(): check_required_headers passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:518]: check_cseq_method(): check_cseq_method entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:552]: check_cseq_method(): check_cseq_method passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:562]: check_cseq_value(): check_cseq_value entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:590]: check_cseq_value(): check_cseq_value passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:600]: check_cl(): check_cl entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:625]: check_cl(): check_cl passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:638]: check_expires_value(): check_expires_value entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:674]: check_expires_value(): no expires header found Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:771]: check_parse_uris(): check_parse_uris entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:775]: check_parse_uris(): parsing ruri Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:788]: check_parse_uris(): looking up From header Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:803]: check_parse_uris(): looking up To header Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:853]: check_parse_uris(): check_parse_uris passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity_mod.c:252]: w_sanity_check(): sanity checks result: 1 Thanks

4 5

not enough memory for safe operation
by David Cunningham 24 Jul '25

24 Jul '25

Hello, Would anyone have insight into the following errors? We saw several thousand of them appear in a short period of time: Jul 24 10:41:36 vpbx11 /sbin/kamailio[54805]: ERROR: tls [tls_server.c:192]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=67537152 threshold1=76546048 Jul 24 10:41:36 vpbx11 /sbin/kamailio[54805]: ERROR: tls [tls_server.c:192]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=67536032 threshold1=76546048 However there should have been plenty of shared memory available. These were take around 30 minutes later: # kamctl stats shmem { "jsonrpc": "2.0", "result": [ "shmem:fragments = 407525", "shmem:free_size = 4117928416", "shmem:max_used_size = 4256807952", "shmem:real_used_size = 177038880", "shmem:total_size = 4294967296", "shmem:used_size = 111803416" ], "id": 56272 } # kamcmd pkg.stats pid 54805 { entry: 121 pid: 54805 rank: -1 used: 1249880 free: 6475408 real_used: 1913200 total_size: 8388608 total_frags: 1185 } # ps -ef | grep kama | wc -l 148 Thanks in advance for any tips or insight! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

1 0

Basic Configuration
by smh2017＠zoho.com 23 Jul '25

23 Jul '25

I am trying to set up a very basic SIP server. I can only establish external-to-internal calls using the following parameters with the default configuration files: RTP Engine Config File interface=server_local_ip!public_domain_name Kamailio Config File alias="public_domain_name" listen=server_local_ip:5061 adverise public_domain_name:5061 I cannot establish internal-to-external calls nor external-to-external calls with the above configuration settings. In these failed calls, the answering external callee UA sends 200-OK, but the caller UA does not ACK. In looking at the sip trace messages, no alias for the public ip address is appended to the Contact header of the external UA's 200-OK SIP message. So perhaps the caller doesn't know where to send the ACK. The network setup has the local UAs and the Kamailio server behind a port-forwarded NAT routher. External (internet) UAs are also behind NAT routers. Is there a change or addition to the above config snippets that would solve the problem, or do I need to add some instruction to the routing section? Finally, does anyone sell or otherwise offer basic Kamailio/RTPEngine configuration files that work more or less "out-of-the box" for the described setup? Thanks, Steve Hamilton

2 3

Configure TLS 1.3 cipher suites
by caique.cornelio＠mitel.com 22 Jul '25

22 Jul '25

Is the removal of a specific TLS 1.3 cipher supported as today? I am working on making the ciphers accepted configurable and i know it is possible with TLS <1.2, wondering if it is the same case with 1.3.

3 2

Best Book Recommendation for Learning SIP/VoIP
by Fernando Lopes 22 Jul '25

22 Jul '25

Hi everyone, I'm not new but also not a professional to the world of SIP and VoIP but feeling lost, and I'm looking to get a solid foundational understanding. I was wondering if anyone could recommend a good book that explains SIP in a clear and practical way? Whether it's a textbook, a practical guide, or even an eBook, I’d really appreciate your recommendations! Thanks in advance!

4 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 July 2025