sr-dev May 2025

sr-dev@lists.kamailio.org

15 participants
192 discussions

[kamailio/kamailio] siptrace: sip_trace_mode("d") not working (Issue #4178)
by c.long 04 Jul '25

04 Jul '25

longchun4835 created an issue (kamailio/kamailio#4178)  ### Description Using function sip_trace_mode() with parameter d to enable dialog tracing mode logs: ``` BUG: siptrace [siptrace.c:1671]: add_info_xavp(): URI should be in raw format here ERROR: siptrace [siptrace.c:888]: sip_trace_helper(): failed to serialize siptrace info! Won't trace dialog! ``` ### Troubleshooting #### Reproduction my module parameters: ``` #!ifdef WITH_HOMER loadmodule "siptrace.so" modparam("siptrace", "duplicate_uri", HOMER_URL) modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "hep_capture_id", HOMER_HEP_ID) #!endif ... request_route { ... if (is_method("INVITE")) { sip_trace_mode("d"); } } ``` ### Possible Solutions I checked the source code and found that the issue occurs when sip_trace_helper() is called inside the ki_sip_trace_mode() function, with the third parameter (duri) set to NULL. I don’t quite understand the logic behind passing NULL does this mean that the 'D' parameter will never working when calling sip_trace_mode()? Additionally, I have another question: in the sip_trace_helper() function, why does it call trace_transaction() instead of trace_dialog() when strace_type == SIPTRACE_DIALOG? ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.4 (x86_64/linux) a004cf 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 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: a004cf compiled on 09:14:30 Jan 23 2025 with gcc 8.3.1 ``` * **Operating System**: ``` NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4178 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4178(a)github.com>

3 4

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

03 Jul '25

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

2 7

[kamailio/kamailio] SIP Race condition when using dlg.end_dlg (Issue #4268)
by IgorG 02 Jul '25

02 Jul '25

IgorrG created an issue (kamailio/kamailio#4268) ### Description We use RPC dlg.end_dlg command to terminate dialog. In most cases it does operate properly and send BYE from kamailio to both sides of dialog (as show on screenshot). ![Image](https://github.com/user-attachments/assets/b49164a5-6442-4c66-bd4d-f5412678247f) We found that in some cases we have only first BYE sent to calling party. Second BYE never sent, when called party tries to terminate call by timeout it get responded with 481. ![Image](https://github.com/user-attachments/assets/10c90b4c-30a3-4123-8e2b-2ca64cdec3c3) ![Image](https://github.com/user-attachments/assets/f0facce8-3acf-4049-8a23-ad559874af7b) In logs we have such warning: мая 27 15:11:46 service-proxy.iqtek.ru kamailio[3518388]: 2(3518388) WARNING: {1 1 BYE 541d3f2c-43fd-43b6-af24-bad1fbf85eb6} dialog [dlg_handlers.c:1343]: dlg_onroute(): unable to find dialog for BYE with route param 'e1e.4f22' [3614:8948] and call-id '541d3f2c-43fd-43b6-af24-bad1fbf85eb6' We also found that in this case this warning shown in logs 0.04 seconds after kamailio receive 200ok. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` # ./kamailio -V version: kamailio 5.8.6 (x86_64/linux) fb71db flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: fb71db compiled on 17:38:27 May 26 2025 with gcc 12.2.0 ``` * **Operating System**: ``` # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm # uname -a Linux rtp-kamailio2 6.1.0-32-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.129-1 (2025-03-06) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4268 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4268(a)github.com>

2 1

[kamailio/kamailio] branch_failure_route does not handle reply while wt_timer period (Issue #4266)
by IgorG 01 Jul '25

01 Jul '25

IgorrG created an issue (kamailio/kamailio#4266) ### Description While implementing mid-register inspired by pull request (https://github.com/kamailio/kamailio/pull/3360) we found the case when it goes impossible to handle responses for registrar servers. In case some of registrars busy and respond with 401 after 200ok received - it is not possible using any routes and configuration options to handle responses received in branch transactions. According to documentation I think that setting wt_timer should allow to absorb and handle responses on failure-route while transaction kept in memory. In fact wt_timer does not affect handling responses in any way. ![Image](https://github.com/user-attachments/assets/14feb472-91ea-4028-8780-1fee1d4ee0e8) ### Troubleshooting To reproduce this case we have configured sipp to response instant with 200ok on registration request. #### Reproduction To reproduce issue SIPP could be setup as one of the dispatcher nodes with instant 200ok reply to register. Kamailio should use following configuration snippet: https://github.com/ovoshlook/kamailio-mid-registrar-config-snippets/blob/ma… #### Log Messages REGISTER|401tm [t_lookup.c:912]: t_reply_matching(): t_reply_matching: hash 12337 label 0 branch 1 REGISTER|401tm [t_lookup.c:986]: t_reply_matching(): reply (0x7f1fc67f83a8) matched an active transaction (T=0x7f1fc0f0f740)! REGISTER|401tm [t_lookup.c:1122]: t_check_msg(): msg (0x7f1fc67f83a8) id=13/1915035 global id=13/1915035 T end=0x7f1fc0f0f740 REGISTER|401tm [t_reply.c:2363]: reply_received(): transaction found - T:0x7f1fc0f0f740 branch:1 REGISTER|401tm [t_reply.c:2376]: reply_received(): original status uas=200, uac[1]=0 local=0 is_invite=0) REGISTER|401tm [t_reply.c:1363]: t_should_relay_response(): ->>>>>>>>> T_code=200, new_code=401 REGISTER|401tm [t_reply.c:1374]: t_should_relay_response(): final reply already sent REGISTER|401tm [t_reply.c:1625]: t_should_relay_response(): finished with rps discarded - uas status: 200 ### Possible Solutions  ### Additional Information * **Kamailio Version** ``` 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 on 16:35:08 Jun 5 2023 with gcc 10.2.1 ``` * **Operating System**: ``` No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux pbxKamaTest 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4266 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4266(a)github.com>

3 2

[kamailio/kamailio] [Websocket] websocket:closed sometimes is not fired (Issue #3950)
by Gustavo Almeida 27 Jun '25

27 Jun '25

### Description After carrying out some load tests using the `Websocket` module, I noticed that sometimes the `websocket:closed` event is not triggered. This problem seems to be particularly noticeable when the load is high and simultaneous. Example: 1000 records simultaneously. In the tests carried out, I realized that the number of times the event is not triggered is small, in the order of [1-10]/1000. I check that when I do a `ws.dump` I don't have any active connections, and I confirm that they are all effectively cleaned (`netstat -ano | grep 8061`). However, the event is not triggered for some connections. I can see this in the logs, and also when i display the content of an hash table, i'm dropping key inside `websocket:closed` event. ### Troubleshooting The troubleshooting was simplistic, i.e. I ran the same test n times, and validated that the event was triggered for all connections, the number of `ws` connections listed by `Kamailio`, and the open connections. #### Reproduction To reproduce, we can use any mechanism that emulates the use of the `Websocket` module. For example, I used the `sipexer` tool to create a `wss` connection with `Kamailio`, forcing simultaneous registrations. Example command: `sipexer -cb -mt register -ex 60 -au <user> -ap <pass> -fuser example -fd mydomain -wso https://10.0.0.12:10000 -ruri sip:kamailio -su wss://kamailio:8061` Kamailio TLS listener: `listen=tls:10.0.0.12:8061 advertise PUBLIC_IP` Websocket module: ``` loadmodule "websocket.so" tcp_accept_no_cl=yes ``` ``` event_route[websocket:closed] { xlog("L_NOTICE", "WebSocket connection closed $proto:$si:$sp\n"); <I also delete where a htable key> } ``` #### Debugging Data ``` [root@ ~]$ prcmd ws.dump { connections: { } info: { wscounter: 0 truncated: no } } [root@ ~]$ netstat -ano | grep 8061 tcp 0 0 10.0.0.12:8061 0.0.0.0:* LISTEN off (0.00/0/0) [root ~]$ prcmd htable.dump wsauth | grep "name" | wc -l 3 [root ~]$ cat /var/log/kamailio.log | grep "WebSocket connection closed" | wc -l 997 [root ~]$ cat /var/log/proxy-registrar/proxy-registrar.log | grep "ERR" | grep "WAR" | wc -l 0 ``` #### Log Messages Nothing relevant. #### SIP Traffic Nothing relevant here, the SIP Flow is OK. ### Additional Information ``` version: kamailio 5.6.4 (x86_64/linux) a004cf-dirty 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 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: a004cf -dirty compiled on 23:17:27 Jun 7 2024 with gcc 4.8.5 ``` * **Operating System**: ``` CentOS Linux release 7.9.2009 (Core) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3950 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3950(a)github.com>

6 7

[kamailio/kamailio] tcp_main : Crash on local_timer_list_expire (Issue #4238)
by ctylihuai 27 Jun '25

27 Jun '25

ctylihuai created an issue (kamailio/kamailio#4238) ### Description The Kamailio “P” node responsible for 5G messaging encountered an unhandled exception and generated a core dump during operation . This node had been continuously running for over one month (34 days) without any issues, and the failure occurred only once . As of now, no reproducible steps have been identified to trigger the problem again ### Troubleshooting #### Reproduction It cannot be reproduced for the time being #### Debugging Data ``` (gdb) bt full #0 0x0000aaaac25ffd10 in local_timer_list_expire (l=0xaaaac29ef340 <tcp_main_ltimer>, t=1691001057, h=0xaaaac2a10158 <tcp_main_ltimer+134680>) at core/local_timer.c:193 tl = 0xaaaac2a7b528 <tcp_reader_ltimer+197384> ret = 0 #1 0x0000aaaac25ffe98 in local_timer_expire (h=0xaaaac29ef340 <tcp_main_ltimer>, t=1691001057) at core/local_timer.c:222 No locals. #2 0x0000aaaac260031c in local_timer_run (lt=0xaaaac29ef340 <tcp_main_ltimer>, saved_ticks=1691001057) at core/local_timer.c:245 __func__ = "local_timer_run" #3 0x0000aaaac2552bec in tcp_timer_run () at core/tcp_main.c:4875 ticks = 1691001057 #4 0x0000aaaac2555074 in tcp_main_loop () at core/tcp_main.c:5060 si = 0x0 r = 48 __func__ = "tcp_main_loop" #5 0x0000aaaac23d24b0 in main_loop () at main.c:1945 i = 48 pid = 0 si = 0x0 si_desc = "udp receiver child=47 sock=10.185.16.12:5060\000\000\000\000\000\027\065\215sw\247\235\060\346\256\310\377\377\000\000|\312p\302\252\252\000\000@\346\256\310\377\377\000\000\000\263\252\302\252\252\000\000\200\346\256\310\377\377\000\000\n\000\000\000\000\000\000\000\200\346\256\310\377\377\000\000\250\345=\302\252\252\000\000\200\346\256\310\377\377\000" nrprocs = 48 woneinit = 1 __func__ = "main_loop" #6 0x0000aaaac23de5f4 in main (argc=19, argv=0xffffc8aeebe8) at main.c:3212 cfg_stream = 0xaaaafeb0d260 c = -1 r = 0 tmp = 0xffffc8aefe85 "" tmp_len = -1484867064 port = 65535 proto = -1487420584 ahost = 0x0 aport = 0 options = 0xaaaac28ec2a0 ":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 = 3762187974 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 ---Type <return> to continue, or q <return> to quit--- n_lst = 0xffffc8aee8f8 p = 0x0 st = {st_dev = 64772, st_ino = 4298835, st_mode = 16877, st_nlink = 2, st_uid = 103, st_gid = 105, st_rdev = 0, __pad1 = 0, st_size = 6, st_blksize = 4096, __pad2 = 0, st_blocks = 0, st_atim = { tv_sec = 0, tv_nsec = 0}, st_mtim = {tv_sec = 1733885384, tv_nsec = 0}, st_ctim = {tv_sec = 1737443001, tv_nsec = 2493470}, __glibc_reserved = {0, 0}} tbuf = "\210\351\256\310\377\377\000\000\204\351\256\310\377\377\000\000\002\b \200\002\b \200\260\351\256\310\377\377\000\000\234\303~\247\377\377\000\000\230e;\330\000\000\000\000\310*\201\247\377\377\000\000\330\fi\247\377\377\000\000\310\352\256\310\377\377\000\000\070\353\256\310\377\377\000\000\000\000\000\000\000\000\000\000@'\201\247\377\377\000\000\000\000\000\000\000\000\000\000X\352\256\310\377\377\000\000h\352\256\310\377\377\000\000\001", '\000' <repeats 15 times>, "\230e;\330\000\000\000\000h'\201\247\377\377\000\000\000\000\000\000\000\000\000\000X\352\256\310\377\377\000\000h\352\256\310\377\377\000\000\320\352\256\310\377\377\000\000\330\fi\247\377\377\000\000\210\351\256\310\377\377\000\000"... option_index = 12 long_options = {{name = 0xaaaac28ee678 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0xaaaac28e9410 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0xaaaac28ee680 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0xaaaac28ee688 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0xaaaac28ee690 "substdef", has_arg = 1, flag = 0x0, val = 1026}, { name = 0xaaaac28ee6a0 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0xaaaac28ee6b0 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0xaaaac28ee6c0 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0xaaaac28ee6d0 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0xaaaac28ee6e0 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, { name = 0xaaaac28ee6f0 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0xaaaac28ee6f8 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0xaaaac28ee708 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0xaaaac28ee710 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) p tl $30 = (struct timer_ln *) 0xaaaac2a7b528 <tcp_reader_ltimer+197384> (gdb) p *tl $31 = {next = 0x0, prev = 0xaaaac2a10158 <tcp_main_ltimer+134680>, expire = 0, initial_timeout = 0, data = 0x0, f = 0x0, flags = 0, slow_idx = 0} (gdb) p *h $10 = {next = 0x0, prev = 0xfff8adcef5d8} 循环打印 h->prev内容 $177 = (struct timer_ln *) 0xaaaac2a10158 <tcp_main_ltimer+134680> next = 0x0, prev = 0xfff8adcef5d8 $178 = (struct timer_ln * volatile) 0xfff8adcef5d8 next = 0xaaaac2a10158 <tcp_main_ltimer+134680>, prev = 0xfff9437ede60 $179 = (struct timer_ln *) 0xfff9437ede60 next = 0xfff8adcef5d8, prev = 0xfffa58c31970 $180 = (struct timer_ln *) 0xfffa58c31970 next = 0xfff9437ede60, prev = 0xaaaac2a1bd48 $181 = (struct timer_ln *) 0xaaaac2a1bd48 <tcp_main_ltimer+182792> next = 0xfffa58c31970, prev = 0xfffa53da92a8 $182 = (struct timer_ln *) 0xfffa53da92a8 next = 0xaaaac2a1bd48 <tcp_main_ltimer+182792>, prev = 0xfff96e22e0e0 $183 = (struct timer_ln *) 0xfff96e22e0e0 next = 0xfffa53da92a8, prev = 0xfffa4f642a28 $184 = (struct timer_ln *) 0xfffa4f642a28 next = 0xfff96e22e0e0, prev = 0xfff880261368 $185 = (struct timer_ln *) 0xfff880261368 next = 0xfffa4f642a28, prev = 0xfff99e55db30 $186 = (struct timer_ln *) 0xfff99e55db30 next = 0xfff880261368, prev = 0xfff99fe12eb0 $187 = (struct timer_ln *) 0xfff99fe12eb0 next = 0xfff99e55db30, prev = 0xfffa7f14dfa8 $188 = (struct timer_ln *) 0xfffa7f14dfa8 next = 0xfff99fe12eb0, prev = 0xaaaac2a21658 <tcp_main_ltimer+205592 $189 = (struct timer_ln *) 0xaaaac2a21658 <tcp_main_ltimer+205592> next = 0xfffa7f14dfa8, prev = 0xfff82902dfb8 $190 = (struct timer_ln *) 0xfff82902dfb8 next = 0xaaaac2a21658 <tcp_main_ltimer+205592>, prev = 0xfffa3728f340 $191 = (struct timer_ln *) 0xfffa3728f340 next = 0xfff82902dfb8, prev = 0xfff8f0b5ec40 $192 = (struct timer_ln *) 0xfff8f0b5ec40 next = 0xfffa3728f340, prev = 0xfffaa900c338 $193 = (struct timer_ln *) 0xfffaa900c338 next = 0xfff8f0b5ec40, prev = 0xfff888f53088 $194 = (struct timer_ln *) 0xfff888f53088 next = 0xfffaa900c338, prev = 0xfff79d06ff60 $195 = (struct timer_ln *) 0xfff79d06ff60 next = 0xfff888f53088, prev = 0xfff8eea80ff8 $196 = (struct timer_ln *) 0xfff8eea80ff8 next = 0xfffa38e4f870, prev = 0xfff83d1a6a18 $197 = (struct timer_ln *) 0xfff83d1a6a18 next = 0xfff8eea80ff8, prev = 0xfffa5c69fb48 $198 = (struct timer_ln *) 0xfffa5c69fb48 next = 0xfff83d1a6a18, prev = 0xfff8b5c31c58 $199 = (struct timer_ln *) 0xfff8b5c31c58 next = 0xfffa5c69fb48, prev = 0xfff9a4ac6688 $200 = (struct timer_ln *) 0xfff9a4ac6688 next = 0xfff8b5c31c58, prev = 0xfff9e3ee0200 $201 = (struct timer_ln *) 0xfff9e3ee0200 next = 0xfff9a4ac6688, prev = 0xaaaac2a267b8 $202 = (struct timer_ln *) 0xaaaac2a267b8 <tcp_main_ltimer+226424> next = 0xfff9e3ee0200, prev = 0xfff9b6b00188 $203 = (struct timer_ln *) 0xfff9b6b00188 next = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, prev = 0xfffa38e4f870 $204 = (struct timer_ln *) 0xfffa38e4f870 next = 0xfff9b6b00188, prev = 0xfff8eea80ff8 $205 = (struct timer_ln *) 0xfff8eea80ff8 next = 0xfffa38e4f870, prev = 0xfff83d1a6a18 $206 = (struct timer_ln *) 0xfff83d1a6a18 next = 0xfff8eea80ff8, prev = 0xfffa5c69fb48 $207 = (struct timer_ln *) 0xfffa5c69fb48 next = 0xfff83d1a6a18, prev = 0xfff8b5c31c58 $208 = (struct timer_ln *) 0xfff8b5c31c58 next = 0xfffa5c69fb48, prev = 0xfff9a4ac6688 $209 = (struct timer_ln *) 0xfff9a4ac6688 next = 0xfff8b5c31c58, prev = 0xfff9e3ee0200 $210 = (struct timer_ln *) 0xfff9e3ee0200 next = 0xfff9a4ac6688, prev = 0xaaaac2a267b8 <tcp_main_ltimer+226424> $211 = (struct timer_ln *) 0xaaaac2a267b8 <tcp_main_ltimer+226424> next = 0xfff9e3ee0200, prev = 0xfff9b6b00188 $212 = (struct timer_ln *) 0xfff9b6b00188 next = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, prev = 0xfffa38e4f870 $213 = (struct timer_ln *) 0xfffa38e4f870 next = 0xfff9b6b00188, prev = 0xfff8eea80ff8 (gdb) set $node = h->prev (gdb) while ($node != 0) >print *$node >set $node = $node->prev >end $50 = {next = 0xaaaac2a10158 <tcp_main_ltimer+134680>, prev = 0xfff9437ede60, expire = 1691004064, initial_timeout = 5760, data = 0xfff8adcef430, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $51 = {next = 0xfff8adcef5d8, prev = 0xfffa58c31970, expire = 1691004064, initial_timeout = 5760, data = 0xfff9437edcb8, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $52 = {next = 0xfff9437ede60, prev = 0xaaaac2a1bd48 <tcp_main_ltimer+182792>, expire = 1691004064, initial_timeout = 5760, data = 0xfffa58c317c8, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $53 = {next = 0xfffa58c31970, prev = 0xfffa53da92a8, expire = 3125221032, initial_timeout = 65529, data = 0xfffa51099620, f = 0xfff7f9d36838, flags = 4191381560, slow_idx = 65527} $54 = {next = 0xaaaac2a1bd48 <tcp_main_ltimer+182792>, prev = 0xfff96e22e0e0, expire = 1691004064, initial_timeout = 5760, data = 0xfffa53da9100, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $55 = {next = 0xfffa53da92a8, prev = 0xfffa4f642a28, expire = 1691004064, initial_timeout = 5760, data = 0xfff96e22df38, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $56 = {next = 0xfff96e22e0e0, prev = 0xfff880261368, expire = 1691004064, initial_timeout = 5760, data = 0xfffa4f642880, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $57 = {next = 0xfffa4f642a28, prev = 0xfff99e55db30, expire = 1691005489, initial_timeout = 5760, data = 0xfff8802611c0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $58 = {next = 0xfff880261368, prev = 0xfff99fe12eb0, expire = 1691005489, initial_timeout = 5760, data = 0xfff99e55d988, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $59 = {next = 0xfff99e55db30, prev = 0xfffa7f14dfa8, expire = 1691005489, initial_timeout = 5760, data = 0xfff99fe12d08, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $60 = {next = 0xfff99fe12eb0, prev = 0xaaaac2a21658 <tcp_main_ltimer+205592>, expire = 1691005489, initial_timeout = 5760, data = 0xfffa7f14de00, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $61 = {next = 0xfffa7f14dfa8, prev = 0xfff82902dfb8, expire = 888530032, initial_timeout = 65528, data = 0xfff81b870028, f = 0xfff798f80cc0, flags = 522077992, slow_idx = 65529} $62 = {next = 0xaaaac2a21658 <tcp_main_ltimer+205592>, prev = 0xfffa3728f340, expire = 1691005489, initial_timeout = 5760, data = 0xfff82902de10, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $63 = {next = 0xfff82902dfb8, prev = 0xfff8f0b5ec40, expire = 1691005489, initial_timeout = 5760, data = 0xfffa3728f198, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $64 = {next = 0xfffa3728f340, prev = 0xfffaa900c338, expire = 1691005489, initial_timeout = 5760, data = 0xfff8f0b5ea98, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $65 = {next = 0xfff8f0b5ec40, prev = 0xfff888f53088, expire = 1691005489, initial_timeout = 5760, data = 0xfffaa900c190, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $66 = {next = 0xfffaa900c338, prev = 0xfff79d06ff60, expire = 1691005489, initial_timeout = 5760, data = 0xfff888f52ee0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $67 = {next = 0xfff888f53088, prev = 0xfff8eea80ff8, expire = 1691005489, initial_timeout = 5760, data = 0xfff79d06fdb8, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $68 = {next = 0xfffa38e4f870, prev = 0xfff83d1a6a18, expire = 1691006791, initial_timeout = 5760, data = 0xfff8eea80e50, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $69 = {next = 0xfff8eea80ff8, prev = 0xfffa5c69fb48, expire = 1691006791, initial_timeout = 5760, data = 0xfff83d1a6870, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $70 = {next = 0xfff83d1a6a18, prev = 0xfff8b5c31c58, expire = 1691006791, initial_timeout = 5760, data = 0xfffa5c69f9a0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $71 = {next = 0xfffa5c69fb48, prev = 0xfff9a4ac6688, expire = 1691006791, initial_timeout = 5760, data = 0xfff8b5c31ab0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $72 = {next = 0xfff8b5c31c58, prev = 0xfff9e3ee0200, expire = 1691006791, initial_timeout = 5760, data = 0xfff9a4ac64e0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $73 = {next = 0xfff9a4ac6688, prev = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, expire = 1691006791, initial_timeout = 5760, data = 0xfff9e3ee0058, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $74 = {next = 0xfff9e3ee0200, prev = 0xfff9b6b00188, expire = 1429254648, initial_timeout = 65528, data = 0xfff88564eb80, f = 0xfff9cc7da958, flags = 881566008, slow_idx = 65529} $75 = {next = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, prev = 0xfffa38e4f870, expire = 1691006791, initial_timeout = 5760, data = 0xfff9b6afffe0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $76 = {next = 0xfff9b6b00188, prev = 0xfff8eea80ff8, expire = 1691006791, initial_timeout = 5760, data = 0xfffa38e4f6c8, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $77 = {next = 0xfffa38e4f870, prev = 0xfff83d1a6a18, expire = 1691006791, initial_timeout = 5760, data = 0xfff8eea80e50, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $78 = {next = 0xfff8eea80ff8, prev = 0xfffa5c69fb48, expire = 1691006791, initial_timeout = 5760, data = 0xfff83d1a6870, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $79 = {next = 0xfff83d1a6a18, prev = 0xfff8b5c31c58, expire = 1691006791, initial_timeout = 5760, data = 0xfffa5c69f9a0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $80 = {next = 0xfffa5c69fb48, prev = 0xfff9a4ac6688, expire = 1691006791, initial_timeout = 5760, data = 0xfff8b5c31ab0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $81 = {next = 0xfff8b5c31c58, prev = 0xfff9e3ee0200, expire = 1691006791, initial_timeout = 5760, data = 0xfff9a4ac64e0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} ---Type <return> to continue, or q <return> to quit--- $82 = {next = 0xfff9a4ac6688, prev = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, expire = 1691006791, initial_timeout = 5760, data = 0xfff9e3ee0058, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} $83 = {next = 0xfff9e3ee0200, prev = 0xfff9b6b00188, expire = 1429254648, initial_timeout = 65528, data = 0xfff88564eb80, f = 0xfff9cc7da958, flags = 881566008, slow_idx = 65529} $84 = {next = 0xaaaac2a267b8 <tcp_main_ltimer+226424>, prev = 0xfffa38e4f870, expire = 1691006791, initial_timeout = 5760, data = 0xfff9b6afffe0, f = 0xaaaac2551690 <tcpconn_main_timeout>, flags = 512, slow_idx = 0} ``` #### Log Messages ``` 2025-05-02T05:39:54.151913300Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([49.69.41.98]:36121 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.152035620Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff7cd0a8ba0 r: 0xfff7cd0a8cc8 (-1) 2025-05-02T05:39:54.152046140Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([110.252.23.203]:27380 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.152053220Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff9a1658f08 r: 0xfff9a1659030 (-1) 2025-05-02T05:39:54.152067100Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([240e:440:1b18:1fb3:22:da32:6be9:33e7]:50529 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [240e:954:2000:208::31]:5460) 2025-05-02T05:39:54.152468020Z 90(137) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([124.236.136.161]:13636 ->90(137) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.152535370Z 87(134) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([111.61.229.67]:41796 ->87(134) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.152895350Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfffa8d174330 r: 0xfffa8d174458 (-1) 2025-05-02T05:39:54.152916500Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([240e:440:9a08:24:1444:71da:9ff4:a6e6]:57851 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [240e:954:2000:208::31]:5460) 2025-05-02T05:39:54.153179200Z 90(137) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfffa45cedc18 r: 0xfffa45cedd40 (-1) 2025-05-02T05:39:54.153425390Z 87(134) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfffa22771e70 r: 0xfffa22771f98 (-1) 2025-05-02T05:39:54.153520770Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff83da65638 r: 0xfff83da65760 (-1) 2025-05-02T05:39:54.153540580Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([2408:8431:6810:2e2:1cbb:1c9e:63e6:abf1]:61717 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [240e:954:2000:208::31]:5260) 2025-05-02T05:39:54.154460230Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff7ccf40938 r: 0xfff7ccf40a60 (-1) 2025-05-02T05:39:54.154502480Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([123.182.115.202]:21533 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.154629490Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff89ae41378 r: 0xfff89ae414a0 (-1) 2025-05-02T05:39:54.154649140Z 84(131) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection timed out (110) ([183.199.201.13]:3125 ->84(131) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.154830180Z 84(131) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff9acc5d970 r: 0xfff9acc5da98 (-1) 2025-05-02T05:39:54.173624940Z 90(137) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff7de186590 r: 0xfff7de1866b8 (-1) 2025-05-02T05:39:54.325541260Z 117(164) ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection reset by peer (104) ([171.114.149.119]:18629 ->117(164) ERROR: <core> [core/tcp_read.c:299]: tcp_read_data(): -> [10.185.18.67]:5260) 2025-05-02T05:39:54.325597230Z 117(164) ERROR: <core> [core/tcp_read.c:1556]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0xfff83556b7e0 r: 0xfff83556b908 (-1) 2025-05-02T05:39:54.395159000Z 41(88) ERROR: <core> [core/tcp_main.c:1406]: tcp_do_connect(): connect 183.198.156.45:1272 failed Cannot assign requested address 2025-05-02T05:39:54.395211960Z 41(88) ERROR: <core> [core/tcp_main.c:1409]: tcp_do_connect(): connect 183.198.156.45:1272: (99) Cannot assign requested address 2025-05-02T05:39:54.395220020Z 41(88) ERROR: <core> [core/tcp_main.c:1545]: tcpconn_finish_connect(): 183.198.156.45:1272: tcp_do_connect for 0xfff95f7037e0 failed 2025-05-02T05:39:54.395226280Z 41(88) ERROR: <core> [core/tcp_main.c:2200]: tcp_send(): 183.198.156.45:1272: tcpconn_finish_connect(0xfff95f7037e0) failed 2025-05-02T05:39:54.395232270Z 41(88) ERROR: tm [../../core/forward.h:290]: msg_send_buffer(): tcp_send failed 2025-05-02T05:39:54.395337640Z 41(88) ERROR: sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) 2025-05-02T05:39:54.484799620Z 19(66) ERROR: <core> [core/tcp_main.c:1406]: tcp_do_connect(): connect 1.202.124.130:54952 failed Cannot assign requested address 2025-05-02T05:39:54.484847710Z 19(66) ERROR: <core> [core/tcp_main.c:1409]: tcp_do_connect(): connect 1.202.124.130:54952: (99) Cannot assign requested address 2025-05-02T05:39:54.484882280Z 19(66) ERROR: <core> [core/tcp_main.c:1545]: tcpconn_finish_connect(): 1.202.124.130:54952: tcp_do_connect for 0xfff9c7c0d500 failed 2025-05-02T05:39:54.484889320Z 19(66) ERROR: <core> [core/tcp_main.c:2200]: tcp_send(): 1.202.124.130:54952: tcpconn_finish_connect(0xfff9c7c0d500) failed 2025-05-02T05:39:54.484894930Z 19(66) ERROR: tm [../../core/forward.h:260]: msg_send_buffer(): tcp_send failed 2025-05-02T05:39:54.484899790Z 19(66) ERROR: sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) 2025-05-02T05:39:54.759458370Z 118(165) CRITICAL: <core> [core/io_wait.h:594]: io_watch_del(): invalid fd 69, not in [0, 0) 2025-05-02T05:39:54.759506810Z 118(165) ERROR: <core> [core/tcp_read.c:1765]: tcpconn_read_timeout(): io_watch_del failed for 0xfff80ff7f860 id 65244425 fd 69, state 0, flags c018, main fd 48347 ([240e::31]:63566 -> [240e::31]:5460) note：[240e::31] is the service address of kamailio, hiding the real IP address . ``` ### Possible Solutions ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.4 (x86_64/linux) fdc771 ``` * **Operating System**:  ``` OpenEuler 22.03 Linux localhost.localdomain 5.10.0-136.12.0.86.ctl3.x86_64 #1 SMP Fri Jan 13 08:18:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4238 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4238(a)github.com>

3 11

[kamailio/kamailio] If fix_nated_contact is used, then remove_hf("Contact"), the contact header will not be deleted cleanly. (Issue #4190)
by QuincyGao 24 Jun '25

24 Jun '25

QuincyGao created an issue (kamailio/kamailio#4190)  ### Description  I want to use opensips as SBC, When the agent registers to kamailio, the contact content is modified to the ip and port of kamailio, and then Register is forwarded to the agent. remove_hf("Contact") can't remove the whole Contact( field, vlue). here is my config: ``` route[REGISTRAR] { if (!is_method("REGISTER")) return; if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); #!ifdef WITH_NATSIPPING # do SIP NAT pinging setbflag(FLB_NATSIPPING); #!endif } fix_nated_contact(); if (!save("location","0x02")) { #if (!save("location")) { sl_reply_error(); } $fs="udp:172.16.4.111:5461"; $du="sip:172.16.4.114:5060"; remove_hf("Contact"); $var(contact) = "Contact: <sip:" +$fU+"@"+"172.16.4.111:5461>;expires=120\r\n" ; append_hf("$var(contact)"); route(RELAY); exit; } ``` here is the sip message: ``` 2025/03/26 16:36:07.706093 172.16.4.111:5461 -> 172.16.4.114:5060 REGISTER sip:172.16.4.111:5460 SIP/2.0 Via: SIP/2.0/UDP 172.16.4.111:5461;branch=z9hG4bKfc7e.d2df36f3b5681afeb71e442e645de38d.0 Via: SIP/2.0/UDP 172.16.80.3:49309;received=172.16.80.3;rport=49309;branch=z9hG4bKPj8ab8bd1d3c3a4c1bb0cd639540fa3183 Max-Forwards: 69 From: <sip:1008@172.16.4.111>;tag=95f7f5601f8b40458a1efe6923ab0a29 To: <sip:1008@172.16.4.111> Call-ID: f84b643f5d284d18a0d8175e1ef4d747 CSeq: 33264 REGISTER User-Agent: MicroSIP/3.21.6 sip:1008@172.16.80.3:49309;obExpires: 120 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Content-Length: 0 Contact: <sip:1008@172.16.4.111:5461>;expires=120 ``` you can see the problem is that: `sip:1008@172.16.80.3:49309;obExpires: 120` , `sip:1008@172.16.80.3:49309` is the value of the Contact field after fix_nated_contact(). ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.8.5 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: compiled on 11:27:01 Mar 21 2025 with gcc 4.8.5 ``` * **Operating System**:  ``` Centos7.9 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4190 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4190(a)github.com>

2 4

[kamailio/kamailio] topos: Allow contact a/b host like user part (PR #4246)
by Xenofon Karamanos 24 Jun '25

24 Jun '25

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  In this PR we introduce a new mode and two new parameters for accomplishing the same thing for user part also in domain part. Docs incoming if no significant changes are needed. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4246 -- Commit Summary -- * topos: Add new contact_mode=3 and 2 new modparam for contact host domains * topos: Refactor contact_mode handling * topos: Append port and protocol param -- File Changes -- M src/modules/topos/topos_mod.c (13) M src/modules/topos/tps_storage.c (428) M src/modules/topos/tps_storage.h (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4246.patch https://github.com/kamailio/kamailio/pull/4246.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4246 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4246(a)github.com>

3 5

[kamailio/kamailio] Writing to $fU or $tU appends to header user (Issue #3165)
by Benoît Panizzon 24 Jun '25

24 Jun '25

Dear Gang Possibly @oej could provide more in-depth information as he has witnessed this issue. Usually the user of the from URI is the phone number displayed at the destination. There are situations where this phone number is translated. As example. In Switzerland, the user is used to see numbers in a local format. National number starting with 0 and international numbers with 00 but on interconnection between telcos, e164 is used. So basically when a call is sent to a customer '+41' is replaced by '0' and '+' is replaced by '00'. Let's start with an example From: header: `From: "Maurice Moss" <sip:+41991234567@example.com>;user=phone` So shortly before the call is sent out to the location of the registered CPE, this is done: ``` if ($fU =~ "^\+41") { $fU = "0" + $(fU{s.substr,3,0}); } else if ($fU = ~ "^\+") { $fU = "00" + $(fU{s.substr,1,0}); } ``` What is sent to the CPE now looks like this: `From: "Maurice Moss" <sip:0991234567@example.com>;user=phone` Now we hit an error like 486 BUSY and the destination has call forwarding active to a mobile phone on another TSP. So we have to send the call out back the IC and numbers need to be translated back to e164. We handle this in a failure route, which in turn could trigger a branch route. So we revert the number back to e164: `$fU = "+41" + $(fU{s.substr,1,0});` Expected outcome: `From: "Maurice Moss" <sip:+41991234567@example.com>;user=phone` Observed outcome: `From: "Maurice Moss" <sip:0991234567+41991234567@example.com>;user=phone` So setting $fU more than once is appending to the user element of the From header URI. This behavior has not been found in any documentation. I have been working around most of the issues by making sure I change $fU (and $tU) at the latest possible time and only once. But in the case described above, I have not been able to come up with a work-around yet. I also can't think of any benefit of the way those PV are handled or any harm that could be done, to handle them differently and make the last 'write' overwrite and previous value, instead of appending. Thank you for looking into this. -Benoît- -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3165 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3165(a)github.com>

3 4

[kamailio/kamailio] Setting OpenSSL TLS1.3 cipher lists (PR #4256)
by Nicolas Chapleau 24 Jun '25

24 Jun '25

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

2 23

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2025