sr-dev February 2026

sr-dev@lists.kamailio.org

24 participants
246 discussions

[kamailio/kamailio] ims_diameter_server: don't leak on diameter_request() (PR #4570)
by Victor Seva 05 May '26

05 May '26

2 3

[kamailio/kamailio] app_lua: packaging many times with different lua library versions (Issue #4578)
by Daniel-Constantin Mierla 04 May '26

04 May '26

miconda created an issue (kamailio/kamailio#4578) At least Debian/Ubuntu ship many versions of lua and liblua, like 5.1, 5.2, 5.3 and 5.4. So far the package including app_lua compiled with liblua5.1, @linuxmaniac plans to switch to a newer version, but I am thinking that maybe we can ship app_lua many times, to offer a variant linked with each lualib version. The app_lua module can be compiled with any of those available in Debian/Ubuntu. Therefore I am starting this issue more like a discussion to see what can be done. Maybe @xkaraman can comment if cmake could cover easier such needs. We can provide the internal module name as a compile option (i.e., `-DMOD_NAME='"app_lua"'` or `-DMOD_NAME='"app_lua52"'`), then the output object file should have similar name (e.g., `app_lua.so` or `app_lua52.so`). I see a combination of two input values, the name of the module and the library version to compile with. I would say, linking with the latest stable library version should result in the `app_lua.so`, the other variants should be with version number (e.g., `app_lua52.so`). The question is also if @linuxmaniac (and the other packagers) could leverage such mechanism, to compile a module many times and package the results in different packages, because they have different library requirements/dependencies. There is a similar case with `tls` and `tlsa`, which is done a bit awkward, by including tls files completely inside tlsa files. I won't go the same path, the need for tlsa was required by the instability of latest libssl at that moment. Here, if we cannot find a flexible and easy enough solution, we should probably just go with linking against latest stable liblua. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4578 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4578(a)github.com>

6 15

[kamailio/kamailio] Issue with usrloc 'handle_lost_tcp' and dmq_usrloc 'usrloc_delete' (Issue #3479)
by alternatenetwork 02 May '26

02 May '26

### Description When a TLS connection is closed and handle_lost_tcp=1 the entry is deleted for usrloc. This deletion is not synced via DMQ even though usrloc_delete=1. There is also an issue on the same server if a re-registration happens right after before the timeout was supposed to expire then $var(sv_res) = 2 even though the usrloc table is empty. So it seems like the way handle_lost_tcp deletes is not deleting fully in registrar. usrloc db_mode is 0 ### Troubleshooting #### Reproduction Setup 2 servers with DMQ and close the TCP connection. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.1 (x86_64/linux) d8f98b 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: d8f98b compiled on 19:05:04 Aug 16 2022 with gcc 8.3.0 ``` * **Operating System**:  ``` Debian 10 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3479 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3479(a)github.com>

3 6

[kamailio/kamailio] DB_cluster issue (Issue #4467)
by itpanda2024 01 May '26

01 May '26

itpanda2024 created an issue (kamailio/kamailio#4467)  ### Description  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4467 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4467(a)github.com>

4 13

[kamailio/kamailio] remove makefiles (PR #4588)
by Xenofon Karamanos 01 May '26

01 May '26

#### 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  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4588 -- Commit Summary -- * src: make: Remove src/ Makefiles including lib/modules * doc: make: Remove of Makefiles * misc: make: Remove Makefiles * test: make: Remove Makefiles * utils: make: Remove Makefiles -- File Changes -- D doc/docbook/Makefile (204) D doc/docbook/Makefile.module (4) D doc/tutorials/cfg_list/Makefile (352) D doc/tutorials/cfg_list/docbook/Makefile (15) D doc/tutorials/counter_list/Makefile (348) D doc/tutorials/counter_list/docbook/Makefile (15) D doc/tutorials/presence/Makefile (4) D doc/tutorials/rpc/Makefile (4) D doc/tutorials/rpc_list/Makefile (431) D doc/tutorials/rpc_list/docbook/Makefile (15) D doc/tutorials/select_list/Makefile (353) D doc/tutorials/select_list/docbook/Makefile (15) D doc/tutorials/ser_radius/Makefile (4) D doc/tutorials/serdev/Makefile (4) D doc/tutorials/serfaq/Makefile (4) D doc/tutorials/serhowto/Makefile (4) D doc/tutorials/seruser/Makefile (4) D doc/tutorials/sip/Makefile (4) D misc/extra/vim/Makefile (12) D misc/tools/pike_top/Makefile (10) D misc/tools/protoshoot/Makefile (30) D src/Makefile (1124) D src/Makefile.cfg (17) D src/Makefile.defs (2221) D src/Makefile.dirs (19) D src/Makefile.groups (549) D src/Makefile.libs (162) D src/Makefile.modules (293) D src/Makefile.radius (55) D src/Makefile.rules (296) D src/Makefile.shared (50) D src/Makefile.sources (30) D src/Makefile.targets (41) D src/Makefile.utils (153) D src/lib/Makefile (36) D src/lib/Makefile.defs (126) D src/lib/Makefile.nonser (32) D src/lib/doc/Makefile (4) D src/lib/ims/Makefile (15) D src/lib/srdb1/Makefile (9) D src/lib/srdb1/schema/Makefile (339) D src/lib/srdb2/Makefile (9) D src/lib/srdb2/schema/Makefile (97) D src/lib/trie/Makefile (9) D src/modules/acc/Makefile (11) D src/modules/acc/doc/Makefile (4) D src/modules/acc_diameter/Makefile (11) D src/modules/acc_diameter/doc/Makefile (4) D src/modules/acc_json/Makefile (25) D src/modules/acc_json/doc/Makefile (4) D src/modules/acc_radius/Makefile (13) D src/modules/acc_radius/doc/Makefile (4) D src/modules/alias_db/Makefile (13) D src/modules/alias_db/doc/Makefile (4) D src/modules/app_jsdt/Makefile (11) D src/modules/app_jsdt/doc/Makefile (4) D src/modules/app_lua/Makefile (89) D src/modules/app_lua/doc/Makefile (4) D src/modules/app_perl/Makefile (72) D src/modules/app_perl/doc/Makefile (4) D src/modules/app_python/Makefile (40) D src/modules/app_python/doc/Makefile (4) D src/modules/app_python3/Makefile (39) D src/modules/app_python3/doc/Makefile (4) D src/modules/app_python3s/Makefile (39) D src/modules/app_python3s/doc/Makefile (4) D src/modules/app_ruby/Makefile (39) D src/modules/app_ruby/doc/Makefile (4) D src/modules/app_ruby_proc/Makefile (39) D src/modules/app_ruby_proc/doc/Makefile (4) D src/modules/async/Makefile (9) D src/modules/async/doc/Makefile (4) D src/modules/auth/Makefile (17) D src/modules/auth/doc/Makefile (4) D src/modules/auth_arnacon/Makefile (32) D src/modules/auth_arnacon/doc/Makefile (6) D src/modules/auth_db/Makefile (12) D src/modules/auth_db/doc/Makefile (4) D src/modules/auth_diameter/Makefile (13) D src/modules/auth_diameter/doc/Makefile (4) D src/modules/auth_ephemeral/Makefile (43) D src/modules/auth_ephemeral/doc/Makefile (4) D src/modules/auth_radius/Makefile (28) D src/modules/auth_radius/doc/Makefile (4) D src/modules/auth_web3/Makefile (31) D src/modules/auth_web3/doc/Makefile (4) D src/modules/auth_xkeys/Makefile (9) D src/modules/auth_xkeys/doc/Makefile (4) D src/modules/avp/Makefile (12) D src/modules/avp/doc/Makefile (4) D src/modules/avpops/Makefile (12) D src/modules/avpops/doc/Makefile (4) D src/modules/benchmark/Makefile (18) D src/modules/benchmark/doc/Makefile (4) D src/modules/blst/Makefile (9) D src/modules/blst/doc/Makefile (4) D src/modules/call_control/Makefile (13) D src/modules/call_control/doc/Makefile (4) D src/modules/call_obj/Makefile (8) D src/modules/call_obj/doc/Makefile (4) D src/modules/carrierroute/Makefile (11) D src/modules/carrierroute/doc/Makefile (4) D src/modules/cdp/Makefile (34) D src/modules/cdp/doc/Makefile (4) D src/modules/cdp_avp/Makefile (7) D src/modules/cdp_avp/doc/Makefile (4) D src/modules/cfg_db/Makefile (11) D src/modules/cfg_db/doc/Makefile (4) D src/modules/cfg_rpc/Makefile (10) D src/modules/cfg_rpc/doc/Makefile (4) D src/modules/cfgt/Makefile (11) D src/modules/cfgt/doc/Makefile (4) D src/modules/cfgutils/Makefile (13) D src/modules/cfgutils/doc/Makefile (4) D src/modules/cnxcc/Makefile (50) D src/modules/cnxcc/doc/Makefile (4) D src/modules/corex/Makefile (9) D src/modules/corex/doc/Makefile (4) D src/modules/counters/Makefile (10) D src/modules/counters/doc/Makefile (4) D src/modules/cplc/Makefile (27) D src/modules/cplc/doc/Makefile (4) D src/modules/crypto/Makefile (35) D src/modules/crypto/doc/Makefile (4) D src/modules/ctl/Makefile (16) D src/modules/ctl/doc/Makefile (4) D src/modules/db2_ldap/Makefile (18) D src/modules/db2_ldap/doc/Makefile (4) D src/modules/db2_ops/Makefile (13) D src/modules/db2_ops/doc/Makefile (4) D src/modules/db_cluster/Makefile (10) D src/modules/db_cluster/doc/Makefile (4) D src/modules/db_flatstore/Makefile (9) D src/modules/db_flatstore/doc/Makefile (4) D src/modules/db_flatstore/km_doc/Makefile (4) D src/modules/db_mongodb/Makefile (28) D src/modules/db_mongodb/doc/Makefile (4) D src/modules/db_mysql/Makefile (69) D src/modules/db_mysql/doc/Makefile (4) D src/modules/db_oracle/Makefile (22) D src/modules/db_oracle/doc/Makefile (4) D src/modules/db_postgres/Makefile (55) D src/modules/db_postgres/doc/Makefile (4) D src/modules/db_redis/Makefile (81) D src/modules/db_redis/doc/Makefile (4) D src/modules/db_sqlite/Makefile (25) D src/modules/db_sqlite/doc/Makefile (4) D src/modules/db_text/Makefile (25) D src/modules/db_text/doc/Makefile (4) D src/modules/db_unixodbc/Makefile (27) D src/modules/db_unixodbc/doc/Makefile (4) D src/modules/debugger/Makefile (9) D src/modules/debugger/doc/Makefile (4) D src/modules/dialog/Makefile (9) D src/modules/dialog/doc/Makefile (4) D src/modules/dialplan/Makefile (22) D src/modules/dialplan/doc/Makefile (4) D src/modules/dispatcher/Makefile (14) D src/modules/dispatcher/doc/Makefile (4) D src/modules/diversion/Makefile (12) D src/modules/diversion/doc/Makefile (4) D src/modules/dlgs/Makefile (9) D src/modules/dlgs/doc/Makefile (4) D src/modules/dmq/Makefile (12) D src/modules/dmq/doc/Makefile (4) D src/modules/dmq_usrloc/Makefile (5) D src/modules/dmq_usrloc/doc/Makefile (4) D src/modules/dnssec/Makefile (16) D src/modules/dnssec/doc/Makefile (3) D src/modules/domain/Makefile (12) D src/modules/domain/doc/Makefile (4) D src/modules/domainpolicy/Makefile (12) D src/modules/domainpolicy/doc/Makefile (4) D src/modules/drouting/Makefile (9) D src/modules/drouting/doc/Makefile (4) D src/modules/enum/Makefile (12) D src/modules/enum/doc/Makefile (4) D src/modules/erlang/Makefile (26) D src/modules/erlang/doc/Makefile (4) D src/modules/evapi/Makefile (31) D src/modules/evapi/doc/Makefile (4) D src/modules/evrexec/Makefile (12) D src/modules/evrexec/doc/Makefile (4) D src/modules/exec/Makefile (12) D src/modules/exec/doc/Makefile (4) D src/modules/file_out/Makefile (8) D src/modules/file_out/doc/Makefile (4) D src/modules/gcrypt/Makefile (26) D src/modules/gcrypt/doc/Makefile (4) D src/modules/geoip/Makefile (9) D src/modules/geoip/doc/Makefile (4) D src/modules/geoip2/Makefile (10) D src/modules/geoip2/doc/Makefile (4) D src/modules/group/Makefile (12) D src/modules/group/doc/Makefile (4) D src/modules/gzcompress/Makefile (23) D src/modules/gzcompress/doc/Makefile (4) D src/modules/h350/Makefile (14) D src/modules/h350/doc/Makefile (4) D src/modules/htable/Makefile (12) D src/modules/htable/doc/Makefile (4) D src/modules/http_async_client/Makefile (44) D src/modules/http_async_client/doc/Makefile (4) D src/modules/http_client/Makefile (28) D src/modules/http_client/doc/Makefile (4) D src/modules/imc/Makefile (12) D src/modules/imc/doc/Makefile (4) D src/modules/ims_auth/Makefile (34) D src/modules/ims_auth/doc/Makefile (4) D src/modules/ims_charging/Makefile (16) D src/modules/ims_charging/doc/Makefile (4) D src/modules/ims_dialog/Makefile (9) D src/modules/ims_dialog/doc/Makefile (4) D src/modules/ims_diameter_server/Makefile (16) D src/modules/ims_diameter_server/doc/Makefile (4) D src/modules/ims_icscf/Makefile (29) D src/modules/ims_icscf/doc/Makefile (4) D src/modules/ims_ipsec_pcscf/Makefile (31) D src/modules/ims_ipsec_pcscf/doc/Makefile (4) D src/modules/ims_isc/Makefile (29) D src/modules/ims_isc/doc/Makefile (4) D src/modules/ims_ocs/Makefile (16) D src/modules/ims_ocs/doc/Makefile (4) D src/modules/ims_qos/Makefile (16) D src/modules/ims_qos/doc/Makefile (4) D src/modules/ims_qos_npn/Makefile (16) D src/modules/ims_qos_npn/doc/Makefile (4) D src/modules/ims_registrar_pcscf/Makefile (35) D src/modules/ims_registrar_pcscf/doc/Makefile (4) D src/modules/ims_registrar_scscf/Makefile (35) D src/modules/ims_registrar_scscf/doc/Makefile (4) D src/modules/ims_usrloc_pcscf/Makefile (11) D src/modules/ims_usrloc_pcscf/doc/Makefile (4) D src/modules/ims_usrloc_scscf/Makefile (11) D src/modules/ims_usrloc_scscf/doc/Makefile (4) D src/modules/influxdbc/Makefile (9) D src/modules/influxdbc/doc/Makefile (4) D src/modules/ipops/Makefile (13) D src/modules/ipops/doc/Makefile (4) D src/modules/jansson/Makefile (27) D src/modules/jansson/doc/Makefile (4) D src/modules/janssonrpcc/Makefile (24) D src/modules/janssonrpcc/doc/Makefile (4) D src/modules/janssonrpcc/unit_tests/Makefile (11) D src/modules/json/Makefile (33) D src/modules/json/doc/Makefile (4) D src/modules/jsonrpcc/Makefile (35) D src/modules/jsonrpcc/doc/Makefile (4) D src/modules/jsonrpcs/Makefile (11) D src/modules/jsonrpcs/doc/Makefile (4) D src/modules/jwt/Makefile (25) D src/modules/jwt/doc/Makefile (4) D src/modules/kafka/Makefile (23) D src/modules/kafka/doc/Makefile (4) D src/modules/kazoo/Makefile (39) D src/modules/kazoo/doc/Makefile (4) D src/modules/keepalive/Makefile (13) D src/modules/keepalive/doc/Makefile (4) D src/modules/kemix/Makefile (9) D src/modules/kemix/doc/Makefile (4) D src/modules/kex/Makefile (12) D src/modules/kex/doc/Makefile (4) D src/modules/lcr/Makefile (26) D src/modules/lcr/doc/Makefile (4) D src/modules/ldap/Makefile (24) D src/modules/ldap/doc/Makefile (4) D src/modules/log_custom/Makefile (8) D src/modules/log_custom/doc/Makefile (4) D src/modules/log_systemd/Makefile (23) D src/modules/log_systemd/doc/Makefile (4) D src/modules/lost/Makefile (43) D src/modules/lost/doc/Makefile (4) D src/modules/lrkproxy/Makefile (14) D src/modules/lrkproxy/doc/Makefile (4) D src/modules/lwsc/Makefile (25) D src/modules/lwsc/doc/Makefile (4) D src/modules/mangler/Makefile (12) D src/modules/mangler/doc/Makefile (4) D src/modules/math/Makefile (9) D src/modules/math/doc/Makefile (4) D src/modules/matrix/Makefile (8) D src/modules/matrix/doc/Makefile (4) D src/modules/maxfwd/Makefile (12) D src/modules/maxfwd/doc/Makefile (4) D src/modules/mediaproxy/Makefile (13) D src/modules/mediaproxy/doc/Makefile (4) D src/modules/memcached/Makefile (21) D src/modules/memcached/doc/Makefile (4) D src/modules/microhttpd/Makefile (23) D src/modules/microhttpd/doc/Makefile (4) D src/modules/misc_radius/Makefile (10) D src/modules/misc_radius/doc/Makefile (4) D src/modules/misctest/Makefile (12) D src/modules/misctest/doc/Makefile (4) D src/modules/mohqueue/Makefile (12) D src/modules/mohqueue/doc/Makefile (4) D src/modules/mqtt/Makefile (42) D src/modules/mqtt/doc/Makefile (4) D src/modules/mqueue/Makefile (9) D src/modules/mqueue/doc/Makefile (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4588.patch https://github.com/kamailio/kamailio/pull/4588.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4588 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4588(a)github.com>

6 24

[kamailio/kamailio] Permissions module: add locks support (PR #4539)
by Donat Zenichev 27 Apr '26

27 Apr '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 - [ ] 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 - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description Move permissions module to work with hash tables instead of directly working with lists. Use locks to cover these hash tables. This allows to avoid using crutches alike 0039c50e83916, and gives a race-free usage of tables regardless the amount of data inserted into tables and regardless how many competitive reloads are pending at a time (e.g. 2-3 RPC commands sent at a time to reload same tables). Use hash indexes for a quicker lookup in buckets. Improve the mechanism of duplicate entries detection, use: the source ip, ruri pattern, from pattern and the protocol to detect existing similar entries. Add more safety checks in functions manipulating hash tables, like checking NULL pointers, empty patterns for matching purposes etc. Align return values in trusted/hash implementations so that return values are everywhere considered in the similar way (everything != 0 is considered as failure, 0 is considered as fine). Split tables allocation and initialization. Add destruction handlers for tables instead of manually handling entries freeing. Some other minor improvements. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4539 -- Commit Summary -- * permissions: remove the permissions reload rework * permissions: hash header, remove dangling declarations * permissions: support locked tables * permissions: module rework to support locks * permissions: remove unsed hash functions -- File Changes -- M src/modules/permissions/hash.c (566) M src/modules/permissions/hash.h (64) M src/modules/permissions/rpc.c (18) M src/modules/permissions/trusted.c (143) M src/modules/permissions/trusted.h (11) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4539.patch https://github.com/kamailio/kamailio/pull/4539.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4539 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4539(a)github.com>

3 20

[kamailio/kamailio] tls: coredump on Alpine (Issue #4534)
by sergey-safarov 26 Apr '26

26 Apr '26

sergey-safarov created an issue (kamailio/kamailio#4534) ### Description On Alpine Linux th `tls` module load is crashing Kamailio with a coredump ``` #0 0x00007fcbdf45f8d2 in __pthread_getspecific (k=0) at src/thread/pthread_getspecific.c:7 self = 0x7fcbdf4ac588 <builtin_tls+136> #1 0x00007fcbdeb6201c in mod_init () at tls_mod.c:406 method = <optimized out> verify_client = <optimized out> rand_buf = "\270\f=\337\313\177\000\000\230X\201\203\000\001\000\000\000\001\000\000\0011\0010\00217\003172\a" k = 0 __func__ = "mod_init" __llevel = <optimized out> __kld = <optimized out> #2 0x00005557fdcdf2a7 in init_mod (m=0x7fcbded4a390) at core/sr_module.c:1037 ret = <optimized out> __func__ = "init_mod" #3 0x00005557fdcdf060 in init_mod (m=0x7fcbded4d9d0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #4 0x00005557fdcdf060 in init_mod (m=0x7fcbded4e380) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #5 0x00005557fdcdf060 in init_mod (m=0x7fcbded4f100) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #6 0x00005557fdcdf060 in init_mod (m=0x7fcbded51380) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #7 0x00005557fdcdf060 in init_mod (m=0x7fcbded51b90) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #8 0x00005557fdcdf060 in init_mod (m=0x7fcbded52af0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #9 0x00005557fdcdf060 in init_mod (m=0x7fcbded5d010) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #10 0x00005557fdcdf060 in init_mod (m=0x7fcbded5d650) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #11 0x00005557fdcdf060 in init_mod (m=0x7fcbded5ea30) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #12 0x00005557fdce389b in init_modules () at core/sr_module.c:1068 t = <optimized out> i = <optimized out> __func__ = "init_modules" #13 0x00005557fdab83b2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:3353 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0x3d3980 <error: Cannot access memory at address 0x3d3980> tmp_len = 32715 port = 5060 proto = 0 aproto = 0 ahost = 0x0 socket_name = <optimized out> aport = 0 listen_field_count = <optimized out> listen_fields = {0x0, 0x0, 0x0} options = 0x5557fdd8ec35 ":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 = 3379987412 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> n_lst = <optimized out> p = <optimized out> tbuf = 0x13190 <error: Cannot access memory at address 0x13190> tbuf_tmp = <optimized out> st = {st_dev = 82, st_ino = 15305750, st_nlink = 2, st_mode = 16877, st_uid = 100, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 6, st_blksize = 4096, st_blocks = 0, st_atim = { tv_sec = 1766246263, tv_nsec = 624197245}, st_mtim = {tv_sec = 1766246163, tv_nsec = 172268511}, st_ctim = {tv_sec = 1766246163, tv_nsec = 172268511}, __unused = {0, 0, 0}} l1 = <optimized out> lim = {rlim_cur = 1024, rlim_max = 524288} option_index = 12 long_options = {{name = 0x5557fdd90051 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x5557fdd9dc1d "version", has_arg = 0, flag = 0x0, val = 118}, { name = 0x5557fdda8d6e "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x5557fdd90056 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x5557fdd9005c "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x5557fdd90065 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x5557fdd9006f "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x5557fdd90079 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x5557fdd90084 "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0x5557fdd9008d "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x5557fdd9dd3a "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x5557fdd90098 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x5557fdd900a2 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x5557fdd900a9 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" ``` Here is called `pthread_getspecific` https://github.com/kamailio/kamailio/blob/6.0.4/src/modules/tls/tls_mod.c#L… Source code for this function at https://github.com/kraj/musl/blob/kraj/master/src/thread/pthread_getspecifi… In the standard musl package `self` variable is optimised and not available for printing. I have compiled musl with disabled optimization and the `self` variable available for printing. ``` (gdb) p self $5 = (struct __pthread *) 0x7fcbdf4ac588 <builtin_tls+136> (gdb) p *self $6 = {self = 0x7fcbdf4ac588 <builtin_tls+136>, dtv = 0x7fcbdf4ac500 <builtin_tls>, prev = 0x7fcbdf4ac588 <builtin_tls+136>, next = 0x7fcbdf4ac588 <builtin_tls+136>, sysinfo = 0, canary = 5087873141211791600, tid = 30511, errno_val = 9, detach_state = 2, cancel = 0, canceldisable = 0 '\000', cancelasync = 0 '\000', tsd_used = 0 '\000', dlerror_flag = 0 '\000', map_base = 0x0, map_size = 0, stack = 0x0, stack_size = 0, guard_size = 0, result = 0x0, cancelbuf = 0x0, tsd = 0x0, robust_list = {head = 0x7fcbdf4ac610 <builtin_tls+272>, off = 0, pending = 0x0}, h_errno_val = 0, timer_id = 0, locale = 0x7fcbdf4aa8b8 <__libc+56>, killlock = {0}, dlerror_buf = 0x0, stdio_locks = 0x0} (gdb) p self->tsd $7 = (void **) 0x0 (gdb) p self->tsd[0] Cannot access memory at address 0x0 ``` Probably need to call `pthread_setspecific` before calling `pthread_getspecific`. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` ~/packages/root/x86_64 # kamailio -v version: kamailio 6.0.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 16:06:16 Dec 16 2025 with gcc 15.2.0 ``` * **Operating System**: ``` ~/packages/root/x86_64 # cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.23.2 PRETTY_NAME="Alpine Linux v3.23" 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/4534 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4534(a)github.com>

5 13

[kamailio/kamailio] http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table (Issue #4431)
by fulhade 20 Apr '26

20 Apr '26

fulhade created an issue (kamailio/kamailio#4431) Testing 6.0.3 noticed that log is filled with INFO log messages from title (every 5s). No errors in logs, usual stuff except info on tcpcon ``` Oct 12 00:40:24 kamailio[4350]: INFO: <core> [core/tcp_main.c:3124]: tcpconn_1st_send(): quick connect for 0x7f78f8c79b10 sock 38 Oct 12 22:42:26 kamailio[4355]: INFO: <core> [core/tcp_main.c:3124]: tcpconn_1st_send(): quick connect for 0x7f78f8c79b10 sock 32 ... Oct 13 07:42:12 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table Oct 13 07:42:17 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table Oct 13 07:42:22 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table Oct 13 07:42:27 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table Oct 13 07:42:32 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table Oct 13 07:42:37 kamailio[4355]: INFO: http_async_client [http_multi.c:88]: event_cb(): Cell for handler 0x7f78f8c79b10 not found in table ``` Using docker image built on trixie: https://pastebin.com/0wZ0X9wb Not sure how to reproduce, it just appear on testing machine after couple of days. Unfortunately we used 5.6.3 before this, so not sure when did it break for us. http_async_client usage: ``` $http_req(hdr) = "Content-Type: application/json"; $http_req(hdr) = "Expect: "; $http_req(body) = $dlg_var(http_body); http_async_query("${URL}/RoutingService/route", "ROUTING_RESPONSE"); ``` Memory looks fine, but one of four CPU core spike to 96%. <img width="1119" height="955" alt="Image" src="https://github.com/user-attachments/assets/ffff8680-84ad-4866-9892-a6e6eefd…" /> core.tcp_info, mod.stats all shm, mod.stats all pkg https://pastebin.com/QLZ8mZdD -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4431 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4431(a)github.com>

4 8

[kamailio/kamailio] Potential SHM memory leak in pua_dialoginfo / pua modules ? (Issue #4503)
by Alessio Garzi 20 Apr '26

20 Apr '26

Ozzyboshi created an issue (kamailio/kamailio#4503) Hello, on my Kamailio installation I am experiencing a significant memory leak in SHM. Here are the details of my system: ``` version: kamailio 6.0.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, NO_SIG_DEBUG, 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 compiled with gcc 14.2.0 ``` The memory leak appears only when the presence feature is enabled. When presence is active, Kamailio starts running dialog_publish(), whose code is here: https://github.com/kamailio/kamailio/blob/9dc160d1d2bdf0542d3d9d8ae090bb135… This function does not send the PUBLISH directly: it calls pua_send_publish(), which is a function pointer referring to the send_publish() implementation in the pua module. Then send_publish() eventually calls set_uac_req() and tmb.t_request(): https://github.com/kamailio/kamailio/blob/9dc160d1d2bdf0542d3d9d8ae090bb135… Digging further, tmb.t_request() maps to request() in the TM module, which calls t_uac_with_ids() and then t_uac_prepare(). Now comes the suspicious part: If I comment out the call to t_uac_prepare(), the memory leak disappears. This doesn’t necessarily mean the bug is inside t_uac_prepare(), but it’s a strong hint. t_uac_prepare() allocates a new struct cell and returns it: https://github.com/kamailio/kamailio/blob/9dc160d1d2bdf0542d3d9d8ae090bb135… My concern is: is this cell always freed? The matching cleanup function is free_cell(), used only here: https://github.com/kamailio/kamailio/blob/9dc160d1d2bdf0542d3d9d8ae090bb135… From what I can tell, free_cell() is called only if all these conditions are true: - dst_cell == 0 - is_ack == 1 - dst_req == 0 - In my situation no ACK is involved (Kamailio is a proxy that sends PUBLISH and immediately gets a 200 OK). Therefore, is_ack is always false meaning the free_cell() cleanup logic is skipped entirely. I tried forcing free_cell() unconditionally, but it leads to crashes, so clearly other parts of the code still rely on this structure. Does the current free_cell() logic look correct to you? Is it expected that struct cell allocated by t_uac_prepare() remains unfreed in cases where PUBLISH → 200 OK occurs without ACK? Any guidance on how to proceed or where else to look would be greatly appreciated. Thanks -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4503 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4503(a)github.com>

5 30

[kamailio/kamailio] topos: Allow contact a/b host like user part (PR #4246)
by Xenofon Karamanos 16 Apr '26

16 Apr '26

4 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev February 2026