- sr-dev - kamailio.org

[kamailio/kamailio] kamailio crash alert (Issue #3290)
by 6ecbl 23 Nov '23

23 Nov '23

### Description crashes the server, raised by qm_debug_check_frag()[?] ### Troubleshooting #### Reproduction happens randomly #### Debugging Data ``` [New LWP 13364] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/var/lib/ums/sbin/kamailio -m 2048 -M 12 -P /var/run/kamailio/kamailio.pid -f /'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt full #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 No locals. #1 0x00007fbaf0bf99ef in _IO_vfprintf_internal (s=s@entry=0x1874040, format=format@entry=0xa6217c "%s: %.*s%s%s%sBUG: qm: fragm. %p (address %p) beginning overwritten (%lx)! Memory allocator was called from %s:%u. Fragment marked by %s:%lu. Exec from %s:%u.\n", ap=ap@entry=0x7ffc043b3b60) at vfprintf.c:1638 len = <optimized out> string_malloced = 0 step0_jumps = {0, 3637, 3213, 3109, 4653, 2997, 4437, 4037, 3717, 4869, 4773, 3397, 4557, 4549, 3589, 4981, 3701, 4757, 3317, 2021, 1429, 1221, 2261, 1701, 1653, 797, 1773, 437, 437, 4333} space = 0 is_short = 0 use_outdigits = 0 outc = <optimized out> step1_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 4869, 4773, 3397, 4557, 4549, 3589, 4981, 3701, 4757, 3317, 2021, 1429, 1221, 2261, 1701, 1653, 797, 1773, 437, 437, 0} group = 0 prec = <optimized out> step2_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4773, 3397, 4557, 4549, 3589, 4981, 3701, 4757, 3317, 2021, 1429, 1221, 2261, 1701, 1653, 797, 1773, 437, 437, 0} string = 0x8 <error: Cannot access memory at address 0x8> left = 0 is_long_double = <optimized out> width = 0 signed_number = <optimized out> step3a_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3493, 0, 0, 0, 3589, 4981, 3701, 4757, 3317, 0, 0, 0, 0, 1701, 0, 0, 0, 0, 0, 0} alt = 0 showsign = 0 is_long = <optimized out> is_char = <optimized out> pad = 32 ' ' step3b_jumps = {0 <repeats 11 times>, 4557, 0, 0, 3589, 4981, 3701, 4757, 3317, 2021, 1429, 1221, 2261, 1701, 1653, 797, 1773, 0, 0, 0} step4_jumps = {0 <repeats 14 times>, 3589, 4981, 3701, 4757, 3317, 2021, 1429, 1221, 2261, 1701, 1653, 797, 1773, 0, 0, 0} args_value = <optimized out> is_negative = <optimized out> number = <optimized out> base = <optimized out> the_arg = {pa_wchar = 10882210 L'\xa60ca2', pa_int = 10882210, pa_long_int = 10882210, pa_long_long_int = 10882210, pa_u_int = 10882210, pa_u_long_int = 10882210, pa_u_long_long_int = 10882210, pa_double = 5.3765261118300716e-317, pa_long_double = <invalid float value>, pa_string = 0xa60ca2 "fragm. from qm_malloc", pa_wstring = 0xa60ca2 L"\x67617266\x66202e6d\x206d6f72\x6d5f6d71\x6f6c6c61\x633c0063\x3e65726f\x6f635b20\x6d2f6572\x712f6d65\x6c616d5f\x2e636f6c\x31343a63\x203a5d39\x64322500\x29642528\x3a732520\x2a2e2520\x25732573\x71732573\x616d5f6d\x636f6c6c\x2c702528\x756c2520\x65722029\x6e727574\x64612073\x73657264\x70252073\x61726620\x25202e67\x73282070\x3d657a69\x29756c25\x206e6f20\x2d206425\x68206874\xa7469\x726f633c\x5b203e65\x65726f63\x6d656d2f\x6d5f712f\x6f6c6c61\x3a632e63\x5d323334\x2500203a\x25286432\x25202964\x25203a73\x25732a2e\x25732573\x5f6d7173\x6c6c616d\x2528636f\x25202c70\x2029756c\x6c6c6163\x66206465\x206d6f72\x203a7325\x25287325\x202c2964\x75646f6d\x203a656c\x203b7325\x65657246\x61726620\x6e656d67\x6f6e2074\x6f662074\x21646e75\x6d71000a\x6572665f\x633c0065\x3e65726f\x6f635b20\x6d2f6572\x712f6d65\x6c616d5f\x2e636f6c\x38343a63\x203a5d32\x64322500\x29642528\x3a732520\x2a2e2520\x25732573\x71732573\x72665f6d\x25286565\x25202c70\x202c2970\x6c6c6163\x66206465\x206d6f72\x203a7325\x25287325\xa2964\x726f633c\x5b203e65\x65726f63\x6d656d2f\x6d5f712f\x6f6c6c61\x3a632e63\x5d373834\x2500203a\x25286432\x25202964\x25203a73\x25732a2e\x25732573\x52415773\x474e494e\x7266203a\x30286565\x61632029\x64656c6c\x6f726620\x7325206d\x7325203a\x29642528\x633c000a\x3e65726f\x6f635b20\x6d2f6572\x712f6d65\x6c616d5f\x2e636f6c\x39343a63\x203a5d38\x64322500\x29642528\x3a732520\x2a2e2520\x25732573\x42732573\x203a4755\x20646162\x6e696f70\x20726574\x28207025\x2074756f\x6d20666f\x726f6d65\x6c622079\x216b636f\x61632029\x64656c6c\x6f726620\x7325206d\x7325203a\x29642528\x61202d20\x74726f62\xa676e69\x6f633c00\x203e6572\x726f635b\x656d2f65\x5f712f6d\x6c6c616d\x632e636f\x3230353a\x203a5d\x28643225\x20296425\x203a7325\x732a2e25\x73257325\x55427325\x62203a47\x70206461\x746e696f\x25207265\x6f282070\x6f207475\x656d2066\x79726f6d\x6f6c6220\x29216b63\x6c616320\x2064656c\x6d6f7266\x3a732520\x28732520\x20296425\x6769202d\x69726f6e\xa676e\x726f633c\x5b203e65\x65726f63\x6d656d2f\x6d5f712f\x6f6c6c61\x3a632e63\x5d363135\x2500203a"..., pa_pointer = 0xa60ca2, pa_user = 0xa60ca2} spec = 115 's' _buffer = {__routine = 0xe043b3a30, __arg = 0xaab0000000000000, __canceltype = 70989632, __prev = 0x87aa86 <qm_find_free+70>} _avail = <optimized out> thousands_sep = 0x0 grouping = 0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff> done = 223 f = 0xa62203 "s:%lu. Exec from %s:%u.\n" lead_str_end = 0xa6217c "%s: %.*s%s%s%sBUG: qm: fragm. %p (address %p) beginning overwritten (%lx)! Memory allocator was called from %s:%u. Fragment marked by %s:%lu. Exec from %s:%u.\n" end_of_spec = <optimized out> work_buffer = '\000' <repeats 88 times>, "\035\270\314\357\272\177", '\000' <repeats 22 times>, "\020\000\000\000\000\000\000\000\000\000|\266\340\066;\004\374\177\000\000\221\222\207\000\000\000\000\000\003\b\000\000\000\000\000\000\001\b\000\000\003\b\000\000\220\301\264o\272\177\000\000\220\301\264o\272\177\000\000\360-+y\272\177\000\000\000@\261o\272\177\000\000@7;\004\374\177\000\000"... workstart = 0x0 workend = <optimized out> ap_save = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffc043b3c40, reg_save_area = 0x7ffc043b3b80}} nspecs_done = 10 save_errno = 0 readonly_format = 0 __PRETTY_FUNCTION__ = "_IO_vfprintf_internal" __result = <optimized out> #2 0x00007fbaf0c9bc68 in __GI___vsyslog_chk (pri=<optimized out>, flag=-1, fmt=<optimized out>, ap=0x7ffc043b3b60) at ../misc/syslog.c:220 now_tm = {tm_sec = 47, tm_min = 6, tm_hour = 6, tm_mday = 1, tm_mon = 11, tm_year = 122, tm_wday = 4, tm_yday = 334, tm_isdst = 0, tm_gmtoff = -28800, tm_zone = 0x175a950 "PST"} now = 1669903607 fd = <optimized out> f = 0x1874040 buf = 0x0 bufsize = 0 msgoff = 21 saved_errno = 0 failbuf = "\000\000\000\000\001", '\000' <repeats 23 times> clarg = <optimized out> #3 0x00007fbaf0c9bd4c in __syslog (pri=<optimized out>, fmt=<optimized out>) at ../misc/syslog.c:117 ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7ffc043b3c80, reg_save_area = 0x7ffc043b3b80}} #4 0x000000000087b7e1 in qm_debug_check_frag (qm=0x7fba6fb14000, f=0x7fba792aa810, file=0x7fbaeff5065c "tls: tls_init.c", line=293, efile=0xa61ea3 "core/mem/q_malloc.c", eline=391) at core/mem/q_malloc.c:123 __llevel = -3 p = 0x7ffc043b41a0 #5 0x0000000000879b37 in qm_malloc (qmp=0x7fba6fb14000, size=120, file=0x7fbaeff5065c "tls: tls_init.c", func=0x7fbaeff5066c "ser_malloc", line=293, mname=0x7fbaeff4e021 "tls") at core/mem/q_malloc.c:391 qm = 0x7fba6fb14000 f = 0x7fba792aa810 hash = 710 list_cntr = 1 #6 0x000000000088fd7a in qm_shm_malloc (qmp=0x7fba6fb14000, size=120, file=0x7fbaeff5065c "tls: tls_init.c", func=0x7fbaeff5066c "ser_malloc", line=293, mname=0x7fbaeff4e021 "tls") at core/mem/q_malloc.c:1227 r = 0x7fba792b6fd8 #7 0x00007fbaefee3b8e in ser_malloc (size=120, fname=0x7fbaefd6dab1 "crypto/bio/bio_lib.c", fline=73) at tls_init.c:293 No locals. #8 0x00007fbaefcc8e51 in CRYPTO_zalloc () from /var/lib/ums/lib/libcrypto.so.1.1 No symbol table info available. #9 0x00007fbaefbc449e in BIO_new () from /var/lib/ums/lib/libcrypto.so.1.1 No symbol table info available. #10 0x00007fbaefe632a0 in ssl_init_wbio_buffer () from /var/lib/ums/lib/libssl.so.1.1 No symbol table info available. #11 0x00007fbaefe748e3 in state_machine () from /var/lib/ums/lib/libssl.so.1.1 No symbol table info available. #12 0x00007fbaefee9fc8 in tls_accept (c=0x7fba792a3a10, error=0x7ffc043d5fc8) at tls_server.c:468 ret = 16383 ssl = 0x7fba792abf78 cert = 0x7ffc043b4d80 tls_c = 0x7fba792abee0 tls_log = 0 pkey = 0x0 #13 0x00007fbaefefc11c in tls_h_read_f (c=0x7fba792a3a10, flags=0x7ffc043d844c) at tls_server.c:1172 r = 0x7fba792a3b38 bytes_free = 16383 bytes_read = 296 read_size = 16383 ssl_error = 0 ssl_read = 0 ssl = 0x7fba792abf78 rd_buf = "\026\003\001\001#\001\000\001\037\003\003\236\244\005YYR5\"\367\370\213\352p\340\250~\020\376\a\265\224\360\064ՃvF\361\066\242\274\300\000\000\202\300\060\300,\300(\300$\300\024\300\n\000\245\000\243\000\241\000\237\000k\000j\000i\000h\000\071\000\070\000\067\000\066\000\210\000\207\000\206\000\205\300\062\300.\300*\300&\300\017\300\005\000\235\000=\000\065\000\204\300/\300+\300'\300#\300\023\300\t\000\244\000\242\000\240\000\236\000g\000@\000?\000>\000\063\000\062\000\061\000\060\000E\000D\000C\000B\300\061\300-\300)\300%\300\016\300\004\000\234\000<\000/\000A\000\377\001\000\000t\000\000\000\033\000\031\000\000\026"... wr_buf = '\000' <repeats 1856 times>... rd = {buf = 0x7ffc043c5fb0 "\026\003\001\001#\001", pos = 0, used = 296, size = 65536} wr = {buf = 0x7ffc043b5fb0 "", pos = 0, used = 0, size = 65536} tls_c = 0x7fba792abee0 enc_rd_buf = 0x0 n = 0 flush_flags = 0 err_src = 0x7fbaeff51207 "TLS read:" ip_buf = '\000' <repeats 63 times> x = 0 tls_dbg = 0 #14 0x0000000000801508 in tcp_read_headers (c=0x7fba792a3a10, read_flags=0x7ffc043d844c) at core/tcp_read.c:457 bytes = 32698 remaining = 2013924776 p = 0xffff780a14b3 <error: Cannot access memory at address 0xffff780a14b3> r = 0x7fba792a3b38 mc = 32698 body_len = 29151 mfline = 0x33100000080 <error: Cannot access memory at address 0x33100000080> mtransid = {s = 0x400000002 <error: Cannot access memory at address 0x400000002>, len = -2099512625} #15 0x00000000008099bd in tcp_read_req (con=0x7fba792a3a10, bytes_read=0x7ffc043d8450, read_flags=0x7ffc043d844c) at core/tcp_read.c:1472 bytes = -1 total_bytes = 0 resp = 1 size = 140720379622384 req = 0x7fba792a3b38 dst = {send_sock = 0x7fbaf0034118, to = {s = {sa_family = 2, sa_data = "\260Y\317\372ۂ\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 22960, sin_addr = {s_addr = 2195454671}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 22960, sin6_flowinfo = 2195454671, sin6_addr = {__in6_u = { __u6_addr8 = "\000\000\000\000\000\000\000\000H\360\264o\272\177\000", __u6_addr16 = {0, 0, 0, 0, 61512, 28596, 32698, 0}, __u6_addr32 = {0, 0, 1874128968, 32698}}}, sin6_scope_id = 160}, sas = {ss_family = 2, __ss_padding = "\260Y\317\372ۂ\000\000\000\000\000\000\000\000H\360\264o\272\177\000\000\240\000\000\000\200\a\000\000\243\276\202a\005\000\000\000\377\377\377\377\001\000\000\000\200%\000\000\200%\000\000\024\000\000\000\000\000\000\000\001\000\000\000\001\000\000\000s\000\000\000\272\177\000\000\270s=\004\374\177\000\000\310s=\004\374\177\000\000\070hPr\272\177\000\000\b\000\000\000\377\377\377\377@\204=\004\374\177\000", __ss_align = 8}}, id = -1, send_flags = {f = 0, blst_imask = 0}, proto = 0 '\000', proto_pad0 = 0 '\000', proto_pad1 = 0} c = 54 '6' ret = 0 #16 0x000000000082310b in handle_io (fm=0x7fbaf01ff0b0, events=1, idx=-1) at core/tcp_read.c:1782 ret = 8 n = 8 read_flags = RD_CONN_SHORT_READ con = 0x7fba792a3a10 s = 115 resp = 1 t = 1646043924 ee = 0x0 #17 0x000000000081fee0 in io_wait_loop_epoll (h=0xb51830 <io_w>, t=2, repeat=0) at core/io_wait.h:1070 n = 1 r = 0 fm = 0x7fbaf01ff0b0 revents = 1 #18 0x000000000081341e in tcp_receive_loop (unix_sock=44) at core/tcp_read.c:1978 No locals. #19 0x00000000005fc385 in tcp_init_children (woneinit=0x7ffc043da918) at core/tcp_main.c:5153 r = 0 i = 7 reader_fd_1 = 44 pid = 0 si_desc = "tcp receiver (generic)\000\000\a\000\000\000\000\000\000\000\320[\003\360\272\177\000\000P\027\036\360\272\177\000\000\300\216=\004\374\177\000\000\234\b\232\000\000\000\000\000\060\375\210\000\000\000\000\000\360\311=\004\374\177\000\000\000\004\000\000\001\000\000\000H\360\264o\272\177\000\000\000\217=\004\374\177\000\000,\256\232\000\000\000\000\000\350\322\037\360\000\000\000\000pR\003\360$\000\000" si = 0x0 #20 0x0000000000439e28 in main_loop () at main.c:1857 i = 8 pid = 13357 si = 0x0 si_desc = "udp receiver child=7 sock=127.0.0.1:5060\000\060\066\060", '\000' <repeats 12 times>, "\260\373A", '\000' <repeats 21 times>, "\240\251=\004\374\177\000\000m\361}\000\000\000\000\000\300x\327\357\272\177\000\000\000\000\000\000\004\000\000\000\210\033\272", '\000' <repeats 12 times> nrprocs = 8 woneinit = 1 #21 0x0000000000448d4d in main (argc=9, argv=0x7ffc043dc9f8) at main.c:3053 long_options = {{name = 0xa7fe94 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0xa2a4bd "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0xa3e626 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0xa28a8f "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0xa28a95 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0xa28a9e "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0xa28aa8 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0xa28ab2 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0xa28abd "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0xa28ac6 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0xa2a5cd "debug", has_arg = 1, flag = 0x0, val = 1032}, { name = 0xa28ad1 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0xa28adb "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} cfg_stream = 0x1691290 c = -1 r = 0 tmp = 0x7ffc043dd7b6 "" tmp_len = 0 port = 10641941 proto = 0 ahost = 0x0 aport = 0 options = 0xa28ae2 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2591128234 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x0 st = {st_dev = 21, st_ino = 1379545578, st_nlink = 2, st_mode = 16877, st_uid = 990, st_gid = 990, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = { tv_sec = 1669273250, tv_nsec = 445763824}, st_mtim = {tv_sec = 1669273250, tv_nsec = 445763824}, st_ctim = {tv_sec = 1669273250, tv_nsec = 445763824}, __glibc_reserved = {0, 0, 0}} tbuf = '\000' <repeats 24 times>, "\200\037\000\000\377\377\000\000kage/lib/mysql:", '\000' <repeats 153 times>... option_index = 0 ``` #### Log Messages ``` /var/lib/ums/sbin/kamailio[13339]: ALERT: <core> [main.c:789]: handle_sigs(): child process 13364 exited by a signal 11 /var/lib/ums/sbin/kamailio[13339]: ALERT: <core> [main.c:792]: handle_sigs(): core was generated /var/lib/ums/sbin/kamailio[13339]: INFO: <core> [main.c:813]: handle_sigs(): terminating due to SIGCHLD /var/lib/ums/sbin/kamailio[13371]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13370]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13367]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13365]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13366]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13360]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13369]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13350]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13353]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13356]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13340]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13355]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13348]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13354]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13351]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13349]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13347]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13344]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13342]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13343]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13346]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13345]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13341]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13357]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13363]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13359]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13362]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13361]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received /var/lib/ums/sbin/kamailio[13358]: INFO: <core> [main.c:868]: sig_usr(): signal 15 received ``` ### Additional Information * **Kamailio Version** ``` version: kamailio 5.5.4 (x86_64/linux) 54c9df 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: 54c9df compiled on 09:03:48 Nov 17 2022 with clang 9.0 ``` * **Operating System**: ``` Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3290 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3290(a)github.com>

3 4

[kamailio/kamailio] pua_usrloc doesn't send PUBLISH requests when a AOR has been removed by usrloc keepalive timeout (Issue #3273)
by admin-toneca 23 Nov '23

23 Nov '23

Hello, module pua_usrloc doesn't send PUBLISH when AOR has been removed by nathelper or usrloc keepalive timeout. modparam("usrloc", "timer_interval", 30) modparam("usrloc", "timer_procs", 1) modparam("usrloc", "use_domain", MULTIDOMAIN) /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL_USRLOC) modparam("usrloc", "db_mode", 1) #!endif modparam("usrloc", "ka_mode", 1) modparam("usrloc", "ka_from", KEEPALIVE_FROM) modparam("usrloc", "ka_timeout", 120) modparam("presence", "db_url", FSDBURL) modparam("presence", "presentity_table", "sbc_presentity") modparam("presence", "active_watchers_table", "sbc_active_watchers") modparam("presence", "watchers_table", "sbc_watchers") modparam("presence_xml", "db_url", FSDBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) modparam("presence_dialoginfo", "force_single_dialog", 1) modparam("pua", "db_url", FSDBURL) modparam("pua", "db_table", "sbc_pua") modparam("pua_usrloc", "default_domain", HOSTNAME) modparam("pua_dialoginfo", "include_callid", 0) modparam("pua_dialoginfo", "include_tags", 0) modparam("pua_dialoginfo", "include_localremote", 0) ### Additional Information ``` version: kamailio 5.6.2 (x86_64/linux) 54a9c1 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: 54a9c1 compiled on 15:40:44 Nov 1 2022 with gcc 9.4.0 ``` * **Operating System**: ``` No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.5 LTS Release: 20.04 Codename: focal ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3273 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3273(a)github.com>

3 3

[kamailio/kamailio] packaging: cannot merge config files on system with ostree (Issue #3252)
by sergey-safarov 23 Nov '23

23 Nov '23

On Fedora Core when installed Kamailio and then installed additional packages then receive error ``` [root@caloes-1 ~]# journalctl -flu ostree-boot-complete.service -o cat Starting ostree-boot-complete.service - OSTree Complete Boot... error: ostree-finalize-staged.service failed on previous boot: During /etc merge: Modified config file newly defaults to directory 'kamailio', cannot merge ostree-boot-complete.service: Main process exited, code=exited, status=1/FAILURE ostree-boot-complete.service: Failed with result 'exit-code'. Failed to start ostree-boot-complete.service - OSTree Complete Boot. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ``` Suggestion place default Kamailio config into dedicated package "kamailio-config-default". -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3252 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3252(a)github.com>

3 5

[kamailio/kamailio] PUBLISH presence terminated state results in NOTIFY confirmed or early (Issue #3229)
by Duncan Palmer 23 Nov '23

23 Nov '23

### Description I established a call between two extensions using TLS, and the presence state was replicated between two Kamailio servers using presence_dmq (no database backing). This all worked correctly except when it comes to sending a PUBLISH with a state terminated in the body, the presence_dmq sent the serialized data correctly, but the Kamailio server sends the wrong state and the caller is marked as busy on all subscribed phones until Kamailio is restarted. This occurs on version 5.6.1. In order generate this data, we use a separate script which responds to Asterisk events and sends the right PUBLISH at the right time to Kamailio, eg. if it sees a Hangup event, it sends a PUBLISH with the state in the body set to 'terminated' and the Expires: header set to 0. This appears to prompt Kamailio to send a NOTIFY with a state of early or confirmed to all subscribers. ### Troubleshooting #### Reproduction Install two Kamailio servers running Kamailio 5.6.1. I am using this installation command: `sudo apt install kamailio=5.6.1+bpo9 kamailio-dbg=5.6.1+bpo9 kamailio-lua-modules=5.6.1+bpo9 kamailio-memcached-modules=5.6.1+bpo9 kamailio-mysql-modules=5.6.1+bpo9 kamailio-presence-modules=5.6.1+bpo9 kamailio-redis-modules=5.6.1+bpo9 kamailio-tls-modules=5.6.1+bpo9 kamailio-utils-modules=5.6.1+bpo9` Some configuration detail for /etc/kamailio/kamailio.cfg: listen=tls:172.22.0.155:5061 # This ensures we have a UDP socket for sending HEP datagrams (we also send the plaintext UDP PUBLISH here) listen=udp:172.22.0.155:9060 port=5061 enable_tls=yes tcp_connection_lifetime=3605 #modules (this is not an exhaustive list) loadmodule "dmq.so" loadmodule "dialog.so" loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "pua.so" loadmodule "pua_dialoginfo.so" loadmodule "tls.so" modparam("dmq", "server_address", "sip:172.22.0.155:9060") modparam("dmq", "notification_address", "sip:172.22.1.124:9060") modparam("dialog", "db_url", DBURL) modparam("dialog", "enable_stats", 1) modparam("dialog", "db_mode", 0) # 0 - NO_DB - the memory content is not flushed into DB modparam("dialog", "dlg_flag", 9) modparam("dialog", "enable_dmq", 1) modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) # high speed memory based storage modparam("pua", "outbound_proxy", "sips:172.22.0.155:5061;transport=tls") modparam("pua_dialoginfo", "include_localremote", 0) modparam("presence", "db_url", DBURL) modparam("presence", "server_address", "sips:this.host.example.org:5061;transport=tls") modparam("presence", "db_table_lock_type", 0) modparam("presence", "subs_db_mode", 0) # 0 - This disables database completely. modparam("presence", "enable_dmq", 1) modparam("presence", "publ_cache", 2) modparam("presence", "subs_remove_match", 1) modparam("presence", "timeout_rm_subs", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) modparam("presence_dialoginfo", "force_single_dialog", 1) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "force_presence_single_body", 1) #### Log Messages These log aren't directly linked but Kamailio reports a 200 OK in response to the PUBLISH, but the NOTIFY to the handset is _not_ terminated. Difficult to capture this because of TLS. ``` Aug 26 13:32:26 this.host.example.org /usr/sbin/kamailio[4187]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX469","etag":"a.1661495738.4187.2612.0","expires":3600,"recv":1661520746,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-630869ce-105b-43a","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX469@sip.prod.example.org\">\n<dialog id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" call-id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" direction=\"recipient\">\n<state>confirmed</state>\n</dialog>\n</dialog-info>\n"} Aug 26 13:33:00 this.host.example.org /usr/sbin/kamailio[4187]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX469","etag":"a.1661495738.4187.2622.0","expires":0,"recv":1661520780,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-630869ce-105b-e3a","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX469@sip.prod.example.org\">\n<dialog id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" call-id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" direction=\"recipient\">\n<state>terminated</state>\n</dialog>\n</dialog-info>\n"} ``` This is a similar example: ``` Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: INFO: presence [notify.c:1738]: send_notify_request(): NOTIFY sip:XXXX475@sip.prod.example.org via ÿÿÿÿÿÿÿÿ on behalf of sip:XXXX472@sip.prod.example.org for event dialog : 2_2191795053(a)172.31.29.18 Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:400]: pres_dmq_replicate_presentity(): replicating presentity record - old etag a.1662035772.5176.17.0, new etag , ruid pres-6310a741-1438-11 Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX472","etag":"a.1662035772.5176.17.0","expires":0,"recv":1662035834,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-6310a741-1438-11","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX472@sip.prod.example.org\">\n<dialog id=\"76024a0e-2d35-47d8-afd1-a1363acbf859\" call-id=\"76024a0e-2d35-47d8-afd1-a1363acbf859\" direction=\"recipient\">\n<state>terminated</state>\n</dialog>\n</dialog-info>\n"} Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:149]: pres_dmq_send(): sending dmq broadcast... ``` #### SIP Traffic ``` PUBLISH sip:XXXX469@sip.prod.example.org SIP/2.0 Via: SIP/2.0/UDP this.host.example.org;branch=656ebca4-5e71-4082-984a-7efa54bdd2cc To: sip:XXXX469@sip.prod.example.org From: sip:XXXX469@sip.prod.example.org;tag=a06f8d92-609b-4210-a1f0-f7042b871f07 CSeq: 12 PUBLISH Call-ID: d67c8bb5-f507-4ada-8f98-d7caa6d86721(a)this.host.example.org Content-Length: 323 User-Agent: Astertisk-Event-Bridge Max-Forwards: 70 Event: dialog Expires: 0 Content-Type: application/dialog-info+xml <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:XXXX469@sip.prod.example.org"> <dialog id="9fa5bf3c-63f3-4d3f-82c5-cdff374c4e13" call-id="9fa5bf3c-63f3-4d3f-82c5-cdff374c4e13" direction="recipient"> <state>terminated</state> </dialog> </dialog-info> ``` ### Possible Solutions Downgrading to Kamailio version 5.5.4 resolves this problem. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` $ kamailio -v version: kamailio 5.6.1 (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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 $ dpkg -l | egrep '^ii' | grep kamailio | awk '{ print $2, $3 }' kamailio 5.6.1+bpo9 kamailio-dbg:amd64 5.6.1+bpo9 kamailio-lua-modules:amd64 5.6.1+bpo9 kamailio-memcached-modules:amd64 5.6.1+bpo9 kamailio-mysql-modules:amd64 5.6.1+bpo9 kamailio-presence-modules:amd64 5.6.1+bpo9 kamailio-redis-modules:amd64 5.6.1+bpo9 kamailio-tls-modules:amd64 5.6.1+bpo9 kamailio-utils-modules:amd64 5.6.1+bpo9 ``` * **Operating System**: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.2 (stretch) Release: 9.2 Codename: stretch $ uname -a Linux this.host.example.org 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3229 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3229(a)github.com>

3 6

[kamailio/kamailio] do not generate waring when used UDP protocol and no "Content-Length" header (Issue #3210)
by sergey-safarov 23 Nov '23

23 Nov '23

### Description According to [RFC3261](https://datatracker.ietf.org/doc/html/rfc3261#section-20.14) > The Content-Length header field indicates the size of the message- > body, in decimal number of octets, sent to the recipient. > Applications SHOULD use this field to indicate the size of the > message-body to be transferred, regardless of the media type of the > entity. If a stream-based protocol (such as TCP) is used as > transport, the header field MUST be used. When UDP protocol is used then this header is optional. When Kamailio receives an OPTIONS request like in the example, then it floods Kamailio logs with messages like ``` sanity [sanity.c:612]: check_cl(): content length header missing in request ``` OPTIONS message example ``` OPTIONS sip:sbc-0.example.com:5060 SIP/2.0 Via: SIP/2.0/UDP 64.58.61.151:5060;branch=z9hG4bKl7oo3f30a0som61aeu00 Call-ID: 49bc1fcac14b779958dad4b9c43954b400149n2(a)64.58.61.151 To: sip:ping@sbc-0.example.com From: <sip:ping@64.58.61.151>;tag=8fbe5af9178677655bc3a5388c2a8b8c00149n2 Max-Forwards: 70 CSeq: 299694 OPTIONS Route: <sip:3.236.25.4:5060;lr> ``` ### Expected behavior Do not generate warnings about SIP messages that are allowed according to RFC. #### Actual observed behavior Generated warning when "Content-Length" header missing and used UDP protocol. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3210 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3210(a)github.com>

4 5

[kamailio/kamailio] [stirshaken] copy identity header and forward (Issue #3214)
by Artiom Baloian 23 Nov '23

23 Nov '23

### Description I am using STIR/SHAKEN as a third party service and wanted to know if there is a function to copy the Identity header from the 302 response into the original INVITE and then forward it. The Contact header from the 302 will make Kamailio server forward the INVITE to the SBC. Ideally having one function which does everything in one place would be a nice feature to have. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3214 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3214(a)github.com>

3 4

[kamailio/kamailio] path & RFC5626: flow-token is not added if +sip.instance and reg-id are missing (Issue #3190)
by space88man 23 Nov '23

23 Nov '23

### Description If the INVITE contains `;ob` but no `;+sip.instance=xxxx;reg-id=N` then a flow-token is not added to the record-route header. This is contrary to RFC5626. #### Reproduction Configure 2 x kamailio according to module outbound; i.e 1 x edge proxy and 1 x internal proxy/registrar. UA1 and UA2 have already REGISTER'ed with `;+sip.instance=...;reg-id=...`. ``` UA1, UA2 --- edge proxy --- internal proxy ``` Send INVITE from UA1 to UA2 with `;ob` but no other params: ``` Contact: <sip:user1250@192.168.12.45:5063;transport=TLS;ob> Record-Route: <sip:127.0.0.1;r2=on;lr> Record-Route: <sip:192.168.13.50:5061;transport=tls;r2=on;lr> ``` Observe that there is no flow-token added. Send INVITE from UA1 to UA2 with `;ob` with `;+sip.instance=...;reg-id=...`: ``` Contact: <sip:user1200@192.168.122.15;transport=tls;ob>;+sip.instance="<urn:uuid:0000 `0000-0000-0000-0000-0012341234>";reg-id=7 Record-Route: <sip:Jz0HaDIr1ZoqEAPAqA0yE8XAqAwqyAo=@127.0.0.1;r2=on;lr> Record-Route: <sip:Jz0HaDIr1ZoqEAPAqA0yE8XAqAwqyAo=@192.168.13.50:5061;transport=tls;r2=on;lr> ``` Observe that there is a flow-token added. #### Debugging Data #### SIP Traffic ### Possible Solutions ### Additional Information Version; kamailio 5.6.0 #### RFC5626 Section 9.5 https://datatracker.ietf.org/doc/html/rfc5626#section-9.5 INVITE must contain `ob;` but does not need to contain `;+sip.instance=...;reg-id=...` ``` INVITE sip:alice@a.example SIP/2.0 From: Bob <sip:bob@example.com>;tag=ldw22z To: Alice <sip:alice@a.example> Call-ID: 95KGsk2V/Eis9LcpBYy3 CSeq: 1 INVITE Route: <sip:ep1.example.com;lr> Contact: <sip:bob@192.0.2.2;transport=tcp;ob> ``` EP1 adds a Record-Route with a flow-token in message #43. ``` Record-Route: <sip:3yJEbr1GYZK9cPYk5Snocez6DzO7w+AX@ep1.example.com;lr> ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3190 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3190(a)github.com>

2 2

[kamailio/kamailio] dialog module does not update callee tag until 2xx received (Issue #3155)
by patrickarton 23 Nov '23

23 Nov '23

### Description dialog module does not update callee tag until it receives a 2xx response to an INVITE. and so we can not use is_know_dlg() function for in-dialog request like UPDATE when the session is still in early state.  ### 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` ``` kamailio 5.5.4 ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3155 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3155(a)github.com>

4 5

[kamailio/kamailio] RPC command app_jsdt.reload does not reload "require()" files (Issue #3145)
by Vincent Handfield 23 Nov '23

23 Nov '23

### Description If the file loaded with the modparam "load" uses CommonJS modules (Issue #3037-PR #3038), the modules are not reloaded when issuing the command app_jsdt.reload. Only the "main" file is reloaded. #### Reproduction 1 - Start Kamailio with those files as the initial configuration ```generic # kamailio.cfg ## Only the part concerning app_jsdt is included. ## The rest of the config file is ommited for the sake of clarity loadmodule "app_jsdt.so" modparam("app_jsdt", "load", "/etc/kamailio/js/index.js") modparam("app_jsdt", "mode", 1) cfgengine "jsdt" ``` ```js // index.js var myModule = require('./myModule'); function ksr_request_route() { myModule.myFunction() KSR.log("info", "KSR.log called from the index.js file"); } ``` ```js // myModule.js exports.myFunction = function() { KSR.log("info", "KSR.log called from the myModule.js file" } ``` 2 - Modify the myModule.js file ```js // myModule.js exports.myFunction = function() { KSR.log("info", "KSR.log called from the MODIFIED myModule.js file" } ``` 3 - Run the reload command ```console foo@bar:~# kamcmd app_jsdt.reload { old: 0 new: 1 } ``` > Log file > > INFO: app_jsdt [app_jsdt_api.c:1557]: app_jsdt_rpc_reload(): marking for reload js script file: /etc/kamailio/js/index.js (0 => 0) > DEBUG: app_jsdt [app_jsdt_api.c:534]: jsdt_kemi_reload_script(): reloading js script file: /etc/kamailio/js/index.js (0 => 1) 4 - The log file still show those lines: > Log file > >INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the myModule.js file >INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the index.js file 5 - Modify the index.js file ```js // index.js var myModule = require('./myModule'); function ksr_request_route() { myModule.myFunction() KSR.log("info", "KSR.log called from the MODIFIED index.js file"); } ``` 6 - Run the reload command ```console foo@bar:~# kamcmd app_jsdt.reload { old: 1 new: 2 } ``` > Log file > > INFO: app_jsdt [app_jsdt_api.c:1557]: app_jsdt_rpc_reload(): marking for reload js script file: /etc/kamailio/js/index.js (0 => 1) > DEBUG: app_jsdt [app_jsdt_api.c:534]: jsdt_kemi_reload_script(): reloading js script file: /etc/kamailio/js/index.js (1 => 2) 7 - The log file now show those lines: > Log file > > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the myModule.js file > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED index.js file 8 - Restart kamailio completly 9 - The log file now show those lines: > Log file > > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED myModule.js file > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED index.js file ### Possible Solutions Sorry, I would really like to provide one, but, as I'm a new Kamailio user, I don't know all the internals yet. ### Additional Information * **Kamailio Version** ```console foo@bar:~# kamailio -v version: kamailio 5.6.0 (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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 ``` * **Operating System**: ```console foo@bar:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye foo@bar:~# uname -a Linux localhost 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3145 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3145(a)github.com>

3 3

[kamailio/kamailio] usrloc OPTIONS not tracing with HEP (Issue #3136)
by Luke Escudé 23 Nov '23

23 Nov '23

### Description OPTIONS keepalives sent by usrloc are not being traced with HEP/Homer ### Troubleshooting #### Reproduction Module setup: modparam("siptrace", "duplicate_uri","sip:HOMERIP:9060"); modparam("siptrace", "hep_mode_on",1); modparam("siptrace", "trace_to_database",0); modparam("siptrace", "trace_flag",22); modparam("siptrace", "trace_on", 1); modparam("siptrace", "hep_version", 3); modparam("siptrace", "trace_mode", 1) I believe the above setup should duplicate ALL packets to homer, which is working just fine, except for usrloc-generated OPTIONS. The 200 OK from endpoints is showing up just fine, just not the initial request. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3136 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3136(a)github.com>

3 3

[kamailio/kamailio] Add file support to user blocklist for feeding caller numbers list (Issue #3132)
by soroshsabz 23 Nov '23

23 Nov '23

ITNOA ### Description I think for non-db deployment of Kamailio it is very useful to add support static data (like another configurations) for caller numbers list in user blocklist module. because if we do not have this feature we cannot use this module in non-db deployment of Kamailio. ### Expected behavior We have a configuration files (like dispatcher file) that contains below information in format of space separated list (like dispatcher file format) ``` +----+----------------+-------------+-----------+-----------+ | id | username | domain | prefix | whitelist | +----+----------------+-------------+-----------+-----------+ | 23 | 49721123456788 | | 1234 | 0 | | 22 | 49721123456788 | | 123456788 | 1 | | 21 | 49721123456789 | | 12345 | 0 | | 20 | 494675231 | | 499034133 | 1 | | 19 | 494675231 | test | 499034132 | 0 | | 18 | 494675453 | test.domain | 49901 | 0 | | 17 | 494675454 | | 49900 | 0 | +----+----------------+-------------+-----------+-----------+ ``` and user blocklist module read this file and load it, and apply this data for blocking call -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3132 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3132(a)github.com>

3 3

[kamailio/kamailio] kamailio 5.5 (commit 54c9df) SIGSEGV on atomic_get (Issue #3107)
by MayamaTakeshi 23 Nov '23

23 Nov '23

### Description Crash occurred during load test. #### Reproduction This cannot be reproduced at will. It happened after about 45 days of load testing. #### Debugging Data ``` [root@lab002207-flip-server ~]$ gdb /usr/local/src/git/kamailio-5.5/src/kamailio /core GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/src/git/kamailio-5.5/src/kamailio... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 189001] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/src/git/kamailio-5.5/src/kamailio -m 1024 -f /usr/local/etc/kamailio'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f909231e31e in atomic_get (v=0x7f96781153a0) at ../../core/mem/../atomic/atomic_common.h:66 66 return atomic_get_int(&(v->val)); (gdb) bt full #0 0x00007f909231e31e in atomic_get (v=0x7f96781153a0) at ../../core/mem/../atomic/atomic_common.h:66 No locals. #1 0x00007f909232b1a4 in dlg_ref_helper (dlg=0x7f905640bbe0, cnt=1, fname=0x7f9092368a61 "dlg_handlers.c", fline=1057) at dlg_hash.c:1074 mypid = 189001 d_entry = 0x7f9678115388 __func__ = "dlg_ref_helper" #2 0x00007f9092311fbf in dlg_set_tm_waitack (t=0x7f9053a98af8, dlg=0x7f905640bbe0) at dlg_handlers.c:1057 iuid = 0x7f905739a3c8 __func__ = "dlg_set_tm_waitack" #3 0x00007f909230c412 in dlg_onreply (t=0x7f9053a98af8, type=1048576, param=0x7ffeb3d73300) at dlg_handlers.c:578 dlg = 0x7f905640bbe0 iuid = 0x7f9055715ea0 new_state = 5 old_state = 2 unref = 1 event = 4 tag = {s = 0x80d000001ff <error: Cannot access memory at address 0x80d000001ff>, len = -1832753723} req = 0x7f90555eff70 rpl = 0xffffffffffffffff __func__ = "dlg_onreply" #4 0x00007f9092b5d399 in run_trans_callbacks_internal (cb_lst=0x7f9053a98b70, type=1048576, trans=0x7f9053a98af8, params=0x7ffeb3d73300) at t_hooks.c:258 cbp = 0x7f905362d490 backup_from = 0x555a7cfc3e90 <def_list+16> backup_to = 0x555a7cfc3e98 <def_list+24> backup_dom_from = 0x555a7cfc3ea0 <def_list+32> backup_dom_to = 0x555a7cfc3ea8 <def_list+40> backup_uri_from = 0x555a7cfc3e80 <def_list> backup_uri_to = 0x555a7cfc3e88 <def_list+8> backup_xavps = 0x555a7cfc3fd8 <_xavp_list_head> backup_xavus = 0x555a7cfc3fe0 <_xavu_list_head> backup_xavis = 0x555a7cfc3fe8 <_xavi_list_head> __func__ = "run_trans_callbacks_internal" #5 0x00007f9092b5d5b2 in run_trans_callbacks_with_buf (type=1048576, rbuf=0x7f9053a98bc8, req=0x7f90555eff70, repl=0xffffffffffffffff, flags=0) at t_hooks.c:303 params = {req = 0x7f90555eff70, rpl = 0xffffffffffffffff, param = 0x7f905362d4a0, code = 408, flags = 0, branch = 0, t_rbuf = 0x7f9053a98bc8, dst = 0x7f9053a98c18, send_buf = { s = 0x7f9054157d60 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 10.255.255.208:5015;rport=5015;branch=z9hG4bK-2093375-4498-18;received=192.168.2.253\r\nFrom: \"the.username.for.the.user.546\" <sip:the.username.for.the.user"..., len = 449}} trans = 0x7f9053a98af8 #6 0x00007f9092bd422d in relay_reply (t=0x7f9053a98af8, p_msg=0xffffffffffffffff, branch=0, msg_status=408, cancel_data=0x7ffeb3d73520, do_put_on_wait=0) at t_reply.c:2094 relay = 0 save_clone = 0 buf = 0x7f9092f17b68 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 10.255.255.208:5015;rport=5015;branch=z9hG4bK-2093375-4498-18;received=192.168.2.253\r\nFrom: \"the.username.for.the.user.546\" <sip:the.username.for.the.user"... res_len = 449 relayed_code = 408 relayed_msg = 0xffffffffffffffff reply_bak = 0x7ffeb3d734c0 bm = {to_tag_val = { s = 0x7f9092f17c88 "67946a7773289cd2c8623ce9ed050d66-614e90ad\r\nCall-ID: 4498-2093375(a)10.255.255.208\r\nCSeq: 802 INVITE\r\nServer: kamailio (5.5.4 (x86_64/linux))\r\nContent-Length: 0\r\n\r\n", len = 41}} totag_retr = 0 reply_status = RPS_COMPLETED uas_rb = 0x7f9053a98bc8 to_tag = 0x7f9092c3db30 <tm_tag> reason = {s = 0x555a7ce2b463 "Request Timeout", len = 15} --Type <RET> for more, q to quit, c to continue without paging--c onsend_params = {req = 0x28, rpl = 0x7f9052b1eac0, param = 0x157b82568, code = 1365092040, flags = 32656, branch = 0, t_rbuf = 0x7ffeb3d73450, dst = 0x0, send_buf = {s = 0x21d8 <error: Cannot access memory at address 0x21d8>, len = 1365092040}} ip = {af = 3017225408, len = 32766, u = {addrl = {140257839409728, 1}, addr32 = {1387391552, 32656, 1, 0}, addr16 = {59968, 21169, 32656, 0, 1, 0, 0, 0}, addr = "@\352\261R\220\177\000\000\001\000\000\000\000\000\000"}} __func__ = "relay_reply" #7 0x00007f9092b61ec0 in fake_reply (t=0x7f9053a98af8, branch=0, code=408) at timer.c:295 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 1403620088}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 1403620088}}}} do_cancel_branch = 1 reply_status = 189001 #8 0x00007f9092b6232e in final_response_handler (r_buf=0x7f9053a98d98, t=0x7f9053a98af8) at timer.c:462 silent = 0 branch_ret = 0 prev_branch = 0 now = 0 #9 0x00007f9092b623f2 in retr_buf_handler (ticks=2176292369, tl=0x7f9053a98db8, p=0x1f40) at timer.c:518 rbuf = 0x7f9053a98d98 fr_remainder = 0 retr_remainder = 32656 retr_interval = 1365093472 new_retr_interval_ms = 4294967296 crt_retr_interval_ms = 0 t = 0x7f9053a98af8 __func__ = "retr_buf_handler" #10 0x0000555a7ccb5a9f in timer_list_expire (t=2176292369, h=0x7f905161ed40, slow_l=0x7f905161fab8, slow_mark=5300) at core/timer.c:857 tl = 0x7f9053a98db8 ret = 0 #11 0x0000555a7ccb5fa9 in timer_handler () at core/timer.c:922 saved_ticks = 2176292369 run_slow_timer = 0 i = 180 __func__ = "timer_handler" #12 0x0000555a7ccb64ac in timer_main () at core/timer.c:961 No locals. #13 0x0000555a7c9fe6cf in main_loop () at main.c:1839 i = 12 pid = 0 si = 0x0 si_desc = "udp receiver child=11 sock=192.168.2.207:9060\000\270\000\200\070׳\376\177\000\000\000\000\000\000\000\000\000\000\220\070׳\376\177\000\000);]\221\220\177\000\000\b$Β\220\177\000\000]\201]\221\220\177", '\000' <repeats 14 times>, "\001\000\000\000\220\070׳\376\177\000\000\342\f\320|ZU\000" nrprocs = 12 woneinit = 1 __func__ = "main_loop" #14 0x0000555a7ca092ab in main (argc=8, argv=0x7ffeb3d73e78) at main.c:3053 cfg_stream = 0x555a7ea552d0 c = -1 r = 0 tmp = 0x7ffeb3d74d0a "" tmp_len = 0 port = 0 proto = 0 ahost = 0x0 aport = 0 options = 0x555a7ce150b8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 487513963 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0xc2 <error: Cannot access memory at address 0xc2> st = {st_dev = 22, st_ino = 2337, st_nlink = 2, st_mode = 16877, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1646805011, tv_nsec = 284331240}, st_mtim = {tv_sec = 1647223778, tv_nsec = 289750340}, st_ctim = {tv_sec = 1647223782, tv_nsec = 957818051}, __glibc_reserved = {0, 0, 0}} tbuf = "\020\377y\223\220\177\000\000\300\nG\223\001\000\000\000\377\377\377\377", '\000' <repeats 12 times>, "(\346z\223\220\177\000\000\350\231}\223\220\177\000\000\377\377\377\377", '\000' <repeats 12 times>, "@\305E\223\220\177\000\000\020\004z\223\220\177\000\000\350\244}\223\220\177\000\000\204\351z\223\220\177\000\000\060\344z\223\220\177\000\000Xbc\223\220\177\000\000h\231}\223\220\177\000\000`\220}\223\220\177\000\000\300>׳\376\177\000\000\200\241}\223\220\177\000\000\000\000\000\000\000\000\000\000#\326{\223\220\177\000\000\001", '\000' <repeats 23 times>, "(\346z\223\220\177\000\000\320<׳\376\177\000\000\003E"... option_index = 12 long_options = {{name = 0x555a7ce17516 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x555a7ce12514 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x555a7ce1751b "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x555a7ce17521 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x555a7ce17527 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x555a7ce17530 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x555a7ce1753a "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x555a7ce17544 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x555a7ce1754f "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x555a7ce17558 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x555a7ce17563 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x555a7ce17569 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x555a7ce17573 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) info locals No locals. (gdb) list 61 62 #define atomic_set(at_var, value) (atomic_set_int(&((at_var)->val), (value))) 63 64 inline static int atomic_get(atomic_t *v) 65 { 66 return atomic_get_int(&(v->val)); 67 } 68 69 /*@} */ 70 (gdb) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.4 (x86_64/linux) 54c9df 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: 54c9df compiled on 10:27:27 Mar 14 2022 with gcc 10.2.1 ``` * **Operating System**: ``` [root@lab002207-flip-server ~]$ lsb_release -a uNo LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye [root@lab002207-flip-server ~]$ uname -a Linux lab002207-flip-server 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3107 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3107(a)github.com>

2 2

[kamailio/kamailio] sdpops: signedness issue w/ sess-version in o= line (Issue #3099)
by Bastian Triller 23 Nov '23

23 Nov '23

I incremented sess-version w/ value `2147483648` via `$sdp(sess_version) = -1` as well as `$sdp(sess_version) = 2147483648`. sess-version in SDP should be 2147483649 but is `-1941279658`. ### Troubleshooting [RFC4566 5.2. Origin ("o=")](https://datatracker.ietf.org/doc/html/rfc4566#section-5.2) ``` <sess-version> is a version number for this session description. Its usage is up to the creating tool, so long as <sess-version> is increased when a modification is made to the session data. Again, it is RECOMMENDED that an NTP format timestamp is used. ``` [Wikipedia NTP Timestamps](https://en.wikipedia.org/wiki/Network_Time_Protocol#Timestamps) ``` The 64-bit binary fixed-point timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving a time scale that rolls over every 232 seconds (136 years) and a theoretical resolution of 2−32 seconds (233 picoseconds). NTP uses an epoch of January 1, 1900. Therefore, the first rollover occurs on February 7, 2036.[28][29] ``` #### Reproduction Receive SDP w/ sess-version greater equal 2^31 (2147483648) and increase version via `$sdp(sess-version) = -1` or setting a value greater than 2^31.  #### Log Messages  ``` May 02 06:43:20.578496 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} <core> [core/parser/sdp/sdp_helpr_funcs.c:622]: extract_sess_version(): oline(46): >o=user1 53655765 2147483648 IN IP4 127.0.0.1 < May 02 06:43:20.578501 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} <core> [core/parser/sdp/sdp_helpr_funcs.c:651]: extract_sess_version(): end 10: >2147483648< May 02 06:43:20.578508 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} <core> [core/parser/sdp/sdp_helpr_funcs.c:506]: extract_mediaip(): located IP address [127.0.0.1] in `o=' field May 02 06:43:20.578512 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} <core> [core/parser/sdp/sdp_helpr_funcs.c:506]: extract_mediaip(): located IP address [127.0.0.1] in `c=' field May 02 06:43:20.578532 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1918]: sdp_get_sess_version(): sdp_session_num 0 sess-version: 2147483648 May 02 06:43:20.578536 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1923]: sdp_get_sess_version(): sdp_session_num 1 May 02 06:43:20.578576 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1918]: sdp_get_sess_version(): sdp_session_num 0 sess-version: 2147483648 May 02 06:43:20.578581 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1923]: sdp_get_sess_version(): sdp_session_num 1 May 02 06:43:20.578695 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:2111]: pv_set_sdp(): res->flags: 24 May 02 06:43:20.578702 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:2112]: pv_set_sdp(): PV_TYPE_INT: 16 May 02 06:43:20.578705 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:2113]: pv_set_sdp(): PV_VAL_INT: 8 May 02 06:43:20.578708 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:2116]: pv_set_sdp(): param.pvn.u.isname.name.n = 1 May 02 06:43:20.578710 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:2125]: pv_set_sdp(): do $sdp(sess_version) = -1941279658 May 02 06:43:20.578713 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1918]: sdp_get_sess_version(): sdp_session_num 0 sess-version: 2147483648 May 02 06:43:20.578716 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1923]: sdp_get_sess_version(): sdp_session_num 1 May 02 06:43:20.578750 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1971]: sdp_set_sess_version(): old_sess_version_num: -2147483648 autoincrement: 0 May 02 06:43:20.578756 debian11 /usr/sbin/kamailio[121163]: DEBUG: {1 2 INVITE 1-121317(a)127.0.0.1} sdpops [sdpops_mod.c:1972]: sdp_set_sess_version(): *new_sess_version_num: -1941279658 autoincrement: 0 ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 ``` * **Operating System**:  ``` Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux debian11 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3099 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3099(a)github.com>

3 4

[kamailio/kamailio] CDP module fails to properly send DPA upon DPR (Issue #3092)
by Atanas Bakalov 23 Nov '23

23 Nov '23

### Description It seems there is a problem with the sending of the DPA from the cdp module to the diameter peer. When we receive the DPR the `Snd_DPA()` and `I_Disc()` are executed from peerstatemachine.c (I_Open/I_Rcv_DPR branch). Since the socket is closed from `I_Disc()` the `select()` in the `receive_loop` exits with a failure and the send pipe (which holds the DPA) is never sent to the other side. ### Troubleshooting #### Reproduction ``` 1. Send DPR from diameter peer to Kamailio 2. DPA is never received on the other end ``` #### Log Messages ``` Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [peerstatemachine.c:89]: sm_process(): sm_process(): Peer chordlet State I_Open Event I_Rcv_DPR Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 120) called from cdp: diameter_msg.c: AAANewMessage(192) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 120) returns address 0x7f54a1005888 frag. 0x7f54a1005850 (size=120) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) called from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) returns address 0x7f54d53ae668 frag. 0x7f54d53ae630 (size=56) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 41) called from cdp: diameter_avp.c: AAACreateAVP(157) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 48) returns address 0x7f54d68446e8 frag. 0x7f54d68446b0 (size=48) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) called from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) returns address 0x7f54d2c2e888 frag. 0x7f54d2c2e850 (size=56) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 29) called from cdp: diameter_avp.c: AAACreateAVP(157) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 32) returns address 0x7f54d4eef830 frag. 0x7f54d4eef7f8 (size=40) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [diameter_msg.c:82]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=112 Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 112) called from cdp: diameter_msg.c: AAABuildMsgBuffer(84) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 112) returns address 0x7f54d1242b00 frag. 0x7f54d1242ac8 (size=112) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [receiver.c:1013]: peer_send_msg(): peer_send_msg(): Pipe push [0x7f54a1005888] Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [diameter_msg.c:411]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7f54d75aeb50) 282 Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d52aff78), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d52aff40 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54c170eff0), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54c170efb8 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d31942a0), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d3194268 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d70d3508), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d70d34d0 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d5febb38), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d5febb00 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d1e24700), called from cdp: diameter_msg.c: AAAFreeMessage(421) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d1e246c8 alloc'ed from cdp: receiver.c: do_receive(580) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d75aeb50), called from cdp: diameter_msg.c: AAAFreeMessage(424) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d75aeb18 alloc'ed from cdp: diameter_msg.c: AAATranslateMessage(485) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) ERROR: cdp [receiver.c:688]: receive_loop(): select_recv(): Bad file descriptor Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) INFO: cdp [receiver.c:222]: disconnect_serviced_peer(): drop_serviced_peer(): [chordlet] Disconnecting from peer ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.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, 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_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 ``` * **Operating System**: ``` Linux 5.10.69-flatcar #1 SMP Wed Sep 29 20:48:40 -00 2021 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3092 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3092(a)github.com>

2 2

[kamailio/kamailio] http_async_client module crashing kamailio v5.5 on startup (Issue #2999)
by Joey Golan 23 Nov '23

23 Nov '23

### Description Hello, Loading http_async_client module causes kamailio to crash on startup with the following errors: 0(60541) INFO: http_async_client [async_http.c:85]: async_http_init_worker(): started worker process: 1 [warn] kevent: Bad file descriptor 16(60557) CRITICAL: <core> [core/pt.c:405]: fork_tcp_process(): called from a non "main" process 16(60557) ERROR: <core> [core/tcp_main.c:5121]: tcp_init_children(): fork failed: Bad file descriptor 0(60541) ALERT: <core> [main.c:786]: handle_sigs(): child process 60557 exited normally, status=255 0(60541) INFO: <core> [main.c:813]: handle_sigs(): terminating due to SIGCHLD 1(60542) INFO: <core> [main.c:868]: sig_usr(): signal 15 received 5(60546) INFO: <core> [main.c:868]: sig_usr(): signal 15 received Issue reproduced with kamailio sample configuration + loadmodule "http_async_client.so" ### Additional Information * **Kamailio Version** * ``` kamailio -v version: kamailio 5.5.3 (x86_64/darwin) b42dfd flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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, select, kqueue. id: b42dfd compiled on 22:25:21 Jan 6 2022 with gcc Apple clang version 13.0.0 (clang-1300.0.29.30) ``` * **Operating System**: ``` MacOS ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2999 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2999(a)github.com>

4 7

[kamailio/kamailio] WebSocket keepalive logging "forcibly closing connection" with TCP connection errors (Issue #2990)
by Max Wardell 23 Nov '23

23 Nov '23

### Description Similar to [issue #1886](https://github.com/kamailio/kamailio/issues/1886), we have Kamailio receiving WebRTC connections from clients and we see many errors related to connections being forcibly closed. We see two cases where this occurs, the former of which occurs much more often. ``` Dec 29 01:12:43.909934 tlx-dal-ecv2-staging kamailio_edge[14813]: WARNING: websocket [ws_frame.c:810]: ws_keepalive(): forcibly closing connection Dec 29 01:12:43.910179 tlx-dal-ecv2-staging kamailio_edge[14813]: ERROR: websocket [ws_conn.c:375]: wsconn_close_now(): getting TCP/TLS connection while trying to close. src_ip:src_port=x.x.x.x:49319, dst_port=443 ``` ``` Dec 29 00:53:28.110949 tlx-dal-ecv2-staging kamailio_edge[14817]: WARNING: websocket [ws_frame.c:227]: encode_and_send_ws_frame(): TCP/TLS connection get failed Dec 29 00:53:28.111187 tlx-dal-ecv2-staging kamailio_edge[14817]: ERROR: websocket [ws_frame.c:761]: ping_pong(): sending keepalive. src_ip:src_port=x.x.x.x:46712, dst_port=443 ``` ### Troubleshooting There seems to be a common occurrence where the WebSocket keepalive will not receive a pong and close the websocket connection. While closing, we see that the underlying TCP connection has already been closed. While that may be harmless, I am concerned there is a race condition that could lead to other problems. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.3.1 (x86_64/linux) d68f5c 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_BLACKLIST, 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: d68f5c compiled on 07:32:16 Dec 29 2021 with gcc 8.3.0 ``` * **Operating System**:  ``` > lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster > uname -a Linux tlx-dal-ecv2-staging 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2990 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2990(a)github.com>

6 13

[kamailio/kamailio] Kafka: Wrong format on RPC responses (Issue #2991)
by Olle E. Johansson 23 Nov '23

23 Nov '23

The kafka module use printf-like message to print statistics in rpc_kafka_stats() which doesn't follow the style for other RPC commands that produce data structures parsable as data, like when using jsonrpc. ``` if (rpc->rpl_printf(ctx, "Total messages: %" PRIu64 " Errors: %" PRIu64, msg_total, msg_error) < 0) { rpc->fault(ctx, 500, "Internal error showing total statistics"); return; } ``` I think this is a bug, but easy to fix. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2991 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2991(a)github.com>

2 2

[kamailio/kamailio] CNXCC doesn't update values on Redis DB (Issue #2948)
by Simone de Blasiis 23 Nov '23

23 Nov '23

### Description We are trying to use CNXCC in order to monitor credit usage but it doesn't appear to be working. The cnxcc_set_max_credit call appears to be working partially as we can see that a new key is created in the Redis DB but with all the values set to 0. The values that we set in the cnxcc_set_max_credit are hardcoded but it doesn't seem to work. This is an example of what we find in the Redis DB: ``` 1637599472.872820 [1 127.0.0.1:53578] "HEXISTS" "cnxcc:money:pippo@dom.domain.it" "concurrent_calls" 1637599472.872942 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873043 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "concurrent_calls" "0" 1637599472.873159 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873292 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "consumed_amount" "0.000000" 1637599472.873404 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873515 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "ended_calls_consumed_amount" "0.000000" 1637599472.873634 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873752 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "max_amount" "0.000000" 1637599472.873875 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874000 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "number_of_calls" "0" 1637599472.874115 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874269 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "type" "1" 1637599472.874381 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874481 [1 127.0.0.1:53578] "SREM" "cnxcc:kill_list:money" "\"pippo(a)dom.domain.it\"" 1637599472.874585 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874747 [1 127.0.0.1:53578] "HINCRBY" "cnxcc:money:pippo@dom.domain.it" "number_of_calls" "1" 1637599472.874845 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" ``` This issue is identical to the one described in #1387 ### Troubleshooting #### Reproduction We are running Kamailio 5.5 from the official repos on Debian 10. All the modules are installed through the repo. This is the config that we are currently using to set the values for the modules. We also tried setting the values straight into the function bypassing the variables but the result is the same. ``` $dlg_var(credit) = "50.0"; $var(connect_cost) = "5.0"; $var(cost_per_sec) = "1.0"; $var(i_pulse) = 1; $var(f_pulse) = 1; xlog("$dlg_var(label) $var(credit) $var(connect_cost) "); if (cnxcc_set_max_credit("$dlg_var(label)", "$dlg_var(credit)", "$var(connect_cost)", "$var(cost_per_sec)", "$var(i_pulse) ", "$var(f_pulse)") < 0) { xlog("Failed to setup credit control"); sl_send_reply("503", "Internal Server Error"); exit; } ``` #### Log Messages The call to cnxcc_set_max_credit() doesn't throw any errors and returns 1 as if everything worked correctly ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.2 (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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 8.3.0 ``` * **Operating System**: ``` No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster Linux kamailio 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64 GNU/Linux ``` -- 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/2948

4 5

[kamailio/kamailio] kazoo_query causes crash of kamailio (Issue #2922)
by mihovilkolaric 23 Nov '23

23 Nov '23

### Description Found following issue when trying to solve #2895 :  function kazoo_query (as shown in the module's documentation) causes kamailio to crash. ### Troubleshooting #### Reproduction Compile kamailio master-branch from scratch (with module "kazoo" enabled). Modify kamailio-config with minimal settings required to use function "kazoo_query": ``` diff /usr/local/etc/kamailio/kamailio.cfg.sample /usr/local/etc/kamailio/kamailio.cfg 496a497,501 > loadmodule "kazoo.so" > modparam("kazoo", "amqp_connection", "amqp://guest:guest@rabbitmqhost:5672") > modparam("kazoo", "node_hostname", "sipproxy.mydomain.com") > modparam("kazoo", "pua_mode", 0) > 517a523,533 > xlog("SCRIPT: Snipppet from kazoo_query-documentation:\n"); > $var(amqp_payload_request) = "{'Event-Category' : 'call_event' , 'Event-Name' : 'query_user_channels_req', 'Realm' : '" + $fd + "', 'Username' : '" + $fU + "', 'Active-Only' : false }"; > kazoo_encode("$ci", "$var(callid_encoded)"); > $var(amqp_routing_key) = "call.status_req.$var(callid_encoded)"; > if(kazoo_query("callevt", $var(amqp_routing_key), $var(amqp_payload_request), "$var(amqp_result)")) { > kazoo_json("$var(amqp_result)", "Channels[0].switch_url", "$du"); > if($du != $null) { > xlog("L_INFO", "$ci|log|user channels found redirecting call to $du"); > return; > } > } ``` Start kamailio and register. Kamailio crashes when reaching kazoo_query: ``` Nov 6 16:19:37 hostname kamailio: INFO: <core> [core/tcp_main.c:4997]: init_tcp(): using epoll_lt as the io watch method (auto detected) Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [main.c:3035]: main(): processes (at least): 52 - shm size: 67108864 - pkg size: 8388608 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352200]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/352200 Nov 6 16:19:37 hostname src/kamailio[352202]: INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Nov 6 16:19:37 hostname src/kamailio[352203]: ERROR: kazoo [kz_amqp.c:2387]: kz_amqp_consumer_event_cfg(): kazoo:consumer-event not found Nov 6 16:19:42 hostname src/kamailio[352203]: ERROR: kazoo [kz_amqp.c:2387]: kz_amqp_consumer_event_cfg(): kazoo:consumer-event not found Nov 6 16:19:49 hostname src/kamailio[352213]: ERROR: {1 1 REGISTER OUfeIVS08Xrbmw8Nr-udtg..} <script>: SCRIPT: Snipppet from kazoo_query-documentation: Nov 6 16:19:49 hostname src/kamailio[352221]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 72 Nov 6 16:19:49 hostname src/kamailio[352171]: ALERT: <core> [main.c:774]: handle_sigs(): child process 352213 exited by a signal 6 Nov 6 16:19:49 hostname src/kamailio[352171]: ALERT: <core> [main.c:777]: handle_sigs(): core was generated Nov 6 16:19:49 hostname src/kamailio[352171]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Nov 6 16:19:49 hostname src/kamailio[352220]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352218]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352209]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352219]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352201]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352187]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352207]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352205]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352202]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352199]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352195]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352210]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352193]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352196]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352183]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352191]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352176]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352203]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352189]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352192]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352175]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352208]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352185]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352182]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352216]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352190]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352206]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352194]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352177]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352215]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352186]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352173]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352204]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352184]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352188]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352217]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352214]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352180]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352198]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352172]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352221]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352174]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352197]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352200]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352211]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352212]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352181]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352179]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352178]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352171]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ``` #### Debugging Data  backtrace with gdb shows: ``` (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007fc47407a859 in __GI_abort () at abort.c:79 #2 0x00007fc47407a729 in __assert_fail_base (fmt=0x7fc474210588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fc46f0fe2d0 "json_object_get_type(jso) == json_type_object", file=0x7fc46f0fe044 "json_object.c", line=476, function=<optimized out>) at assert.c:92 #3 0x00007fc47408bf36 in __GI___assert_fail (assertion=0x7fc46f0fe2d0 "json_object_get_type(jso) == json_type_object", file=0x7fc46f0fe044 "json_object.c", line=476, function=0x7fc46f0fe280 "json_object_object_add_ex") at assert.c:101 #4 0x00007fc46f0f7d26 in json_object_object_add_ex () from /lib/x86_64-linux-gnu/libjson-c.so.4 #5 0x00007fc46f14ebe4 in kz_amqp_add_payload_common_properties (json_obj=0x559b3c3b30c0, server_id=0x7ffda57606f0 "kamailio(a)sipproxy.mydomain.com-<352213>-script-0", unique=0x7ffda5760660) at kz_amqp.c:1023 #6 0x00007fc46f1509a0 in kz_amqp_pipe_send_receive (str_exchange=0x7ffda57609c0, str_routing_key=0x7ffda57609d0, str_payload=0x7ffda57609b0, kz_timeout=0x7ffda57609e0, json_ret=0x7ffda5760a10) at kz_amqp.c:1159 #7 0x00007fc46f158763 in kz_amqp_query_ex (msg=0x7fc47394beb8, exchange=0x7fc4738f03d0 "(q\216s\304\177", routing_key=0x7fc4738f57c8 "0\213\207s\304\177", payload=0x7fc4738f58d8 "hX\217s\304\177") at kz_amqp.c:1494 #8 0x00007fc46f1588b2 in kz_amqp_query (msg=0x7fc47394beb8, exchange=0x7fc4738f03d0 "(q\216s\304\177", routing_key=0x7fc4738f57c8 "0\213\207s\304\177", payload=0x7fc4738f58d8 "hX\217s\304\177", dst=0x7fc4738f04f0 "p\004\217s\304\177") at kz_amqp.c:1517 #9 0x0000559b3b1c7355 in do_action (h=0x7ffda5761370, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1151 #10 0x0000559b3b1d0463 in run_actions (h=0x7ffda5761370, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1581 #11 0x0000559b3b1d0bd6 in run_actions_safe (h=0x7ffda5761f70, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1645 #12 0x0000559b3b16a4b0 in rval_get_int (h=0x7ffda5761f70, msg=0x7fc47394beb8, i=0x7ffda5761750, rv=0x7fc4738f4040, cache=0x0) at core/rvalue.c:949 #13 0x0000559b3b16fa9c in rval_expr_eval_int (h=0x7ffda5761f70, msg=0x7fc47394beb8, res=0x7ffda5761750, rve=0x7fc4738f4038) at core/rvalue.c:1947 #14 0x0000559b3b1c0ec8 in do_action (h=0x7ffda5761f70, a=0x7fc4738f7f28, msg=0x7fc47394beb8) at core/action.c:1052 #15 0x0000559b3b1d0463 in run_actions (h=0x7ffda5761f70, a=0x7fc4738e8ca8, msg=0x7fc47394beb8) at core/action.c:1581 #16 0x0000559b3b1d0ce6 in run_top_route (a=0x7fc4738e8ca8, msg=0x7fc47394beb8, c=0x0) at core/action.c:1666 #17 0x0000559b3b37f932 in receive_msg ( buf=0x559b3c3a0960 "REGISTER sip:10.0.0.24:5060;transport=TCP SIP/2.0\r\nVia: SIP/2.0/TCP 10.0.0.33:47335;branch=z9hG4bK-524287-1---83d016a408b857dd;rport\r\nMax-Forwards: 69\r\nContact: <sip:1234@10.0.0.33:47335;rinstance=837"..., len=578, rcv_info=0x7fc46f4c01a8) at core/receive.c:513 #18 0x0000559b3b41dfb3 in receive_tcp_msg ( tcpbuf=0x7fc46f4c0530 "REGISTER sip:10.0.0.24:5060;transport=TCP SIP/2.0\r\nVia: SIP/2.0/TCP 10.0.0.33:47335;branch=z9hG4bK-524287-1---83d016a408b857dd;rport\r\nMax-Forwards: 70\r\nContact: <sip:1234@10.0.0.33:47335;rinstance=837"..., len=578, rcv_info=0x7fc46f4c01a8, con=0x7fc46f4c0190) at core/tcp_read.c:1424 #19 0x0000559b3b4205f8 in tcp_read_req (con=0x7fc46f4c0190, bytes_read=0x7ffda5762618, read_flags=0x7ffda576261c) at core/tcp_read.c:1607 #20 0x0000559b3b423af5 in handle_io (fm=0x7fc473954a08, events=1, idx=-1) at core/tcp_read.c:1782 #21 0x0000559b3b40eccc in io_wait_loop_epoll (h=0x559b3b6f62e0 <io_w>, t=2, repeat=0) at core/io_wait.h:1070 #22 0x0000559b3b426aa8 in tcp_receive_loop (unix_sock=75) at core/tcp_read.c:1978 #23 0x0000559b3b2a161e in tcp_init_children (woneinit=0x7ffda5762a00) at core/tcp_main.c:5153 #24 0x0000559b3b153f0b in main_loop () at main.c:1843 #25 0x0000559b3b15e745 in main (argc=1, argv=0x7ffda57630e8) at main.c:3058 ``` #### Log Messages  #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions This somehow pointed me to the payload - so I tried to change the AMQP-payload in the config to a minimalistic custom JSON document. With this config, the crash does no longer occur: ``` diff /usr/local/etc/kamailio/kamailio.cfg /usr/local/etc/kamailio/kamailio.cfg.sample 497,501d496 < loadmodule "kazoo.so" < modparam("kazoo", "amqp_connection", "amqp://guest:guest@guest@rabbitmqhost:5672") < modparam("kazoo", "node_hostname", "sipproxy.mydomain.com") < modparam("kazoo", "pua_mode", 0) < 523,533d517 < xlog("SCRIPT: Snipppet from kazoo_query-documentation:\n"); < #$var(amqp_payload_request) = "{'Event-Category' : 'call_event' , 'Event-Name' : 'query_user_channels_req', 'Realm' : '" + $fd + "', 'Username' : '" + $fU + "', 'Active-Only' : false }"; < kazoo_encode("$ci", "$var(callid_encoded)"); < $var(amqp_routing_key) = "call.status_req.$var(callid_encoded)"; < if(kazoo_query("callevt", $var(amqp_routing_key), "{\"blop\":\"example\"}", "$var(amqp_result)")) { < kazoo_json("$var(amqp_result)", "Channels[0].switch_url", "$du"); < if($du != $null) { < xlog("L_INFO", "$ci|log|user channels found redirecting call to $du"); < return; < } < } ``` So, some issue in the exmaple's payload causes the crash. One the one hand, I think an example from the documentation should somehow work, on the other hand I think that an error in a JSON-payload is not indended to crash kamailio anyway.  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` kamailio -v version: kamailio 5.6.0-dev2 (x86_64/linux) 63a349 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: 63a349 compiled on 16:12:36 Nov 6 2021 with gcc 9.3.0 ``` * **Operating System**:  ``` uname -a Linux hostname 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal ``` -- 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/2922

3 4

[kamailio/kamailio] ims_usrloc_pcscf can not fetch protocol field from mysql DB (#2871)
by Erhan Onur Sendag 23 Nov '23

23 Nov '23

### Description Kamailio's ims_usrloc_pcscf module fetches all contact informations from location table at startup. I noticed that it fails to fetch protocol information. I checked the function which reads the contact row: https://github.com/kamailio/kamailio/blob/c3629f877500373028d2c7cdefd976cdd… I saw that it is read the value as INT. Then checked database table and saw that protocol field is CHAR(5). https://github.com/kamailio/kamailio/blob/master/utils/kamctl/mysql/ims_usr… ``` CREATE TABLE `location` ( ... `protocol` char(5) DEFAULT NULL, ... ); ``` The protocol fields needs to be INT in location table as well. This bug leads to other bugs because protocol information is used in aor_hash calculation. Best regards Erhan Sendag ### Troubleshooting #### Reproduction Put a record in location table with protocol value as 1. Set ims_usrloc_pcscf module parameter db_mode as 1. After kamailio startup, on debug log, protocol information will be seen as a big integer value. #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  The protocol fields can be defined as INT in location table. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- 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/2871

3 5

[kamailio/kamailio] Recrod-Route header without socket port for calls to WebRTC clients (#2850)
by sergey-safarov 23 Nov '23

23 Nov '23

### Description When call routed to WebRTC client and used `record_route()`, then Record-Router header does not contain port of socket where WebRTC client connected. When used `tcp_reuse_port = yes`, then `ACK` cannot be delivered to WebRTC client (#2849). #### Reproduction I prepared a minimal config that allows reproduce the issue and attached a log file for the test call. ``` # use compact IPv6 addresses ipv6_hex_style = "c" enable_tls=1 tcp_accept_no_cl=yes ######## Kamailio control connector module ######## loadmodule "ctl.so" modparam("ctl", "binrpc_buffer_size", 4096) loadmodule "pv.so" loadmodule "sl.so" loadmodule "xlog.so" loadmodule "tls.so" loadmodule "nathelper.so" modparam("tls", "config", "/etc/kamailio/tls.cfg") loadmodule "xhttp.so" loadmodule "websocket.so" loadmodule "ipops.so" loadmodule "siputils.so" loadmodule "rr.so" loadmodule "debugger.so" modparam("debugger", "cfgtrace", 1) modparam("debugger", "log_level_name", "exec") log_stderror=yes # IPv4 listeners listen=udp:eth0:5060 listen=tcp:eth0:5060 listen=tls:eth0:5061 listen=tls:eth0:7001 # IPv6 listeners listen=udp:[2600:1f18:578:5701::7e]:5060 listen=tcp:[2600:1f18:578:5701::7e]:5060 listen=tls:[2600:1f18:578:5701::7e]:5061 listen=tls:[2600:1f18:578:5701::7e]:7001 request_route { if (!has_totag()) { record_route(); } if (is_ipv4($si)) { route(WEBRTC_PBX); } else { route(PBX_WEBRTC); } } route[WEBRTC_PBX] { set_contact_alias(); $du = "sip:[2600:1f14:6d8:5409::100]:5080;transport=tcp"; forward(); exit; } route[PBX_WEBRTC] { handle_ruri_alias(); forward(); exit; } event_route[xhttp:request] { if (!($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm=~"GET")) { $var(status_code) = 400; $var(reason_phrase) = "Bad Request"; xhttp_reply("$var(status_code)", "$var(reason_phrase)", "text/plain", "$var(reason_phrase)"); exit; } if (!ws_handle_handshake()) { $var(status_code) = 400; $var(reason_phrase) = "Bad Request"; xhttp_reply("$var(status_code)", "$var(reason_phrase)", "text/plain", "$var(reason_phrase)"); exit; } exit; } ``` #### Log Messages For Call-ID: a8c7450a-131c-11ec-9546-a727fc4b684e ``` INVITE sips:safarov@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss SIP/2.0^M Record-Route: <sips:3.236.25.254;transport=ws;r2=on;lr;ftag=FNBFNvy0atDeK>^M Record-Route: <sips:[2600:1f18:578:5701::7e];transport=tcp;r2=on;lr;ftag=FNBFNvy0atDeK>^ ``` Client connected to socket `tls:3.236.25.254:7001` but using `record_route()` generated ``` Record-Route: <sips:3.236.25.254;transport=ws;r2=on;lr;ftag=FNBFNvy0atDeK> ``` Full logs at [kam.log](https://github.com/kamailio/kamailio/files/7148185/kam.log) ### Additional Information * **Kamailio Version** - output of `kamailio -v` used master branch with small customization, base commit c503d2bd31a580138a67f1d4a265ccde5791d271 * **Operating System**: aarch64 ``` [root@tmp kamailio]# cat /etc/os-release NAME="CentOS Linux" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Linux 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-8" CENTOS_MANTISBT_PROJECT_VERSION="8" ``` -- 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/2850

5 7

[kamailio/kamailio] Kamailio crashes after the call (Issue #2970)
by Eugeniy 23 Nov '23

23 Nov '23

### Description Hi, I am a junior with Kamailio, if I show you where I am wrong, I will. Often during a call between two sip clients (located on the same subnet with pcscf) Kamailio P-CSCF crashes with a core dump. But sometimes the call goes through normally, I can’t see why this is happening.  ### Troubleshooting #### Reproduction It is reproduced often, the error is most likely somewhere with me.  #### Debugging Data  ``` GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git Copyright (C) 2021 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 "i686-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... (No debugging symbols found in /usr/sbin/kamailio) warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 14196] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-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 0xb6f1eab9 in ?? () from /usr/lib/i386-linux-gnu/kamailio/modules/ims_ipsec_pcscf.so (gdb) bt full #0 0xb6f1eab9 in ?? () from /usr/lib/i386-linux-gnu/kamailio/modules/ims_ipsec_pcscf.so No symbol table info available. #1 0xb6f25b1e in ipsec_forward () from /usr/lib/i386-linux-gnu/kamailio/modules/ims_ipsec_pcscf.so No symbol table info available. #2 0xb6f2901a in ?? () from /usr/lib/i386-linux-gnu/kamailio/modules/ims_ipsec_pcscf.so No symbol table info available. #3 0x004bc49d in do_action () No symbol table info available. #4 0x004bae10 in run_actions () No symbol table info available. #5 0x004ca3a0 in run_top_route () No symbol table info available. #6 0xb73c1695 in reply_received () from /usr/lib/i386-linux-gnu/kamailio/modules/tm.so No symbol table info available. #7 0x0052fa14 in ?? () No symbol table info available. #8 0x005b9170 in receive_msg () No symbol table info available. #9 0x006bb830 in udp_rcv_loop () No symbol table info available. #10 0x004b74e8 in main_loop () No symbol table info available. #11 0x004ab0f1 in main () No symbol table info available. ``` #### Log Messages  ``` Dec 10 15:33:07 pcscf /usr/sbin/kamailio[14194]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:33:07 pcscf /usr/sbin/kamailio[14194]: ERROR: rtpengine [rtpengine.c:3236]: set_rtpengine_set_from_avp(): could not locate engine set 2 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14204]: ERROR: <script>: INVITE (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55149) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14204]: ERROR: ims_ipsec_pcscf [cmd.c:806]: ipsec_forward(): Contact doesn't exist Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14204]: ERROR: ims_ipsec_pcscf [cmd.c:806]: ipsec_forward(): Contact doesn't exist Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14193]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14195]: ERROR: <script>: INVITE (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14195]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14195]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14195]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14195]: ERROR: rtpengine [rtpengine.c:3236]: set_rtpengine_set_from_avp(): could not locate engine set 2 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14205]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14205]: ERROR: rtpengine [rtpengine.c:3236]: set_rtpengine_set_from_avp(): could not locate engine set 2 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14210]: ERROR: ims_ipsec_pcscf [cmd.c:252]: fill_contact(): Reply No contact headers Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14210]: ERROR: ims_ipsec_pcscf [cmd.c:799]: ipsec_forward(): Error filling in contact data Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14201]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14201]: ERROR: rtpengine [rtpengine.c:3236]: set_rtpengine_set_from_avp(): could not locate engine set 2 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14274]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14191]: ALERT: <core> [main.c:782]: handle_sigs(): child process 14196 exited by a signal 11 Dec 10 15:35:14 pcscf /usr/sbin/kamailio[14191]: ALERT: <core> [main.c:785]: handle_sigs(): core was generated Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14324]: WARNING: <core> [core/daemonize.c:596]: mem_lock_pages(): failed to lock the memory pages (disable swap): Cannot allocate memory [12] Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14324]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14324]: WARNING: tm [tm.c:521]: fixup_routes(): t_on_failure("NATMANAGE"): empty/non existing route Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14324]: ERROR: <script>: event_route[htable:mod-init] { Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14324]: ERROR: ims_ipsec_pcscf [cmd.c:950]: ipsec_destroy(): Contact doesn't exist Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14400]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14406]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14403]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14405]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14401]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14404]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14402]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14399]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14396]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14334]: ERROR: <script>: PRACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55149) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14334]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14334]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14337]: ERROR: <script>: PRACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14337]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14337]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14329]: ERROR: <script>: PRACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55149) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14329]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14329]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14341]: ERROR: <script>: PRACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14341]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:15 pcscf /usr/sbin/kamailio[14341]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14328]: ERROR: <script>: ACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55149) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14328]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14328]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14326]: ERROR: <script>: ACK (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14326]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:17 pcscf /usr/sbin/kamailio[14326]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14327]: ERROR: <script>: BYE (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55149) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14327]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14327]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14325]: ERROR: <script>: BYE (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, dca98f98-8bb9-c01d-ff0c-e55794e9bcaa) Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14325]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14325]: ERROR: ims_ipsec_pcscf [cmd.c:816]: ipsec_forward(): No security parameters found in contact Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14325]: ERROR: rtpengine [rtpengine.c:2957]: select_rtpp_set(): script error-invalid id_set to be selected Dec 10 15:35:26 pcscf /usr/sbin/kamailio[14325]: ERROR: rtpengine [rtpengine.c:3236]: set_rtpengine_set_from_avp(): could not locate engine set 2 Dec 10 15:35:30 pcscf /usr/sbin/kamailio[14396]: ERROR: <script>: Preloading NAT-PING. Rows: 921 Dec 10 15:35:30 pcscf /usr/sbin/kamailio[14396]: ERROR: <script>: OPTIONS to sip:alice@192.168.56.107:57838;transport=udp via sip:192.168.56.107:57838... ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` [pcscf_dump.zip](https://github.com/kamailio/kamailio/files/7692913/pcscf_du… ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.4 (i386/linux) 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_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 ``` * **Operating System**:  ``` Linux pcscf.ims.mnc001.mcc001.3gppnetwork.org 5.10.0-9-686-pae #1 SMP Debian 5.10.70-1 (2021-09-30) i686 GNU/Linux ``` [kamailio_cfg.zip](https://github.com/kamailio/kamailio/files/7692905/kamail… [kamailio_log.zip](https://github.com/kamailio/kamailio/files/7692934/kamail… -- 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/2970

6 21

[kamailio/kamailio] ims_usrloc_pcscf module loads registration records from the db twice (#2809)
by ErhanOnur 23 Nov '23

23 Nov '23

### Description ims_registrar_pcscf module create a process with rank 1 (PROC_SIPINIT) if reginfo flag is open.. This is wrong because it is written that PROC_SIPINIT rank should be given only to the first worker process. ``` #define PROC_SIPINIT 1 /**< First (special) SIP worker - some modules do special processing in this child, like loading db data */ ``` This leads to a problem. ims_usrloc_pcscf loads registration records from the db twice. The codes are demonstrated below. Similar old issue exists here for another module: https://github.com/kamailio/kamailio/issues/975 ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  Here are fork operations and their ranks: ``` [root@n5gc-ims-dev src]# cat /usr/src/erhan5.log | grep init_mod_child | grep ims_usrloc_pcscf 0(10662) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 0 rank -127: ims_usrloc_pcscf [main] 1(10671) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 1 rank 1: ims_usrloc_pcscf [udp receiver child=0 sock=10.10.12.101:5060 (172.30.65.101:5060)] 3(10673) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 3 rank 3: ims_usrloc_pcscf [udp receiver child=2 sock=10.10.12.101:5060 (172.30.65.101:5060)] 2(10672) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 2 rank 2: ims_usrloc_pcscf [udp receiver child=1 sock=10.10.12.101:5060 (172.30.65.101:5060)] 5(10675) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 5 rank -1: ims_usrloc_pcscf [slow timer] 0(10662) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 0 rank 0: ims_usrloc_pcscf [main] 6(10679) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 6 rank -1: ims_usrloc_pcscf [timer] 4(10674) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 4 rank 4: ims_usrloc_pcscf [udp receiver child=3 sock=10.10.12.101:5060 (172.30.65.101:5060)] 7(10680) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 7 rank -1: ims_usrloc_pcscf [secondary timer] 8(10686) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 8 rank 1: ims_usrloc_pcscf [RegInfo Event Processor] 9(10687) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 9 rank -1: ims_usrloc_pcscf [Dialog Clean Timer] 10(10688) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 10 rank -2: ims_usrloc_pcscf [ctl handler] 11(10689) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 11 rank 5: ims_usrloc_pcscf [tcp receiver (generic) child=0] 12(10694) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 12 rank 6: ims_usrloc_pcscf [tcp receiver (generic) child=1] 13(10695) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 13 rank 7: ims_usrloc_pcscf [tcp receiver (generic) child=2] 14(10697) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 14 rank 8: ims_usrloc_pcscf [tcp receiver (generic) child=3] 15(10699) DEBUG: <core> [core/sr_module.c:845]: init_mod_child(): idx 15 rank -4: ims_usrloc_pcscf [tcp main process] ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  In following code ims_registrar_pcscf module create a process with rank 1 (PROC_SIPINIT) : fork_process(PROC_SIPINIT, "RegInfo Event Processor", 1); ``` static int child_init(int rank) { LM_DBG("Initialization of module in child [%d] \n", rank); if ((subscribe_to_reginfo == 1) && (rank == PROC_MAIN)) { LM_DBG("Creating RegInfo Event Processor process\n"); int pid = fork_process(PROC_SIPINIT, "RegInfo Event Processor", 1); if (pid < 0) return -1; //error if (pid == 0) { if (cfg_child_init()) return -1; //error reginfo_event_process(); } } if (rank == PROC_MAIN || rank == PROC_TCP_MAIN) return 0; if (rank == 1) { /* init stats */ //TODO if parameters are modified via cfg framework do i change them? //update_stat( max_expires_stat, default_registrar_cfg.max_expires ); update_stat( max_contacts_stat, default_registrar_cfg.max_contacts ); update_stat( default_expire_stat, default_registrar_cfg.default_expires ); } /* don't do anything for main process and TCP manager process */ if (rank == PROC_MAIN || rank == PROC_TCP_MAIN) return 0; return 0; } ``` Here is how ims_usrloc_pcscf loads records from db at its child init callback function: ``` if (_rank==PROC_SIPINIT && db_mode!=DB_ONLY) { // if cache is used, populate domains from DB for( ptr=root ; ptr ; ptr=ptr->next) { LM_DBG("Preloading domain %.*s\n", ptr->name.len, ptr->name.s); if (preload_udomain(ul_dbh, ptr->d) < 0) { LM_ERR("child(%d): failed to preload domain '%.*s'\n", _rank, ptr->name.len, ZSW(ptr->name.s)); return -1; } } } ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` it exists at latest version on master branch. [here](https://github.com/kamailio/kamailio/blob/master/src/modules/ims_regi… ``` * **Operating System**:  ``` CentOS 7.1 ``` -- 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/2809

4 7

[kamailio/kamailio] [stirshaken] RCD (Rich Call Data) support in STIR/SHAKEN module (#2780)
by sergei lavrov 23 Nov '23

23 Nov '23

### Description It would be nice to have RCD (Rich Call Data) support in STIR/SHAKEN module. -- 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/2780

3 7

[kamailio/kamailio] kamailio mariadb error lock table active_watcher (#2805)
by ReznikovAlexei 23 Nov '23

23 Nov '23

### Description I am using Kamailio with Mariadb module And i am get in Kamailio log some error messages: ``` "ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Table 'active_watchers' was not locked with LOCK TABLES (1100)" "ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Table 'active_watchers' was not locked with LOCK TABLES (1100)" "ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Table 'active_watchers' was not locked with LOCK TABLES (1100)" ``` After start debug log queries in Mariadb, i see queries in logfile like this: ``` 1141 Query SET autocommit=0 1141 Query LOCK TABLES presentity WRITE 1141 Query update `presentity` set `etag`='a.1620236063.17716.2514.101',`expires`=1625215189,`received_time`=1625214589,`priority`=205144189,`body`='<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<presence xmlns:dm=\"urn:ietf:params:xml:ns:pidf:data-model\" xmlns:rpid=\"urn:ietf:params:xml:ns:pidf:rpid\" xmlns:pidfonline=\"http://www.linphone.org/xsds/pidfonline.xsd\" entity=\"sip:name_user@office-dev.com\" xmlns=\"urn:ietf:params:xml:ns:pidf\">\n <tuple id=\"bephbl\">\n <status>\n <basic>open</basic>\n <pidfonline:online/>\n </status>\n <contact priority=\"0.8\">sip:name_user@office-dev.com</contact>\n <timestamp>2021-07-01T17:20:41Z</timestamp>\n </tuple>\n</presence>\n' where `domain`='office-dev.com' AND `username`='name_user' AND `event`='presence' AND `etag`='a.1620236063.17716.2513.100' 1141 Query select `to_user`,`to_domain`,`from_user`,`from_domain`,`watcher_username`,`watcher_domain`,`event_id`,`from_tag`,`to_tag`,`callid`,`local_cseq`,`record_route`,`contact`,`expires`,`reason`,`socket_info`,`local_contact`,`version`,`flags`,`user_agent` from `active_watchers` where `presentity_uri`='sip:name_user@office-dev.com' AND `event`='presence' AND `status`=1 AND `contact`<>'' 1141 Query COMMIT 1141 Query SET autocommit=1 1141 Query UNLOCK TABLES ``` or this one ``` 1141 Query LOCK TABLES presentity WRITE 1141 Query insert into `presentity` (`domain`,`username`,`event`,`etag`,`sender`,`body`,`received_time`,`priority`,`expires` ) values ('dev.com','+121342','presence','a.1620236063.17716.2532.0','','<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<presence xmlns:dm=\"urn:ietf:params:xml:ns:pidf:data-model\" xmlns:rpid=\"urn:ietf:params:xml:ns:pidf:rpid\" xmlns:pidfonline=\"http://www.linphone.org/xsds/pidfonline.xsd\" entity=\"sip:+121342@dev.com\" xmlns=\"urn:ietf:params:xml:ns:pidf\">\n <tuple id=\"wumhh7\">\n <status>\n <basic>open</basic>\n <pidfonline:online/>\n </status>\n <contact priority=\"0.8\">sip:+121342@dev.com</contact>\n <timestamp>2021-07-02T10:55:26Z</timestamp>\n </tuple>\n</presence>\n',1625223329,205152929,1625226929) 1141 Query select `to_user`,`to_domain`,`from_user`,`from_domain`,`watcher_username`,`watcher_domain`,`event_id`,`from_tag`,`to_tag`,`callid`,`local_cseq`,`record_route`,`contact`,`expires`,`reason`,`socket_info`,`local_contact`,`version`,`flags`,`user_agent` from `active_watchers` where `presentity_uri`='sip:+121342@dev.com' AND `event`='presence' AND `status`=1 AND `contact`<>'' 1141 Query COMMIT 1141 Query SET autocommit=1 1141 Query UNLOCK TABLES ``` This queries matches for time with reproduced errors in above kamailio log. #### Reproduction In test lab ``` MariaDB [kamailio]> LOCK TABLES presentity WRITE; Query OK, 0 rows affected (0.00 sec) MariaDB [kamailio]> select * from presentity; Empty set (0.00 sec) MariaDB [kamailio]> select * from active_watcher; ERROR 1100 (HY000): Table 'active_watcher' was not locked with LOCK TABLES MariaDB [kamailio]> ``` I get same error Also i am found in additional documentation from Mysql next: ``` A session that requires locks must acquire all the locks that it needs in a single LOCK TABLES statement. While the locks thus obtained are held, the session can access only the locked tables. ``` or from Mariadb docs ``` While a connection holds an explicit lock on a table, it cannot access a non-locked table. If you try, the following error will be produced: ERROR 1100 (HY000): Table 'tab_name' was not locked with LOCK TABLES ``` ### Additional Information * **Kamailio Version** * ``` Kamailio ver 5.4.5 or 5.6.0 ``` So, maybe need add additional lock for table active_watchers or need take out query select from space LOCK - UNLOCK for resolve this issue? -- 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/2805

4 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev