sr-users December 2025

sr-users@lists.kamailio.org

28 participants
23 discussions

Planning to next major release series Kamailio v6.1.x
by Daniel-Constantin Mierla 08 Jan '26

08 Jan '26

Hello, last week several developers went to Dusseldorf for the Kamailio Devel Meeting for two fruitful days working on merging some of the pull request, address many reported issues, building a new deb packaging infrastructure, as well as add new features. Among achievements: reviewing/merging a couple of PRs, including merging a new module; pull request to use stdatomic; completing the building of debs with cmake; start of creating the new platform for deb building; proper support for async sql queries with no connection available at start up; more modules not destroying structures at shut down to avoid races; archiving a few modules ... During a video conference with other main developers, it was also discussed about the roadmap to the next major release series, respectively Kamailio v6.1.x, agreeing more or less to continue the development for about 2-3 weeks to allow people to still contribute new features, then enter the testing phase. Based on that, I would propose: - freeze the development at the beginning of January 7, 2027 (to be after the winter/season holidays, before many devs might be offline) - testing phase as needed for 4 to 6 weeks - release likely to be by mid of February or slightly later The new features have to be pushed to the git repository or made pull requests by freeze date. Should anyone want to suggest alternatives, just propose them to sr-dev mailing list to be discussed further with the developers. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 2

Kamailio 6.0 failed to start on Alpine
by Cindy Leung 05 Jan '26

05 Jan '26

Hello, We have recently upgraded our Alpine base image (3.23) along with Kamailio (6.0.4) and we are getting segfault at startup. Our custom config was working in Alpine 3.22 with Kamailio 5.8.4. We are not building Kamailio from source. We're getting it from apk. We were able to locate the problem with TLS. We tested with the default config that shipped with the package - segfault. Our self-signed cert is generated by this: openssl req -newkey rsa:2048 -x509 -keyout private.key -out cert.pem -days 3650 -nodes -subj "/C=US/ST=/L=/O=/OU=/CN=" We tried to build it from source - segfault Then we tried the same exercise with Ubuntu - apt install kamailio kamailio-tls-modules Using the same certificate, using the default config in the package, no segfault. I wish you all Happy Holidays!! TIA. Here're the logs from the alpine startup: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.2:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.2:5060 tls: 127.0.0.1:5061 tls: 172.17.0.2:5061 Aliases: tls: ef79bc4947ca:5061 tls: localhost:5061 tcp: ef79bc4947ca:5060 tcp: localhost:5060 udp: ef79bc4947ca:5060 udp: localhost:5060 0(45) INFO: <core> [core/tcp_main.c:5252]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(45) INFO: <core> [main.c:3322]: main(): current open file limits [soft/hard]: [1048576/1048576] Segmentation fault (core dumped) /usr/sbin/kamailio -E -f /etc/kamailio/kamailio.cfg -DD (gdb) bt full #0 0x0000ffffbe397df4 in __pthread_getspecific (k=k@entry=0) at src/thread/pthread_getspecific.c:8 self = <optimized out> #1 0x0000ffffbe2c2300 in mod_init () at tls_mod.c:406 method = <optimized out> verify_client = <optimized out> rand_buf = "\210\000\001\000\001\000\000\000\200\004\360\330\377\377\000\000\024\3518\276\377\377\000\000\275@ =\276\377\377\000" k = 0 __func__ = "mod_init" __llevel = <optimized out> __kld = <optimized out> #2 0x0000aaaad4e659b8 in init_mod (m=0xffffbdb86660) at core/sr_module.c:1037 ret = <optimized out> __func__ = "init_mod" #3 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb89bb0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #4 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8a110) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #5 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8aac0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #6 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8b840) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #7 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8dad0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #8 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8eab0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #9 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8f2c0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #10 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb90220) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #11 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9a740) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #12 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ac60) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #13 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9b0b0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #14 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9bad0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #15 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ceb0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #16 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9dc70) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #17 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9eba0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #18 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9f410) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #19 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9f8c0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #20 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ff70) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #21 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba1b60) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #22 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba2060) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #23 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba3040) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #24 0x0000aaaad4e6a34c in init_modules () at core/sr_module.c:1068 t = <optimized out> i = <optimized out> __func__ = "init_modules" #25 0x0000aaaad4c349b4 in main (argc=<optimized out>, argv=<optimized out>) at main.c:3353 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffbe3f7ba0 <ldso> "" tmp_len = 0 port = 5060 proto = 0 aproto = 0 ahost = 0x0 socket_name = 0x0 aport = 0 listen_field_count = <optimized out> listen_fields = {0x18 <error: Cannot access memory at address 0x18>, 0x99ba <error: Cannot access memory at address 0x99ba>, 0x18 <error: Cannot access memory at address 0x18>} options = 0xaaaad4f178ee ":f:cm:M:dVIhEeb:B:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1938757098 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> n_lst = <optimized out> p = <optimized out> tbuf = 0xffffd8f01ab0 "!" tbuf_tmp = <optimized out> st = {st_dev = 63, st_ino = 48481, st_mode = 16877, st_nlink = 1, st_uid = 100, st_gid = 0, st_rdev = 0, __pad = 0, st_size = 4096, st_blksize = 4096, __pad2 = 0, st_blocks = 8, st_atim = {tv_sec = 1766082557, tv_nsec = 947394010}, st_mtim = {tv_sec = 1766093215, tv_nsec = 591712013}, st_ctim = {tv_sec = 1766093215, tv_nsec = 591712013}, __unused = {0, 0}} l1 = <optimized out> lim = {rlim_cur = 1048576, rlim_max = 1048576} option_index = 0 long_options = {{name = 0xaaaad4f18d0a "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0xaaaad4f2682c "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0xaaaad4f3197d "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0xaaaad4f18d0f "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0xaaaad4f18d15 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0xaaaad4f18d1e "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0xaaaad4f18d28 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0xaaaad4f18d32 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0xaaaad4f18d3d "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0xaaaad4f18d46 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0xaaaad4f26949 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0xaaaad4f18d51 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0xaaaad4f18d5b "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0xaaaad4f18d62 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" Cindy

