October 2025 - sr-dev - kamailio.org

[kamailio/kamailio] topos_htable: remove smethod from transaction key (PR #4425)
by Stefan Mititelu 09 Jan '26

09 Jan '26

#### Pre-Submission Checklist    - [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [X] Each component has a single commit (if not, squash them into one commit) - [X] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [X] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [X] PR should be backported to stable branches - [X] Tested changes locally - [X] Related to issue #4415 #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4425 -- Commit Summary -- * topos_htable: remove smethod from transaction key -- File Changes -- M src/modules/topos_htable/topos_htable_storage.c (44) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4425.patch https://github.com/kamailio/kamailio/pull/4425.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4425 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4425(a)github.com>

3 10

[kamailio/kamailio] TLS: sporadic decrypt error (Issue #4445)
by Sebastian Damm 08 Jan '26

08 Jan '26

SipSeb created an issue (kamailio/kamailio#4445) ### Description  After a small outage, where a large number of TLS clients had to reconnect, we see this error on some of our Kamailio proxies. The Kamailio processes were not restarted. See log messages below. These errors did not occur before the outage. And on some hosts we still don't see them. It can also be reproduced with running openssl manually, and our monitoring script registering through each proxy is also affected. A pcap trace shows that Kamailio sends its Server Hello, Change Cipher Spec message and some application data and then the client drops the connection with a "Decrypt Error". The next monitoring check run mostly works. Below is a graph showing the log volume of lines containing "decrypt error" in the time before and after the outage. <img width="1385" height="223" alt="Image" src="https://github.com/user-attachments/assets/f9522986-ef10-4798-bd8c-5dd51abd…" /> #### Log Messages  ``` ERROR: tls [tls_server.c:1312]: tls_h_read_f(): protocol level error ERROR: tls [tls_util.h:49]: tls_err_ret(): TLS accept:error:0A00041B:SSL routines::tlsv1 alert decrypt error (sni: unknown) ERROR: tls [tls_server.c:1316]: tls_h_read_f(): src addr: 2a05:d014:85b:a080:f1e7:affe:affe:cc1e:35604 ERROR: tls [tls_server.c:1319]: tls_h_read_f(): dst addr: 2a05:d014:cda:9301:81e5:affe:affe:251a:5061 ERROR: <core> [core/tcp_read.c:1524]: tcp_read_req(): error reading - c: 0x784904a5bfa0 r: 0x784904a5c0c8 (-1) ERROR: tls [tls_server.c:1312]: tls_h_read_f(): protocol level error ERROR: tls [tls_util.h:49]: tls_err_ret(): TLS accept:error:0A00041B:SSL routines::tlsv1 alert decrypt error (sni: unknown) ERROR: tls [tls_server.c:1316]: tls_h_read_f(): src addr: 192.0.2.42:33278 ERROR: tls [tls_server.c:1319]: tls_h_read_f(): dst addr: 100.68.1.13:5061 ERROR: <core> [core/tcp_read.c:1524]: tcp_read_req(): error reading - c: 0x784904a5bfa0 r: 0x784904a5c0c8 (-1) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` root@sipproxy:/WORKSPACE/sipproxy-container# kamailio -V version: kamailio 5.8.6 (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, MEM_JOIN_FREE, 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_SEND_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 13.3.0 ``` * **Operating System**:  Running in a podman container. Underlying system is Ubuntu Noble as well. ``` root@sipproxy:/WORKSPACE/sipproxy-container# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.3 LTS Release: 24.04 Codename: noble root@sipproxy:/WORKSPACE/sipproxy-container# uname -a Linux sipproxy 6.8.0-83-generic #83-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 5 21:46:54 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4445 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4445(a)github.com>

4 7

[kamailio/kamailio] Topos not working Properly for ACK (Issue #4208)
by Pandi1981 03 Jan '26

03 Jan '26

Pandi1981 created an issue (kamailio/kamailio#4208) We are facing an issue while using TOPOS in Kamailio P-CSCF (running under Docker). Kamailio version: 6.0.0 operating system: "10 (buster)" **Call Flow & Issue Description:** Note: Public IP and Private IP mapping using the below configuration. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ listen=udp:LOCAL_IP:5060 name "internal" listen=udp:LOCAL_IP:6080 advertise PUBLIC_IP:6080 name "external" ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ **Call Flow (INVITE):** A-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) B-Party <-- Kamailio P-CSCF (Public IP) <-- Kamailio P-CSCF (Private IP) <-- Kamailio S-CSCF (Private IP) Everything works correctly up to the point where the 200 OK is received by the A-Party. However, when the A-Party sends the ACK, it is received by the Kamailio P-CSCF but is not forwarded to the B-Party. Upon investigation, we found that when Kamailio receives the ACK from the A-Party, the rr (Record-Route) module fails to recognize its own Route header and thus falls back to strict routing instead of performing loose routing. This results in an incorrect rewrite of the Request-URI of the ACK, causing it to fail to reach the B-Party. Essentially, the Route header is not popped as expected and the ACK routing breaks. TOPOS module is configured as follows: loadmodule "topos_redis.so" loadmodule "ndb_redis.so" loadmodule "topos.so" modparam("ndb_redis", "server", "name=tps;addr=127.0.0.1;port=6379;db=0") modparam("topos", "storage", "redis") modparam("topos_redis", "serverid", "tps") modparam("topos", "rr_update", 1) modparam("topos", "contact_mode", 1) modparam("topos", "xavu_field_a_contact", "a_contact") modparam("topos", "xavu_field_b_contact", "b_contact") modparam("topos", "xavu_cfg", "tps") Please guide us how to achieve and what we are doing wrong. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208(a)github.com>

5 10

[kamailio/kamailio] dlg_vars are not deleted from database after deleting dialog (Issue #4385)
by asechv 24 Dec '25

24 Dec '25

asechv created an issue (kamailio/kamailio#4385) ### Description dlg_vars are not deleted from database after deleting dialog. Dialogs are deleted fine, but some dlg_vars from some dialogs are not deleted and table dialog_vars increases. We use dialog module and uac_replace: ``` modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 2) modparam("dialog", "db_update_period",15); modparam("dialog", "dlg_flag", FLAG_DIALOG) modparam("dialog", "profiles_with_value", "caller ; callee") modparam("dialog", "enable_stats", 1) modparam("dialog", "track_cseq_updates", 1) modparam("uac","reg_db_url",DBURL) modparam("uac","reg_db_table","uacreg") modparam("uac","auth_username_avp","$avp(uac_username)") modparam("uac","auth_password_avp","$avp(uac_password)") modparam("uac","auth_realm_avp","$avp(uac_realm)") modparam("uac", "reg_contact_addr", SBC_DOMAIN) modparam("uac", "reg_timer_interval", 5) modparam("uac", "reg_retry_interval", 20) modparam("uac", "restore_dlg", 1) ``` #### Reproduction Make many calls to the same number with uac_replace usage and calls immediately after answer. #### Log Messages last debug messages: ``` 2(448) DEBUG: {2 429 BYE 2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3} <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 2(448) DEBUG: {2 429 BYE 2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3} <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 2(448) DEBUG: {2 429 BYE 2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3} <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 2(448) DEBUG: {2 429 BYE 2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3} <core> [core/receive.c:635]: receive_msg(): cleaning up 18(464) DEBUG: dialog [dlg_hash.c:352]: destroy_dlg(): removed timer for dlg 0x7f12e1eafd38 [4095:408] with clid '2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3' and tags '1e3a6bd8-be1b-472d-b500-cf150a5cca7f' '7c5607ce-78bb-453a-9146-ebd8f75f8e47' 18(464) DEBUG: dialog [dlg_db_handler.c:732]: remove_dialog_from_db(): trying to remove dialog [2ebe0db3-0d5a-4e25-9e02-92e09fa4d0b3], update_flag is 519 ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` kamailio -v version: kamailio 5.7.7 (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, MEM_JOIN_FREE, 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 9.4.0 * **Operating System**: Kamailio in Docker. Docker version 24.0.7, build 24.0.7-0ubuntu2~22.04.1 OS - Ubuntu 22.04.5 LTS Kernel - 5.15.0-136-generic -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4385 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4385(a)github.com>

5 10

[kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)
by Joe Mordica 18 Dec '25

18 Dec '25

### Description We are now using kamailio on the edge as a presence proxy to scale presence. We have 3 internal kamailio instances handling the actual subscriptions and publishing. This works well, however, once per 24-36hours we experience a crash on the border proxy instance. We did not experience this when using the border proxy as a presence server (there was no proxying SUBSCRIBE). ### Troubleshooting #### Reproduction I believe this is happening when a customers network randomly experiences issues where it doesn't receive our replies to subscribes (and continues to send a subscribe). Logs are below. #### Debugging Data  Here's the output while replacing any sensitive info in the payload. ``` GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/sbin/kamailio... Reading symbols from /usr/lib/debug/.build-id/ce/c19d0ed1a928e4e25a84ae20d77e9c904a4892.debug... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 26] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `kamailio -DD -E -m 8000 -M 512 -f /etc/kamailio/kamailio.cfg -P /var/run/kamail'. Program terminated with signal SIGSEGV, Segmentation fault. #0 via_builder (len=len@entry=0x7ffed7e3ecb8, msg=msg@entry=0x7ff9529548b0, send_info=send_info@entry=0x7ff764d20bb0, branch=branch@entry=0x7ffed7e3ecc0, extra_params=0x0, hp=hp@entry=0x7ffed7e3ebb0) at core/msg_translator.c:2910 2910 core/msg_translator.c: No such file or directory. (gdb) bt full #0 via_builder (len=len@entry=0x7ffed7e3ecb8, msg=msg@entry=0x7ff9529548b0, send_info=send_info@entry=0x7ff764d20bb0, branch=branch@entry=0x7ffed7e3ecc0, extra_params=0x0, hp=hp@entry=0x7ffed7e3ebb0) at core/msg_translator.c:2910 via_len = <optimized out> extra_len = <optimized out> line_buf = <optimized out> max_len = <optimized out> via_prefix_len = <optimized out> address_str = <optimized out> port_str = 0x0 send_sock = 0x0 comp_len = <optimized out> comp_name_len = <optimized out> port = <optimized out> proto = <optimized out> ip = {af = 536870912, len = 0, u = {addrl = {534820896, 1586192}, addr32 = {534820896, 0, 1586192, 0}, addr16 = {47136, 8160, 0, 0, 13328, 24, 0, 0}, addr = " \270\340\037\000\000\000\000\0204\030\000\000\000\000"}} from = 0x0 local_addr = {s = {sa_family = 16, sa_data = "#\000\000\000\000\000\020\000\000\000\000\000\000"}, sin = {sin_family = 16, sin_port = 35, sin_addr = {s_addr = 0}, sin_zero = "\020\000\000\000\000\000\000"}, sin6 = {sin6_family = 16, sin6_port = 35, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = "\020\000\000\000\000\000\000\000\003\000\000\000\000\000\000", __u6_addr16 = {16, 0, 0, 0, 3, 0, 0, 0}, __u6_addr32 = {16, 0, 3, 0}}}, sin6_scope_id = 3000082688}, sas = {ss_family = 16, __ss_padding = "#\000\000\000\000\000\020\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000\000\241\321\262cg\357`@\000\000\000\000\000\000\000X\f-\177!V\000\000\020\016\217R\371\177\000\000\001\000\000\000!V\000\000*\000\000\000\000\000\000\000\001\000\000\000\376\177\000\000\004\360;\177!V\000\000\250,A\177!V\000\000\000\355\343\327\376\177\000\000\000\241\321\262cg\357`h\256\006R\371\177\000", __ss_align = 94701866020241}} con = 0x0 rxavp = 0x0 xname = {s = 0x0, len = -2141140176} __func__ = "via_builder" #1 0x000056217f155030 in create_via_hf (len=len@entry=0x7ffed7e3ecb8, msg=msg@entry=0x7ff9529548b0, send_info=send_info@entry=0x7ff764d20bb0, branch=branch@entry=0x7ffed7e3ecc0) at core/msg_translator.c:3232 via = <optimized out> extra_params = {s = 0x0, len = 0} hp = {host = 0x56217f4fb380 <default_global_address>, port = 0x56217f4fb370 <default_global_port>} sbuf = "\331\023\000\000\001", '\000' <repeats 18 times> --Type <RET> for more, q to quit, c to continue without paging--info locals slen = <optimized out> xparams = <optimized out> id_buf = <optimized out> id_len = 0 __func__ = "create_via_hf" __llevel = <optimized out> __kld = <optimized out> #2 0x000056217f1592f7 in build_req_buf_from_sip_req (msg=msg@entry=0x7ff9529548b0, returned_len=returned_len@entry=0x7ffed7e3eeac, send_info=send_info@entry=0x7ff764d20bb0, mode=mode@entry=128) at core/msg_translator.c:2096 len = 581 new_len = <optimized out> received_len = 0 rport_len = 0 uri_len = 0 via_len = 0 body_delta = 0 line_buf = 0x0 received_buf = 0x0 rport_buf = 0x0 new_buf = 0x0 buf = 0x56217f5866c0 <buf> "SUBSCRIBE sip:74@sip.domain.co SIP/2.0\r\nVia: SIP/2.0/UDP 12.171.207.82:25744;branch=z9hG4bK1805670803;rport\r\nFrom: \"Heather Myers\" <sip:1086448@sip.domain.co>;tag=1805518213\r\nTo: <sip:74@sip.domain.co>\r\nCa"... path_buf = {s = 0x0, len = 0} offset = 0 s_offset = 0 size = <optimized out> via_anchor = 0x7ff952951300 via_lump = <optimized out> via_rm = <optimized out> via_insert_param = 0x0 path_anchor = <optimized out> path_lump = <optimized out> branch = {s = 0x7ff952954ed8 "z9hG4bKc7ed.5819b4295fe83f981a2fc19b7f739d7e.0", len = 46} flags = 262273 --Type <RET> for more, q to quit, c to continue without paging--list udp_mtu = <optimized out> di = {send_sock = 0x0, to = {s = {sa_family = 18608, sa_data = "\225R\371\177\000\000\002\000\023\331\n4\001\r"}, sin = {sin_family = 18608, sin_port = 21141, sin_addr = { s_addr = 32761}, sin_zero = "\002\000\023\331\n4\001\r"}, sin6 = {sin6_family = 18608, sin6_port = 21141, sin6_flowinfo = 32761, sin6_addr = {__in6_u = { __u6_addr8 = "\002\000\023\331\n4\001\r\000\000\000\000\000\000\000", __u6_addr16 = {2, 55571, 13322, 3329, 0, 0, 0, 0}, __u6_addr32 = {3641901058, 218182666, 0, 0}}}, sin6_scope_id = 0}, sas = {ss_family = 18608, __ss_padding = "\225R\371\177\000\000\002\000\023\331\n4\001\r", '\000' <repeats 103 times>, __ss_align = 0}}, id = 0, send_flags = {f = 0, blst_imask = 0}, proto = 0 '\000', proto_pad0 = 0 '\000', proto_pad1 = 0} ret = <optimized out> __func__ = "build_req_buf_from_sip_req" error00 = <optimized out> #3 0x00007ff951fbe90d in prepare_new_uac (t=t@entry=0x7ff764d20880, i_req=i_req@entry=0x7ff9529548b0, branch=branch@entry=0, uri=<optimized out>, uri@entry=0x7ff9529548e8, path=<optimized out>, path@entry=0x7ff952954f60, next_hop=<optimized out>, fsocket=0x7ff9528f0e10, snd_flags=..., fproto=<optimized out>, flags=<optimized out>, instance=<optimized out>, ruid=<optimized out>, location_ua=<optimized out>) at ./src/modules/tm/t_fwd.c:482 shbuf = 0x0 add_rm_backup = <optimized out> body_lumps_backup = <optimized out> parsed_uri_bak = {user = { s = 0x56217f5866ce <buf+14> "74(a)sip.domain.co SIP/2.0\r\nVia: SIP/2.0/UDP 12.171.207.82:25744;branch=z9hG4bK1805670803;rport\r\nFrom: \"Heather Myers\" <sip:1086448@sip.domain.co>;tag=1805518213\r\nTo: <sip:74@sip.domain.co>\r\nCall-ID: 0_18056"..., len = 2}, passwd = {s = 0x0, len = 0}, host = { s = 0x56217f5866d1 <buf+17> "sip.domain.co SIP/2.0\r\nVia: SIP/2.0/UDP 12.171.207.82:25744;branch=z9hG4bK1805670803;rport\r\nFrom: \"Heather Myers\" <sip:1086448@sip.domain.co>;tag=1805518213\r\nTo: <sip:74@sip.domain.co>\r\nCall-ID: 0_18056078"..., len = 11}, port = {s = 0x0, len = 0}, params = {s = 0x0, len = 0}, sip_params = {s = 0x0, len = 0}, headers = { s = 0x0, len = 0}, port_no = 0, proto = 0, type = SIP_URI_T, flags = 0, transport = {s = 0x0, len = 0}, ttl = {s = 0x0, len = 0}, user_param = {s = 0x0, len = 0}, maddr = { s = 0x0, len = 0}, method = {s = 0x0, len = 0}, lr = {s = 0x0, len = 0}, r2 = {s = 0x0, len = 0}, gr = {s = 0x0, len = 0}, transport_val = {s = 0x0, len = 0}, ttl_val = { s = 0x0, len = 0}, user_param_val = {s = 0x0, len = 0}, maddr_val = {s = 0x0, len = 0}, method_val = {s = 0x0, len = 0}, lr_val = {s = 0x0, len = 0}, r2_val = {s = 0x0, len = 0}, gr_val = {s = 0x0, len = 0}} ret = -1 len = 32761 parsed_uri_ok_bak = <optimized out> free_new_uri = 1 msg_uri_bak = {s = 0x0, len = 0} dst_uri_bak = {s = 0x7ff9529525f0 "sip:10.52.1.13:5081", len = 19} dst_uri_backed_up = 1 path_bak = {s = 0x0, len = 0} free_path = 1 instance_bak = {s = 0x0, len = 0} ``` #### Log Messages  ``` ERROR 2025-01-10T06:00:31.847348563Z [resource.labels.containerName: kamailio] 8(28) CRITICAL: {1 1 SUBSCRIBE 0_1907143137(a)192.168.100.28} tm [timer.h:188]: _set_fr_retr(): already added: 0x7ff763e62250 , tl=0x7ff763e62270!!! ERROR 2025-01-10T06:00:31.847388483Z [resource.labels.containerName: kamailio] 8(28) CRITICAL: {1 1 SUBSCRIBE 0_1907143137(a)192.168.100.28} tm [t_fwd.c:1613]: t_send_branch(): BUG: retransmission already started for: 0x7ff763e62250 ERROR 2025-01-10T06:00:31.847394809Z [resource.labels.containerName: kamailio] 8(28) ERROR: {1 1 SUBSCRIBE 0_1907143137(a)192.168.100.28} sl [sl_funcs.c:428]: sl_reply_error(): stateless error reply used: No error (0/SL) ERROR 2025-01-10T06:00:31.847400738Z [resource.labels.containerName: kamailio] 8(28) BUG: {1 1 SUBSCRIBE 0_1907143137(a)192.168.100.28} tm [t_lookup.c:2052]: t_unref(): REQ_ERR DELAYED should have been caught much earlier for 0x7ff763e61f70: 24 (hex 18) ERROR 2025-01-10T06:00:47.346744773Z [resource.labels.containerName: kamailio] 45(65) ERROR: <core> [core/tcp_main.c:4818]: tcpconn_main_timeout(): connect 64.63.142.90:12190 failed (timeout) ERROR 2025-01-10T06:00:58.274915089Z [resource.labels.containerName: kamailio] 45(65) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 20 ERROR 2025-01-10T06:01:02.715789076Z [resource.labels.containerName: kamailio] 0(1) ALERT: <core> [main.c:805]: handle_sigs(): child process 26 exited by a signal 11 ERROR 2025-01-10T06:01:02.715827333Z [resource.labels.containerName: kamailio] 0(1) ALERT: <core> [main.c:809]: handle_sigs(): core was generated ERROR 2025-01-10T06:01:02.718815287Z [resource.labels.containerName: kamailio] 45(65) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 25 ERROR 2025-01-10T06:01:02.720985493Z [resource.labels.containerName: kamailio] 45(65) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 23 ERROR 2025-01-10T06:01:02.725450552Z [resource.labels.containerName: kamailio] 45(65) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 30 ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions I can atleast say that when this segfault happens that these logs are always present right before the crash. However, I also see instances of these logs without a crash immediately following. On the proxy we are doing this is withindlg route to send subscribes to the presence route: ``` if KSR.is_SUBSCRIBE() and KSR.is_myself_ruri() then -- in-dialog subscribe requests ksr_route_presence(); KSR.x.exit(); end ``` Any then this is our ksr_route_presence(): ``` function ksr_route_presence() if not KSR.is_SUBSCRIBE() then return 1; end local fuser = KSR.kx.get_fuser(); if fuser=='' then KSR.xlog.xinfo('Subscription attempt without username from IP ' .. KSR.kx.get_srcip() .. ' - Rejecting\n'); KSR.sl.sl_send_reply(404, 'Not Found'); KSR.x.exit(); end KSR.pv.sets('$avp(s:tenant)', string.match(fuser, '-(.*)')); local setId = '6' .. KSR.kx.get_def('DEFAULT_DISPATCH_SET'); local modeId = '7'; if KSR.dispatcher.ds_select_dst(setId, modeId)<0 then KSR.sl.send_reply(404, 'No destination'); KSR.x.exit(); end KSR.corex.set_send_socket(KSR.kx.get_def('PRIVATE_LISTEN_IP') .. ':' .. KSR.kx.get_def('INTERNAL_PORT')); KSR.tm.t_on_failure('ksr_route_rtf_dispatch'); ksr_route_relay(); end ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.8.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, MEM_JOIN_FREE, 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_SEND_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 12.2.0 ``` * **Operating System**:  ``` PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ``` ``` Linux gke-us-south1-external-sip-800ca69e-qyb3 5.15.0-1048-gke #53-Ubuntu SMP Tue Nov 28 00:39:01 UTC 2023 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4102(a)github.com>

7 54

[kamailio/kamailio] CMake Auto detect lock method according to priority (PR #4363)
by Xenofon Karamanos 09 Dec '25

09 Dec '25

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  This PR implements an option for locking methods. It detects what options are available and applys the nessecary definitions. It introduces the AUTO which, automatically selects one of the available on the platform according to the priority found in https://github.com/kamailio/kamailio/blob/2ca2ba1b2cbd73924f5b09396ff194402… Also fixes some other missing definitions You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4363 -- Commit Summary -- * cmake: Fix FMSTATS and KMSTATS compile defs * cmake: Remove duplicate definition * cmake: Add missing defintion * cmake: Update locking method detection -- File Changes -- M cmake/defs.cmake (71) A cmake/lock_methods.cmake (136) M cmake/os-specific/linux.cmake (32) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4363.patch https://github.com/kamailio/kamailio/pull/4363.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4363 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4363(a)github.com>

3 21

[kamailio/kamailio] Feature/auth web3 (PR #4328)
by Ariana 09 Dec '25

09 Dec '25

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Add auth_web3 module for blockchain-based authentication This PR introduces a new authentication module that provides blockchain-powered digest authentication via Oasis Sapphire smart contracts while maintaining full compatibility with standard Kamailio auth module functions. **Key Features:** - Blockchain-based digest authentication via Oasis Sapphire smart contracts - RFC2617 compliant MD5 and SHA-256 digest authentication - Full compatibility with standard auth functions (www_authenticate, proxy_authenticate) - Configurable parameters: web3_rpc_url, web3_contract_address, web3_debug_mode, web3_timeout - Comprehensive error handling for network failures and blockchain connectivity - Nonce management and replay protection identical to traditional auth **Files Added:** - src/modules/auth_web3/ (complete module with 9 .c files and supporting headers) - Comprehensive documentation in doc/ subfolder - CMakeLists.txt with curl dependency handling **Testing Summary:** - **Build Verification**: Module compiles successfully with curl dependency - **Load Testing**: Module loads without errors in Kamailio configuration - **Authentication Scenarios**: - Valid credentials: Successful authentication with correct blockchain credentials - Invalid credentials: Proper rejection of wrong passwords (tested with Zoiper) - Network failures: Graceful handling of blockchain RPC connectivity issues - Parameter validation: All module parameters properly validated - **Compatibility Testing**: Full compatibility with existing auth module functions - **Error Handling**: Comprehensive error logging and fallback behavior **Documentation Status:** - Complete XML documentation in doc/ subfolder - Module parameters documented (auth_web3_params.xml) - Functions documented (auth_web3_functions.xml) - Configuration examples provided - Usage patterns and best practices included **Limitations:** - Requires external blockchain RPC endpoint (Oasis Sapphire) - Network dependency for authentication (no offline fallback) - Requires curl library for HTTP requests to blockchain - Smart contract must be deployed on target blockchain network - Authentication speed depends on blockchain network response time **Build System:** - Added to MOD_LIST_UTILS group for proper curl dependency handling - Includes CMakeLists.txt with find_package(CURL REQUIRED) This module provides a drop-in replacement for traditional authentication while leveraging blockchain technology for credential verification. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4328 -- Commit Summary -- * auth_web3: initial blockchain authentication module * cmake: add auth_web3 to MOD_LIST_UTILS group -- File Changes -- M cmake/groups.cmake (4) A src/modules/auth_web3/CMakeLists.txt (9) A src/modules/auth_web3/Makefile (17) A src/modules/auth_web3/README (1229) A src/modules/auth_web3/api.c (324) A src/modules/auth_web3/api.h (170) A src/modules/auth_web3/auth_web3_mod.c (1739) A src/modules/auth_web3/auth_web3_mod.h (54) A src/modules/auth_web3/challenge.c (316) A src/modules/auth_web3/challenge.h (54) A src/modules/auth_web3/doc/Makefile (4) A src/modules/auth_web3/doc/auth_web3.xml (174) A src/modules/auth_web3/doc/auth_web3_faq.xml (174) A src/modules/auth_web3/doc/auth_web3_functions.xml (405) A src/modules/auth_web3/doc/auth_web3_params.xml (922) A src/modules/auth_web3/nc.c (246) A src/modules/auth_web3/nc.h (78) A src/modules/auth_web3/nid.c (96) A src/modules/auth_web3/nid.h (88) A src/modules/auth_web3/nonce.c (460) A src/modules/auth_web3/nonce.h (228) A src/modules/auth_web3/ot_nonce.c (232) A src/modules/auth_web3/ot_nonce.h (83) A src/modules/auth_web3/rfc2617.c (145) A src/modules/auth_web3/rfc2617.h (97) A src/modules/auth_web3/rfc2617_sha256.c (150) A src/modules/auth_web3/rfc2617_sha256.h (71) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4328.patch https://github.com/kamailio/kamailio/pull/4328.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4328 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4328(a)github.com>

4 30

[kamailio/kamailio] Outbound (PR #4449)
by sergey-safarov 08 Dec '25

08 Dec '25

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #4315 #### Description Added a function to check the flow token. Useful to make sure the client TCP connection is alive. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4449 -- Commit Summary -- * outbound: added check_flow_token function * outbound: docbook - fixed 'Attribute "xmlns:xi" must be declared for element type' * outbound: fixed xml validation errors * outbound: added check_flow_token documentation -- File Changes -- M src/modules/outbound/doc/outbound.xml (3) M src/modules/outbound/doc/outbound_admin.xml (78) M src/modules/outbound/outbound_mod.c (149) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4449.patch https://github.com/kamailio/kamailio/pull/4449.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4449 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4449(a)github.com>

4 24

[kamailio/kamailio] outbound + loose_route: new exit code when flow token does not exist (Issue #4315)
by sergey-safarov 08 Dec '25

08 Dec '25

sergey-safarov created an issue (kamailio/kamailio#4315) ### Description Use case WebRTC client connected to Kaamilio Edge proxy. For network connectivity reasons, the flow token may no longer be valid. In this case, behavior should be described in the [RFC5626, 5.3.1 Processing Incoming Requests](https://datatracker.ietf.org/doc/html/rfc5626#section-5.3.1) > If the flow no longer exists, the proxy SHOULD send a 430 (Flow Failed) response to the request. Also [9.3 Incoming Call and Proxy Crash](https://datatracker.ietf.org/doc/html/rfc5626#section-9.3) > Bob's authoritative proxy first tries the flow to EP1, but EP1 no longer has a flow to Bob, so it responds with a 430 (Flow Failed) response. To get it working, it will be fine to use construction like ``` if (!loose_route()) { switch($rc) { case -4: sl_send_reply("403", "Flow Failed"); exit; case -2: sl_send_reply("403", "Forbidden"); exit; default: xlog("L_ERR", "in request_route\n"); sl_reply_error(); exit; } } ``` Where `loose_route` returns a new error code (`-4` for example). This error code is generated when the flow token points to not existing TCP/TLS/WSS connection. ### Expected behavior Kamailio `loose_route` allows the check of flow token validity before messages related via non-existent TCP/TLS/WSS connections. #### Actual observed behavior For now, Kamailio tries to relay messages to non-existent client connections and generate an error message like ``` 477 Unfortunately error on sending to next hop occurred (477/TM) 500 Message processing error (2/TM) ``` #### How to reproduce Required to start Kamailio with a config like ``` listen=udp:127.0.0.1:5060 listen=tcp:127.0.0.1:5060 loadmodule "pv.so" loadmodule "xlog.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "siputils.so" loadmodule "rr.so" loadmodule "stun.so" loadmodule "outbound.so" modparam("outbound", "force_outbound_flag", 1) modparam("outbound", "flow_token_secret", "kamailio") loadmodule "debugger.so" modparam("debugger", "cfgtrace", 1) modparam("debugger", "log_level_name", "exec") request_route { loose_route(); switch($rc) { case -3: xlog("L_ERR", "loose_route code -3\n"); break; case -2: xlog("L_ERR", "loose_route code -2\n"); break; case -1: xlog("L_ERR", "loose_route code -1\n"); break; case 1: xlog("L_ERR", "loose_route code 1\n"); break; case 2: xlog("L_ERR", "loose_route code 2\n"); break; } record_route(); if (has_totag()) { t_relay(); } else { t_relay_to_udp("127.0.0.1", "5080"); } } ``` Then need to start SIPp server script using the command ``` sipp -sf uas.xml -p 5080 -d 4000 -bind_local 127.0.0.1 ``` And then start SIPp client script using the command ``` sipp -sf uac.xml -m 1 -t t1 127.0.0.1 ``` Where `uac.xml` and `uas.xml` are attached [sipp-scripts.tar.gz](https://github.com/user-attachments/files/21187724/sip… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4315 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4315(a)github.com>

3 7

[kamailio/kamailio] siptrace: core uac send request and $sel() used (Issue #4356)
by sergey-safarov 08 Dec '25

08 Dec '25

sergey-safarov created an issue (kamailio/kamailio#4356) ### Description Kamailio core generated when `siptrace` module tries to relay a message generated by `uac` module. ### Troubleshooting #### Reproduction To reproduce the issue need to start Kamailio with the config file. ``` #!KAMAILIO #!define L_INFO 2 #!trydef TROUBLESHOOT_NET "" local.trace_troubleshooting_net = TROUBLESHOOT_NET descr "trace all SIP messages from given network" # IPv4 listeners listen=udp:lan debug=L_INFO log_stderror=yes loadmodule "pv.so" loadmodule "tm.so" ####### DATABASE module ########## #!substdef "!KAMAILIO_DB_URL!mysql://kamailio:change_me@127.0.0.1:3306/kamailio!g" loadmodule "db_mysql.so" loadmodule "uac.so" modparam("uac", "reg_db_url", "KAMAILIO_DB_URL") modparam("uac", "reg_contact_addr", "192.168.1.2:5080") modparam("uac","restore_mode","none") ####### siptrace module ########## loadmodule "siptrace.so" modparam("siptrace", "duplicate_uri", "sip:127.0.0.1:9060") modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_mode", 1) ####### Routing Logic ######## request_route { drop; } event_route[siptrace:msg] { if ($sel(cfg_get.local.trace_troubleshooting_net) != "") { return; } } ``` In the database, need to inserta record ```sql INSERT INTO `uacreg` VALUES (1,'120','120','example.com','120','10.191.1.21','','120','','8e789f9318c98b9ffd4f0fd9e0b8a747','sip:10.191.1.21;transport=udp',120,0,0,'',''); ``` #### Debugging Data Backtrace for the generated core in the attached file [kamailio-bt-full.txt](https://github.com/user-attachments/files/21671121/ka… #### Log Messages ``` / # kamailio -DD --atexit=no -m 64 -M 8 -E 0(43) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.191.1.20:5060 Aliases: udp: ip-10-191-1-20.ec2.internal:5060 0(43) INFO: <core> [core/tcp_main.c:5232]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(43) INFO: siptrace [siptrace.c:438]: mod_init(): can't load dlg api. Will not install dialog callbacks. 0(43) ERROR: siptrace [../../modules/sl/sl.h:107]: sl_load_api(): cannot find bind_sl 0(43) WARNING: siptrace [siptrace.c:450]: mod_init(): cannot bind to SL API. Will not install sl callbacks. 0(43) INFO: <core> [main.c:3233]: main(): processes (at least): 14 - shm size: 67108864 - pkg size: 8388608 0(43) INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 4 0(43) INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 4 0(43) INFO: <core> [core/udp_server.c:264]: probe_max_send_buffer(): SO_SNDBUF is initially 212992 for fd 4 0(43) INFO: <core> [core/udp_server.c:334]: probe_max_send_buffer(): SO_SNDBUF is finally 425984 on fd 4 0(43) ALERT: <core> [main.c:805]: handle_sigs(): child process 55 exited by a signal 11 0(43) ALERT: <core> [main.c:809]: handle_sigs(): core was generated 0(43) INFO: <core> [main.c:832]: handle_sigs(): terminating due to SIGCHLD 1(44) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 2(45) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 3(46) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 4(47) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 5(48) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 6(49) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 7(50) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 8(51) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 9(52) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 13(56) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 10(53) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 11(54) INFO: <core> [main.c:888]: sig_usr(): signal 15 received 0(43) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ``` ### Possible Solutions As temporary workaround we use ```diff diff --git a/src/core/cfg/cfg_select.c b/src/core/cfg/cfg_select.c index f948dd4ab4..1a36ef378a 100644 --- a/src/core/cfg/cfg_select.c +++ b/src/core/cfg/cfg_select.c @@ -207,8 +207,10 @@ int select_cfg_var(str *res, select_t *s, struct sip_msg *msg) group = (cfg_group_t *)s->params[1].v.p; var = (cfg_mapping_t *)s->params[2].v.p; - if(!group || !var) + if(!group || !var || NULL == *(group->handle)) { + LM_ERR("incorrect input args\n"); return -1; + } /* use the module's handle to access the variable, so the variables * are read from the local config */ ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` / # kamailio -v version: kamailio 5.8.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, MEM_JOIN_FREE, 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_SEND_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 14:31:12 Nov 18 2024 with gcc 14.2.0 ``` * **Operating System**:  ``` NAME="Alpine Linux" ID=alpine VERSION_ID=3.21.4 PRETTY_NAME="Alpine Linux v3.21" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues" ``` uname ``` Linux sbc0-site0-stage.ph.nga911.com 6.15.5-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jul 6 09:16:17 UTC 2025 x86_64 Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4356 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4356(a)github.com>

3 6