sr-users December 2025

sr-users@lists.kamailio.org

28 participants
26 discussions

Postgres connections optimization #4342
by Stephane Savonitto 11 Jun '26

11 Jun '26

Hello, On P-CSCF when running we have 200+ permanent connection to postgres db, even if there is no traffic. Is there a way to manage connections dynamically using a pool like using PgBouncer ? Regards, Stéphane

5 9

Kamailio & Asterisk SIP Registration Forwarding - Asterisk replies 401 Unauthorized
by Ben Fitzgerald 17 Apr '26

17 Apr '26

Hi, I've been following this integration tutorial http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb and have a successful registration and I can even make calls through my asterisk box. However what is unusual to me is that every time a phone registers with Kamailio, that is forwarded to Asterisk (as expected), yet Asterisk replies with 401 Unauthorized. Oddly enough the phone registers and can still make calls. What worries me is that as we scale to 100's of cps, this seemingly erroneous message may slow down Asterisk because it's trying to handle authentication for users which have already been authenticated by Kamailio. If this behavior is expected, then that would be good to know as well. This is the sip debug from ASTERISK (I have replaced IP's with the names of the servers): <--- SIP read from TCP:kamailio:41205 ---> REGISTER sip:asteriskIP:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP kamailio;branch=z9hG4bK998f.2846e405000000000000000000000000.0 To: <sip:40081@asteriskIP> From: <sip:40081@asteriskIP>;tag=32fda68bf54efeeb04e3edc67b53c63d-cfb0 CSeq: 10 REGISTER Call-ID: 0005ce130bcee5c4-26538@kamailio Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.3.0 (x86_64/linux)) Contact: <sip:40081@kamailio:5060> Expires: 3600 <-------------> --- (11 headers 0 lines) --- Sending to kamailio:5060 (no NAT) Sending to kamailio:5060 (no NAT) <--- Transmitting (no NAT) to kamailio:5060 ---> SIP/2.0 401 Unauthorized Via: SIP/2.0/TCP kamailio;branch=z9hG4bK998f.2846e405000000000000000000000000.0;received= kamailio From: <sip:40081@asteriskIP>;tag=32fda68bf54efeeb04e3edc67b53c63d-cfb0 To: <sip:40081@asteriskIP>;tag=as404bac9a Call-ID: 0005ce130bcee5c4-26538@ kamailio CSeq: 10 REGISTER Server: Asterisk PBX 11.6-cert2 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="262b338e" Content-Length: 0 <------------> Scheduling destruction of SIP dialog '0005ce130bcee5c4-26538@ kamailio' in 32000 ms (Method: REGISTER) Scheduling destruction of SIP dialog '0005ce130bcee5c4-26538@ kamailio' in 32000 ms (Method: REGISTER) Really destroying SIP dialog '0005ce130bcee5c1-26536@ kamailio' Method: REGISTER ========================= sip.conf for kamailio trunk: [kamailio-inbound] type=friend dtmfmode=auto host=kamailioIP allow=all context=sipout insecure=port,invite canreinvite=no ======================== Asterisk version: 11.6-cert2 Kamailio version: 4.3 Benjamin Fitzgerald LETS Corporation (925) 235-1154 ben(a)letscorp.us *******Confidential Notice: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this message in error, please delete this message from all computers and contact Orion Systems/LETS Corp immediately by return e-mail and/or telephone at (925) 566-5600

4 8

problems using kamailio
by Peter Walber 17 Apr '26

17 Apr '26