4 7

topos-redis kamailio 6.x
by Angel Elena 02 Jan '26

02 Jan '26

hi, good afternoon. I'm testing Kamailio 6.0 on Debian 13 and I need to hide the network topology for a specific provider and keeping the contact header simple (topos.so style). My topos.so config loadmodule "topos_redis.so" loadmodule "topos.so" loadmodule "ndb_redis.so" modparam("topos", "storage", "redis") modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379;db=0") modparam("topos_redis", "serverid", "srv1") modparam("topos", "sanity_checks", 1) modparam("topos", "branch_expire", 3600) modparam("topos", "dialog_expire", 14400) with this config in kamailio.log appears this issue (it's a migrated config from 5.4 version): Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61635]: ERROR: topos [tps_storage.c:663]: tps_storage_record(): failed to store (dlg: 0 dir: 0 metid: 512) Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61636]: ERROR: topos_redis [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for a_contact Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61634]: ERROR: topos_redis [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for a_contact Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61633]: ERROR: topos_redis [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for a_contact I'm reading the documentation, but I don't see how to increase these values to avoid these errors. Thank you and happy holidays --------------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://diablo.craem.net _(___V @craem_ www.linkedin.com/in/angel-elena-medina --------------------------------------- Kopano Webapp.

3 3

Intermittent S-CSCF → HSS Diameter Connection Failure - CER Not Sent After TCP Connect
by Qasim Loay 30 Dec '25

30 Dec '25

Hello Kamailio Community, We're experiencing a *critical issue* in Kamailio where S-CSCF randomly stops sending CER to HSS in some cases after establishing TCP connections, causing complete authentication failures. Please find the attached (IMS containers + HSS )logs and the current configuration. *Environment* - *Kamailio Version:* kamailio 6.0.2 (x86_64/linux) d4dc5d - *Deployment:* SCSCF and HSS as a container on same physical machine using macvlan networking *Components:* - SCSCF: 172.22.1.20 - HSS: 172.22.1.3 - ICSCF: 172.22.1.19 *Problem Description* *The issue occurs randomly* - the system works normally for periods of time, then suddenly the Diameter connection between SCSCF and HSS fails and enters a reconnection seems loop. *Here's the cycle we're observing:* *1. *SCSCF: WARNING: cdp [peermanager.c:337]: peer_timer(): Inactivity on peer [hss.epc.mnc092.mcc418.3gppnetwork.org] and no DWA, Closing peer... *2. State Timeout (~40 seconds later):* S-CSCF: ERROR: cdp [peerstatemachine.c:164]: sm_process(): in state Closed timeout event Timeout *3. Reconnection Attempt (~30 seconds later):* SCSCF: INFO: cdp [peerstatemachine.c:551]: I_Snd_Conn_Req(): Peer hss.epc.mnc092.mcc418.3gppnetwork.org SCSCF: INFO: cdp [receiver.c:991]: peer_connect(): Trying to connect to 172.22.1.3 port 3870 SCSCF: INFO: cdp [receiver.c:1090]: peer_connect(): Peer hss.epc.mnc092.mcc418.3gppnetwork.org:3870 connected *4. HSS Side (waiting indefinitely):*HSS: [hss:0.19.37] 2025/12/25 04:46:39.060208 [INF] [scscf>hss:0][waiting for CER from 172.22.1.20:33284] *Cascading Effects:* *ICSCF accumulates branches:* ICSCF: ERROR: tm [t_fwd.c:792]: add_uac(): maximum number of branches exceeded ICSCF: ERROR: tm [t_fwd.c:1771]: t_forward_nonack(): failure to add branches *Result:* each UE cannot be able to register to IMS and VoLTE service outage for all UEs Best regards, Qasim Loay

2 1

Merry Christmas and Happy Holidays 2025-2026!
by Daniel-Constantin Mierla 25 Dec '25

25 Dec '25

The 2025 was one of the best years for Kamailio project development and evolution, with significant contributions from community, among them: - many new modules from new and non-core developers (some still PRs to be merged soon) - cmake-based building system - a new platform to build Debian packages - optional multi-threading handling for UDP and TLS, stdatomic support for ARM, ... - use of OpenCollective platform as a collaborative source for funding the project A new major release is planned during the first months of 2026! Relying on an amazing community of developers and users, we hope that Kamailio kept helping people and companies world wide to connect with the dear ones and build a better way of living. The season holidays are ahead, from the winter in the Northern to the summer in the Southern Hemisphere, it is the time to relax, spend time with family and friends! I take again this chance to express my thanks and greetings to all the friends, developers, supporting companies and community members that made 2025 another fantastic year for Kamailio project. Enjoy the holidays! Merry Christmas! Daniel * Santa is flying Kamailio! * -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 0

Merry Christmas and Happy Holidays
by Henning Westerholt 24 Dec '25

24 Dec '25

Hello, I wish you Merry Christmas and Happy Holidays! Thank you for all the interesting discussions, bug reports, pull-requests and any other contribution for the Kamailio project this year. Best regards, Henning Westerholt -- Kamailio and VoIP services - gilawa.com

2 1

Kamailio + RTPEngine same host question
by Brandon Armstead 24 Dec '25

24 Dec '25

Hey all, Curious on the idea of running kamailio and rtpengine on the same host, has anyone done this with production levels of traffic? Looking to get some various opinions. Pros / Cons? Thanks in advance! - Brandon

2 1

how to kamcmd htable.get name starting with + sign
by Benoît Panizzon 19 Dec '25

19 Dec '25

Hi all We store stuff like cfw information for a local number in a htable. Numbers are in e164 format. With the cli kamcmd tool I don't seem to be able to access such names. I verified with htable.dump that the entry is present: # kamcmd htable.dump assignedtn | grep 6608 name: +41315996608 [...] But no matter what I try, don't get the values: kamcmd> htable.get assignedtn +41315996608 error: 500 - Not enough parameters (htable name and key name) kamcmd> htable.get assignedtn \+41315996608 error: 500 - Key name doesn't exist in htable. kamcmd> htable.get assignedtn '+41315996608' error: 500 - Key name doesn't exist in htable. kamcmd> htable.get assignedtn "+41315996608" error: 500 - Key name doesn't exist in htable. kamcmd> htable.get assignedtn "\+41315996608" error: 500 - Key name doesn't exist in htable. kamcmd> htable.get assignedtn "\\+41315996608" error: 500 - Key name doesn't exist in htable. kamcmd> htable.get assignedtn %2B41315996608 error: 500 - Key name doesn't exist in htable. How do I have to escape the + sign? -- 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

Replacing an attribute in the SDP
by David Cunningham 19 Dec '25

19 Dec '25

Hello, We need to replace a=sendrecv with a=sendonly in the 200 OK reply to an INVITE. In theory it should be something straightforward, like in the onreply_route using: replace_body_all( "a=sendrecv", "a=sendonly" ); or: subst_body( '/^a=sendrecv/a=sendonly/' ) Our first problem is that these both are appending a=sendonly to the end of the SDP, not replacing values within it. Does anyone know why this might happen? Our second problem is that we really only want to do this for video media, and not touch the audio media. Are there any text tools that allow you to work with specific media within the SDP? Thanks in advance for any tips! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 6

Regresion from 5.8.4 to 5.8.6
by Ihor Olkhovskyi 18 Dec '25

18 Dec '25

Not sure where the bug is, just noticed when playing on local development Kamailio installation, that simple rewrite of $fu start to act funky. Initial From field in a packet is: From: sip:90001@localhost.localdomain ;tag=83017fca-9fe4-493e-9e66-406034482628 In the code I'm having a statement $fu = "sip:" + $avp(callerID) + "@localhost.localdomain"; Resulting From field on 5.8.4 looks like From: sip:90001@localhost.localdomain ;tag=83017fca-9fe4-493e-9e66-406034482628 Note the 2 spaces after From, but it's ok, I guess, no other changes which is fine. But exact the same config file on 5.8.6 giving this: From: <sip:90001@localhost.localdomain>sip:90001@localhost.localdomain ;tag=83017fca-9fe4-493e-9e66-406034482628 Which is not correct SIP URI. I'm not sure when the issue was introduced, but that's what I've found. If will have a bit more time, will try to investigate deeper, maybe just to warn about possible bugs with the versions greater than 5.8.4 (have not tested 5.8.5) -- Best regards, Ihor (Igor)

3 9

2026

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 December 2025