March 2025 - sr-dev - kamailio.org

git:master:a5f69e46: modules: readme files regenerated - registrar ... [skip ci]
by Kamailio Dev 20 Sep '26

20 Sep '26

Module: kamailio Branch: master Commit: a5f69e46613af05097debf1c373a138dd69fbdaf URL: https://github.com/kamailio/kamailio/commit/a5f69e46613af05097debf1c373a138… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2022-12-17T13:31:18+01:00 modules: readme files regenerated - registrar ... [skip ci] --- Modified: src/modules/registrar/README --- Diff: https://github.com/kamailio/kamailio/commit/a5f69e46613af05097debf1c373a138… Patch: https://github.com/kamailio/kamailio/commit/a5f69e46613af05097debf1c373a138… --- diff --git a/src/modules/registrar/README b/src/modules/registrar/README index 406fd0fe25..1e5d041324 100644 --- a/src/modules/registrar/README +++ b/src/modules/registrar/README @@ -1152,7 +1152,7 @@ xinfo("first contact record - socket: $xavp(cul>socket)\n"); 4.6. registered(domain [, uri [, match_option [, match_action]]]) The function returns true if the AOR in the URI is registered, false - otherwise. The function does not modify the message being process, it + otherwise. The function does not modify the message being processed, it neither rewrites the Request-URI if a contact is found nor append branches. If uri parameter is not provided, then it considered to be the Request-URI for SIP requests and To-URI for SIP replies.

2 1

[tracker] Assignee added: Assignment operators don't work
by sip-router 04 Sep '26

04 Sep '26

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#100 - Assignment operators don't work User who did this - Alex Hermann (axlh) http://sip-router.org/tracker/index.php?do=details&task_id=100 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 10

[kamailio/kamailio] Issue with usrloc 'handle_lost_tcp' and dmq_usrloc 'usrloc_delete' (Issue #3479)
by alternatenetwork 02 Sep '26

02 Sep '26

### Description When a TLS connection is closed and handle_lost_tcp=1 the entry is deleted for usrloc. This deletion is not synced via DMQ even though usrloc_delete=1. There is also an issue on the same server if a re-registration happens right after before the timeout was supposed to expire then $var(sv_res) = 2 even though the usrloc table is empty. So it seems like the way handle_lost_tcp deletes is not deleting fully in registrar. usrloc db_mode is 0 ### Troubleshooting #### Reproduction Setup 2 servers with DMQ and close the TCP connection. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.1 (x86_64/linux) d8f98b 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: d8f98b compiled on 19:05:04 Aug 16 2022 with gcc 8.3.0 ``` * **Operating System**:  ``` Debian 10 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3479 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3479(a)github.com>

4 7

[kamailio/kamailio] Bug: SIP message fails to send over WSS after upgrade to Kamailio 5.8 (Issue #4115)
by Dongsun 17 Aug '26

17 Aug '26

### Description After upgrading from Kamailio 5.7 to 5.8, we encountered an issue where SIP messages fail to send over WSS, resulting in a 477 error. The problem seems to be related to the addition of protocol validation logic in tcp_main.c: https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#L1747 https://github.com/kamailio/kamailio/commit/4a40b16d4f9bef9bc75d3272c83878e… ``` a->parent->rcv.proto == proto ``` `a->parent->rcv.proto` is `6 (indicating WSS)`, while `proto` is `5 (indicating WS)`, causing the connection lookup to fail. Removing this validation line resolves the issue, restoring the previous behavior where SIP messages are successfully sent over WSS. #### INFO level Log Messages ``` Jan 17 00:07:08.948495 kamailio[3487903]: WARNING: [799a4e2e-5fdf-444a-8dab-b2ab554c4933] tm [../../core/forward.h:204]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found Jan 17 00:07:08.948516 kamailio[3487903]: WARNING: [799a4e2e-5fdf-444a-8dab-b2ab554c4933] tm [t_fwd.c:1586]: t_send_branch(): sending request on branch 0 failed Jan 17 00:07:08.948536 kamailio[3487903]: INFO: [799a4e2e-5fdf-444a-8dab-b2ab554c4933] sl [sl_funcs.c:420]: sl_reply_error(): message marked with delayed-reply flag ``` #### DEBUG Level Log Messages ``` Jan 17 00:15:03.377043 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.377102 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Allow-Events] type 39 Jan 17 00:15:03.377122 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 39, name=<Allow-Events>, body=<talk, hold, conference, refer> Jan 17 00:15:03.377178 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Subscription-State] type 37 Jan 17 00:15:03.377196 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 37, name=<Subscription-State>, body=<terminated;reason=noresource> Jan 17 00:15:03.377254 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Route] type 9 Jan 17 00:15:03.377274 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 9, name=<Route>, body=<<sip:1.1.1.1:9060;lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws>> Jan 17 00:15:03.377331 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Supported] type 17 Jan 17 00:15:03.377349 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 17, name=<Supported>, body=<path, replaces> Jan 17 00:15:03.377406 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Contact] type 7 Jan 17 00:15:03.377426 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 7, name=<Contact>, body=<sip:dialpadgw@example.com> Jan 17 00:15:03.377483 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Content-Type] type 11 Jan 17 00:15:03.377501 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 11, name=<Content-Type>, body=<application/data> Jan 17 00:15:03.377555 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Event] type 22 Jan 17 00:15:03.377575 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:661]: parse_headers(): header field type 22, name=<Event>, body=<message-summary> Jan 17 00:15:03.377641 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header Jan 17 00:15:03.377698 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 115 Jan 17 00:15:03.377716 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 373:route[0]: <sip:1.1.1.1:9060;lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws> Jan 17 00:15:03.377736 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.377754 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] pv [pv_core.c:1971]: pv_get_hdr_helper(): index out of range Jan 17 00:15:03.377773 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 17 Jan 17 00:15:03.377793 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 374:route[1]: <null> Jan 17 00:15:03.377812 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.377832 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.377849 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Supported] type 17 Jan 17 00:15:03.377867 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [X-carrier] type 0 Jan 17 00:15:03.377887 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.377905 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 Jan 17 00:15:03.377924 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [X-FS-Support] type 0 Jan 17 00:15:03.377943 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Allow-Events] type 39 Jan 17 00:15:03.377962 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [X-FS-Support] type 0 Jan 17 00:15:03.377982 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Content-Type] type 11 Jan 17 00:15:03.378001 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [X-FS-Support] type 0 Jan 17 00:15:03.378020 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378038 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378056 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378076 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378096 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378115 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378174 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378194 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378327 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=200 Jan 17 00:15:03.378383 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 117 Jan 17 00:15:03.378403 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 387:Route-URI is: sip:1.1.1.1:9060;lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws Jan 17 00:15:03.378422 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] pv [pv_core.c:1343]: pv_get_dsturi(): no destination URI Jan 17 00:15:03.378442 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:1565]: t_check_msg(): msg (0x7f845f8bc2c0) id=3/3519371 global id=2/3519371 T start=0xffffffffffffffff Jan 17 00:15:03.378461 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.378479 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=78 Jan 17 00:15:03.378499 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:781]: t_lookup_request(): start searching: hash=32072, isACK=0 Jan 17 00:15:03.378517 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:499]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK84d7.eabb4795000000000000000000000000.0] Jan 17 00:15:03.378537 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:981]: t_lookup_request(): no transaction found Jan 17 00:15:03.378555 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:1637]: t_check_msg(): msg (0x7f845f8bc2c0) id=3/3519371 global id=3/3519371 T end=(nil) Jan 17 00:15:03.378572 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1326]: parse_uri(): state=5 Jan 17 00:15:03.378589 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1327]: parse_uri(): parsed uri:#012 type=1 user=<+11234567890-1234>(52)#012 passwd=<>(0)#012 host=<example.com>(22)#012 port=<>(0): 0#012 params=<>(0)#012 headers=<>(0) Jan 17 00:15:03.378607 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1336]: parse_uri(): uri flags : Jan 17 00:15:03.378634 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1341]: parse_uri(): value=0 Jan 17 00:15:03.378655 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1342]: parse_uri(): uri params:#012 transport=<>, val=<>, proto=0 Jan 17 00:15:03.378672 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1345]: parse_uri(): user-param=<>, val=<> Jan 17 00:15:03.378691 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1348]: parse_uri(): method=<>, val=<> Jan 17 00:15:03.378711 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1350]: parse_uri(): ttl=<>, val=<> Jan 17 00:15:03.378730 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1352]: parse_uri(): maddr=<>, val=<> Jan 17 00:15:03.379547 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1354]: parse_uri(): lr=<> Jan 17 00:15:03.379584 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1355]: parse_uri(): r2=<> Jan 17 00:15:03.379759 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] siputils [checks.c:122]: has_totag(): no totag Jan 17 00:15:03.379779 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=200 Jan 17 00:15:03.379799 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [loose.c:80]: is_preloaded(): is_preloaded: Yes Jan 17 00:15:03.379817 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1326]: parse_uri(): state=10 Jan 17 00:15:03.379835 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1327]: parse_uri(): parsed uri:#012 type=1 user=<>(0)#012 passwd=<>(0)#012 host=<1.1.1.1>(13)#012 port=<9060>(4): 9060#012 params=<lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws>(79)#012 headers=<>(0) Jan 17 00:15:03.379856 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1336]: parse_uri(): uri flags : Jan 17 00:15:03.379874 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1341]: parse_uri(): value=0 Jan 17 00:15:03.379892 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1342]: parse_uri(): uri params:#012 transport=<>, val=<>, proto=0 Jan 17 00:15:03.379913 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1345]: parse_uri(): user-param=<>, val=<> Jan 17 00:15:03.379931 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1348]: parse_uri(): method=<>, val=<> Jan 17 00:15:03.379950 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1350]: parse_uri(): ttl=<>, val=<> Jan 17 00:15:03.379969 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1352]: parse_uri(): maddr=<>, val=<> Jan 17 00:15:03.379987 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1354]: parse_uri(): lr=<lr> Jan 17 00:15:03.380007 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1355]: parse_uri(): r2=<> Jan 17 00:15:03.380025 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/socket_info.c:737]: grep_sock_info(): checking if host==us: 13==11 && [1.1.1.1] == [10.128.0.35] Jan 17 00:15:03.380044 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/socket_info.c:741]: grep_sock_info(): checking if port 9060 (advertise 9060) matches port 9060 Jan 17 00:15:03.380064 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/socket_info.c:763]: grep_sock_info(): checking advertise if host==us: 13==13 && [1.1.1.1] == [1.1.1.1] Jan 17 00:15:03.380081 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/forward.c:446]: check_self(): host (0:1.1.1.1:9060) == me Jan 17 00:15:03.380173 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [loose.c:886]: after_loose(): Topmost route URI: 'sip:1.1.1.1:9060;lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws' is me Jan 17 00:15:03.380238 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=200 Jan 17 00:15:03.380295 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header Jan 17 00:15:03.380351 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [loose.c:181]: find_next_route(): No next Route HF found Jan 17 00:15:03.380379 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [loose.c:916]: after_loose(): No next URI found Jan 17 00:15:03.380398 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [rr_cb.c:94]: run_rr_callbacks(): callback id 1 entered with <lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws> Jan 17 00:15:03.380415 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] uac [replace.c:567]: restore_uri(): getting 'vsf' Route param Jan 17 00:15:03.380435 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] uac [replace.c:570]: restore_uri(): route param 'vsf' not found Jan 17 00:15:03.380453 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] uac [replace.c:567]: restore_uri(): getting 'vst' Route param Jan 17 00:15:03.380473 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] uac [replace.c:570]: restore_uri(): route param 'vst' not found Jan 17 00:15:03.380491 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] rr [rr_cb.c:94]: run_rr_callbacks(): callback id 0 entered with <lr;received=sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797%3Btransport%3Dws> Jan 17 00:15:03.380584 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/strutils.c:207]: unescape_user(): unescaped string is <sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797;transport=ws> Jan 17 00:15:03.380602 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] path [path.c:504]: path_rr_callback(): setting dst uri: sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797;transport=ws Jan 17 00:15:03.380768 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 83 Jan 17 00:15:03.380786 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 497:outbound proxy is: sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797;transport=ws Jan 17 00:15:03.381032 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 66 Jan 17 00:15:03.381049 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 514:found target_ip from du: [2604:3d08:777a:61a0:601f:864:1234:1234] Jan 17 00:15:03.383827 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/action.c:1477]: do_action(): setting send-socket to [tls:[2600:1900:4000:f7cd:0:f::]:443] Jan 17 00:15:03.383849 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.383911 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.383931 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.383949 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.384006 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.384065 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 22 Jan 17 00:15:03.384181 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1326]: parse_uri(): state=5 Jan 17 00:15:03.384206 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1327]: parse_uri(): parsed uri:#012 type=1 user=<dialpadgw>(9)#012 passwd=<>(0)#012 host=<example.com>(22)#012 port=<>(0): 0#012 params=<>(0)#012 headers=<>(0) Jan 17 00:15:03.384225 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1336]: parse_uri(): uri flags : Jan 17 00:15:03.384244 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1341]: parse_uri(): value=0 Jan 17 00:15:03.384265 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1342]: parse_uri(): uri params:#012 transport=<>, val=<>, proto=0 Jan 17 00:15:03.384286 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1345]: parse_uri(): user-param=<>, val=<> Jan 17 00:15:03.384304 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1348]: parse_uri(): method=<>, val=<> Jan 17 00:15:03.384324 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1350]: parse_uri(): ttl=<>, val=<> Jan 17 00:15:03.384344 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1352]: parse_uri(): maddr=<>, val=<> Jan 17 00:15:03.384362 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1354]: parse_uri(): lr=<> Jan 17 00:15:03.384401 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1355]: parse_uri(): r2=<> Jan 17 00:15:03.384578 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1714]: _tcpconn_find(): 0 port 0 Jan 17 00:15:03.384595 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/pvapi.c:1450]: pv_printf_mode(): final buffer length 95 Jan 17 00:15:03.384612 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] 1168:<==== Relaying to sip:[2604:3d08:777a:61a0:601f:864:1234:1234]:52797;transport=ws conid=<null> Jan 17 00:15:03.384630 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:1868]: t_newtran(): msg (0x7f845f8bc2c0) id=3/3519371 global id=3/3519371 T start=(nil) Jan 17 00:15:03.384648 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.384666 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=78 Jan 17 00:15:03.384682 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:781]: t_lookup_request(): start searching: hash=32072, isACK=0 Jan 17 00:15:03.384701 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:499]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK84d7.eabb4795000000000000000000000000.0] Jan 17 00:15:03.384717 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:981]: t_lookup_request(): no transaction found Jan 17 00:15:03.384733 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1326]: parse_uri(): state=65 Jan 17 00:15:03.384751 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1327]: parse_uri(): parsed uri:#012 type=1 user=<36k22ler>(8)#012 passwd=<>(0)#012 host=<f6sbiii372li.invalid>(20)#012 port=<>(0): 0#012 params=<transport=ws>(12)#012 headers=<>(0) Jan 17 00:15:03.384768 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1336]: parse_uri(): uri flags : Jan 17 00:15:03.384793 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1341]: parse_uri(): value=0 Jan 17 00:15:03.384812 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1342]: parse_uri(): uri params:#012 transport=<transport=ws>, val=<ws>, proto=5 Jan 17 00:15:03.384828 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1345]: parse_uri(): user-param=<>, val=<> Jan 17 00:15:03.384848 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1348]: parse_uri(): method=<>, val=<> Jan 17 00:15:03.384868 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1350]: parse_uri(): ttl=<>, val=<> Jan 17 00:15:03.384886 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1352]: parse_uri(): maddr=<>, val=<> Jan 17 00:15:03.384907 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1354]: parse_uri(): lr=<> Jan 17 00:15:03.384925 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1355]: parse_uri(): r2=<> Jan 17 00:15:03.385025 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=78 Jan 17 00:15:03.385045 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/crypto/md5utils.c:67]: MD5StringArray(): MD5 calculated: 6e9568ded8dde3ef89a05a4f03829dc5 Jan 17 00:15:03.385065 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [h_table.c:415]: build_cell(): created new cell 0x7f8424c15380 Jan 17 00:15:03.385084 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [h_table.h:549]: insert_into_hash_table_unsafe(): cell label: 1965846678 Jan 17 00:15:03.385457 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1326]: parse_uri(): state=65 Jan 17 00:15:03.385476 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1327]: parse_uri(): parsed uri:#012 type=1 user=<>(0)#012 passwd=<>(0)#012 host=<[2604:3d08:777a:61a0:601f:864:1234:1234]>(40)#012 port=<52797>(5): 52797#012 params=<transport=ws>(12)#012 headers=<>(0) Jan 17 00:15:03.385496 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1336]: parse_uri(): uri flags : Jan 17 00:15:03.385515 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1341]: parse_uri(): value=0 Jan 17 00:15:03.385534 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1342]: parse_uri(): uri params:#012 transport=<transport=ws>, val=<ws>, proto=5 Jan 17 00:15:03.385553 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1345]: parse_uri(): user-param=<>, val=<> Jan 17 00:15:03.385571 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1348]: parse_uri(): method=<>, val=<> Jan 17 00:15:03.385591 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1350]: parse_uri(): ttl=<>, val=<> Jan 17 00:15:03.385608 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1352]: parse_uri(): maddr=<>, val=<> Jan 17 00:15:03.385628 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1354]: parse_uri(): lr=<> Jan 17 00:15:03.385649 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/parse_uri.c:1355]: parse_uri(): r2=<> Jan 17 00:15:03.385668 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/msg_translator.c:1845]: check_boundaries(): no multi-part body Jan 17 00:15:03.385772 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1714]: _tcpconn_find(): 0 port 52797 Jan 17 00:15:03.385792 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): tcpconn_find: ip 2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.385812 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1735]: _tcpconn_find(): a=0x7f8424c013a0, c=0x7f8424c01150, c->id=1, alias port= 52797 port=52797 Jan 17 00:15:03.385830 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): ip=2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.385850 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1746]: _tcpconn_find(): found connection by peer address (id: 1) Jan 17 00:15:03.385869 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/msg_translator.c:162]: check_via_address(): (1.1.1.1, 1.1.1.1, 0) Jan 17 00:15:03.386610 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1714]: _tcpconn_find(): 0 port 52797 Jan 17 00:15:03.386628 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): tcpconn_find: ip 2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.386648 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1735]: _tcpconn_find(): a=0x7f8424c013a0, c=0x7f8424c01150, c->id=1, alias port= 52797 port=52797 Jan 17 00:15:03.386666 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): ip=2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.386685 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1714]: _tcpconn_find(): 0 port 52797 Jan 17 00:15:03.386707 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): tcpconn_find: ip 2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.386726 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/tcp_main.c:1735]: _tcpconn_find(): a=0x7f8424c01380, c=0x7f8424c01150, c->id=1, alias port= 52797 port=52797 Jan 17 00:15:03.386747 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/ip_addr.c:580]: print_ip(): ip=2604:3d08:777a:61a0:601f:864:1234:1234 Jan 17 00:15:03.386766 kamailio[3519371]: WARNING: [61e5f40c-acba-471f-94be-e66334eb217d] tm [../../core/forward.h:204]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found Jan 17 00:15:03.386786 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_fwd.c:1566]: t_send_branch(): send to 2604:3d08:777a:61a0:601f:864:1234:1234:52797 (5) failed Jan 17 00:15:03.386805 kamailio[3519371]: WARNING: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_fwd.c:1586]: t_send_branch(): sending request on branch 0 failed Jan 17 00:15:03.386825 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_funcs.c:358]: t_relay_to(): t_forward_nonack returned error -1 (-477) Jan 17 00:15:03.386842 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_funcs.c:376]: t_relay_to(): -477 error reply generation delayed Jan 17 00:15:03.386862 kamailio[3519371]: INFO: [61e5f40c-acba-471f-94be-e66334eb217d] sl [sl_funcs.c:420]: sl_reply_error(): message marked with delayed-reply flag Jan 17 00:15:03.386955 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/receive.c:531]: receive_msg(): request-route executed in: 3370 usec Jan 17 00:15:03.386972 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_lookup.c:2032]: t_unref(): delayed error reply generation(-477) Jan 17 00:15:03.386989 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/parser/msg_parser.c:324]: parse_headers(): flags=ffffffffffffffff Jan 17 00:15:03.387008 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/msg_translator.c:162]: check_via_address(): (1.1.1.1, 1.1.1.1, 0) Jan 17 00:15:03.387180 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_reply.c:1782]: cleanup_uac_timers(): RETR/FR timers reset Jan 17 00:15:03.387198 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] siptrace [siptrace.c:2476]: siptrace_net_data_sent(): processing message mode 1 Jan 17 00:15:03.387217 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] siptrace [siptrace_hep.c:523]: pipport2su(): the port string is 9060 Jan 17 00:15:03.387236 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] siptrace [siptrace_hep.c:523]: pipport2su(): the port string is 8060 Jan 17 00:15:03.387331 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/proxy.c:267]: mk_proxy(): doing DNS lookup... Jan 17 00:15:03.387512 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] siptrace [siptrace_hep.c:185]: trace_send_hep3_duplicate(): setting up the socket_info Jan 17 00:15:03.388083 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_reply.c:634]: _reply_light(): reply sent out - buf=0x7f845f88e060: SIP/2.0 477 Unfortun... shmem=0x7f8424c1b010: SIP/2.0 477 Unfortun Jan 17 00:15:03.388181 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_funcs.c:133]: put_on_wait(): put T [0x7f8424c15380] on wait Jan 17 00:15:03.388330 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] tm [t_reply.c:650]: _reply_light(): finished Jan 17 00:15:03.388390 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388437 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388483 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388531 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388578 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388625 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) Jan 17 00:15:03.388675 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) Jan 17 00:15:03.388722 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) Jan 17 00:15:03.388782 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) Jan 17 00:15:03.388801 kamailio[3519371]: DEBUG: [61e5f40c-acba-471f-94be-e66334eb217d] <core> [core/receive.c:635]: receive_msg(): cleaning up ``` #### SIP Traffic  ### Test Scenario: 1. A client connects to Kamailio over WSS on port 443 and sends a REGISTER request, successfully registering. 2. Another SIP server attempts to send a NOTIFY request to the client via Kamailio. - Kamailio fails to send the NOTIFY request to the client and responds with a 477 error. ``` Client Kamailio SIP Server | | | |--- REGISTER (WSS:443) -------> | | | | | |<--- 200 OK (Registration) ---- | | | | | | | <-- NOTIFY (UDP) -------------- | | | | | | | | | --- 477 Error -----------------> | | | (Failed to send NOTIFY) | | | | | | | ``` I replaced our Kamailio server domain in the SIP message with 'example.com'. kamailio IP: 1.1.1.1 client IP:3.3.3.3 ``` REGISTER sip:example.com SIP/2.0 Via: SIP/2.0/WSS hfotrcsa7jk0.invalid;branch=z9hG4bK769149 ... Contact: <sip:23ao5h15@hfotrcsa7jk0.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:35e6e004-4a78-4c5f-999c-be70dda68e1f>";expires=900 ... ``` ``` NOTIFY sip:23ao5h15@hfotrcsa7jk0.invalid;transport=ws SIP/2.0 Via: SIP/2.0/UDP 2.2.2.2:8060;branch=z9hG4bKa769.503729f6000000000000000000000000.0 To: <sip:+11234567890-1234@example.com> From: <sip:mygw@example.com>;tag=5e6acf4bd0c73e10f5120f096b1fc95c-e0aa3a8f User-Agent: kamailio (5.8.3 (x86_64/linux)) ... Route: <sip:1.1.1.1:9060;lr;received=sip:3.3.3.3:63549%3Btransport%3Dws> ... ``` ``` SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) ``` ### Possible Solutions  https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#L1747 ``` && (proto == PROTO_NONE || a->parent->rcv.proto == proto)) { ``` Removing this validation line resolves the issue, restoring the previous behavior where SIP messages are successfully sent over WSS. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` # ./kamailio -v version: kamailio 5.8.3 (x86_64/linux) 42401c flags: , EXTRA_DEBUGUSE_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: 42401c compiled on 23:24:48 Jan 16 2025 with gcc 10.2.1 ``` * **Operating System**:  debian 11.11 ``` # uname -a Linux 5.10.0-33-cloud-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4115 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4115(a)github.com>

4 5

[kamailio/kamailio] a single digit is a valid enum_query() request (#593)
by Jonas 05 Aug '26

05 Aug '26

We use enum_query() to dispatch calls over a set of gateways. In our case single digits (for instance "8") can be a valid direct dial number which we would like to through against our enum server. Is there any good reason to limit the request to 2 digits as minimum? You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/593 -- Commit Summary -- * a single number should be a valid in function enum_query() * print out malformed enum_query() request in enum.c -- File Changes -- M modules/enum/enum.c (11) -- Patch Links -- https://github.com/kamailio/kamailio/pull/593.patch https://github.com/kamailio/kamailio/pull/593.diff --- 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/pull/593

3 3

[kamailio/kamailio] Add Username support for authentication in redis and sentinel w.r.t NDB REDIS (Issue #3552)
by hemanth-vulavala 27 Jul '26

27 Jul '26

### Description The current issue revolves around the absence of username support within the NDB REDIS KAMALIO framework when dealing with Redis, particularly concerning the Redis and Sentinel components. While Redis inherently offers the capability to utilize both usernames and passwords during authentication, this capability is not currently extended to the NDB REDIS KAMALIO setup. As a result, when attempting to establish connections to Redis instances through NDB REDIS KAMALIO, there is no provision for providing a username as part of the authentication process. Instead, the framework only accommodates the usage of passwords for authentication. This stands in contrast to Redis, which permits the inclusion of both usernames and passwords for enhanced security measures. Consequently, the limitation within NDB REDIS KAMALIO can hinder organizations seeking to ensure comprehensive security practices, especially when the requirement is to employ both usernames and passwords for authentication. This divergence between the authentication capabilities of Redis and NDB REDIS KAMALIO can potentially compromise security standards and hinder compatibility with certain authentication setups. To address this issue, it would be essential for the development team behind NDB REDIS KAMALIO to enhance the framework's capabilities by incorporating support for username-based authentication in addition to passwords. This alignment with Redis's authentication model would ensure that organizations can confidently implement secure data interactions while maintaining consistency with established security policies  ### Expected behavior The expected behavior entails an improvement within the NDB REDIS KAMALIO framework to support both usernames and passwords for authentication when interacting with Redis instances, particularly in the Redis and Sentinel components. This enhancement would bring NDB REDIS KAMALIO in line with Redis's native authentication capabilities, where both usernames and passwords are accepted during the authentication process. Upon implementing this improvement, users of NDB REDIS KAMALIO should be able to configure their connections by providing both a username and a password as part of the authentication details. This allows NDB REDIS KAMALIO to establish connections to Redis instances that require both authentication credentials, thereby enhancing security and ensuring compatibility with various authentication setups. By incorporating support for usernames in addition to passwords, NDB REDIS KAMALIO can accommodate organizations that require comprehensive security measures, especially in scenarios where username-based authentication is mandated. This alignment with Redis's authentication model would enable organizations to effectively collect, manage, and interact with data while adhering to established security policies. In summary, the expected behavior is that NDB REDIS KAMALIO should be upgraded to offer support for usernames and passwords during authentication, mirroring Redis's capabilities. This enhancement ensures a consistent and secure approach to data interactions and supports various authentication requirements within Redis environments #### Actual observed behavior The current actual behavior is that NDB REDIS KAMALIO does not have the capability to accept usernames as part of the authentication process when connecting to Redis instances, specifically in both the Redis and Sentinel components. While Redis itself allows for the usage of both usernames and passwords for authentication, this feature is not currently integrated into the NDB REDIS KAMALIO framework. As a result, when configuring connections to Redis instances using NDB REDIS KAMALIO, there is no provision to include a username alongside the authentication details. The framework only accommodates the use of passwords for authentication purposes. This deviation from Redis's authentication model could lead to compatibility issues with certain authentication setups, particularly those that mandate the use of both usernames and passwords. In essence, the actual behavior is that NDB REDIS KAMALIO falls short of aligning with Redis's authentication capabilities, thereby potentially hindering secure data interactions and limiting compatibility with certain security policies. Users attempting to adhere to comprehensive authentication practices may face challenges when utilizing NDB REDIS KAMALIO due to its inability to support usernames during authentication. To address this actual behavior, it would be necessary to enhance NDB REDIS KAMALIO's capabilities to include support for both usernames and passwords during the authentication process. This enhancement would ensure that organizations can confidently utilize NDB REDIS KAMALIO while maintaining the security standards and authentication requirements necessary for their Redis environments. #### 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` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3552 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3552(a)github.com>

5 7

[kamailio/kamailio] Memory usage increases everytime tls.reload is executed (Issue #3823)
by Sebastian Denz 10 Jul '26

10 Jul '26

### Description We are using Kamailio 5.7.4 on Debian 12 (from http://deb.kamailio.org/kamailio57) with rtpengine as an Edgeproxy for our clients. The instance terminates SIP/TLS (with Cliencertificates) and forwards the SIP Traffic to internal systems. After some days we are getting errors like this `tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=7318616 threshold1=8912896` First we thought Kamailio just doesnt have enough memory, so we doubled it.. But after some days the Logmessage (and Userissues) occured again. So we monitored the shmmem statistics and found that used and max_used are constantly growing til it reaches the limit. As i mentioned we are using client-certificates and so we are also using the CRL feature. We do have a systemd-timer which fetches the CRL every hour and runs 'kamcmd tls.reload' when finished. Our tls.cfg looks like this: ``` [server:default] method = TLSv1.2+ private_key = /etc/letsencrypt/live/hostname.de/privkey.pem certificate = /etc/letsencrypt/live/hostname.de/fullchain.pem ca_list = /etc/kamailio/ca_list.pem ca_path = /etc/kamailio/ca_list.pem crl = /etc/kamailio/combined.crl.pem verify_certificate = yes require_certificate = yes [client:default] verify_certificate = yes require_certificate = yes ``` After testing a bit we found that every time tls.reload is executed Kamailio consumes a bit more memory which eventually leads to all the memory being consumed which leads to issues for our users. See following example: ``` [0][root@edgar-dev:~]# while true ; do /usr/sbin/kamcmd tls.reload ; /usr/sbin/kamcmd core.shmmem ; sleep 1 ; done Ok. TLS configuration reloaded. { total: 268435456 free: 223001520 used: 41352552 real_used: 45433936 max_used: 45445968 fragments: 73 } Ok. TLS configuration reloaded. { total: 268435456 free: 222377960 used: 41975592 real_used: 46057496 max_used: 46069232 fragments: 78 } Ok. TLS configuration reloaded. { total: 268435456 free: 221748664 used: 42604992 real_used: 46686792 max_used: 46698080 fragments: 77 } Ok. TLS configuration reloaded. { total: 268435456 free: 221110832 used: 43242408 real_used: 47324624 max_used: 47335608 fragments: 81 } ^C [130][root@edgar-dev:~]# ``` ### Troubleshooting #### Reproduction Everytime tls.reload is called the memory consumptions grows.. #### Debugging Data  ``` If you let me know what would be interesting for tracking this down, i am happy to provide logs/debugging data! ``` #### Log Messages  ``` If you let me know what would be interesting for tracking this down, i am happy to provide logs/debugging data! ``` #### SIP Traffic SIP doesnt seem to be relevant here ### Possible Solutions Calling tls.reload less often or restart kamailio before memory is consumed ;) ### Additional Information ``` version: kamailio 5.7.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, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 12.2.0 ``` * **Operating System**: ``` * Debian GNU/Linux 12 (bookworm) * Linux edgar-dev 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3823 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3823(a)github.com>

12 55

[kamailio/kamailio] http_client/http_async_client crash at startup if used with tls and openssl 1.1 (Issue #2912)
by kdanderso 01 Jun '26

01 Jun '26

### Description When attempting to use either http_client or http_async_client with tls support enabled and openssl version 1.1.x, Kamailio crashes at startup. If openssl is reverted to version 1.0.2r as described in #1860, the issue does not occur. #### Reproduction On a system using openssl version 1.1.x (e.g. 1.1.1l) start Kamailio 5.5.2 with this config file for http_client failure: [kamailio.cfg.txt](https://github.com/kamailio/kamailio/files/7442436/kamail… To test http_async_client, load pv.so and http_async_client.so instead of http_client.so. #### Debugging Data [bt.txt](https://github.com/kamailio/kamailio/files/7442493/bt.txt) #### Log Messages [kam.log.txt](https://github.com/kamailio/kamailio/files/7442496/kam.log.txt) ### Additional Information * **Kamailio Version**: [kamversion.txt](https://github.com/kamailio/kamailio/files/7442506/kamversi… * **Operating System**: Linux 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux [os.txt](https://github.com/kamailio/kamailio/files/7442509/os.txt) -- 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/2912

5 10

[kamailio/kamailio] ims_diameter_server not freeing shared memory (Issue #4116)
by MGrimby 20 May '26

20 May '26

### Description I have run in to an issue when sending diameter requests using the ims_diameter_server module. Shared memory keeps increasing and are not being freed until restart of kamailio. This leads to all shared memory is being used and no more are able to be allocated. This only happens when the request is sent synchronously. When sent asynchronously shared memory is being freed as far as I can see. Following functions have been used for sending requests. diameter_request([peer], appid, commandcode, message) diameter_request_async([peer], appid, commandcode, message) ### Troubleshooting Sent a bunch of diameter requests and verified that shared memory for the following functions are not freed. do_receive(600): AAATranslateMessage(500): AAACreateAVP(137): #### Reproduction It's possible to reproduce by sending sync diameter request and verify shared memory. Example of diameter request block ``` route[CHECK_LOCATION] { diameter_request("hss.ims.test.local", "16777217", "306", "[ " + "{ \"avpCode\":260, \"vendorId\":0, \"Flags\":64, \"list\":[ { \"avpCode\":266, \"vendorId\":0, \"Flags\":64, \"int32\":10415 }, { \"avpCode\":258, \"vendorId\":0, \"Flags\":64, \"int32\":16777217 } ] }, " + "{ \"avpCode\":277, \"vendorId\":0, \"Flags\":64, \"int32\":1 }, " + "{ \"avpCode\":283, \"vendorId\":0, \"Flags\":64, \"string\":\"ims.test.local\"}, " + "{ \"avpCode\":706, \"vendorId\":10415, \"Flags\":192, \"int32\":0 }, " + "{ \"avpCode\":700, \"vendorId\":10415, \"Flags\":192, \"list\": [ { \"avpCode\":601, \"vendorId\":10415, \"Flags\":192, \"string\":\"tel:" + $fU + "\" }]}, " + "{ \"avpCode\":707, \"vendorId\":10415, \"Flags\":192, \"int32\":0 }, " + "{ \"avpCode\":703, \"vendorId\":10415, \"Flags\":192, \"int32\":14 } ]"); xlog("L_INFO", "Sent Diameter request"); } ``` Stats cdp:replies_received = 343310 shmem:fragments = 142 shmem:free_size = 1221489992 shmem:max_used_size = 948242168 shmem:real_used_size = 925993656 shmem:total_size = 2147483648 shmem:used_size = 558205656 kamcmd mod.stats cdp shm do_receive(600): 256245808 AAATranslateMessage(500): 64420712 AAACreateAVP(137): 218100320 Total: 538774000 #### 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.7.4 (x86_64/linux) dc393e 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: dc393e compiled on 13:56:27 Feb 27 2024 with gcc 8.5.0 ``` * **Operating System**:  ``` Linux bmatkamas1 4.18.0-553.16.1.el8_10.x86_64 #1 SMP Thu Aug 1 04:16:12 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.10 (Ootpa) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4116 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4116(a)github.com>

4 10

[kamailio/kamailio] Kamailio 5.4.x dialog profiles functionality dead-lock on certain high-load scenarios (Issue #2923)
by Henning Westerholt 03 Apr '26

03 Apr '26

### Description The Kamailio 5.4.x dialog profiles functionality can lead to dead-lock on certain high-load scenarios. The Kamailio dialog profiles are used to track parallel channels for about 200 outgoing PSTN carrier interconnections. During high traffic times (like several thousands parallel calls) the Kamailio server will frequently (e.g. hourly) goes into an end-less loop while executing get_profile_size in the configuration script. This causes the locking for the dialog profiles never be released and Kamailio will stop serving traffic. Internal monitoring tools and RPC commands stay working, as long as they do not touch the dialog functionality. A similar (dedicated) Kamailio setup is used for tracking parallel channels for customers. Here the dead-lock is not observed that frequently, but aparentely also some crashes happens in a much longer time interval. ### Troubleshooting After analysis of the back-traces with GDB the get_profile_size() function was removed from the configuration script. After this change the crash did not happened anymore for several days. #### Reproduction Issue could not be reproduced so far. #### Debugging Data ##### bt 1 (some data removed) (gdb) bt \# 0 0x00007f57cf3b00da in get_profile_size (profile=0x7f50ccbc7e80, value=0x7ffd9928f300) at dlg_profile.c:859 n = 364 i = 12 ph = 0x7f50d3e4b7d0 \# 1 0x00007f57cf419c67 in w_get_profile_size_helper (msg=0x7f57d699d418, profile=0x7f50ccbc7e80, value=0x7ffd9928f300, spd=0x7f57d6916960) at dialog.c:941 \# 2 0x00007f57cf41a459 in w_get_profile_size3 (msg=0x7f57d699d418, profile=0x7f50ccbc7e80, value=0x7f57d6935118, result=0x7f57d6916960) at dialog.c:982 \# 3 0x0000000000463fea in do_action (h=0x7ffd99293610, a=0x7f57d6936488, msg=0x7f57d699d418) at core/action.c:1094 \# 4 0x00000000004711ee in run_actions (h=0x7ffd99293610, a=0x7f57d6936488, msg=0x7f57d699d418) at core/action.c:1581 \# 5 0x000000000046058b in do_action (h=0x7ffd99293610, a=0x7f57d690fda8, msg=0x7f57d699d418) at core/action.c:700 The first back-trace was taking from a running process with gdb. The counter in f0 does not increased that much during this time, probably due the overflow of the loop counter. ##### bt2 (analysis with data structure with gdb scripts) Here the loop counter in f0 showed a really high value. Expected size of dialog profiles hash table: (gdb) p profile->entries[3] $4 = {first = 0x7f9bfd4aad98, content = 2068} (gdb) p profile->entries[7] $3 = {first = 0x7f9c12079f70, content = 784} (gdb) p profile->entries[12] $6 = {first = 0x7f9c02be5d50, content = 7600} (gdb) p profile->entries[14] $2 = {first = 0x7f9bff636de8, content = 6764} hash table bucket 14 shows a lot of corruption and the loop never ends (carrier names and IPs replaced). The list for hash bucket 7 got linked to the list for hash bucket 14: counter 6755: prev 0x7f9c0b9dcde0 - current 0x7f9c02e5b378 - next 0x7f9c0a5f9ba0 - value carrier1-XX.XX - hash 14 counter 6756: prev 0x7f9c02e5b378 - current 0x7f9c0a5f9ba0 - next 0x7f9c0860b968 - value carrier1-XX.XX▒▒▒▒ - hash 14 counter 6757: prev 0x7f9c0a5f9ba0 - current 0x7f9c0860b968 - next 0x7f9bfe3f3a78 - value carrier1-XX.XX▒▒▒▒ - hash 14 counter 6758: prev 0x7f9c0860b968 - current 0x7f9bfe3f3a78 - next 0x7f9c10d977f0 - value carrier1-XX.XX - hash 14 counter 6759: prev 0x7f9bfe3f3a78 - current 0x7f9c10d977f0 - next 0x7f9c0ae198b0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 6760: prev 0x7f9c10d977f0 - current 0x7f9c0ae198b0 - next 0x7f9c12079f70 - value carrier3-XX.XX - hash 7 counter 6761: prev 0x7f9c0ae198b0 - current 0x7f9c12079f70 - next 0x7f9c011f2540 - value-carrier2-XX.XX▒▒▒▒ - hash 7 counter 6762: prev 0x7f9c12079f70 - current 0x7f9c011f2540 - next 0x7f9bfff886f0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 6763: prev 0x7f9c011f2540 - current 0x7f9bfff886f0 - next 0x7f9c05db00a8 - value carrier3-XX.XX= - hash 7 [...] counter 28270: prev 0x7f9c019d06e8 - current 0x7f9bfaf18290 - next 0x7f9c12c90680 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 28271: prev 0x7f9bfaf18290 - current 0x7f9c12c90680 - next 0x7f9c086a2b58 - value-carrier2-XX.XX▒▒▒▒ - hash 7 counter 28272: prev 0x7f9c12c90680 - current 0x7f9c086a2b58 - next 0x7f9c0b4f09e8 - value carrier2-XX.XX▒▒▒▒ - hash 7 [...] hash table bucket 7 is still consistent regarding the loop, but already shows initial sign of corruption. There is one item of the list for hash bucket 14 visible: counter 780: prev 0x7f9c0db57ac8 - current 0x7f9c02225700 - next 0x7f9bfbf7db08 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 781: prev 0x7f9c02225700 - current 0x7f9bfbf7db08 - next 0x7f9c10d977f0 - value carrier1-XX.XX- hash 14 counter 782: prev 0x7f9bfe3f3a78 - current 0x7f9c10d977f0 - next 0x7f9c0ae198b0 - value carrier2-XX.XX▒▒▒▒ - hash 7 counter 783: prev 0x7f9c10d977f0 - current 0x7f9c0ae198b0 - next 0x7f9c12079f70 - value carrier3-XX.XX - hash 7 total size of hash table is 784 #### Log Messages No special log messages observed. #### SIP Traffic SIP traffic looked ok during analysis of the core dumps. ### Possible Solutions * adding additional safe-guards for the get_profile_size function to not access data from other hash buckets * stopping the loop counter after some threshold * finding and fixing the source of the internal data corruption (obviously) * refactoring the dialog modules to use another approach for storing the dialog profile information ### Additional Information * **Kamailio version**: Kamailio 5.4.7, compiled from git repository * **Operating System**: CentOS 7.9 -- 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/2923

3 8