sr-dev October 2025

sr-dev@lists.kamailio.org

12 participants
145 discussions

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

15 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 3

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

15 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 4

[kamailio/kamailio] ndb_redis: TLS/auth fixes and cluster robustness (PR #4442)
by jack.cao 14 Nov '25

14 Nov '25

Signed-off-by: Jack Cao <jack.cao(a)cresta.ai> You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4442 -- Commit Summary -- * ndb_redis: fix tls parsing, set timeout before AUTH, bound sentinel copy, prep dyn-node attrs -- File Changes -- M src/modules/ndb_redis/redis_client.c (67) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4442.patch https://github.com/kamailio/kamailio/pull/4442.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4442 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4442(a)github.com>

2 4

[kamailio/kamailio] failed alpine docker image build (Issue #4241)
by sergey-safarov 14 Nov '25

14 Nov '25

sergey-safarov created an issue (kamailio/kamailio#4241) ### Description In the GitHub Actions present Alpine Docker image build error ``` tar (child): kamailio_min-without_os_files.tar.gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ``` https://github.com/kamailio/kamailio/actions/runs/14722992691/job/413201110… With high probability, this does not work I will work to fix this, but if possible, it will be fine to switch to use `cmake` for Alpine Docker image. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4241 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4241(a)github.com>

3 29

[kamailio/kamailio] KEMI: Add htable count/match API equivalent to $shtcn() (to avoid pv_cache growth with dynamic PV strings) (Issue #4426)
by Hendrik Wedhorn 14 Nov '25

14 Nov '25

wedhornsipgate created an issue (kamailio/kamailio#4426) **Description:** We're missing a KEMI function in the htable module that provides the same functionality as the PV function `$shtcn(table=>pattern)` to count the number of keys in an htable that match a given pattern (prefix/suffix/regex). The goal is to let KEMI scripts perform pattern counts without constructing dynamic PV expressions, which currently causes unbounded pv_cache growth in PKG memory. **Use case / motivation:** We implemented rolling-window rate limiting by writing short-lived, per-call entries into an htable and then counting keys that match a number-derived pattern. Using $shtcn() works well for the logic, but in KEMI (JS/TypeScript) we must call it via pv.gete("$shtcn(...)"). Because the PV string varies per INVITE (different pattern/key each time), these dynamic PV expressions accumulate in the PV cache, growing PKG/private memory over time. We’d like a native KEMI function to perform the same count/match so we can avoid the PV layer entirely. **Environment** Kamailio: 5.8.6 on Debian 12 Scripting: KEMI (JavaScript/TypeScript) Symptom: steady PKG/private memory increase over ~24h under load when using pv.gete("$shtcn(...)"). Disabling the $shtcn() call stops the growth. Related log line: the one discussed in [#3440](https://github.com/kamailio/kamailio/issues/3440) (“pv cache … pkg memory may get filled with pv declarations”). Current line in our script: ```if (ksr.pv.gete(`$shtcn(${htable_count}=>%~${number})`) > threshold) { ... }``` **Current workaround** Restarting the Kamailio every day or disabling rate limit on instances with KEMI. **Idea for API** Minimal, PV-parity: ``` // KEMI export int shtcn_match(str table, str pattern, int mode /* 0=exact, 1=prefix, 2=suffix, 3=regex */); ``` JS example: `const n = KSR.htable.shtcn_match("from_number_count", number, 3); // regex` More explicit helpers (avoids integer modes): ``` KSR.htable.shtcn_exact(table, key) -> int KSR.htable.shtcn_prefix(table, prefix) -> int KSR.htable.shtcn_suffix(table, suffix) -> int KSR.htable.shtcn_regex(table, pattern) -> int ``` **Behavioral notes / expectations** Should mirror $shtcn() semantics where reasonable (esp. regex behavior), but returning an integer directly to KEMI. Must not allocate PV expressions or interact with pv_cache. **Why this belongs in htable KEMI** $shtcn() is already offered at the PV level; parity in KEMI keeps feature consistency across scripting engines. It enables memory-safe implementations of rolling-window rate limits and similar patterns (without touching PV). **Alternatives considered** Replace pattern counting with per-bucket counters (sht_inc), which leads to other problems like increment/decrement handling and locking. Use ratelimit/pike modules—useful for IP/method limits, but our use case is PAI/From/To based and currently hinges on pattern counts. **Acceptance criteria** A KEMI function exists to count matching keys in an htable without PV parsing. Verified that repeated calls with dynamic patterns do not grow PV cache / PKG memory. Basic tests for exact/prefix/suffix/regex modes (and skip_expired if implemented). Thank you! This would let KEMI users keep $shtcn()-style logic with the same performance characteristics, but without the PV-cache side effects. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4426 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4426(a)github.com>

3 2

[kamailio/kamailio] Not using advertised transport protocol when generating BYE Message. (Issue #4349)
by Jonas Swiatek 14 Nov '25

14 Nov '25

jonastelzio created an issue (kamailio/kamailio#4349) ### Description  Kamailio configured with the following listeners: ``` listen=udp:LOCAL_IP:5060 advertise DNS_HOST:5060 listen=tcp:LOCAL_IP:5060 advertise DNS_HOST:5060 listen=tcp:LOCAL_IP:5061 advertise tls:DNS_HOST:5061 ``` Notice `tls:` in the advertise part of the last listener. TLS Termination happens upstream by, in this case, haproxy. The following happens: 1. Kamailio receives invite from a phone via TCP, on the TLS advertised listener. The phone is communicating via TLS, but it's terminated upstream. 2. Dispatcher is used to select where to forward it 3. Forwards via UDP and the call is connected downstream. 4. The downstream asterisk ends the call by sending a BYE request 5. Kamailio receives this, and generates a BYE request for the phone. The generated BYE request has an incorrect Via-header: `Via: SIP/2.0/TCP jswiatek.dk.office.tlz:5060;branch=z9hG4bK2e8f.2625efdb2ab26c466f55b8baf1bf807d.0` This should be `SIP/2.0/TLS`, and the host should be `:5061` In the provided PCAP, this is message is message number 15. A similar issue was addressed in this commit: https://github.com/kamailio/kamailio/commit/3322bea764036deba6340e435c25724… ### Troubleshooting #### SIP Traffic  PCAP of this happening: [advertise_tls_bye_fail.zip](https://github.com/user-attachments/files/21597… ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.0.2 (x86_64/linux) d4dc5d-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, 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: d4dc5d -dirty ``` * **Operating System**:  ``` Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm Linux 44298e54e0b8 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun 5 18:30:46 UTC 2025 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4349 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4349(a)github.com>

3 5

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

13 Nov '25

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

4 15

[kamailio/kamailio] segfault due to expired timer broken "next" list (Issue #4345)
by Stefan Mititelu 13 Nov '25

13 Nov '25

stefan-mititelu-idt created an issue (kamailio/kamailio#4345)  ### Description Crash in kamailio 5.8.5 due to broken "next" pointer of circular double linked list of expired timers.  ### Troubleshooting - #### Reproduction Not easily reproducible  #### Debugging Data  ``` (gdb) bt full #0 timer_list_expire (slow_mark=<optimized out>, slow_l=0x7ff891b59d60, h=0x7ff891b56ff0, t=<optimized out>) at core/timer.c:850 tl = 0x7ff89d214810 ret = <optimized out> tl = <optimized out> ret = <optimized out> #1 timer_handler () at core/timer.c:925 saved_ticks = <optimized out> run_slow_timer = 0 i = <optimized out> saved_ticks = <optimized out> run_slow_timer = <optimized out> i = <optimized out> __func__ = "timer_handler" __llevel = <optimized out> __kld = {v_facility = <optimized out>, v_level = <optimized out>, v_lname = <optimized out>, v_fname = <optimized out>, v_fline = <optimized out>, v_mname = <optimized out>, v_func = <optimized out>, v_locinfo = <optimized out>, v_pid = <optimized out>, v_pidx = <optimized out>} __llevel = <optimized out> __kld = {v_facility = <optimized out>, v_level = <optimized out>, v_lname = <optimized out>, v_fname = <optimized out>, v_fline = <optimized out>, v_mname = <optimized out>, v_func = <optimized out>, v_locinfo = <optimized out>, v_pid = <optimized out>, v_pidx = <optimized out>} #2 timer_main () at core/timer.c:963 No locals. #3 0x000055e671830461 in main_loop () at main.c:1933 i = <optimized out> pid = <optimized out> si = 0x0 si_desc = "udp receiver child=15 sock=x.x.x.x:5080 (y.y.y.y:5080)", '\000' <repeats 16 times>, "\002\000\000\000\004\000\000\000\n_\022:\372\177\000\000\003\000\000\000\000\000\000\000\000kt\234s8\b\rThu Jul \a\000\000\000\000\000\000" nrprocs = <optimized out> woneinit = 1 __func__ = "main_loop" error = <optimized out> #4 0x000055e671824ff2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:3257 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0x7ffe2850be85 "" tmp_len = 0 port = 5060 proto = 0 aproto = 0 ahost = 0x0 aport = 0 options = 0x55e671bacd30 ":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 = 1220594137 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> --Type <RET> for more, q to quit, c to continue without paging-- dont_fork_cnt = <optimized out> n_lst = <optimized out> p = <optimized out> st = {st_dev = 22, st_ino = 1081, st_nlink = 2, st_mode = 16888, st_uid = 109, st_gid = 115, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1751525619, tv_nsec = 801181720}, st_mtim = {tv_sec = 1751525619, tv_nsec = 117175705}, st_ctim = {tv_sec = 1751525636, tv_nsec = 937332387}, __glibc_reserved = {0, 0, 0}} l1 = <optimized out> tbuf = "\000\000\000\000\000\000\000\000\030\"U(\376\177\000\000\000\000\000\000 ", '\000' <repeats 27 times>, "\001\000\000\000\000\000\000\000\366u\256\003\001", '\000' <repeats 67 times>, "\060Wj\242\372\177\000\000\004\000\000\024\000\000\000\000@!k\242\372\177", '\000' <repeats 138 times>, "\020\000\000\000\000\000\000\000 \265P(\376\177\000\000\020\000\000\000\376\177\000\000\060\265P(\376\177\000\000\370\264P(\376\177\000\000x\221\205\242\372\177\000\000\300\t\000\000\300\t\000\000x\221\205\242\372\177\000\000\300\t\000\000\300\t\000\000L\206\204\242\372\177\000\000\300\t\000\000\300\t\000\000L\206\204\242\372\177\000\000\300\t\000\000\300\t\000\000\300\t\000\000\300\t\000\000\377\377\377\377\000\000\000\000\020_\202\242\372\177\000\000H\000\000\000\000\000\000\000\312<k\242\372\177\000\000`\200\205\242d\000\000\000\000kt\234s8\b\r\377\377\377\377\000\000\000\000j[j\242\372\177\000\000\000\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\000\000\200\000\000\000\000\000\377\377\377\377\377\377\377\377\377\265\360\000\000\000\000\000\302\000\000\000\000\000\000" option_index = 12 long_options = {{name = 0x55e671bab333 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x55e671bb4a8e "version", has_arg = 0, flag = 0x0, val = 118}, { name = 0x55e671bc48d1 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x55e671bab338 "subst", has_arg = 1, flag = 0x0, val = 1025}, { name = 0x55e671bab33e "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x55e671bab347 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, { name = 0x55e671bab351 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x55e671bab35b "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, { name = 0x55e671bab366 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x55e671bab36f "log-engine", has_arg = 1, flag = 0x0, val = 1031}, { name = 0x55e671bb4bab "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x55e671bab37a "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, { name = 0x55e671bab384 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x55e671bab38b "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" ``` Some more debugging info: ``` (gdb) p tl $203 = (struct timer_ln *) 0x7ff89d214810 (gdb) p h $202 = (struct timer_head *) 0x7ff891b56ff0 (gdb) p *(struct timer_ln *) 0x7ff891e21af0 $6 = {next = 0x7ff891e24b00, prev = 0x7ff89d214810, expire = 1057066680, initial_timeout = 480, data = 0x7ff891e21af0, f = 0x55e671a570a0 <compat_old_handler>, flags = 512, slow_idx = 0} (gdb) p *tl $205 = {next = 0x0, prev = 0x7ff891b56ff0, expire = 1057066648, initial_timeout = 48, data = 0xfffffffe, f = 0x7ffa91f77e30 <retr_buf_handler>, flags = 512, slow_idx = 0} (gdb) p *h $204 = {next = 0x0, prev = 0x7ff891e00e10} (gdb) p *(struct timer_ln *) 0x7ff891e00e10 $7 = {next = 0x7ff891b56ff0, prev = 0x7ff89e47d538, expire = 1057066680, initial_timeout = 16, data = 0x7ff891e00e10, f = 0x55e671a570a0 <compat_old_handler>, flags = 512, slow_idx = 0} (gdb) p h->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev $198 = (struct timer_ln *) 0x7ff891e21af0 (gdb) p h->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev $199 = (struct timer_ln *) 0x7ff89d214810 (gdb) p h->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev $200 = (struct timer_ln *) 0x7ff891b56ff0 (gdb) p h->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev->prev $201 = (struct timer_ln *) 0x7ff891e00e10 ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (gdb) p *(struct retr_buf *)((char *)(tl)-((size_t)((char *)&((struct retr_buf*)(0))->timer - (char *)0))) $13 = {rbtype = 0, flags = 164, t_active = 0, branch = 0, buffer_len = 1021, buffer = 0x7ff897731ef0 "KDMQ sip:usrloc@x.x.x.x:5040;transport=tcp SIP/2.0\r\nVia: SIP/2.0/TCP y.y.y.y:5045;branch=z9hG4bK6411.2eec64c5", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@x.x.x.x:5040;transport=tcp>\r\nFrom: <sip:usrloc@y.y.y.y:5040;transport=tcp>;tag=ea5c1e4b006551edd6973f0c22cc35ec-9c6994fe\r\nCSeq: 10 KDMQ\r\nCall-ID: 3bc128ce41f9d5e5-3737(a)x.x.x.x\r\nContent-Length: 574\r\nUser-Agent: UNITE 3.0\r\nMax-Forwards: 1\r\nContent-Type: application/json\r\n\r\n{\"action\":1,\"aor\":\"01537833832a5ccc75058ef5839f\",\"ruid\":\"uloc-a71cb2-68662908-e99-e6b85\",\"c\":\"sip:01537833832a5ccc75058ef5839f@z.z.z.z:11916;transport=TCP\",\"received\":\"sip:x.x.x.x:11916;transport=tcp\",\"path\":\"<sip:z.z.z.z:5040;transport=tcp;lr;received=sip:w.w.w.w:11916%3Btransport%3Dtcp;socket=clientTCPListener>\",\"callid\":\"0_912990869(a)192.168.1.7\",\"user_agent\":\"Yealink SIP-T30 t.t.t.t\",\"instance\":\"\",\"expires\":1751822448,\"cseq\":28,\"flags\":0,\"cflags\":96,\"q\":-1,\"last_modified\":1751822148,\"methods\":16383,\"reg_id\":0,\"server_id\":10951858,\"xavps\":{}}", my_T = 0x7ff89d214510, timer = {next = 0x0, prev = 0x7ff891b56ff0, expire = 1057066648, initial_timeout = 48, data = 0xfffffffe, f = 0x7ffa91f77e30 <retr_buf_handler>, flags = 512, slow_idx = 0}, dst = {send_sock = 0x7ffa9264fae0, to = {s = {sa_family = 2, sa_data = "\023\260\n_\020\210\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 45075, sin_addr = {s_addr = 2282774282}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 45075, sin6_flowinfo = 2282774282, 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\260\n_\020\210", '\000' <repeats 111 times>, __ss_align = 0}}, id = 0, send_flags = {f = 4, blst_imask = 0}, proto = 2 '\002', proto_pad0 = 0 '\000', proto_pad1 = 0}, retr_expire = 1057066599, fr_expire = 1057066648} ``` ### Possible Solutions Check if "next" list is broken and recover the pointers form "prev" list, and viceversa.  ### Additional Information Using 1s transaction timeout for KDMQs. * **Kamailio Version** - output of `kamailio -v` ``` 5.8.5 kamailio version ``` * **Operating System**:  ``` Debian 11 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4345 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4345(a)github.com>

3 4

[kamailio/kamailio] cmake: switching deb rules (Issue #4053)
by Victor Seva 13 Nov '25

13 Nov '25

Opening this generic issue to track issues when trying to switch deb package generation to cmake: -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4053 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4053(a)github.com>

5 63

[kamailio/kamailio] Multiple Modules: integer support for extra DB fields (PR #4438)
by Tyler Moore 12 Nov '25

12 Nov '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>

2 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2025