sr-dev January 2026

sr-dev@lists.kamailio.org

24 participants
400 discussions

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

05 May '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:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [x] Related to issue #4116 #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4570 -- Commit Summary -- * ims_diameter_server: don't leak on diameter_request() -- File Changes -- M src/modules/ims_diameter_server/ims_diameter_server.c (13) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4570.patch https://github.com/kamailio/kamailio/pull/4570.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4570 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4570(a)github.com>

2 3

[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] 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

#### 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  In this PR we introduce a new mode and two new parameters for accomplishing the same thing for user part also in domain part. Docs incoming if no significant changes are needed. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4246 -- Commit Summary -- * topos: Add new contact_mode=3 and 2 new modparam for contact host domains * topos: Refactor contact_mode handling * topos: Append port and protocol param -- File Changes -- M src/modules/topos/topos_mod.c (13) M src/modules/topos/tps_storage.c (428) M src/modules/topos/tps_storage.h (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4246.patch https://github.com/kamailio/kamailio/pull/4246.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4246 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4246(a)github.com>

4 8

[kamailio/kamailio] jwt module - build by default and upload to deb.kamailio.org (Issue #4416)
by Michael Kanchuker 07 Apr '26

07 Apr '26

mkl262 created an issue (kamailio/kamailio#4416) Hello, Im asking to add the JWT Module to the default list of modules that are being built and uploaded to [deb.kamailio.org](https://deb.kamailio.org/). Will editing the CMAKE scripts will be enough (in which case I can open a PR for it), or does it require modifying the Jenkins pipelines? Thanks, Michael. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4416 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4416(a)github.com>

3 9

[kamailio/kamailio] Kamailio 5.4.x dialog profiles functionality dead-lock on certain high-load scenarios (Issue #2923)
by Henning Westerholt 03 Apr '26

03 Apr '26

### Description The Kamailio 5.4.x dialog profiles functionality can lead to dead-lock on certain high-load scenarios. The Kamailio dialog profiles are used to track parallel channels for about 200 outgoing PSTN carrier interconnections. During high traffic times (like several thousands parallel calls) the Kamailio server will frequently (e.g. hourly) goes into an end-less loop while executing get_profile_size in the configuration script. This causes the locking for the dialog profiles never be released and Kamailio will stop serving traffic. Internal monitoring tools and RPC commands stay working, as long as they do not touch the dialog functionality. A similar (dedicated) Kamailio setup is used for tracking parallel channels for customers. Here the dead-lock is not observed that frequently, but aparentely also some crashes happens in a much longer time interval. ### Troubleshooting After analysis of the back-traces with GDB the get_profile_size() function was removed from the configuration script. After this change the crash did not happened anymore for several days. #### Reproduction Issue could not be reproduced so far. #### Debugging Data ##### bt 1 (some data removed) (gdb) bt \# 0 0x00007f57cf3b00da in get_profile_size (profile=0x7f50ccbc7e80, value=0x7ffd9928f300) at dlg_profile.c:859 n = 364 i = 12 ph = 0x7f50d3e4b7d0 \# 1 0x00007f57cf419c67 in w_get_profile_size_helper (msg=0x7f57d699d418, profile=0x7f50ccbc7e80, value=0x7ffd9928f300, spd=0x7f57d6916960) at dialog.c:941 \# 2 0x00007f57cf41a459 in w_get_profile_size3 (msg=0x7f57d699d418, profile=0x7f50ccbc7e80, value=0x7f57d6935118, result=0x7f57d6916960) at dialog.c:982 \# 3 0x0000000000463fea in do_action (h=0x7ffd99293610, a=0x7f57d6936488, msg=0x7f57d699d418) at core/action.c:1094 \# 4 0x00000000004711ee in run_actions (h=0x7ffd99293610, a=0x7f57d6936488, msg=0x7f57d699d418) at core/action.c:1581 \# 5 0x000000000046058b in do_action (h=0x7ffd99293610, a=0x7f57d690fda8, msg=0x7f57d699d418) at core/action.c:700 The first back-trace was taking from a running process with gdb. The counter in f0 does not increased that much during this time, probably due the overflow of the loop counter. ##### bt2 (analysis with data structure with gdb scripts) Here the loop counter in f0 showed a really high value. Expected size of dialog profiles hash table: (gdb) p profile->entries[3] $4 = {first = 0x7f9bfd4aad98, content = 2068} (gdb) p profile->entries[7] $3 = {first = 0x7f9c12079f70, content = 784} (gdb) p profile->entries[12] $6 = {first = 0x7f9c02be5d50, content = 7600} (gdb) p profile->entries[14] $2 = {first = 0x7f9bff636de8, content = 6764} hash table bucket 14 shows a lot of corruption and the loop never ends (carrier names and IPs replaced). The list for hash bucket 7 got linked to the list for hash bucket 14: counter 6755: prev 0x7f9c0b9dcde0 - current 0x7f9c02e5b378 - next 0x7f9c0a5f9ba0 - value carrier1-XX.XX - hash 14 counter 6756: prev 0x7f9c02e5b378 - current 0x7f9c0a5f9ba0 - next 0x7f9c0860b968 - value carrier1-XX.XX▒▒▒▒ - hash 14 counter 6757: prev 0x7f9c0a5f9ba0 - current 0x7f9c0860b968 - next 0x7f9bfe3f3a78 - value carrier1-XX.XX▒▒▒▒ - hash 14 counter 6758: prev 0x7f9c0860b968 - current 0x7f9bfe3f3a78 - next 0x7f9c10d977f0 - value carrier1-XX.XX - hash 14 counter 6759: prev 0x7f9bfe3f3a78 - current 0x7f9c10d977f0 - next 0x7f9c0ae198b0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 6760: prev 0x7f9c10d977f0 - current 0x7f9c0ae198b0 - next 0x7f9c12079f70 - value carrier3-XX.XX - hash 7 counter 6761: prev 0x7f9c0ae198b0 - current 0x7f9c12079f70 - next 0x7f9c011f2540 - value-carrier2-XX.XX▒▒▒▒ - hash 7 counter 6762: prev 0x7f9c12079f70 - current 0x7f9c011f2540 - next 0x7f9bfff886f0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 6763: prev 0x7f9c011f2540 - current 0x7f9bfff886f0 - next 0x7f9c05db00a8 - value carrier3-XX.XX= - hash 7 [...] counter 28270: prev 0x7f9c019d06e8 - current 0x7f9bfaf18290 - next 0x7f9c12c90680 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 28271: prev 0x7f9bfaf18290 - current 0x7f9c12c90680 - next 0x7f9c086a2b58 - value-carrier2-XX.XX▒▒▒▒ - hash 7 counter 28272: prev 0x7f9c12c90680 - current 0x7f9c086a2b58 - next 0x7f9c0b4f09e8 - value carrier2-XX.XX▒▒▒▒ - hash 7 [...] hash table bucket 7 is still consistent regarding the loop, but already shows initial sign of corruption. There is one item of the list for hash bucket 14 visible: counter 780: prev 0x7f9c0db57ac8 - current 0x7f9c02225700 - next 0x7f9bfbf7db08 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 781: prev 0x7f9c02225700 - current 0x7f9bfbf7db08 - next 0x7f9c10d977f0 - value carrier1-XX.XX- hash 14 counter 782: prev 0x7f9bfe3f3a78 - current 0x7f9c10d977f0 - next 0x7f9c0ae198b0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 783: prev 0x7f9c10d977f0 - current 0x7f9c0ae198b0 - next 0x7f9c12079f70 - value carrier3-XX.XX - hash 7 total size of hash table is 784 #### Log Messages No special log messages observed. #### SIP Traffic SIP traffic looked ok during analysis of the core dumps. ### Possible Solutions * adding additional safe-guards for the get_profile_size function to not access data from other hash buckets * stopping the loop counter after some threshold * finding and fixing the source of the internal data corruption (obviously) * refactoring the dialog modules to use another approach for storing the dialog profile information ### Additional Information * **Kamailio version**: Kamailio 5.4.7, compiled from git repository * **Operating System**: CentOS 7.9 -- 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/issues/2923

3 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 January 2026