sr-dev January 2023

sr-dev@lists.kamailio.org

14 participants
279 discussions

[kamailio/kamailio] kamailio crash alert (Issue #3290)

by 6ecbl

### 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>

12 months

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

by admin-toneca

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>

12 months

[kamailio/kamailio] packaging: cannot merge config files on system with ostree (Issue #3252)

by sergey-safarov

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>

12 months

[kamailio/kamailio] PUBLISH presence terminated state results in NOTIFY confirmed or early (Issue #3229)

by Duncan Palmer

### 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>

12 months

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

by sergey-safarov

### 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>

12 months

[kamailio/kamailio] [stirshaken] copy identity header and forward (Issue #3214)

by Artiom Baloian

### 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>

12 months

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

by space88man

### 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>

12 months

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

by patrickarton

### 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>

12 months

[kamailio/kamailio] RPC command app_jsdt.reload does not reload "require()" files (Issue #3145)

by Vincent Handfield

### 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>

12 months

[kamailio/kamailio] usrloc OPTIONS not tracing with HEP (Issue #3136)

by Luke Escudé

### 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>

12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2023