Hello, I try to use kamailio as webrtc-sip-gateway between my openhab smart home system and my doorbird doorbell with phone and camera. I try to use the product of "https://github.com/florian-h05/webrtc-sip-gw". Which integrates kamailio together with rtpengine to the gateway. I want to use openhab as SIP Client and have a Telekom Speedport Smart 4 Router on the other side. The webrtc-sip-gw from florian-h05 shall be the software between Openhab and the speedport smart 4. On the speedport smart router the SIP Server is enabled and configured. I can sucessfully call with zoiper extern phone numbers. The doorbird als is configured correctly. I can call the doorbird with my zioper softphone using the SIP interface of the doorbird. The runtime system is a docker container on debian 12. I want to call the doorbird by SIP from my openhab SIP client. I can initiate the call, but it doesn't establish Here is the log from the docker container. --------------------------------------------------------------------------------------------------- 2025-08-07T07:46:57.384687165Z 9(52) INFO: <script>: HTTP Request Received 2025-08-07T07:46:57.391479050Z 9(52) INFO: <script>: START: REGISTER from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:46:57.391516534Z 9(52) INFO: <script>: Current Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:243e461d-f0cb-4c09-9a63-f57c9bba8d6b>";expires=600 2025-08-07T07:46:57.391526535Z 9(52) INFO: <script>: Setting new Contact header: <sip:**73@192.168.2.209:5060> 2025-08-07T07:47:00.195739350Z 9(52) INFO: <script>: START: INVITE from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:47:00.195800424Z 9(52) INFO: <script>: Current Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws;ob> 2025-08-07T07:47:00.195811886Z 9(52) INFO: <script>: Setting new Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws;ob;alias=192.168.2.185~39510~6;alias=192.168.2.185~39510~6> 2025-08-07T07:47:00.196163528Z 9(52) INFO: <script>: MANAGE_BRANCH: New branch [0] to sip:**72@speedport.ip 2025-08-07T07:47:00.196181228Z 9(52) INFO: <script>: NATMANAGE branch_id:0 ruri: sip:**72@speedport.ip, method:INVITE, status:<null>, extra_id: z9hG4bK44082210, rtpengine_manage: replace-origin replace-session-connection via-branch=extra rtcp-mux-demux SDES-off ICE=remove RTP/AVP 2025-08-07T07:47:00.196608235Z INFO: [penvq8f06ehafutk9ivf]: [control] Received command 'offer' from 127.0.0.1:50790 2025-08-07T07:47:00.196625247Z NOTICE: [penvq8f06ehafutk9ivf]: [core] Creating new call 2025-08-07T07:47:00.198519843Z INFO: [penvq8f06ehafutk9ivf]: [control] Replying to 'offer' from 127.0.0.1:50790 (elapsed time 0.001979 sec) 2025-08-07T07:47:01.927528447Z 9(52) INFO: <script>: START: CANCEL from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:47:01.927577111Z 9(52) INFO: <script>: Current Contact header: <null> 2025-08-07T07:47:01.927586439Z 9(52) INFO: <script>: Setting new Contact header: <null> 2025-08-07T07:47:09.169489716Z 7(50) INFO: <script>: WebSocket connection from 192.168.2.185:39510 has closed *2025-08-07T07:47:27.355185671Z 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found* 2025-08-07T07:47:27.914769340Z 9(52) INFO: <script>: HTTP Request Received 2025-08-07T07:47:27.951608347Z 9(52) INFO: <script>: START: REGISTER from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:27.951663073Z 9(52) INFO: <script>: Current Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:39eac0ca-0aea-4526-a5c7-0516bc8a2d71>";expires=600 2025-08-07T07:47:27.951915520Z 9(52) INFO: <script>: Setting new Contact header: <sip:**73@192.168.2.209:5060> 2025-08-07T07:47:30.168546446Z 2(45) INFO: <script>: BRANCH FAILED: z9hG4bK4408221 + 0INFO: [penvq8f06ehafutk9ivf]: [control] Received command 'delete' from 127.0.0.1:36296 2025-08-07T07:47:30.168587880Z INFO: [penvq8f06ehafutk9ivf]: [core] Deleting call branch '' (via-branch 'z9hG4bK44082210') 2025-08-07T07:47:30.168597011Z INFO: [penvq8f06ehafutk9ivf]: [core] Call branch '' (via-branch 'z9hG4bK44082210') deleted, no more branches remaining 2025-08-07T07:47:30.168605215Z INFO: [penvq8f06ehafutk9ivf]: [core] Deleting entire call 2025-08-07T07:47:30.168612883Z INFO: [penvq8f06ehafutk9ivf]: [core] Final packet stats: 2025-08-07T07:47:30.168620604Z INFO: [penvq8f06ehafutk9ivf]: [core] --- Tag 'utenlull77', created 0:30 ago for branch '' 2025-08-07T07:47:30.168628359Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscribed to '' 2025-08-07T07:47:30.168636445Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscription for '' 2025-08-07T07:47:30.168645446Z INFO: [penvq8f06ehafutk9ivf]: [core] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using unknown codec 2025-08-07T07:47:30.168653691Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23484 <> 192.168.2.185:60650, SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168661939Z INFO: [penvq8f06ehafutk9ivf]: [core] --- Tag '', created 0:30 ago for branch 'z9hG4bK44082210' 2025-08-07T07:47:30.168669844Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscribed to 'utenlull77' 2025-08-07T07:47:30.168677713Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscription for 'utenlull77' 2025-08-07T07:47:30.168685661Z INFO: [penvq8f06ehafutk9ivf]: [core] ------ Media #1 (audio over RTP/AVP) using unknown codec 2025-08-07T07:47:30.168693705Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23472 <> :0 , SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168718608Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23473 <> :0 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168728065Z INFO: [penvq8f06ehafutk9ivf]: [control] Replying to 'delete' from 127.0.0.1:36296 (elapsed time 0.000505 sec) *2025-08-07T07:47:30.169042099Z 2(45) INFO: <script>: Failure: <null> 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found* 2025-08-07T07:47:30.265075785Z 9(52) INFO: <script>: START: INVITE from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:30.265125134Z 9(52) INFO: <script>: Current Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws;ob> 2025-08-07T07:47:30.265135557Z 9(52) INFO: <script>: Setting new Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws;ob;alias=192.168.2.185~44816~6;alias=192.168.2.185~44816~6> 2025-08-07T07:47:30.265484502Z 9(52) INFO: <script>: MANAGE_BRANCH: New branch [0] to sip:**72@speedport.ip 2025-08-07T07:47:30.265664116Z 9(52) INFO: <script>: NATMANAGE branch_id:0 ruri: sip:**72@speedport.ip, method:INVITE, status:<null>, extra_id: z9hG4bK16860370, rtpengine_manage: replace-origin replace-session-connection via-branch=extra rtcp-mux-demux SDES-off ICE=remove RTP/AVP 2025-08-07T07:47:30.265819591Z INFO: [412n0o8dedgair81t70p]: [control] Received command 'offer' from 127.0.0.1:50790 2025-08-07T07:47:30.265979425Z NOTICE: [412n0o8dedgair81t70p]: [core] Creating new call 2025-08-07T07:47:30.267497852Z INFO: [412n0o8dedgair81t70p]: [control] Replying to 'offer' from 127.0.0.1:50790 (elapsed time 0.001599 sec) 2025-08-07T07:47:30.469565385Z 9(52) INFO: <script>: START: CANCEL from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:30.469629711Z 9(52) INFO: <script>: Current Contact header: <null> 2025-08-07T07:47:30.469645116Z 9(52) INFO: <script>: Setting new Contact header: <null> 2025-08-07T07:47:41.207672567Z 7(50) INFO: <script>: WebSocket connection from 192.168.2.185:44816 has closed 2025-08-07T07:47:57.917754216Z 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found 2025-08-07T07:48:00.230412646Z 2(45) INFO: <script>: BRANCH FAILED: z9hG4bK1686037 + 0INFO: [412n0o8dedgair81t70p]: [control] Received command 'delete' from 127.0.0.1:36296 2025-08-07T07:48:00.230457143Z INFO: [412n0o8dedgair81t70p]: [core] Deleting call branch '' (via-branch 'z9hG4bK16860370') 2025-08-07T07:48:00.230466718Z INFO: [412n0o8dedgair81t70p]: [core] Call branch '' (via-branch 'z9hG4bK16860370') deleted, no more branches remaining 2025-08-07T07:48:00.230475640Z INFO: [412n0o8dedgair81t70p]: [core] Deleting entire call 2025-08-07T07:48:00.230483968Z INFO: [412n0o8dedgair81t70p]: [core] Final packet stats: 2025-08-07T07:48:00.230491909Z INFO: [412n0o8dedgair81t70p]: [core] --- Tag 'hc7h5imu96', created 0:30 ago for branch '' 2025-08-07T07:48:00.230518917Z INFO: [412n0o8dedgair81t70p]: [core] --- subscribed to '' 2025-08-07T07:48:00.230528302Z INFO: [412n0o8dedgair81t70p]: [core] --- subscription for '' 2025-08-07T07:48:00.230537387Z INFO: [412n0o8dedgair81t70p]: [core] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using unknown codec 2025-08-07T07:48:00.230545867Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23400 <> 192.168.2.185:46431, SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230554949Z INFO: [412n0o8dedgair81t70p]: [core] --- Tag '', created 0:30 ago for branch 'z9hG4bK16860370' 2025-08-07T07:48:00.230563124Z INFO: [412n0o8dedgair81t70p]: [core] --- subscribed to 'hc7h5imu96' 2025-08-07T07:48:00.230570851Z INFO: [412n0o8dedgair81t70p]: [core] --- subscription for 'hc7h5imu96' 2025-08-07T07:48:00.230578827Z INFO: [412n0o8dedgair81t70p]: [core] ------ Media #1 (audio over RTP/AVP) using unknown codec 2025-08-07T07:48:00.230587091Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23494 <> :0 , SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230595631Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23495 <> :0 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230603868Z INFO: [412n0o8dedgair81t70p]: [control] Replying to 'delete' from 127.0.0.1:36296 (elapsed time 0.000253 sec) *2025-08-07T07:48:00.230753116Z 2(45) INFO: <script>: Failure: <null> 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found* --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- especially the bold lines confuse me. Why is the TCP/TLS closed and can not be found ? Could that be the problem ?* * * * Thanks for some help and best regards Peter* *

7 15

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

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