June 2023 - sr-dev - kamailio.org

[kamailio/kamailio] dnssec: stop using libdnsval-dev for DNSSEC validation (#851)
by Victor Seva 23 Nov '23

23 Nov '23

From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843477 > From: Ondřej Surý <ondrej(a)debian.org> > To: Debian Bug Tracking System <submit(a)bugs.debian.org> > Subject: src:kamailio: stop using libval-dev for DNSSEC validation > > Package: src:kamailio > Version: 4.4.3-2 > Severity: serious > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Dear maintainer, > > please stop using libdnsval-dev for DNSSEC validation. src:dnsval > is very poorly upstream maintained (SVN repository, issue tracker, > mailing list are non-functional) and I am going to schedule it for > removal for stretch. > > In a long term you should migrated to better and maintained library > (preferrably getdns or just libunbound), but now please just drop > it. > > Cheers, > Ondrej > > - -- System Information: > Debian Release: 8.6 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.2.0-41-generic (SMP w/24 CPU cores) > Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > -----BEGIN PGP SIGNATURE----- So I'm going to remove **dnssec** module from the official Debian package -- 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/851

2 2

[kamailio/kamailio] track_cseq_updates does not update Rack SIP header in PRACK. (#801)
by scfcplummy 23 Nov '23

23 Nov '23

Hi, When using dialog module and track_cseq_updates when needing to update CSeq for authenticated invites, if early media is present the CSeq in the Rack header is not also incremented. Kamailio version: version: kamailio 4.4.2 (x86_64/linux) 892ad6 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 892ad6 compiled on 11:18:36 Sep 28 2016 with gcc 5.4.0 -- 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/801

4 6

[kamailio/kamailio] sca: implement db_mode only (#781)
by Victor Seva 23 Nov '23

23 Nov '23

Sipwise hat ON: We have more than one server and we need to keep things in db in order to share sca subscription/appearance between servers -- 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/781

4 6

[kamailio/kamailio] core: add socket timestamp of received packets and keep track of receive delay (PR #3404)
by Nicolas C 20 Nov '23

20 Nov '23

#### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description This is a proposed evolution that adds socket timestamping of received UDP packets (using SO_TIMESTAMPNS). It computes the delay between this timestamp and the time at which the packet is read by Kamailio. This can then be accessed using pv "$TV(RD)" (RD for "receive relay"). Rationale : The Kamailio server is handling traffic that is irregular and can temporarily spike to a point where all children are still busy when new packets are incoming on the network interface. Consequently, these packets have to wait until a worker is available. The client will see a higher response time, that currently cannot be monitored by Kamailio itself. This evolution allows to make this wait time observable by Kamailio, allowing to log or write the information to CDR for example. If this is possible, I'd like to merge this feature in Kamailio. Of course, I'm ready to discuss the PR and make any necessary changes. All comments and reviews are most welcome. I've tested this locally on Linux (3.10.0-957.10.1.el7.x86_64) with the latest Kamailio master as of 2023/03/23. Thanks! You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3404 -- Commit Summary -- * core: add socket timestamp of received packets and keep track of receive delay * pv: add $TV(RD) to get the new information "receive delay" -- File Changes -- M src/core/ip_addr.h (1) M src/core/parser/msg_parser.h (1) M src/core/receive.c (8) M src/core/udp_server.c (60) M src/core/ut.h (34) M src/modules/pv/pv_time.c (15) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3404.patch https://github.com/kamailio/kamailio/pull/3404.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3404 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3404(a)github.com>

5 8

[kamailio/kamailio] Allow function set_advertised_address to receive variable as parameter (#2137)
by pwakano 17 Nov '23

17 Nov '23

### Description Currently the functions set_advertised_address and set_advertised_port only accept strings as parameters. Trying to use it with variable causes an error. Having the function using a hard coded value is not a good practice and in order to add flexibility to the script in different installations it would be nice to have this function accepting variables. Also, the 'advertise' option on the 'listen' parameter is not always desired because it apply for all messages sent via the socket, and there are situations where different advertised IP for the same interface are necessary. ### Expected behavior set_advertised_address should receive a variable as parameter and use its value to change the SIP headers. ### Actual observed behavior Kamailio won't start if set_advertised_address is used with a variable due to script parse error or it will set the SIP message with the literal string "$var(test)" for example, instead of using the value of $var(test). ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` # kamailio -v version: kamailio 5.2.2 (x86_64/linux) 67f967 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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: 67f967 compiled on 11:40:41 Mar 11 2019 with gcc 4.8.5 ``` * **Operating System**:  ``` # uname -a Linux voice-conn-kamailio-1 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 UTC 2017 x86_64 x86_64 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/2137

7 9

[kamailio/kamailio] dialplan: implement Iterative dialplan matching (#764)
by Victor Seva 13 Nov '23

13 Nov '23

>From http://lists.kamailio.org/pipermail/sr-dev/2016-August/036231.html On 24/08/16 10:17, Andreas Granig wrote: > Hi, > > When translating strings with the dialplan module, you sometimes end up > with very complex patterns for sanitizing the target string and > performing some replacements, since for a given dialplan id, processing > stops on the first match within the dialplan entries for a given dpid. > > The idea is to introduce a "continue" flag (default 0) in the dialplan > table indicating to proceed with processing further dialplan entries > within the given dpid after a match. The use case is to have a sanitize > rule with highest priority which e.g. removes any spaces, dashes and > parentheses from the target string, then with a lower priority do > further processing with the cleaned up string, e.g. stripping leading > double-zeroes or a plus when normalizing to E164 numbers, or replacing a > single leading zero with the country code and so on. > > This is particularly useful when a user dials a number from an address > book of some sort (e.g. on a mobile app) where number formats are stored > with country-specific formating characters like "+1-(234)-567 890", and > catching all of that in one rule results in really messy match/replace > patterns. -- 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/764

4 5

[kamailio/kamailio] kamailio 5.5 (commit 54c9df) SIGSEGV on run_dlg_callbacks (Issue #3106)
by MayamaTakeshi 13 Nov '23

13 Nov '23

### Description Crash occurred during load test. #### Reproduction This cannot be reproduced at will. It happened after about 40 days of load testing. #### Debugging Data ``` [root@lab002201-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 730446] [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 0x00007fb609cba495 in run_dlg_callbacks (type=4, dlg=0x7fb5ca1798d0, req=0x7fb5ce0a7380, rpl=0xffffffffffffffff, dir=2, dlg_data=0x0) at dlg_cb.c:273 273 cb->callback( dlg, type, &params ); (gdb) bt full #0 0x00007fb609cba495 in run_dlg_callbacks (type=4, dlg=0x7fb5ca1798d0, req=0x7fb5ce0a7380, rpl=0xffffffffffffffff, dir=2, dlg_data=0x0) at dlg_cb.c:273 cb = 0x7fb609ce7a23 <dlg_iuid_sfree> __func__ = "run_dlg_callbacks" #1 0x00007fb609ceb3ee in dlg_onreply (t=0x7fb5cfa8a1f0, type=1048576, param=0x7fff4bdc6060) at dlg_handlers.c:576 dlg = 0x7fb5ca1798d0 iuid = 0x7fb5cca0bbf0 new_state = 5 old_state = 2 unref = 1 event = 4 tag = {s = 0x80d000001ff <error: Cannot access memory at address 0x80d000001ff>, len = 174085573} req = 0x7fb5ce0a7380 rpl = 0xffffffffffffffff __func__ = "dlg_onreply" #2 0x00007fb60a53c399 in run_trans_callbacks_internal (cb_lst=0x7fb5cfa8a268, type=1048576, trans=0x7fb5cfa8a1f0, params=0x7fff4bdc6060) at t_hooks.c:258 cbp = 0x7fb5cb5b2520 backup_from = 0x5591e2acbe90 <def_list+16> backup_to = 0x5591e2acbe98 <def_list+24> backup_dom_from = 0x5591e2acbea0 <def_list+32> backup_dom_to = 0x5591e2acbea8 <def_list+40> backup_uri_from = 0x5591e2acbe80 <def_list> backup_uri_to = 0x5591e2acbe88 <def_list+8> backup_xavps = 0x5591e2acbfd8 <_xavp_list_head> backup_xavus = 0x5591e2acbfe0 <_xavu_list_head> backup_xavis = 0x5591e2acbfe8 <_xavi_list_head> __func__ = "run_trans_callbacks_internal" #3 0x00007fb60a53c5b2 in run_trans_callbacks_with_buf (type=1048576, rbuf=0x7fb5cfa8a2c0, req=0x7fb5ce0a7380, repl=0xffffffffffffffff, flags=0) at t_hooks.c:303 params = {req = 0x7fb5ce0a7380, rpl = 0xffffffffffffffff, param = 0x7fb5cb5b2530, code = 408, flags = 0, branch = 0, t_rbuf = 0x7fb5cfa8a2c0, dst = 0x7fb5cfa8a310, send_buf = { s = 0x7fb5caa9cda0 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 192.168.2.202:5020;rport=5020;branch=z9hG4bK-2375372-4769-10;received=192.168.2.202\r\nFrom: \"0312341234\" <sip:0312341234@fakedomain.com>;tag=2375372SIPpTag"..., len = 407}} trans = 0x7fb5cfa8a1f0 #4 0x00007fb60a5b322d in relay_reply (t=0x7fb5cfa8a1f0, p_msg=0xffffffffffffffff, branch=0, msg_status=408, cancel_data=0x7fff4bdc6280, do_put_on_wait=0) at t_reply.c:2094 relay = 0 save_clone = 0 buf = 0x7fb60a8f6b68 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 192.168.2.202:5020;rport=5020;branch=z9hG4bK-2375372-4769-10;received=192.168.2.202\r\nFrom: \"0312341234\" <sip:0312341234@fakedomain.com>;tag=2375372SIPpTag"... res_len = 407 relayed_code = 408 relayed_msg = 0xffffffffffffffff reply_bak = 0x7fff4bdc6220 bm = {to_tag_val = { s = 0x7fb60a8f6c5f "0a86cd31e4e6805cdd7f1dffc4ec5169-53cd2e21\r\nCall-ID: 4769-2375372(a)192.168.2.202\r\nCSeq: 801 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 = 0x7fb5cfa8a2c0 to_tag = 0x7fb60a61cb30 <tm_tag> reason = {s = 0x5591e2933463 "Request Timeout", len = 15} onsend_params = {req = 0x40, rpl = 0x0, param = 0x1c9f56660, code = -923035960, flags = 32693, branch = 0, t_rbuf = 0x7fff4bdc61b0, dst = 0x5591e27f9149 <futex_release+29>, send_buf = { s = 0x2260 <error: Cannot access memory at address 0x2260>, len = -923035960}} ip = {af = 3407219152, len = 32693, u = {addrl = {140418773026976, 1}, addr32 = {3407218848, 32693, 1, 0}, addr16 = {2208, 51990, 32693, 0, 1, 0, 0, 0}, addr = "\240\b\026˵\177\000\000\001\000\000\000\000\000\000"}} __func__ = "relay_reply" #5 0x00007fb60a540ec0 in fake_reply (t=0x7fb5cfa8a1f0, branch=0, code=408) at timer.c:295 --Type <RET> for more, q to quit, c to continue without paging--c cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = -811032080}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = -811032080}}}} do_cancel_branch = 1 reply_status = 730446 #6 0x00007fb60a54132e in final_response_handler (r_buf=0x7fb5cfa8a490, t=0x7fb5cfa8a1f0) at timer.c:462 silent = 0 branch_ret = 0 prev_branch = 0 now = 0 #7 0x00007fb60a5413f2 in retr_buf_handler (ticks=280654947, tl=0x7fb5cfa8a4b0, p=0x7d0) at timer.c:518 rbuf = 0x7fb5cfa8a490 fr_remainder = 0 retr_remainder = 32693 retr_interval = 3371932768 new_retr_interval_ms = 4294967296 crt_retr_interval_ms = 0 t = 0x7fb5cfa8a1f0 __func__ = "retr_buf_handler" #8 0x00005591e27bda9f in timer_list_expire (t=280654947, h=0x7fb5c8ffdd40, slow_l=0x7fb5c8fff2a8, slow_mark=48435) at core/timer.c:857 tl = 0x7fb5cfa8a4b0 ret = 0 #9 0x00005591e27bdfa9 in timer_handler () at core/timer.c:922 saved_ticks = 280654947 run_slow_timer = 0 i = 307 __func__ = "timer_handler" #10 0x00005591e27be4ac in timer_main () at core/timer.c:961 No locals. #11 0x00005591e25066cf in main_loop () at main.c:1839 i = 12 pid = 0 si = 0x0 si_desc = "udp receiver child=11 sock=192.168.2.201:9060\000\270\000\340e\334K\377\177\000\000\000\000\000\000\000\000\000\000\360e\334K\377\177\000\000)+\373\b\266\177\000\000\b\024l\n\266\177\000\000]q\373\b\266\177", '\000' <repeats 14 times>, "\001\000\000\000\360e\334K\377\177\000\000⌀\342\221U\000" nrprocs = 12 woneinit = 1 __func__ = "main_loop" #12 0x00005591e25112ab in main (argc=8, argv=0x7fff4bdc6bd8) at main.c:3053 cfg_stream = 0x5591e46482d0 c = -1 r = 0 tmp = 0x7fff4bdc8d08 "" tmp_len = 0 port = 0 proto = 0 ahost = 0x0 aport = 0 options = 0x5591e291d0b8 ":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 = 529371157 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 = 2420, 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 = 1646813990, tv_nsec = 961425837}, st_mtim = {tv_sec = 1647220116, tv_nsec = 385726158}, st_ctim = {tv_sec = 1647220120, tv_nsec = 853813654}, __glibc_reserved = {0, 0, 0}} tbuf = "\020\357\027\v\266\177\000\000\300\372\344\n\001\000\000\000\377\377\377\377", '\000' <repeats 12 times>, "(\326\030\v\266\177\000\000\350\211\033\v\266\177\000\000\377\377\377\377", '\000' <repeats 12 times>, "@\265\343\n\266\177\000\000\020\364\027\v\266\177\000\000\350\224\033\v\266\177\000\000\204\331\030\v\266\177\000\000\060\324\030\v\266\177\000\000XR\001\v\266\177\000\000h\211\033\v\266\177\000\000`\200\033\v\266\177\000\000 l\334K\377\177\000\000\200\221\033\v\266\177\000\000\000\000\000\000\000\000\000\000#\306\031\v\266\177\000\000\001", '\000' <repeats 23 times>, "(\326\030\v\266\177\000\000\060j\334K\377\177\000\000"... option_index = 12 long_options = {{name = 0x5591e291f516 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x5591e291a514 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x5591e291f51b "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x5591e291f521 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x5591e291f527 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x5591e291f530 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x5591e291f53a "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x5591e291f544 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x5591e291f54f "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x5591e291f558 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x5591e291f563 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x5591e291f569 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x5591e291f573 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) info locals cb = 0x7fb609ce7a23 <dlg_iuid_sfree> __func__ = "run_dlg_callbacks" (gdb) list 268 269 for ( cb=dlg->cbs.first; cb; cb=cb->next) { 270 if ( (cb->types)&type ) { 271 LM_DBG("dialog=%p, type=%d\n", dlg, type); 272 params.param = &cb->param; 273 cb->callback( dlg, type, &params ); 274 } 275 } 276 return; 277 } (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:32:51 Mar 9 2022 with gcc 10.2.1 ``` * **Operating System**: ``` [root@lab002201-flip-server ~]$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye [root@lab002201-flip-server ~]$ uname -a Linux lab002201-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/3106 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3106(a)github.com>

4 6

[kamailio/kamailio] tcp_send_timeout not used on reused socket (Issue #3443)
by schoberw 13 Nov '23

13 Nov '23

### Description Having clients connected via TCP doing only passive connections in the kamailio server it seems the tcp_send_timeout is not used on messages going out to the clients. While tcp_keepalive is doing well as long as there was not sent any packet to the client tcp_send_timout does nothing. The underlying Linux tries to send the SIP message for ages (15 minutes in my case). Do I have a wrong understanding of tcp_send_timeout? I tried with tcp_async yes and no with same results. ### Troubleshooting These are my tcp settings: ``` # def = 10 Time in seconds after a TCP connection will be closed if it is not available for writing in this interval (and Kamailio wants to send something on it). # Lower this value for faster detection of broken TCP connections. tcp_send_timeout=3 tcp_connect_timeout=10 # def = 10 tcp_connection_lifetime=3605 tcp_rd_buf_size=32768 tcp_max_connections=2048 tcp_connection_match=1 # match also local port tcp_keepalive=yes # Enables keepalive for tcp (sets SO_KEEPALIVE socket option) tcp_keepcnt=3 # Number of keepalives sent before dropping the connection (TCP_KEEPCNT socket option). Linux only. tcp_keepidle=30 # Time before starting to send keepalives, if the connection is idle (TCP_KEEPIDLE socket option). Linux only. tcp_keepintvl=10 # Time interval between keepalive probes, when the previous probe failed (TCP_KEEPINTVL socket option). Linux only. tcp_async=yes # alias tcp_buf_write, default=yes tcp_crlf_ping=no ``` I also tried to set the tcp_send_timeout to much too high value 333666 to trigger this line of code in tcp_options.c: ``` WARN("%s: timeout too big (%u), the maximum value is %u\n", name, *to, max_val); ``` But even in -d -d -d debugging that line never hits. I do **not** make any connections outbound (senseless on NAT). Instead I'd like to reject this: ``` if ($dP =~ "tcp") { set_forward_no_connect(); xlog("L_INFO", ">> checking tcp connection to $dd:$dp"); if(tcp_get_conid("$dd:$dp", "$var(conid)")) { xlog("L_INFO", ">> connection id to $dd:$dp is: $var(conid)"); } else { xlog("L_ERR", ">> connection to $dd:$dp is no longer connected. Client must reregister!"); sl_send_reply("480", "TCP not connected"); exit; } } ``` But the connection ID is still there for a long time. And there are no keepalives done since the outgoing packets are in the queue. #### Reproduction 1. Register a client with TCP. 2. Pull the plug. 3. Make a call to it. 4. Run a `'watch 'netstat -tapen | grep <client_ip>'`: The connected client never vanishes. 5. Run a `tcpdump -i ethX tcp port <kamailio_server_port>`: the system tries to send the packet for a long time #### Log Messages There is not much to see in the log, even in debug level. `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.sbc.pid -f /etc/kamailio.sbc/kamailio.cfg -m 48 -M 24 -u kamailio -g kamailio -d -d -d` At that moment the switchport was already shutdown: ``` May 9 10:48:19 p01t-1 kamailio.sbc[150273]: INFO: sbc:<script>: Network sending: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> INVITE sip:22@ws2.domain.tld;user=phone SIP/2.0 Record-Route: <sip:192.168.48.131:5065;r2=on;lr;ftag=97p54nlxgb;x-rtpp=1> Record-Route: <sip:10.101.65.131:5082;r2=on;lr;ftag=97p54nlxgb;x-rtpp=1> Via: SIP/2.0/UDP 192.168.48.131:5065;branch=z9hG4bKe01f.07e0d03fb0af18dcdb76154be67bea1d.0 Via: SIP/2.0/UDP 192.168.41.57:48310;received=10.101.65.130;branch=z9hG4bK-nzdt1be9c4xn;rport=48310 From: "01/301102-21" <sip:15553010221@ws2.domain.tld>;tag=97p54nlxgb To: <sip:22@ws2.domain.tld;user=phone> Call-ID: 3136383336323230393839333336-jg7spjsktbm2 CSeq: 2 INVITE Max-Forwards: 69 User-Agent: snomD765/10.1.49.11 Contact: <sip:15553010221@192.168.48.131:5065;ntv3=2;alias=10.101.65.130~48310~1;fs=udp:10.101.65.131:5082;uri=sip:15553010221%40192.168.41.57:48310%3bline%3dbq029ivo;line=bq029ivo>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600 Min-SE: 90 Proxy-Authorization: Digest username="45487cfdffef4777",realm="ws2.domain.tld",nonce="d84c8d657ba6e3081547bbb6e0c1817c",uri="sip:22@ws2.domain.tld;user=phone",qop=auth,nc=00000001,cnonce="6be15ae9",response="9455eafa4f6b2b78e971a87cb2716132",opaque="485307819b9fa9a1f7e2ca58ae77f795",algorithm=MD5 Content-Type: application/sdp Content-Length: 258 P-Charging-Vector: icid-value=31363833363232;icid-generated-at=c5sbcp01t X-User: <sip:45487cfdffef4777@ws2.domain.tld> X-Location: dev.DefaultGroup;reg=192.168.48.68:5060;sig=192.168.48.74:5060;bt=0 X-Realm: p01t v=0 o=root 711904586 711904586 IN IP4 10.101.65.133 s=call c=IN IP4 10.101.65.133 t=0 0 m=audio 10490 RTP/AVP 9 8 101 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:10491 a=ptime:20 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:tm [t_funcs.c:373]: t_relay_to(): new transaction forwarded May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/receive.c:528]: receive_msg(): request-route executed in: 45584 usec May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/receive.c:628]: receive_msg(): cleaning up May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:863]: free_sdp(): _sdp = 0x7fa8d478c728 May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:865]: free_sdp(): sdp = 0x7fa8d44ef100 May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:867]: free_sdp(): session = 0x7fa8d44ee018 ... May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:1664]: _tcpconn_find(): found connection by peer address (id: 1) May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2541]: tcpconn_send_put(): found fd in cache (11, 0x7fa8d0965140, 1) May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2763]: tcpconn_do_send(): sending... May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2796]: tcpconn_do_send(): after real write: c= 0x7fa8d0965140 n=1261 fd=11 May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2797]: tcpconn_do_send(): buf= INVITE sip:22@192.168.41.157:39342;line=5z2d2k8i;ob SIP/2.0 ... ``` Finally the Application Server in front cancels the call. But look at this: ``` root@p01t-1:~# tcpdump -nn -i eth1 tcp port 5082 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on eth1, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:47:31.915062 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [.], ack 3024626659, win 501, options [nop,nop,TS val 924881395 ecr 4525523], length 0 10:47:31.916129 IP 10.101.65.130.39342 > 10.101.65.131.5082: Flags [.], ack 1, win 4836, options [nop,nop,TS val 4528662 ecr 924819977], length 0 10:48:02.635024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [.], ack 1, win 501, options [nop,nop,TS val 924912115 ecr 4528662], length 0 10:48:02.636100 IP 10.101.65.130.39342 > 10.101.65.131.5082: Flags [.], ack 1, win 4836, options [nop,nop,TS val 4531734 ecr 924819977], length 0 ----- switch port port shutdown ------ ----- make the call: 10:48:19.690401 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929170 ecr 4531734], length 1261 10:48:19.899036 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929379 ecr 4531734], length 1261 10:48:20.331011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929811 ecr 4531734], length 1261 10:48:21.194994 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924930675 ecr 4531734], length 1261 10:48:22.891001 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924932371 ecr 4531734], length 1261 10:48:26.446978 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924935927 ecr 4531734], length 1261 10:48:33.355070 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924942835 ecr 4531734], length 1261 10:48:40.011057 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924949491 ecr 4531734], length 1261 10:48:46.667041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924956147 ecr 4531734], length 1261 10:48:53.323039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924962803 ecr 4531734], length 1261 10:48:59.979042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924969459 ecr 4531734], length 1261 10:49:06.635029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924976115 ecr 4531734], length 1261 10:49:13.291079 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924982771 ecr 4531734], length 1261 10:49:19.947045 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924989427 ecr 4531734], length 1261 10:49:26.603048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924996083 ecr 4531734], length 1261 10:49:33.259016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925002739 ecr 4531734], length 1261 10:49:39.915052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925009395 ecr 4531734], length 1261 10:49:46.571046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925016051 ecr 4531734], length 1261 10:49:53.227015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925022707 ecr 4531734], length 1261 10:49:59.883017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925029363 ecr 4531734], length 1261 10:50:06.539037 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925036019 ecr 4531734], length 1261 10:50:13.195051 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925042675 ecr 4531734], length 1261 10:50:19.850986 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925049331 ecr 4531734], length 1261 10:50:26.507018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925055987 ecr 4531734], length 1261 10:50:33.163011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925062643 ecr 4531734], length 1261 10:50:39.819015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925069299 ecr 4531734], length 1261 10:50:46.475056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925075955 ecr 4531734], length 1261 10:50:53.135023 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925082615 ecr 4531734], length 1261 10:51:00.043094 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925089523 ecr 4531734], length 1261 10:51:06.699024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925096179 ecr 4531734], length 1261 10:51:13.355049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925102835 ecr 4531734], length 1261 10:51:20.011080 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925109491 ecr 4531734], length 1261 10:51:26.667023 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925116147 ecr 4531734], length 1261 10:51:33.323042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925122803 ecr 4531734], length 1261 10:51:39.979029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925129459 ecr 4531734], length 1261 10:51:46.635040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925136115 ecr 4531734], length 1261 10:51:53.291007 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925142771 ecr 4531734], length 1261 10:51:59.947009 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925149427 ecr 4531734], length 1261 10:52:06.603019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925156083 ecr 4531734], length 1261 10:52:13.259033 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925162739 ecr 4531734], length 1261 10:52:19.915011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925169395 ecr 4531734], length 1261 10:52:26.571014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925176051 ecr 4531734], length 1261 10:52:33.227032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925182707 ecr 4531734], length 1261 10:52:39.883041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925189363 ecr 4531734], length 1261 10:52:46.539013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925196019 ecr 4531734], length 1261 10:52:53.199018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925202679 ecr 4531734], length 1261 10:53:00.107035 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925209587 ecr 4531734], length 1261 10:53:06.763039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925216243 ecr 4531734], length 1261 10:53:13.419041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925222899 ecr 4531734], length 1261 10:53:20.075014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925229555 ecr 4531734], length 1261 10:53:26.731046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925236211 ecr 4531734], length 1261 10:53:33.387027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925242867 ecr 4531734], length 1261 10:53:40.043077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925249523 ecr 4531734], length 1261 10:53:46.699076 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925256179 ecr 4531734], length 1261 10:53:53.355055 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925262835 ecr 4531734], length 1261 10:54:00.011019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925269491 ecr 4531734], length 1261 10:54:06.667071 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925276147 ecr 4531734], length 1261 10:54:13.323026 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925282803 ecr 4531734], length 1261 10:54:19.979077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925289459 ecr 4531734], length 1261 10:54:26.635284 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925296115 ecr 4531734], length 1261 10:54:33.291019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925302771 ecr 4531734], length 1261 10:54:39.946998 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925309427 ecr 4531734], length 1261 10:54:46.603049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925316083 ecr 4531734], length 1261 10:54:53.259008 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925322739 ecr 4531734], length 1261 10:54:59.915019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925329395 ecr 4531734], length 1261 10:55:06.571100 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925336051 ecr 4531734], length 1261 10:55:13.227056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925342707 ecr 4531734], length 1261 10:55:19.883016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925349363 ecr 4531734], length 1261 10:55:26.539021 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925356019 ecr 4531734], length 1261 10:55:33.195043 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925362675 ecr 4531734], length 1261 10:55:39.850991 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925369331 ecr 4531734], length 1261 10:55:46.507013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925375987 ecr 4531734], length 1261 10:55:53.163060 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925382643 ecr 4531734], length 1261 10:55:59.819014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925389299 ecr 4531734], length 1261 10:56:06.475045 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925395955 ecr 4531734], length 1261 10:56:13.131065 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925402611 ecr 4531734], length 1261 10:56:19.787052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925409267 ecr 4531734], length 1261 10:56:26.443048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925415923 ecr 4531734], length 1261 10:56:33.099016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925422579 ecr 4531734], length 1261 10:56:39.755032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925429235 ecr 4531734], length 1261 10:56:46.411005 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925435891 ecr 4531734], length 1261 10:56:53.067116 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925442547 ecr 4531734], length 1261 10:56:59.723032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925449203 ecr 4531734], length 1261 10:57:06.379062 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925455859 ecr 4531734], length 1261 10:57:13.035003 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925462515 ecr 4531734], length 1261 10:57:19.691077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925469171 ecr 4531734], length 1261 10:57:26.347050 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925475827 ecr 4531734], length 1261 10:57:33.003004 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925482483 ecr 4531734], length 1261 10:57:39.659029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925489139 ecr 4531734], length 1261 10:57:46.314989 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925495795 ecr 4531734], length 1261 10:57:52.971040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925502451 ecr 4531734], length 1261 10:57:59.631026 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925509111 ecr 4531734], length 1261 10:58:06.539039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925516019 ecr 4531734], length 1261 10:58:13.195056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925522675 ecr 4531734], length 1261 10:58:19.851012 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925529331 ecr 4531734], length 1261 10:58:26.507049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925535987 ecr 4531734], length 1261 10:58:33.163017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925542643 ecr 4531734], length 1261 10:58:39.819091 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925549299 ecr 4531734], length 1261 10:58:46.475017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925555955 ecr 4531734], length 1261 10:58:53.131046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925562611 ecr 4531734], length 1261 10:58:59.786990 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925569267 ecr 4531734], length 1261 10:59:06.443029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925575923 ecr 4531734], length 1261 10:59:13.099009 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925582579 ecr 4531734], length 1261 10:59:19.754984 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925589235 ecr 4531734], length 1261 10:59:26.411053 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925595891 ecr 4531734], length 1261 10:59:33.067041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925602547 ecr 4531734], length 1261 10:59:39.723053 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925609203 ecr 4531734], length 1261 10:59:46.379016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925615859 ecr 4531734], length 1261 10:59:53.035054 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925622515 ecr 4531734], length 1261 10:59:59.691058 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925629171 ecr 4531734], length 1261 11:00:06.347021 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925635827 ecr 4531734], length 1261 11:00:13.003052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925642483 ecr 4531734], length 1261 11:00:19.659043 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925649139 ecr 4531734], length 1261 11:00:26.315011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925655795 ecr 4531734], length 1261 11:00:32.971015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925662451 ecr 4531734], length 1261 11:00:39.627039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925669107 ecr 4531734], length 1261 11:00:46.283052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925675763 ecr 4531734], length 1261 11:00:52.939024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925682419 ecr 4531734], length 1261 11:00:59.595048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925689075 ecr 4531734], length 1261 11:01:06.251017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925695731 ecr 4531734], length 1261 11:01:12.907013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925702387 ecr 4531734], length 1261 11:01:19.563042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925709043 ecr 4531734], length 1261 11:01:26.219027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925715699 ecr 4531734], length 1261 11:01:32.875010 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925722355 ecr 4531734], length 1261 11:01:39.531004 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925729011 ecr 4531734], length 1261 11:01:46.187040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925735667 ecr 4531734], length 1261 11:01:52.843002 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925742323 ecr 4531734], length 1261 11:01:59.499048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925748979 ecr 4531734], length 1261 11:02:06.155027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925755635 ecr 4531734], length 1261 11:02:12.811044 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925762291 ecr 4531734], length 1261 11:02:19.467018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925768947 ecr 4531734], length 1261 11:02:26.123041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925775603 ecr 4531734], length 1261 11:02:32.779046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925782259 ecr 4531734], length 1261 11:02:39.435015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925788915 ecr 4531734], length 1261 11:02:46.091034 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925795571 ecr 4531734], length 1261 11:02:52.747128 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925802227 ecr 4531734], length 1261 11:02:59.403096 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925808883 ecr 4531734], length 1261 11:03:06.059012 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925815539 ecr 4531734], length 1261 11:03:12.715029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925822195 ecr 4531734], length 1261 11:03:19.370993 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925828851 ecr 4531734], length 1261 11:03:26.027010 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925835507 ecr 4531734], length 1261 11:03:32.683029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925842163 ecr 4531734], length 1261 11:03:39.339046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925848819 ecr 4531734], length 1261 ``` ### Possible Solutions I have no idea why tcp_send_timeout is not set on the connected socket during spawning the listener for this client. ### Additional Information ``` root@p01t-1:~# kamailio -V version: kamailio 5.6.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**: ``` root@p01t-1:~# cat /etc/debian_version 11.7 Linux p01t-1.neotel.at 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux ``` [debug.log](https://github.com/kamailio/kamailio/files/11429302/debug.log) -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3443 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3443(a)github.com>

3 7

[kamailio/kamailio] app_ruby: print backtrace when ruby exception occurs (#1766)
by Fatih Orhan 13 Nov '23

13 Nov '23

### Description Hello, When there is an error in my ruby script, app_ruby prints exception message without a stack trace, like this: ``` Dec 14 16:25:17 servername /usr/sbin/kamailio[24313]: ERROR: app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: wrong number of arguments (1 for 2..3) Dec 14 16:25:17 servername /usr/sbin/kamailio[24313]: ERROR: app_ruby [app_ruby_api.c:1078]: app_ruby_run_ex(): ruby exception (6) on callback for: ksr_request_route (res type: 17) ``` Altough this message tells what is the error, it doesn't tell **where** the error happened, so it's hard to find the source of the problem. In ruby, exceptions have _backtrace()_ method returning stack trace as an array of strings. It would be really helpful if app_ruby also call this method and append its result to error message. ### Reproduction in kamailio.cfg ``` loadmodule "app_ruby.so" modparam("app_ruby", "load", "/etc/kamailio/ruby/routes.rb") cfgengine "ruby" ``` in /etc/kamailio/ruby/routes.rb ``` def some_method(param1, param2) end def ksr_request_route some_method(1) end ``` ### Expected behavior ``` Dec 14 16:46:24 servername /usr/sbin/kamailio[24314]: ERROR: <core> [core/kemi.c:87]: sr_kemi_core_err(): wrong number of arguments (1 for 2): /etc/kamailio/ruby/routes.rb:1:in `some_method' /etc/kamailio/ruby/routes.rb:4:in `ksr_request_route' ``` #### Actual observed behavior ``` Dec 14 16:45:42 servername /usr/sbin/kamailio[24311]: ERROR: app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: wrong number of arguments (1 for 2) ``` ### Possible Solutions Relevant code seem to be here: https://github.com/kamailio/kamailio/blob/master/src/modules/app_ruby/app_r… I found example C code to print stack trace here but couldn't figure out how to integrate to app_ruby: http://zoo-project.org/svn/trunk/zoo-project/zoo-kernel/service_internal_ru… Equivalent ruby code would be (this code is not idiomatic, my aim is to provide C-like ruby code): ``` def some_error_generating_method method_taking_two_params(1) rescue => exception message = exception.to_s() + "\n" stack_trace = exception.backtrace() for line in stack_trace message = message + line + "\n" end print(message) end ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.2.0 (x86_64/linux) 535e13 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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: 535e13 compiled on 10:26:34 Nov 28 2018 with gcc 4.8.5 ``` * **Operating System**: Centos 7.2 64bit ``` Linux servername 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x86_64 x86_64 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/1766

3 3

[kamailio/kamailio] Warnings compiling app_java module (#1984)
by Jaigongon 08 Nov '23

08 Nov '23

### Description I recently downloaded kamailio 5.2.3 and tried to install it for investigation purposes. I was trying to include app_java module in order to execute some brief java apps in kamailio. But then I get the same issue wen I compile and when I run kamailio Thank you for all the help you can give me ### Troubleshooting I get the same bunch of warnings everytime I try to make all java_msgobj.c: In function ‘fill_sipmsg_object’: java_msgobj.c:83:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->id); ^~~~~~~~~~~~~~ java_msgobj.c:83:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:96:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->pid); ^~~~~~~~~~~~~~ java_msgobj.c:96:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:110:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:110:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:127:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:127:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:142:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:142:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:156:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->len); ^~~~~~~~~~~~~~ java_msgobj.c:156:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:172:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:172:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:189:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:189:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:205:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->parsed_orig_ruri_ok); ^~~~~~~~~~~~~~ java_msgobj.c:205:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:222:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:222:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:237:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->add_to_branch_len); ^~~~~~~~~~~~~~ java_msgobj.c:237:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:251:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->hash_index); ^~~~~~~~~~~~~~ java_msgobj.c:251:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:265:27: warning: passing argument 2 of ‘(*env)->SetIntField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetIntField(env, SipMsgInstance, fid, msg->msg_flags); ^~~~~~~~~~~~~~ java_msgobj.c:265:27: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:286:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:286:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ java_msgobj.c:306:30: warning: passing argument 2 of ‘(*env)->SetObjectField’ from incompatible pointer type [-Wincompatible-pointer-types] (*env)->SetObjectField(env, SipMsgInstance, fid, jStrParam); ^~~~~~~~~~~~~~ java_msgobj.c:306:30: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘struct _jobject **’ CC (gcc) [M app_java.so] java_support.o CC (gcc) [M app_java.so] java_iface.o java_iface.c: In function ‘java_exec’: java_iface.c:205:53: warning: passing argument 2 of ‘(*_aj_env)->NewLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] invk_method_ref = (*_aj_env)->NewLocalRef(_aj_env, invk_method); ^~~~~~~~~~~ java_iface.c:205:53: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:205:18: warning: assignment from incompatible pointer type [-Wincompatible-pointer-types] invk_method_ref = (*_aj_env)->NewLocalRef(_aj_env, invk_method); ^ java_iface.c:208:39: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method_ref); ^~~~~~~~~~~~~~~ java_iface.c:208:39: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:216:40: warning: passing argument 2 of ‘(*_aj_env)->MonitorEnter’ from incompatible pointer type [-Wincompatible-pointer-types] if((*_aj_env)->MonitorEnter(_aj_env, invk_method_ref) != JNI_OK) { ^~~~~~~~~~~~~~~ java_iface.c:216:40: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:234:40: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method_ref); ^~~~~~~~~~~~~~~ java_iface.c:234:40: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:235:40: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method); ^~~~~~~~~~~ java_iface.c:235:40: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:258:39: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method_ref); ^~~~~~~~~~~~~~~ java_iface.c:258:39: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:259:39: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method); ^~~~~~~~~~~ java_iface.c:259:39: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:266:39: warning: passing argument 2 of ‘(*_aj_env)->MonitorExit’ from incompatible pointer type [-Wincompatible-pointer-types] if((*_aj_env)->MonitorExit(_aj_env, invk_method_ref) != JNI_OK) { ^~~~~~~~~~~~~~~ java_iface.c:266:39: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:272:38: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method_ref); ^~~~~~~~~~~~~~~ java_iface.c:272:38: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ java_iface.c:273:38: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, invk_method); ^~~~~~~~~~~ java_iface.c:273:38: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ CC (gcc) [M app_java.so] java_native_methods.o java_native_methods.c: In function ‘Java_org_siprouter_SipMsg_ParseSipMsg’: java_native_methods.c:484:9: warning: return from incompatible pointer type [-Wincompatible-pointer-types] return fill_sipmsg_object(jenv, _aj_msg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CC (gcc) [M app_java.so] app_java_mod.o app_java_mod.c: In function ‘child_init’: app_java_mod.c:236:38: warning: passing argument 2 of ‘(*_aj_env)->DeleteLocalRef’ from incompatible pointer type [-Wincompatible-pointer-types] (*_aj_env)->DeleteLocalRef(_aj_env, child_init_id); ^~~~~~~~~~~~~ app_java_mod.c:236:38: note: expected ‘jobject {aka struct _jobject *}’ but argument is of type ‘jmethodID {aka struct _jmethodID *}’ #### Reproduction 1. Download 5.2.3 2. in /usr/local/src/kamailio-5.2.3/ 2.1 make include_modules="app_java" cfg 2.2 make all 2.3 make install 3 kamailo -e -E -ddd #### Debugging Data 0(18169) ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/app_java.so>: libjvm.so: cannot open shared object file: No such file or directory 0(18169) CRITICAL: <core> [core/cfg.y:3507]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 300, column 12-24: failed to load module 0(18169) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <app_java> found 0(18169) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 306, column 46: Can't set module parameter 0(18169) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <app_java> found 0(18169) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 307, column 55: Can't set module parameter 0(18169) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <app_java> found 0(18169) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 308, column 60: Can't set module parameter 0(18169) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <app_java> found 0(18169) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 309, column 41: Can't set module parameter 0(18169) ERROR: <core> [core/cfg.y:3370]: yyparse(): cfg. parser: failed to find command java_method_exec (params 2) 0(18169) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 483, column 37: unknown command, missing loadmodule? ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` version: kamailio 5.2.3 (x86_64/linux) c36229 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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: c36229 * **Operating System**: Ubuntu 18.04 -- 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/1984

2 3

[kamailio/kamailio] kamailio depends on obsolete pcre3 library (Issue #2946)
by Victor Seva 26 Oct '23

26 Oct '23

>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000134: ``` Source: kamailio Severity: important User: matthew-pcredep(a)debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian ``` -- 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/2946

2 4

[kamailio/kamailio] tm:local-request not documented (#980)
by Olle E. Johansson 18 Oct '23

18 Oct '23

The local-request event route is not documented. When using our friend google I find an old blog post by @miconda but not much else. I can come up with some good text, but need to know what can be done in the route, like - modify request uri - add/remove headers - drop request - add/modify destination uri ($du) -- 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/980

3 8

[kamailio/kamailio] core: fixed wrong network interface selection. (PR #3490)
by Ivanuschak Nikolay 25 Sep '23

25 Sep '23

fixed incorrect source IP address selection for the SIP messages sending procedure when TCP transport is used or for UDP with the 'mhomed' setting set as 'mhomed=1'.   #### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #3486(replace XXXX with an open issue number) #### Description  The current service behavior is as follows: if OS contains several network interfaces and the service has a listening TCP socket (or UDP with 'mhomed=1' setting) on the second (third, fourth and so on) interface, then the outbound SIP messages will be always sent from the first (default) interface. These changes make the outbound SIP messages always going through the network_interface/address, which is taken for listening by service. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3490 -- Commit Summary -- * core: fixed wrong network interface selection. -- File Changes -- M src/core/forward.c (7) M src/core/udp_server.c (37) M src/core/udp_server.h (6) M src/main.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3490.patch https://github.com/kamailio/kamailio/pull/3490.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3490 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3490(a)github.com>

3 18

[kamailio/kamailio] No warning generated when UDP and no Content-Length header (PR #3359)
by sergey-safarov 12 Sep '23

12 Sep '23

GH # #### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #3210 #### Description Added 'always_log_missed_content_length' mode for sanity module. If 'always_log_missed_content_length' is 1 then the SIP message with no 'Content-Length' header will cause warning message in the logs. Otherwise warning message is not generated for cases when SIP message with no 'Content-Length' header is sent over UDP. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3359 -- Commit Summary -- * No warning generated when UDP and no Content-Length header -- File Changes -- M src/modules/sanity/doc/sanity_admin.xml (21) M src/modules/sanity/sanity.c (4) M src/modules/sanity/sanity_mod.c (12) M src/modules/sanity/sanity_mod.h (3) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3359.patch https://github.com/kamailio/kamailio/pull/3359.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3359 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3359(a)github.com>

4 9

[kamailio/kamailio] pdt: make add_to_tree() idempotent (PR #3485)
by vcill 12 Sep '23

12 Sep '23

- the function call will suceed even if the prefix being inserted already exists in the tree   #### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  PDT module initialization currently fails if you try to insert a prefix multiple times. We use kamailio as a loadbalancer and have had this change out in the field for quite some time now as our database often contains a prefix multiple times (associated with the same domain). Would it make sense to change the behavior in this case ? Thanks, Vladimir. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3485 -- Commit Summary -- * pdt: make add_to_tree() idempotent -- File Changes -- M src/modules/pdt/pdtree.c (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3485.patch https://github.com/kamailio/kamailio/pull/3485.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3485 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3485(a)github.com>

2 5

[kamailio/kamailio] Module db_postgresql not found (Issue #3196)
by MenschLink 23 Aug '23

23 Aug '23

### Description I loaded module "db_postgres.so". I expected kamilio to start. It didn't ### Troubleshooting #### Reproduction  #### config file ``` #!KAMAILIO #!define WITH_POSTGRESSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_MSGREBUILD #!define WITH_NAT #!define WITH_NATSIPPING .. . .. #!ifdef WITH_POSTGRESSQL loadmodule "db_postgres.so" #!endif ``` #### Log Messages  ``` Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [db.c:204]: db_bind_mod(): Module db_postgresql not found. Missing loadmodule? Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: usrloc [usrloc_mod.c:361]: mod_init(): failed to bind database module Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so) ``` output from ls of modules directory: ``` acc.so call_obj.so dialog.so ipops.so msrp.so presence_conference.so qos.so sipcapture.so statsd.so uid_avp_db.so acc_diameter.so carrierroute.so dialplan.so jsonrpcs.so mtree.so presence_dialoginfo.so ratelimit.so sipdump.so stun.so uid_domain.so alias_db.so cfg_db.so dispatcher.so keepalive.so nat_traversal.so presence_mwi.so regex.so sipjson.so tcpops.so uid_gflags.so app_jsdt.so cfg_rpc.so diversion.so kemix.so nathelper.so presence_profile.so registrar.so sipt.so textops.so uid_uri_db.so app_sqlang.so cfgt.so dmq.so kex.so nosip.so presence_reginfo.so rls.so siptrace.so textopsx.so uri_db.so async.so cfgutils.so dmq_usrloc.so lcr.so outbound.so presence_xml.so rr.so siputils.so timer.so userblocklist.so auth.so corex.so domain.so log_custom.so p_usrloc.so pua.so rtimer.so sl.so tm.so usrloc.so auth_db.so counters.so domainpolicy.so lrkproxy.so path.so pua_bla.so rtjson.so sms.so tmrec.so xcap_client.so auth_diameter.so ctl.so drouting.so mangler.so pdb.so pua_dialoginfo.so rtpengine.so smsops.so tmx.so xcap_server.so auth_xkeys.so db2_ops.so enum.so matrix.so pdt.so pua_reginfo.so rtpproxy.so speeddial.so topoh.so xhttp.so avp.so db_cluster.so evrexec.so maxfwd.so permissions.so pua_rpc.so sanity.so sqlops.so topos.so xhttp_prom.so avpops.so db_flatstore.so exec.so mediaproxy.so pike.so pua_usrloc.so sca.so ss7ops.so tsilo.so xhttp_rpc.so benchmark.so db_postgres.so group.so mohqueue.so pipelimit.so pua_xmpp.so sdpops.so sst.so uac.so xlog.so blst.so db_text.so htable.so mqueue.so prefix_route.so pv.so seas.so statistics.so uac_redirect.so xprint.so call_control.so debugger.so imc.so msilo.so presence.so pv_headers.so secfilter.so statsc.so uid_auth_db.so ``` ### Possible Solutions  tried renaming db_postgres.so to db_postgresql.so, but that didn't work, so I reversed it ### 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 opensips 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3196 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3196(a)github.com>

3 4

[kamailio/kamailio] fix warnings detected via codeql (PR #3497)
by Victor Seva 09 Aug '23

09 Aug '23

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3497 -- Commit Summary -- * sipcapture: use memcpy instead of strncpy for coherence * rtpproxy: use memcpy instead of strcpy for coherence -- File Changes -- M src/modules/rtpproxy/rtpproxy.c (40) M src/modules/sipcapture/sipcapture.c (16) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3497.patch https://github.com/kamailio/kamailio/pull/3497.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3497 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3497(a)github.com>

2 7

Re: Performances issue when freeing shared memory in custom module (Kamailio 5.5.2)
by Henning Westerholt 04 Aug '23

04 Aug '23

Hello, (Adding sr-dev to CC) This looks indeed a bit strange. Do you get any error messages in the log? In which process you are freeing the memory, one of the worker processes or the RPC process? You could also try to use another memory manager to see if you get better performance. There is a command line parameter to choose one during startup. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Chaigneau, Nicolas <nicolas.chaigneau(a)capgemini.com> Sent: Wednesday, January 18, 2023 6:49 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Performances issue when freeing shared memory in custom module (Kamailio 5.5.2) Hello, I'm encountering performance issues with Kamailio (5.5.2). I'm using a custom Kamailio module that loads routing data in memory, using Kamailio shared memory. This routing data is very large. It can be fully reloaded through a Kamailio RPC command (which is done once each day). When reloading, two sets of data are maintained, one "loading" and another "current" (the latter being used to handle SIP requests). When loading of the new data is finished, it is swapped to "current". Then, memory of the old (now unused) data is freed. I've noticed that when Kamailio is freeing the old data, there is a very significant performance impact on SIP requests. This is surprising to me, because the SIP requests do not use this old data. This is not a CPU issue, idle CPU% is at about 99% at that moment. I'm using the following functions : - shm_mallocxz - shm_free From what I understand, shm_free is actually "qm_shm_free" defined in "src\core\mem\q_malloc.c" (the default shared memory manager being "qm"). I've noticed that there is also a variant shm_free_unsafe ("qm_free"), which does not perform locking. I'm wondering if the lock could be the cause of my performances issues ? (But I'm not sure how this could be possible, because although the SIP requests need to access the shared memory allocated, they do not use directly the functions from the share memory manager.) If the performances issues are causes by the lock, could I use the unsafe version "safely" ? (considering that it is guaranteed that the old data cannot be used by anyone else) Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

3 13

[kamailio/kamailio] Kamailio sending CCR TERMINATE request without waiting for the CCR INITIAL request response (#2143)
by harishyadav1465 03 Aug '23

03 Aug '23

**Description** We are using ims_charging module and Freediameter as diameter server for billing process....recently we faced one issue...For Initial **INVITEs** kamailio sending **CCR request (INITIAL_REQUEST)** to **diameter server** but if we receive Immediate **CANCLE** for the **INVITE**, kamailio sending **CCR request ( TERMINATE_REQUEST )** without waiting for the **CCR request (INITIAL_REQUEST) response** from the **Diameter server.**.. **Expected behavior** Kamailio has to send **CCR request ( TERMINATE_REQUEST )** after getting the **response** from the **INITIAL_REQUEST.** **Additional Info** kamailio server : 4.2 platform : 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/2143

3 6

[kamailio/kamailio] siptrace: frong IPv4 address value (#2092)
by sergey-safarov 30 Jul '23

30 Jul '23

### Description Please check attached pcap. [siptrace.pcap.gz](https://github.com/kamailio/kamailio/files/3688791/siptra… Kamailio send INVITE (packet 1) from port `TCP/42394`. SIP trace encapsulate INVITE (packet 2) and encodes Kamailio source port `TCP/5060` #### Debugging Data HEP header parsed by lua [disector](https://github.com/sipcapture/hep-wireshark) ``` HEP3 Protocol HEP ID: HEP3 Length (Bytes): 1574 Protocol family: IPv4 Protocol ID: TCP Source IPv4 address: 172.21.0.131 Destination IPv4 address: 192.168.57.11 Source port: 5060 Destination port: 5060 Timestamp: 1570150645 Timestamp us: 740165 Protocol Type: SIP Capture ID: 1 Payload [truncated]: INVITE sip:911@192.168.57.11;transport=tcp SIP/2.0\r\nRecord-Route: <sip:172.21.0.131;transport=tcp;lr=on;ftag=KvNj7jXrmK89p>\r\nVia: SIP/2.0/TCP 172.21.0.131;branch=z9hG4bK7c2d.2d8104273b7063309f5694ac963c9ad8.0;i=21 ``` [HEP format description located here](https://github.com/sipcapture/HEP/blob/master/docs/HEP3_Network_Proto…. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` / # kamailio -v version: kamailio 5.1.6 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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 on 11:01:40 Oct 4 2018 with gcc 6.4.0 ``` * **Operating System**: Docker container Userland ``` / # cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.8.1 PRETTY_NAME="Alpine Linux v3.8" HOME_URL="http://alpinelinux.org" BUG_REPORT_URL="http://bugs.alpinelinux.org" ``` Kernel Amazon Linux 2 ``` / # uname -a Linux proxy-dc0-0 4.14.128-112.105.amzn2.x86_64 #1 SMP Wed Jun 19 16:53:40 UTC 2019 x86_64 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/2092

2 7

[kamailio/kamailio] Typos (PR #3491)
by Дилян Палаузов 14 Jul '23

14 Jul '23

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3491 -- Commit Summary -- * mohqueue: typo * osp: typos * p_usrloc: typo * permissions: typos * pike: typo * presence: typo * qos: typos * ratelimit: typo * regex: typos * registrar: typos and formatting * rls: typos * rr: typo * rtimer: typo * rtp_media_server: typos * ruxc: typos * sca: typos * seas: typo * snmpstats: typos * statsd: typo * tcpops: typos * textops: typos -- File Changes -- M src/modules/mohqueue/doc/mohqueue_admin.xml (2) M src/modules/osp/destination.c (2) M src/modules/osp/doc/osp_admin.xml (4) M src/modules/osp/orig_transaction.c (2) M src/modules/osp/osp_mod.c (2) M src/modules/osp/osptoolkit.h (2) M src/modules/p_usrloc/udomain.c (2) M src/modules/permissions/trusted.c (4) M src/modules/permissions/trusted.h (2) M src/modules/pike/doc/pike_devel.xml (2) M src/modules/presence/doc/presence_admin.xml (2) M src/modules/qos/doc/qos_devel.xml (6) M src/modules/qos/qos.c (2) M src/modules/qos/qos_cb.c (4) M src/modules/qos/qos_handlers.c (2) M src/modules/ratelimit/doc/ratelimit_admin.xml (2) M src/modules/regex/regex_mod.c (6) M src/modules/registrar/doc/registrar_admin.xml (21) M src/modules/registrar/lookup.c (4) M src/modules/registrar/save.c (2) M src/modules/registrar/save.h (2) M src/modules/rls/notify.c (2) M src/modules/rls/resource_notify.c (6) M src/modules/rls/rls.c (4) M src/modules/rls/subscribe.c (2) M src/modules/rr/doc/rr_devel.xml (2) M src/modules/rtimer/doc/rtimer_admin.xml (2) M src/modules/rtp_media_server/doc/rtp_media_server_admin.xml (4) M src/modules/rtp_media_server/rms_sdp.c (2) M src/modules/rtp_media_server/rtp_media_server.c (6) M src/modules/ruxc/doc/ruxc_admin.xml (8) M src/modules/sca/sca_call_info.c (2) M src/modules/sca/sca_subscribe.c (4) M src/modules/sca/sca_util.c (2) M src/modules/seas/event_dispatcher.c (2) M src/modules/snmpstats/snmpObjects.c (2) M src/modules/snmpstats/snmpstats.c (2) M src/modules/statsd/doc/statsd_admin.xml (2) M src/modules/tcpops/doc/params.xml (2) M src/modules/tcpops/doc/tcpops.xml (2) M src/modules/textops/api.h (2) M src/modules/textops/doc/textops_admin.xml (2) M src/modules/textopsx/api.h (2) M src/modules/textopsx/doc/functions.xml (12) M src/modules/textopsx/textopsx.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3491.patch https://github.com/kamailio/kamailio/pull/3491.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3491 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3491(a)github.com>

2 1

[kamailio/kamailio] siptrace: fix pseudo var direction attribute length (PR #3489)
by Mvondo Eric 13 Jul '23

13 Jul '23

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3489 -- Commit Summary -- * siptrace: fix pseudo var direction attribute length -- File Changes -- M src/modules/siptrace/siptrace.c (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3489.patch https://github.com/kamailio/kamailio/pull/3489.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3489 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3489(a)github.com>

2 3

[kamailio/kamailio] NATS Module not working (Issue #3253)
by iliesh 10 Jul '23

10 Jul '23

### Description Trying to get NATS module working but Kamailio is refusing to start. ``` Sep 27 23:08:27 server kernel: kamailio[338880]: segfault at 70 ip 00007fe97b06f1cc sp 00007fff72d158f0 error 4 in libuv.so.1.0.0[7fe97b066000+1f000] Sep 27 23:08:27 server kernel: Code: 5a 85 ff ff b8 ea ff ff ff c3 0f 1f 40 00 f3 0f 1e fa 8b 4e 30 83 f9 ff 0f 84 80 00 00 00 48 83 ec 08 85 c9 0f 88 90 00 00 00 <3b> 4f 70 73 45 f7 d2 21 56 28 48 8d 4e 18 48 89 f0 48 8b 76 18 75 Sep 27 23:08:27 server systemd[1]: Started Process Core Dump (PID 338886/UID 0). ``` #### Log Messages In the log message I'm getting the following error: ``` INFO: nats [nats_mod.c:437]: nats_init_connection(): adding server [nats://192.168.1.1:4222] [1] ERROR: nats [nats_mod.c:456]: nats_init_connection(): could not create nats options [System Error] ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (version: kamailio 5.6.1 (x86_64/linux) 34e6dd) ``` NATS Server version: ``` nats-server: v2.9.0 ``` libnats version: ``` libnats.so.3.4.0 ``` * **Operating System**: ``` CentOS Stream 9 5.14.0-163.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 8 13:52:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ``` * **Module Configuration**: ``` loadmodule "nats.so" modparam("nats", "nats_url", "nats://192.168.1.1:4222") ``` There is no issue at the network/firewall level as by using telnet I'm able to connect to the NATS server successfully. What is weird is that with tcpdump I can't see even attempts to connect to the NATS server. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3253 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3253(a)github.com>

5 31

[kamailio/kamailio] tlsa + OpenSSL 3.0.5: multiple unpredictable shm corruption (Issue #3222)
by space88man 08 Jul '23

08 Jul '23

### Description * kamailio 5.6.1 on AlmaLinux 9 and OpenSSL 3.0.5 * Used tlsa to separate the OS version of OpenSSL (which is 3.0.1). The same issue happens with the OS version of OpenSSL * Generating TLS client traffic * The issue will occur at about 25 conn/sec * Multiple unpredicatable types of shm corruption ### Troubleshooting * No issue with tlsa + OpenSSL 1.1.1q; the module can sustain 50 conn/sec up to 500 persistent connections. #### Reproduction 1. Used kamailio configuration from the outbound module documentation; i.e., configure kamailio as a TLS edge proxy. To isolate the registrar is another kamailio system 1. Use a SIP load tester to generate REGISTER traffic(Expires: 600) ; at the end of the REGISTER, keep the connection alive and reREGISTER at 300 secs. 1. Generate traffic at > 25 conn/sec (with < 25 conn/sec the test usually succeeds) #### Debugging Data BT in comments below #### Log Messages #### SIP Traffic ### Possible Solutions ### Additional Information 5.6.1 * **Operating System**: AlmaLinux 9, with (OS) OpenSSL 3.0.1. I used tlsa + OpenSSL 3.0.5 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3222 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3222(a)github.com>

4 16

[kamailio/kamailio] Kamailio Random Crash Alert - 5.4.7 (Issue #3186)
by hardikpatel89 07 Jul '23

07 Jul '23

### Description -- Hello Team, We are using Kamailio 5.4.7 and we found there is a random crash. We have observed the core logs and we noticed it is due to some of the RPC events. We have noticed it has been crashed from the "ctl handler" process. -- #### Debugging Data -- Core dump files are attached. [core-7519.txt](https://github.com/kamailio/kamailio/files/9099633/core-7519… [core-17582.txt](https://github.com/kamailio/kamailio/files/9099634/core-175… [core-7519.txt](https://github.com/kamailio/kamailio/files/9099638/core-7519… [core-17582.txt](https://github.com/kamailio/kamailio/files/9099639/core-175… -- ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.7 (x86_64/linux) a19fe1 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: a19fe1 compiled on 02:56:57 Feb 16 2022 with gcc 8.3.0 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3186 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3186(a)github.com>

3 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2023