October 2025 - sr-dev - kamailio.org

[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

[kamailio/kamailio] Multiple Modules: integer support for extra DB fields (PR #4438)
by Tyler Moore 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 - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description This feature addition adds support for loading integer-type DB fields into AVPs, for the "extra" fields that are loaded when matching the authentication / route. The following modules are effected by this change: - dispatcher: support integer fields for ds_db_extra_attrs - permissions: support integer fields for peer_tag - htable: support integer fields for htable param (cols attribute key_name) You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4438 -- Commit Summary -- * htable: support for 32bit and 64bit integer keys * permissions: support for integer peer_tag * dispatcher: support for fields in ds_db_extra_attrs -- File Changes -- M src/modules/dispatcher/dispatch.c (100) M src/modules/dispatcher/doc/dispatcher.xml (9) M src/modules/dispatcher/doc/dispatcher_admin.xml (4) M src/modules/htable/doc/htable.xml (4) M src/modules/htable/ht_db.c (55) M src/modules/htable/ht_db.h (9) M src/modules/permissions/address.c (87) M src/modules/permissions/doc/permissions.xml (11) M src/modules/permissions/doc/permissions_admin.xml (5) M src/modules/permissions/trusted.c (189) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4438.patch https://github.com/kamailio/kamailio/pull/4438.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4438 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4438(a)github.com>

3 15

git:master: pv: use suip2a(...) for $snd(..)
by Daniel-Constantin Mierla 04 Dec '25

04 Dec '25

Module: sip-router Branch: master Commit: e151a9e99b1fed7805eaed5d16ca3d6466e1f517 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e151a9e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Jul 18 22:37:07 2011 +0200 pv: use suip2a(...) for $snd(..) - fixes FS#140, reported by Klaus Darilion --- modules_k/pv/pv_branch.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules_k/pv/pv_branch.c b/modules_k/pv/pv_branch.c index a9dd1bc..4081429 100644 --- a/modules_k/pv/pv_branch.c +++ b/modules_k/pv/pv_branch.c @@ -395,7 +395,7 @@ int pv_get_sndto(struct sip_msg *msg, pv_param_t *param, (int)snd_inf->len); default: /* 0 - ip */ - s.s = su2a(snd_inf->to, sizeof(*snd_inf->to)); + s.s = suip2a(snd_inf->to, sizeof(*snd_inf->to)); s.len = strlen(s.s); return pv_get_strval(msg, param, res, &s); }

2 1

[kamailio/kamailio] db_redis module SSL_set_fd: symbol not found (Issue #4429)
by Lyubomir Yatanski 01 Dec '25

01 Dec '25

lyatanski created an issue (kamailio/kamailio#4429)  ### Description db_redis module SSL_set_fd: symbol not found with CMake build. ### Troubleshooting run kamailio with: `loadmodule "db_redis"` #### Reproduction  #### Debugging Data  Link order issue. The OpenSSL libraries are linked before the libhiredis_ssl library. The symbols are not looked up: ``` /usr/bin/cc -fPIC -O3 -DNDEBUG -m64 -Wl,--dependency-file=src/modules/db_redis/CMakeFiles/db_redis.dir/link.d -shared -Wl,-soname,db_redis.so -o src/modules/db_redis/db_redis.so src/modules/db_redis/CMakeFiles/db_redis.dir/db_redis_mod.c.o src/modules/db_redis/CMakeFiles/db_redis.dir/redis_connection.c.o src/modules/db_redis/CMakeFiles/db_redis.dir/redis_dbase.c.o s rc/modules/db_redis/CMakeFiles/db_redis.dir/redis_table.c.o -Wl,-rpath,::::::::::::::::::::::: /usr/lib/libssl.so /usr/lib/libcrypto.so /usr/lib/libhiredis_ssl.a /usr/lib/libhiredis.so -ldl -lresolv ``` #### Log Messages  ``` 0(1224) DEBUG: <core> [core/cfg.y:2240]: yyparse(): loading module db_redis 0(1224) DEBUG: <core> [core/sr_module.c:537]: ksr_locate_module(): found module to load </usr/local/lib/kamailio/modules/db_redis.so> 0(1224) DEBUG: <core> [core/sr_module.c:592]: ksr_load_module(): trying to load </usr/local/lib/kamailio/modules/db_redis.so> 0(1224) ERROR: <core> [core/sr_module.c:613]: ksr_load_module(): could not open module </usr/local/lib/kamailio/modules/db_redis.so>: Error relocating /usr/local/lib/kamailio/modules/db_redis.so: SSL_set_fd: symbol not found 0(1224) CRITICAL: <core> [core/cfg.y:4091]: yyerror_at(): parse error in config file /etc/cscf/interrogating.cfg, line 24, column 12-21: failed to load module ``` #### SIP Traffic N/A, the issue manifests during process initialization ### Possible Solutions In `src/modules/db_redis/CMakeLists.txt` instead of ` target_link_libraries(${module_name} PRIVATE OpenSSL::SSL OpenSSL::Crypto) ` to enhance the pkg-config target linkage with OpenSSL ` target_link_libraries(PkgConfig::hiredis_ssl INTERFACE OpenSSL::SSL OpenSSL::Crypto) ` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.1.0-dev1 (x86_64/Linux) 9bba10-dirty 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, DBG_QM_MALLOC, DBG_F_MALLOC, DBG_TLSF_MALLOC, 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: 9bba10 dirty compiled on 07:55:24 Oct 11 2025 with gcc 14.2.0 ``` * **Operating System**:  ``` NAME="Alpine Linux" ID=alpine VERSION_ID=3.22.2 PRETTY_NAME="Alpine Linux v3.22" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues" ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4429 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4429(a)github.com>

4 16

[kamailio/kamailio] db_redis: fix link order issue OpenSSL/hiredis_ssl (PR #4430)
by Lyubomir Yatanski 01 Dec '25

01 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 - [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:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #4429 #### Description  change link order to fix `SSL_set_fd: symbol not found` You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4430 -- Commit Summary -- * db_redis: fix link order issue OpenSSL/hiredis_ssl -- File Changes -- M src/modules/db_redis/CMakeLists.txt (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4430.patch https://github.com/kamailio/kamailio/pull/4430.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4430 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4430(a)github.com>

3 6

[kamailio/kamailio] crash in set_dlg_profile (Issue #4414)
by tsearle 29 Nov '25

29 Nov '25

tsearle created an issue (kamailio/kamailio#4414) ### Description A crash randomly occured in our production environment the crash back trace is similar to the one described in #3878 #### Debugging Data bt full output ``` 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 "aarch64-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/24/bb830d80441ecf857819d5cdaac404e1ff987b.debug... [New LWP 1583] [New LWP 1618] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg'. Program terminated with signal SIGSEGV, Segmentation fault. #0 link_profile (linker=linker@entry=0xffff68d91dc0, vkey=vkey@entry=0xffff69019458) at ./src/modules/dialog/dlg_profile.c:492 [Current thread is 1 (Thread 0xffff8c6d9020 (LWP 1583))] (gdb) #0 link_profile (linker=linker@entry=0xffff68d91dc0, vkey=vkey@entry=0xffff69019458) at ./src/modules/dialog/dlg_profile.c:492 hash = <optimized out> p_entry = 0xffff68c1ae90 #1 0x0000ffff88b089f4 in link_dlg_profile (linker=linker@entry=0xffff68d91dc0, dlg=dlg@entry=0xffff690193e0) at ./src/modules/dialog/dlg_profile.c:529 d_entry = <optimized out> #2 0x0000ffff88b0a8e4 in set_dlg_profile (msg=0xffff8b661750, value=<optimized out>, profile=<optimized out>) at ./src/modules/dialog/dlg_profile.c:620 dlg = 0xffff690193e0 linker = 0xffff68d91dc0 __func__ = "set_dlg_profile" #3 0x0000ffff88ab88dc in w_set_dlg_profile_helper (msg=<optimized out>, profile=<optimized out>, value=<optimized out>) at ./src/modules/dialog/dialog.c:899 __func__ = "w_set_dlg_profile_helper" #4 0x0000aaaac1bfca68 in sr_kemi_exec_func (ket=ket@entry=0xffff88b60800 <sr_kemi_dialog_exports+936>, msg=msg@entry=0xffff8b661750, pno=pno@entry=2, vps=vps@entry=0xfffff7b61488) at core/kemiexec.c:102 ret = <optimized out> __func__ = "sr_kemi_exec_func" #5 0x0000ffff89591d40 in sr_apy_kemi_exec_func_ex (ket=0xffff88b60800 <sr_kemi_dialog_exports+936>, self=<optimized out>, args=0xffff6661c140, idx=<optimized out>) at ./src/modules/app_python3/apy_kemi.c:329 fname = {s = 0xffff88b300e0 "set_dlg_profile", len = 15} i = <optimized out> ret = <optimized out> vps = {{vtype = 2, v = {n = 1749996576, l = 281472431739936, s = {s = 0xffff684ed420 "ingress_ip", len = 10}, dict = 0xffff684ed420}}, {vtype = 2, v = {n = 1749584160, l = 281472431327520, s = {s = 0xffff68488920 "23.94.26.58", len = 11}, dict = 0xffff68488920}}, {vtype = 0, v = {n = 0, l = 0, s = {s = 0x0, len = 0}, dict = 0x0}}, {vtype = 0, v = {n = 0, l = 0, s = {s = 0x0, len = 0}, dict = 0x0}}, {vtype = 0, v = {n = 0, l = 0, s = {s = 0x0, len = 0}, dict = 0x0}}, {vtype = 0, v = {n = 0, l = 0, s = {s = 0x0, len = 0}, dict = 0x0}}} env_P = <optimized out> lmsg = 0xffff8b661750 xret = <optimized out> slen = 11 alen = 2 pobj = <optimized out> __func__ = "sr_apy_kemi_exec_func_ex" #6 0x0000ffff8959370c in sr_apy_kemi_exec_func (self=0xffff68615440, args=0xffff6661c140, idx=659) at ./src/modules/app_python3/apy_kemi.c:358 ket = 0xffff88b60800 <sr_kemi_dialog_exports+936> ret = 0x0 pstate = 0x0 pframe = 0x0 pcode = 0x0 tvb = {tv_sec = 0, tv_usec = 0} tve = {tv_sec = 0, tv_usec = 0} tz = {tz_minuteswest = 10, tz_dsttime = 0} tdiff = <optimized out> __func__ = "sr_apy_kemi_exec_func" #7 0x0000ffff88fa5d88 in ?? () from /lib/aarch64-linux-gnu/libpython3.11.so.1.0 No symbol table info available. #8 0x0000ffff88f571d8 in _PyObject_MakeTpCall () from /lib/aarch64-linux-gnu/libpython3.11.so.1.0 No symbol table info available. #9 0x0000ffff88eed03c in _PyEval_EvalFrameDefault () from /lib/aarch64-linux-gnu/libpython3.11.so.1.0 No symbol table info available. #10 0x0000ffff890440fc in ?? () from /lib/aarch64-linux-gnu/libpython3.11.so.1.0 No symbol table info available. #11 0x0000ffff88f5a728 in ?? () from /lib/aarch64-linux-gnu/libpython3.11.so.1.0 No symbol table info available. #12 0x0000ffff89598c44 in apy_exec (_msg=<optimized out>, fname=0xaaaac1eb8b20 "ksr_request_route", fparam=fparam@entry=0x0, emode=emode@entry=1) at ./src/modules/app_python3/python_exec.c:157 pFunc = 0xffff67b824c0 pArgs = 0xffff687ad4e0 pValue = <optimized out> pResult = <optimized out> pmsg = 0xffff668158f0 rval = -1 bmsg = 0x0 gstate = PyGILState_LOCKED locked = 1 __func__ = "apy_exec" #13 0x0000ffff89590c98 in sr_kemi_config_engine_python (msg=<optimized out>, rtype=1, rname=0x0, rparam=<optimized out>) at ./src/modules/app_python3/apy_kemi.c:68 ret = -1 __func__ = "sr_kemi_config_engine_python" #14 0x0000aaaac1bfaae8 in sr_kemi_route (keng=0xaaaac1faf8e0 <_sr_kemi_eng_list>, msg=msg@entry=0xffff8b661750, rtype=rtype@entry=1, ename=ename@entry=0x0, edata=edata@entry=0x0) at core/kemi.c:3853 sfbk = 0 ret = <optimized out> #15 0x0000aaaac1c704f4 in receive_msg ( buf=buf@entry=0xaaaac2064550 <buf> "INVITE sip:441400690026@18.96.32.16:5080;transport=UDP SIP/2.0\r\nRecord-Route: <sip:10.153.16.54:5080;lr=on;stamp=9616eded056fc0110b8fa0da983b32f9825820fdc153661bbfb0d1707e2ee863>\r\nVia: SIP/2.0/UDP 10."..., len=<optimized out>, rcv_info=rcv_info@entry=0xfffff7b61ff8) at core/receive.c:507 msg = 0xffff8b661750 ctx = {rec_lev = 0, run_flags = 0, last_retcode = 0, jmp_env = {{__jmpbuf = {544, 4294967295, 281473035184984, 281473037789088, 16777216, 14728432, 1586192, 2048784, 281474837652176, 281473037621132, 281473020408336, 281474837651448, 281474837651296, 187650375533040, 187650374803456, 187650376419056, 187650375533040, 197, 187650374661248, 281473035184984, 281473036099216, 14021539797695420928}, __mask_was_saved = -139059536, __saved_mask = {__val = {187650373409376, 281473020408512, 281473019950128, 128, 128, 281473020408336, 281474837651292, 65535, 0, 13, 187650376353104, 281474837652176, 187650373237272, 281473020408336, 281474837651448, 281474837651056}}}}} bctx = 0x0 ret = <optimized out> tvb = {tv_sec = 0, tv_usec = 0} tve = {tv_sec = 0, tv_usec = 0} diff = 0 inb = { s = 0xaaaac2064550 <buf> "INVITE sip:441400690026@18.96.32.16:5080;transport=UDP SIP/2.0\r\nRecord-Route: <sip:10.153.16.54:5080;lr=on;stamp=9616eded056fc0110b8fa0da983b32f9825820fdc153661bbfb0d1707e2ee863>\r\nVia: SIP/2.0/UDP 10."..., len = 1070} netinfo = {data = {s = 0x0, len = 0}, bufsize = 0, rcv = 0x0, dst = 0x0} keng = <optimized out> evp = {data = 0xfffff7b61c48, obuf = {s = 0x0, len = 0}, rcv = 0xfffff7b61ff8, dst = 0x0, req = 0x0, rpl = 0x0, rplcode = 0, mode = 0} cidlockidx = 0 cidlockset = 0 errsipmsg = 0 exectime = 0 __func__ = "receive_msg" #16 0x0000aaaac1d6aec8 in udp_rcv_loop () at core/udp_server.c:770 len = 1070 buf = "INVITE sip:441400690026@18.96.32.16:5080;transport=UDP SIP/2.0\r\nRecord-Route: <sip:10.153.16.54:5080;lr=on;stamp=9616eded056fc0110b8fa0da983b32f9825820fdc153661bbfb0d1707e2ee863>\r\nVia: SIP/2.0/UDP 10."... tmp = <optimized out> fromaddr = 0xffff8b653210 fromaddrlen = 16 rcvi = {src_ip = {af = 2, len = 4, u = {addrl = {907057418, 0}, addr32 = {907057418, 0, 0, 0}, addr16 = {39178, 13840, 0, 0, 0, 0, 0, 0}, addr = "\n\231\0206", '\000' <repeats 11 times>}}, dst_ip = {af = 2, len = 4, u = {addrl = {3910179082, 0}, addr32 = {3910179082, 0, 0, 0}, addr16 = {39178, 59664, 0, 0, 0, 0, 0, 0}, addr = "\n\231\020\351", '\000' <repeats 11 times>}}, src_port = 5080, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\330\n\231\0206\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 55315, sin_addr = {s_addr = 907057418}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 55315, sin6_flowinfo = 907057418, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}, sas = {ss_family = 2, __ss_padding = "\023\330\n\231\0206", '\000' <repeats 111 times>, __ss_align = 0}}, bind_address = 0xffff8b5e8ad0, rflags = 0, proto = 1 '\001', proto_pad0 = 0 '\000', proto_pad1 = 0} evp = {data = 0x0, obuf = {s = 0x0, len = 0}, rcv = 0x0, dst = 0x0, req = 0x0, rpl = 0x0, rplcode = 0, mode = 0} printbuf = "\\\375\266\301\252\252\000\000\000\000\000\000\000\000\000\000\360\301\371\301\252\252\000\000P\271\374\301\252\252\000\000\360\301\371\301\252\252\000\000\000\000\000\000\000\000\000\000\350#\266\367\377\377\000\000\340\"\266\367\377\377\000\000d\376\266\301\252\252\000\000\360\301\371\301\252\252\000\000\000Z\243\035(\204\226°!\266\367\377\377\000\000\370\276\316\301\252\252\000\000\260!\266\367\377\377\000\000t3\341\301\252\252\000\0008$\352\301\252\252\000\000\024", '\000' <repeats 16 times>, "Z\243\035(\204\226\302\300!\266\367\377\377\000\000DF\341\301\252\252\000\000\004\000\000\000\000\000\000\000\340!\266\367\377\377\000\000l,[\201\000\000\000\000\001\000\000\000\000\000\000\000\001"... i = <optimized out> j = <optimized out> l = <optimized out> __func__ = "udp_rcv_loop" __llevel = <optimized out> __kld = <optimized out> #17 0x0000aaaac1b5be18 in main_loop () at ./src/main.c:1895 i = <optimized out> pid = <optimized out> si = <optimized out> sx = <optimized out> si_desc = "udp receiver child=0 sock=10.153.16.233:5060\000\000\000\000\260\037\371\301\252\252", '\000' <repeats 18 times>, "ansaction=>size=\000\000\000\000\000\000\000\000\000\377\000\000\000\000\000\377\000\000\000\000\000\000\000\000\000\377\000\000\000\000\000\37733333333" nrprocs = <optimized out> woneinit = 0 agfound = <optimized out> __func__ = "main_loop" error = <optimized out> #18 0x0000aaaac1b4dffc in main (argc=<optimized out>, argv=<optimized out>) at ./src/main.c:3406 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xfffff7b62e5d "" tmp_len = 65535 port = 5060 proto = 0 aproto = 0 ahost = 0x0 socket_name = 0x0 aport = 0 listen_field_count = <optimized out> listen_fields = {0x0, 0xffff8c6ed028 <_rtld_global> "\200\343n\214\377\377", 0xaaaac1f8e6e8 "\200\037\265\301\252\252"} options = 0xaaaac1e9ec00 ":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 = 2178755526 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> n_lst = <optimized out> p = <optimized out> tbuf = 0x0 tbuf_tmp = <optimized out> st = {st_dev = 24, st_ino = 992, st_mode = 16888, st_nlink = 2, st_uid = 107, st_gid = 112, st_rdev = 0, __pad1 = 0, st_size = 40, st_blksize = 4096, __pad2 = 0, st_blocks = 0, st_atim = {tv_sec = 1757332083, tv_nsec = 450116302}, st_mtim = {tv_sec = 1757332083, tv_nsec = 450116302}, st_ctim = {tv_sec = 1757332083, tv_nsec = 450116302}, __glibc_reserved = {0, 0}} l1 = <optimized out> lim = {rlim_cur = 1024, rlim_max = 524288} option_index = 9 long_options = {{name = 0xaaaac1ea0788 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0xaaaac1ea0790 "version", has_arg = 0, flag = 0x0, val = 118}, { name = 0xaaaac1eb8908 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0xaaaac1ea0798 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0xaaaac1ea07a0 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0xaaaac1ea07b0 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0xaaaac1ea07c0 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0xaaaac1ea07d0 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0xaaaac1ea07e0 "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0xaaaac1ea07f0 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0xaaaac1ea0800 "debug", has_arg = 1, flag = 0x0, val = 1032}, { name = 0xaaaac1ea0808 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0xaaaac1ea0818 "atexit", has_arg = 1, flag = 0x0, val = 1034}, { name = 0xaaaac1ea0820 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) ``` info locals ``` (gdb) info locals hash = <optimized out> p_entry = 0xffff68c1ae90 (gdb) print *p_entry $1 = {first = 0xffff6900e1b0, content = 1} (gdb) print *p_entry->first $2 = {value = {s = 0x1136900000d <error: Cannot access memory at address 0x1136900000d>, len = 1761447408}, dlg = 0xffff6900e1e0, puid = "\004\000\000\000-68b\345\341\000i\377\377\000\000$\000\000\000e9\000\000uuid\00031110fa2-43a6-45d4-8387-6bf989507906", puid_len = 22, expires = 3233857728, flags = -1412567059, linker = 0xffff6900e1b0, next = 0xffff6900e1b0, prev = 0x60, hash = 10} (gdb) print *vkey $3 = {s = 0xffff69019558 "uwLrPZ8JybtF5he4yTxai2..", len = 24} (gdb) print *linker $4 = {hash_linker = {value = {s = 0xffff68d91e60 "23.94.26.58\016", len = 11}, dlg = 0xffff690193e0, puid = "dlgp-68befede-62f-c5e9", '\000' <repeats 43 times>, puid_len = 22, expires = 0, flags = 0, linker = 0xffff68d91dc0, next = 0xffff6900e1b0, prev = 0x60, hash = 10}, next = 0x0, profile = 0xffff68c1adc0} ``` list output ``` (gdb) list 487 in ./src/modules/dialog/dlg_profile.c ``` ### Log outputs it may or may not related, while the set dlg profile above looks like it properly has string as a key, I do sometimes have the following in the logs ``` unable to get pv value for [$(dlg_var(dst_uri){uri.domain})] non-string parameter - func: set_dlg_profile idx: 1 argc: 2 ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.0.1 (aarch64/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-NOSMP, 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**:  ``` No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm Linux ******** 6.1.0-38-cloud-arm64 #1 SMP Debian 6.1.147-1 (2025-08-02) aarch64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4414 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4414(a)github.com>

3 4

[kamailio/kamailio] Make the arbitrary DNS 100-records result limit configurable or non-breaking. (Issue #4359)
by Erik B 29 Nov '25

29 Nov '25

pumpagubben created an issue (kamailio/kamailio#4359) ### Description There is a limit in [resolve.c](https://github.com/kamailio/kamailio/blob/4e2a93074476a3e1747eb4… that blocks session with DNS responses containing over 100 record results. This effectively blocks Kamailio from signaling with large SIP clusters since the calls are dropped with an error. ### Expected behavior Kamailio can handle any number of hosts/records in a DNS response. Or if a threshold is desired - truncate the response to desired threshold ignoring rest of the records. #### Actual observed behavior The [code goes to error](https://github.com/kamailio/kamailio/blob/4e2a93074476a3e1747eb46cb1… and the call fails if more than threshold records are returned. ### Possible Solutions This limit should be configurable and the code could instead gracefully truncate the response and continue if you think large results are problematic (with DEBUG/VERBOSE level message instead of ERROR). -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4359 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4359(a)github.com>

3 5

[kamailio/kamailio] misc: examples; ims: Update kamailio.cfg example to function out of the box on current releases (#2203)
by Nick 26 Nov '25

26 Nov '25

Changes to example files for PCSCF in misc/examples/ims to make funcitional with current stable version.  #### 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:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description Changes to example files for PCSCF in misc/examples/ims to make funcitional with current stable version. Changes: - Loading IPsec module prior to IMS Usrloc PCSCF (Now required) - removed modparam("ims_usrloc_pcscf", "hashing_type", 2) from example (This parameter was removed some time ago) - Fix to formatting of single MySQL connection to work in current version - Bind to any IP by default - Dispatcher parameters only loaded if required You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2203 -- Commit Summary -- * misc: examples: IMS PCSCF kamailio.cfg update * misc: examples: IMS PCSCF pcscf.cfg update -- File Changes -- M misc/examples/ims/pcscf/kamailio.cfg (6) M misc/examples/ims/pcscf/pcscf.cfg.sample (12) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2203.patch https://github.com/kamailio/kamailio/pull/2203.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2203

3 4

[kamailio/kamailio] xhttp_rpc crashes when listing kemi APIs on versions >= 5.7 (Issue #4351)
by timando 26 Nov '25

26 Nov '25

timando created an issue (kamailio/kamailio#4351) ### Description Getting the list of kemi APIs via xhttp_rpc causes a segfault and crashes kamailio  ### Troubleshooting #### Reproduction Run kamailio with the following config file: ``` loadmodule "xhttp.so" loadmodule "xhttp_rpc.so" loadmodule "sl.so" loadmodule "app_lua" loadmodule "jsonrpcs" modparam("jsonrpcs", "transport", 1) tcp_accept_no_cl=yes port=8060 pv_buffer_size=65536 pv_buffer_slots=64 request_route { exit; } event_route[xhttp:request] { set_reply_close(); if ($hu =~ "^/rpc") { dispatch_xhttp_rpc(); exit; } jsonrpc_exec('{"jsonrpc": "2.0", "method": "app_lua.api_list", "id": 1}'); xhttp_reply("200", "OK", "text/html", "<html><body><pre>$jsonrpl(body)</pre></body></html>"); exit; } ``` `curl "http://localhost:8060/rpc/app_lua/api_list?arg="` ### Possible Solutions I will create a pull request which fixes it by: - Editing xhttp_rpc to handle nulls without crashing - Editing kemi to not return null when describing long parameters ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.0-dev1 (x86_64/linux) 3406b9-dirty flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 3406b9 -dirty compiled on 10:50:37 Aug 7 2025 with gcc 14.2.1 ``` Note: problem exists in latest git version * **Operating System**:  AlmaLinux 10 container running on AlmaLinux Kitten 10 host. Problem also occurs using Debian 12 container ``` LSB Version: n/a Distributor ID: AlmaLinux Description: AlmaLinux Kitten 10 (Lion Cub) Release: 10 Codename: n/a Linux tim-laptop 6.12.0-109.el10.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jul 15 23:14:08 EDT 2025 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4351 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4351(a)github.com>

3 4

[kamailio/kamailio] PV's inconsistent in numeric context (Issue #4444)
by Alex Hermann 25 Nov '25

25 Nov '25

gaaf created an issue (kamailio/kamailio#4444) ### Description Trying to access a PV in numeric context is highly inconsistent in case the PV contains a string as well as a number. An examples of such PV's are $dP, $rP, $nh(P). These set the protocol as string and as number. ### Troubleshooting #### Reproduction The following script fragment logs the various interactions with such a PV. ``` xinfo("Target proto 1: $rP"); # "tls" xinfo("Target proto 2: $(rP{s.int})"); # "tls" WRONG! $vn(rP) = $(rP{s.int}); xinfo("Target proto 3: $vn(rP)"); # 3 $vn(rP) = $rP; xinfo("Target proto 4: $vn(rP)"); # "tls" $vn(rP) = $rP + 0; xinfo("Target proto 5: $vn(rP)"); # "tls0" WRONG! $vn(rP) = 0 + $rP; xinfo("Target proto 6: $vn(rP)"); # 3 $vn(rP) = $rP + ""; xinfo("Target proto 7: $vn(rP)"); # "tls" $vn(rP) = "" + $rP; xinfo("Target proto 8: $vn(rP)"); # "tls" $vn(isTLS) = $rP == "tls"; xinfo("Target is TLS 9: $vn(isTLS)"); # 1 $vn(isTLS) = $rP == 3; xinfo("Target is TLS 10: $vn(isTLS)"); # 0 WRONG! $vn(isTLS) = $(rP{s.int}) == 3; xinfo("Target is TLS 11: $vn(isTLS)"); # 1 $vn(isTLS) = 3 == $rP; xinfo("Target is TLS 12: $vn(isTLS)"); # 1 ``` Resulting in the following log entries: ``` INFO: Target proto 1: tls INFO: Target proto 2: tls INFO: Target proto 3: 3 INFO: Target proto 4: tls INFO: Target proto 5: tls0 INFO: Target proto 6: 3 INFO: Target proto 7: tls INFO: Target proto 8: tls INFO: Target is TLS 9: 1 INFO: Target is TLS 10: 0 INFO: Target is TLS 11: 1 INFO: Target is TLS 12: 1 ``` Scenario's 2, 3, 5, 6, 10, 11, 12 all access the PV in numeric context, yet only 3, 11 and 12 yield the correct result. Especially 2 is worrying as the clear intention of the author is to fetch a numerical value, not a string. For 4 and 10 I can understand that the type of the first variable item used, but the script parser should throw an error as the concatenated value is not a string. The script parser should not convert a number to a string automatically. And then there is also the fact that the whole numeric part gets lost on assignment to another PV: ``` $vn(rP) = $rP; xinfo("Target proto 13: $(vn(rP){s.int})"); $vn(rP) = $(vn(rP){s.int}); xinfo("Target proto 14: $vn(rP)"); ``` Log: ``` INFO: Target proto 13: ERROR: <core> [core/lvalue.c:346]: lval_pvar_assign(): non existing right pvar ERROR: <core> [core/lvalue.c:404]: lval_assign(): assignment failed at pos: (734,13-734,28) INFO: Target proto 14: <null> ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4444 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4444(a)github.com>

3 12