- sr-users - kamailio.org

Authentication qop auth-int
by 13715209697＠139.com 25 Apr '25

25 Apr '25

Hello! Kamailio 5.7.6 Debian 10.12 Here is my authentication route: ``` route[AUTH] { if (is_method("REGISTER") || from_uri==myself) { if (!auth_check("$fd", "subscriber", "0")) { auth_challenge("$fd", "2"); # flag not 0 exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } ... } ``` start eyebeam Version 1.5.14.4 ``` eyebeam --->REGISTER ----> kamailio <--401 (WWW-Authenticate: Digest realm="192.168.3.10", nonce=..., qop="auth-int") --->REGISTER (Authorization: Digest username="08001",realm="192.168.3.10",nonce=...,uri=...,response=...,cnonce=...,nc=00000001,qop=auth-int,algorithm=MD5) <--401 (auth_challenge() return -2 ) ``` OpenSIPS 3.4.12 register to kamailio, got the same result as eyebeam Any suggestions? Thanks!

1 0

Re: SIP Call Drops After 0.32 Seconds – Asterisk on Kubernetes with Kamailio + RTPengine
by airsay＠duck.com 25 Apr '25

25 Apr '25

I will let the more experienced Kamailio folks comment on the technical/Kamailio/RTP modifications that you need to make. The SIP standard requires an ACK to a 200 OK to be sent within that 32 second window. If an ACK is not received, the session is torn down. You would need to do a packet capture to review the Contact header in the SIP and the c: in the SDP. I'm just getting bedded in with SIP, reading Alan B Johnston's "SIP: Understanding the Session Initiation Protocol". Excellent introduction to understanding SIP. Best regards Sent from my iPhone > On 23 Apr 2025, at 16:35, Fernando Lopes via sr-users <sr-users_at_lists.kamailio.org_airsay(a)duck.com> wrote: > > Hello everyone, > I'm running into an issue with SIP calls in my current setup and would really appreciate some help. > > Setup: > I have a machine named sip00 (IP: 192.168.1.75) running Kamailio + RTPengine. > Kamailio is dispatching calls to sip:192.168.1.190:32210;transport=tcp. This IP points to another machine running Asterisk inside a Kubernetes cluster. > RTPengine is configured with an RTP port range of 10000–20000, and my router is set to allow that same range. > > Asterisk Kubernetes Service Configuration: > yaml > Copy > Edit > spec: > ports: > - name: tcp-port > protocol: TCP > port: 5060 > targetPort: 5060 > nodePort: 32210 > - name: udp-port > protocol: UDP > port: 5060 > targetPort: 5060 > nodePort: 32210 > > Problem: > When I initiate a SIP call, the router forwards traffic to Kamailio + RTPengine, which then sends it to the Asterisk server on 192.168.1.190. > Everything seems fine initially, but at exactly 0.32 seconds into the call, Asterisk sends a BYE and no longer responds with 200 OK to the SIP dialog — even though I'm still receiving and sending audio. Then, at around 01:04, I get a 408 Request Timeout. > > Questions: > Do I need to explicitly expose the RTP port range (10000–20000) in the Asterisk Kubernetes service as well? > Why is Asterisk sending a BYE so early if audio is still flowing? > Could it be a signaling timeout or an issue with SIP dialog tracking? > Any help or pointers would be greatly appreciated! > > Thanks in advance! > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the sender!

3 2

rtpengine module does not detect new nodes in table
by David Cunningham 24 Apr '25

24 Apr '25

Hello, We are using Kamailio 5.8.2 with the rtpengine module on Ubuntu 22.04. The "rtpengine" table is used to define nodes, with a configuration like this: modparam( "rtpengine", "db_url", DB_URL ) modparam( "rtpengine", "table_name", "rtpengine" ) modparam( "rtpengine", "setid_default", 1 ) It works fine if Kamailio is restarted after entries in the "rtpengine" table are inserted or deleted, but new entries in the table aren't detected automatically. Is there a way to configure Kamailio to detect them? Thank you, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

2 1

Re: RTPengine media starts for intiating caller only
by airsay＠duck.com 23 Apr '25

23 Apr '25

Again, not super skilled yet with Kamailio/RTPEngine, but my first instinct is: "why you are advertising myproxyname.domain.net which is possibly a public IP". Your entire setup is in your LAN so you don't need to advertise any public IP. Look forward to others contributing and clarifying that Sent from my iPhone > On 23 Apr 2025, at 20:42, smh2017--- via sr-users <sr-users_at_lists.kamailio.org_airsay(a)duck.com> wrote: > > Hello, > > I have a problem with my basic Kamailio setup using RTPengine. I'm testing initially with two client UAs in the same LAN as the SIP server behind the firewall. The initiating UA starts the media proxy as soon as the receiving UA accepts the call, indicated by the call timer starting. But after accepting the call the receiving UA's timer doesn't start and after 10-15 secs hangs up with a NO ACK error message. > > I am using the kamailio default config file that comes with the Debian package and have made minimal changes recommended by various How-Tos for using Kamailio behind a firewall. Because the clients can successfully register over TLS, I'm assuming the problem is in the rtpengine configuration. The two rtp listen parameters I've tried are: > > interface = internal/192.168.1.100;external/192.168.1.100!myproxyname.domain.net > --or-- > interface = internal/192.168.1.100;external/myproxyname.domain.net > listen-ng = localhost:2223 > > I'm not sure why some example rtpengine configs list both the private and public addresses as external. > > Any suggestions where to start troubleshooting? > > Thanks, > > Steve > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the sender!

2 1

RTPengine media starts for intiating caller only
by smh2017＠zoho.com 23 Apr '25

23 Apr '25

Hello, I have a problem with my basic Kamailio setup using RTPengine. I'm testing initially with two client UAs in the same LAN as the SIP server behind the firewall. The initiating UA starts the media proxy as soon as the receiving UA accepts the call, indicated by the call timer starting. But after accepting the call the receiving UA's timer doesn't start and after 10-15 secs hangs up with a NO ACK error message. I am using the kamailio default config file that comes with the Debian package and have made minimal changes recommended by various How-Tos for using Kamailio behind a firewall. Because the clients can successfully register over TLS, I'm assuming the problem is in the rtpengine configuration. The two rtp listen parameters I've tried are: interface = internal/192.168.1.100;external/192.168.1.100!myproxyname.domain.net --or-- interface = internal/192.168.1.100;external/myproxyname.domain.net listen-ng = localhost:2223 I'm not sure why some example rtpengine configs list both the private and public addresses as external. Any suggestions where to start troubleshooting? Thanks, Steve

1 0

SIP Call Drops After 0.32 Seconds – Asterisk on Kubernetes with Kamailio + RTPengine
by Fernando Lopes 23 Apr '25

23 Apr '25

Hello everyone, I'm running into an issue with SIP calls in my current setup and would really appreciate some help. Setup: I have a machine named sip00 (IP: 192.168.1.75) running Kamailio + RTPengine. Kamailio is dispatching calls to sip:192.168.1.190:32210;transport=tcp. This IP points to another machine running Asterisk inside a Kubernetes cluster. RTPengine is configured with an RTP port range of 10000–20000, and my router is set to allow that same range. Asterisk Kubernetes Service Configuration: yaml Copy Edit spec: ports: - name: tcp-port protocol: TCP port: 5060 targetPort: 5060 nodePort: 32210 - name: udp-port protocol: UDP port: 5060 targetPort: 5060 nodePort: 32210 Problem: When I initiate a SIP call, the router forwards traffic to Kamailio + RTPengine, which then sends it to the Asterisk server on 192.168.1.190. Everything seems fine initially, but at exactly 0.32 seconds into the call, Asterisk sends a BYE and no longer responds with 200 OK to the SIP dialog — even though I'm still receiving and sending audio. Then, at around 01:04, I get a 408 Request Timeout. Questions: Do I need to explicitly expose the RTP port range (10000–20000) in the Asterisk Kubernetes service as well? Why is Asterisk sending a BYE so early if audio is still flowing? Could it be a signaling timeout or an issue with SIP dialog tracking? Any help or pointers would be greatly appreciated! Thanks in advance!

1 0

404 sent from Kamailio NOT from the script
by Richard Robson 23 Apr '25

23 Apr '25

I have a problem where a call comes in and causing a 404 Not Found to be replied. the script does not have a 404 reply set in it anywhere unfortunately I cannot get the script to produce logs, hence my other post. But its making it tricky to find the source of the 404. following the script it should not be producing a 404, but doing a relay. I suspect there is something wrong with the tm or its not getting a result it needs. It looks like the transaction module is triggering thge 404 somehow and Its showing up in debug below. Does anyone have any ideas why i'm getting a 404? version 5.6.6 Regards, Richard Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=3/28700 T start=0xffffffffffffffff Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430] Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:703]: t_lookup_request(): no transaction found Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1172]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T end=(nil) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1394]: t_newtran(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T start=(nil) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430] Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:703]: t_lookup_request(): no transaction found Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 8336) called from tm: h_table.c: build_cell(336) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_hooks.c:342]: run_reqin_callbacks_internal(): trans=0x7faf932f42c0, callback type 1, id 0 entered Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 40) called from tm: t_hooks.c: insert_tmcb(134) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T start=0x7faf932f42c0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1176]: t_check_msg(): T (0x7faf932f42c0) already found for msg (0x7faf977b64b0)! Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 626) called from tm: t_reply.c: _reply_light(488) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:1768]: cleanup_uac_timers(): RETR/FR timers reset Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_hooks.c:252]: run_trans_callbacks_internal(): DBG: trans=0x7faf932f42c0, callback type 512, id 0 entered Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} acc [acc_logic.c:721]: tmcb_func(): acc callback called for t(0x7faf932f42c0) event type 512, reply code 404 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:625]: _reply_light(): reply sent out - buf=0x7faf977bf7f8: SIP/2.0 404 Not Foun... shmem=0x7faf932f0468: SIP/2.0 404 Not Foun Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_funcs.c:122]: put_on_wait(): put T [0x7faf932f42c0] on wait Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:495]: qm_free(): qm_free(0x7faf976b5010, 0x7faf977bf7f8), called from tm: t_reply.c: _reply_light(635) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:636]: _reply_light(): finished Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} sl [sl.c:288]: send_reply(): reply in stateful mode (tm)

4 7

Kamailio docker with missing modules
by Martin Nyström 23 Apr '25

23 Apr '25

Hi, I’m using the docker ghcr.io/kamailio/kamailio:5.8.6-xenial but it appears to be missing the app_python modules. How can I add it, together with other missing modules? /M

1 2

Behaviour of suspended transactions
by Alex Balashov 18 Apr '25

18 Apr '25

Hello! Two questions about suspended transactions: 1) What is the lifetime of a suspended INVITE transaction? Can I change it? 2) While a transaction is suspended, its event hooks (e.g. onreply_route, failure_route) do not run, of course, even if replies that match the transaction are received. Is there a way to intercept these replies externally and resume the transaction upon the receipt of the reply, and prior to the processing of the reply? For example, can the replies be captured in a stateless route, and mapped Call-ID => index/label to t_continue() the transaction, then have the transaction state machine process that very same reply too? t_is_retr_async_reply() seems to hint at this intention, but its scope is more narrow, if I understood the documentation correctly: it seems to deal with retransmissions only. The code path I'm interested in is more akin to a t_is_reply_to_async() function. As you might guess, the driver for this inquiry is a mobile workflow where, in the vast majority of cases, one is contacting a stale registration and should just suspend the transaction, but where occasionally, in a small minority of cases, the endpoint does respond on the existing contact. The standard tsilo workflow of trickling parallel branches into a pending transaction doesn't work here because of the behaviour of Apple's CallKit; we have to try the existing contact _before_ we send a push notification. -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

3 2

XLOG not writing to local0
by Richard Robson 17 Apr '25

17 Apr '25

I have setup the kamailio.log file to receive the logs from kamailio and I am receiving some, but I do mot see any logs from xlog commands in the script. I see logs like this on startup and various others, but none from xlog no matter how I format them. can anyone advise where I may be going wrong? current logs: Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 12 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 12 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 13 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 13 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 14 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9073]: INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 14 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9118]: INFO: jsonrpcs [jsonrpcs_sock.c:453]: jsonrpc_dgram_process(): a new child 0/9118 Apr 17 12:28:49 server01 /usr/local/sbin/kamailio[9120]: INFO: ctl [io_listener.c:217]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) config: debug=4 log_stderror=no log_facility=LOG_LOCAL0 log_prefix="[$mt $hdr(CSeq) $ci] " example xlogs that do not print (they are the start of request route): xlog("LOG_LOCAL0","L_ERR","RIK: Start route\n"); xlog("TRACE: Start Route [Main] for [Call-ID: $ci]\n");

2 2

IPv6 bind wrong IP. #4199
by Vu Nguyen 17 Apr '25

17 Apr '25

*Dear Sir,* I have opened an issue on GitHub: *"IPv6 bind wrong IP. #4199 <https://github.com/kamailio/kamailio/issues/4199>"*. *System Details:* - *Kamailio (5.8.x)* – SIP Proxy - *FreeSWITCH* – Media Server - *OS* – Debian 12 - *Gateway* – aaaa:bbb:cccc:20::1 - *IPv6 Address* – aaaa:bbb:cccc:20::41e ------------------------------ *kamailio.cfg:* #!define ADDR_IPV4 xxx.xxx.xxx.xxx #!define ADDR_IPV6 [aaaa:bbb:cccc:20::41e] listen=ADDR_IPV4 listen=ADDR_IPV6 ------------------------------ *netstat Output:* tcp6 0 0 aaaa:bbb:cccc:20:::5060 :::* LISTEN 1691274/kamailio tcp6 0 0 aaaa:bbb:cccc:20:::5061 :::* LISTEN 1691274/kamailio udp6 0 0 aaaa:bbb:cccc:20:::5060 :::* 1691222/kamailio As shown, although I explicitly set the listen IP to aaaa:bbb:cccc:20::41e, Kamailio strips the last part of the address and binds to aaaa:bbb:cccc:20:: I also upgraded to *version 6.0* with default cfg and set auto_bind_ipv6=1 or changed ipv6 address, but the issue still persists. ------------------------------ *IPv6 Interface Configuration:* auto eth1 iface eth1 inet6 static address aaaa:bbb:cccc:20::41e netmask 64 gateway aaaa:bbb:cccc:20::1 I can successfully ping in and out using this IPv6 address. ------------------------------ Do I need to configure anything else in Kamailio or the system to ensure it binds to the full IPv6 address aaaa:bbb:cccc:20::41e as expected? Currently I can register with ipv4, but ipv6 does not. Thank you for your assistance.

3 2

Handling NAT Keepalive in IMS PCSCF Configuration: Bypassing NATHelper Module
by f.soltanzade72＠gmail.com 16 Apr '25

16 Apr '25

Hi All, In the default Kamailio configuration, keepalive handling for NAT is typically managed through the NATHelper module. However, in the IMS PCSCF configuration, the NATPING route is used to send SIP OPTIONS messages for keepalive, which bypasses the NATHelper module. This approach makes it impossible to send raw UDP packets for keepalive handling. Can any one help me configuring that? Thank you.

1 0

How to place a delay between cancelling branch and retrying next one on timer expiry?
by Alex A 15 Apr '25

15 Apr '25

Hi All, I have an interesting use-case where I need to place a delay between cancelling branch and retrying next one. *Background: * Running Kamailio 5.6.x Kamailio routes requests via a freeswitch B2BUA server on select call flows (where B2BUA functionality is required). Call flow examples: PSTN --> Kamailio --> Freeswitch --> appserver1 PSTN --> Kamailio --> Freeswitch --> appserver2 On attempt failures, a branch retry is required from appserver1 to appserver2; however freeswitch B2BUA remains the same Since Freeswitch does not quite follow the RFC 3261 timer K specifications (should be 0 seconds for reliable transports, but FS keeps transactions for T4 (set to 2 seconds)); I have implemented an artificial delay in failure route before retrying (as per recommendation described here: https://freeswitch-users.freeswitch.narkive.com/TsSye66D/482-request-merged… ) *Script config: * onreply_route[MANAGE_REPLY] { xlog("L_INFO", "reply $T_reply_code received"); if (t_check_status( "1[1-9][0-9]")) { t_reset_fr(); } else { t_set_fr(120000); } } route(NATDETECT); #!ifdef WITH_RTPENGINE route(RTPMANAGE); #!endif } route[RELAY] { if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { setflag(FLT_DLGINFO); } if (!t_relay()) { sl_reply_error(); } exit; } route[TOCARRIER] { process bunch of things, attach custom headers, generate request URI t_on_failure("MANAGE_FAILURE_CARRIER"); route(RELAY); } failure_route[MANAGE_FAILURE_CARRIER] { xlog("L_INFO", "reply $T_reply_code received"); if ($avp(inbound_attempt)<=1){ if ($dlg_var(b2bua)=="true"){ usleep(1900000); } route("TOCARRIER"); } *Call Flows: * The above fix works well when an explicit error reply is received back. *error reply SIP exchange: * SBC --> INVITE(branch0) ---> Freeswitch SBC <-- 503 <-- Freeswitch failure_route executed (sleep runs here) SBC --> INVITE(branch1) ---> Freeswitch call continues as expected. however does not work when NO reply is received at all and the timer expires. *Current timer expiry SIP exchange: * SBC --> INVITE(branch0) ---> Freeswitch SBC <-- 100/180 <-- Freeswitch SBC (timer expires) failure_route executed (sleep runs here) SBC --> INVITE(branch1) ---> Freeswitch SBC <-- 482 Merged <-- Freeswitch SBC --> CANCEL(branch0) ---> Freeswitch I am looking to CANCEL branch0 before the sleep delay runs Based on source code, t_cancel_branches("this") can only be executed in reply_route; however the chellenge is that reply_route never sees the "faked 408" on timer expiry(although the failure route does see $T_reply_code 408). Any suggestions on how to handle this would be greatly appreciated. TIA

6 11

RTPEngine pool selection for in-dialog requests
by Ben Kaufman 15 Apr '25

15 Apr '25

I'm looking for information on the correct way to handle calls to RTPEngine when processing in-dialog requests. I currently have several setid's configured for varying usages. During processing of an initial INVITE, a determination is made as to if the call will require the use of RTPEngine, and if so, which of the sets should be used. The following is done in code: * setid is assigned to AVP $avp(rtpengine_pool_num) * set_rtpengine_set("$avp(rtpengine_pool_num)") is called, * rtpengine_offer is then called. * Additionally, a record-route parameter of proxy_media=yes is added. * The flag PROXY_MEDIA is set In the reply route, the PROXY_MEDIA flag is checked, and if set, set_rtpengine_set("$avp(rtpengine_pool_num)") is called, followed by rtpengine_answer. When handling an in-dialog message my code didn't have anything to evaluate for the setid. rtpengine_offer was just called. Looking at the debug from the rtpengine module, I can see that the record is found in the hashtable, however the node indicated in that result is not necessarily used - rtpengine will select an entry from the default setid instead. From the rtpengine module logs, IP addresses redacted: 2(9) DEBUG: {time=1744651756.968228} rtpengine [rtpengine_funcs.c:139]: check_content_type(): type <application/sdp> found valid 2(9) DEBUG: {time=1744651756.968228} rtpengine [rtpengine.c:2249]: build_rtpp_socks(): same rtpengines list version: 1 (1744651613) 2(9) DEBUG: {time=1744651756.968228} rtpengine [rtpengine.c:3818]: select_rtpp_node_old(): rtpengine hash table lookup find node=udp:A.B.C.D:1234 for calllen=36 callid=ac66f56b-93f8-123e-1b99-0242ac120002 viabranch= 2(9) DEBUG: {time=1744651756.968228} rtpengine [rtpengine.c:3702]: select_rtpp_node_new(): sum is = 210 2(9) DEBUG: {time=1744651756.968228} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d3:sdp288:v=0 o=FreeSWITCH 1744611570 1744611571 IN IP4 W.X.Y.Z s=FreeSWITCH c=IN IP4 W.X.Y.Z My question is really: **SHOULD** rtpengine_offer (and rtpengine_manage, etc) use the node that it finds in the hash table lookup automatically, or should I have to explicitly set the setid? For now I've solved the problem by adding the setid to the record-route headers so I can easily retrieve it in dialog, but it seems that if the module finds a record for a node that there should be some way to rely on that explicitly. Kaufman Senior Voice Engineer E: bkaufman(a)bcmone.com SIP.US Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 | Flowroute Client Support: 855.356.9768 [img]<https://www.sip.us> [img]<https://www.siptrunk.com> [img]<https://www.flowroute.com> NOTE: This e-mail and any attachments are from BCM One, Inc. and are intended solely for the use and review of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail (and any attachments) from your computer and do not copy or disclose it to anyone else.

2 2

Thank you Guys
by Fernando Lopes 15 Apr '25

15 Apr '25

Just want to say thank you for the support. I spent two weeks working on a config, and even though it didn’t work out, I really appreciate the learning process. Today, I found a config that worked here: 🔗 https://github.com/altanai/kamailioexamples/tree/master/RTPEngine_media_pro…

1 0

Nat Problems Kamailio
by Fernando Lopes 14 Apr '25

14 Apr '25

Hello Everyone, I'm having some trouble getting my SIP setup to work properly. 📞 My Call Flow: SIP Client initiates a call The call reaches my router, which forwards it to Kamailio + RTPengine running on 192.168.1.75:5060, which then forwards it to A Kubernetes machine at 192.168.1.190:32210, where Asterisk is running 🔧 Network Setup: Router has the following ports forwarded: UDP 5060 UDP 10000–20000 (for RTP) STUN is enabled on the SIP client ✅ What Works: When I’m connected through a VPN (i.e., inside the local network), everything works fine — both incoming and outgoing audio. ❌ The Problem: When calling from outside the network, signaling works and the call connects, but I can’t receive or send any audio. Here is a little of my config of kamailio modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223") modparam("rtpengine", "setid_avp", "$avp(setid)") listen=udp:192.168.1.75:5060 advertise 62.2x.xxx.xxx:5060 listen=tcp:192.168.1.75:5060 advertise 62.2x.xxx.xxx:5060 listen=udp:127.0.0.1:5060 #Nat Helper modparam("nathelper", "force_socket", "192.168.1.75:5060") modparam("nathelper", "natping_interval", 10) modparam("nathelper", "ping_nated_only", 0) modparam("nathelper", "nat_addr_mode", 1) request_route{ ... route(init); ... if(is_method("INVITE|ACK|BYE|CANCEL|OPTIONS|INFO|UPDATE|PRACK"))\{ route(handle_sip); exit; } } route[init]{ ... if (nat_uac_test("19")){ setflag(FLT_NAT); fix_nated_contact(); force_rport(); } } route[handle_sip]{ if ($rm == "INVITE"){ if (isflagset(FLT_NAT)){ route(natmanage); } if (!ds_select_dst("1", "4")){ sl_send_reply("500", "No destination"); exit; } $ru = "sip:" + $rU + "@" + $rd; # Keeps sip:100@domain $du = "sip:192.168.1.190:32210"; # Matches your dispatcher list route(relay); } if ($rm == "BYE" || $rm == "CANCEL"){ if (isflagset(FLT_NAT)){ rtpengine_delete(); } route(relay); } if ($rm == "ACK"){ if (isflagset(FLT_NAT)){ route(natmanage); } route(relay); } route(relay); } route[natmanage]{ if (is_request()){ if (has_body("application/sdp")){ rtpengine_offer("replace-origin replace-session-connection ICE=remove"); } force_rport(); fix_nated_contact(); }else{ rtpengine_answer("replace-origin replace-session-connection ICE=remove"); } } rtpengine.conf [rtpengine] table = 0 interface = internal/192.168.1.75 listen-ng = 127.0.0.1:2223 log-level = 7 timeout = 60 silent-timeout = 3600 tos = 184 port-min = 10000 port-max = 40000 And here are some logs when I call from outside 2025/04/13 15:58:33.407265 2.8x.xx.xxx:59396 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.116:59396;rport;branch=z9hG4bKPj92490d6b6d0c4cd88dac9f0043b1642e Max-Forwards: 70 From: "6001" <sip:6005@192.168.1.75:5060>;tag=0397d2bdc3ef47f5b6e498126a360b0f To: <sip:100@192.168.1.75:5060> Contact: "6001" <sip:6005@192.168.1.116:59396;ob>;+sip.ice Call-ID: 83a804569c3f489088607c729485cdbd CSeq: 8963 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 537 v=0 o=- 3953552313 3953552313 IN IP4 192.168.1.116 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4032 RTP/AVP 8 0 101 c=IN IP4 192.168.1.116 b=TIAS:64000 a=rtcp:4017 IN IP4 192.168.1.116 a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:1567952351 cname:73284f1717045a81 a=ice-ufrag:37e51dc0 a=ice-pwd:49f7442b5078148140877b44 a=candidate:Hc0a80174 1 UDP 2130706431 192.168.1.116 4032 typ host a=candidate:Hc0a80174 2 UDP 2130706430 192.168.1.116 4017 typ host 2025/04/13 15:58:33.412683 192.168.1.75:5060 -> 192.168.1.190:32210 INVITE sip:100@192.168.1.75 SIP/2.0 Via: SIP/2.0/UDP 62.2x.2xx.xxx:5060;branch=z9hG4bK6362.26a75297a4ccf4984dd1f68644c2148f.0 Via: SIP/2.0/UDP 192.168.1.116:59396;received=2.8x.xx.xxx;rport=59396;branch=z9hG4bKPj92490d6b6d0c4cd88dac9f0043b1642e Max-Forwards: 69 From: "6001" <sip:6005@192.168.1.75:5060>;tag=0397d2bdc3ef47f5b6e498126a360b0f To: <sip:100@192.168.1.75:5060> Contact: "6001" <sip:6005@2.8x.xx.xxx:59396;ob>;+sip.ice Call-ID: 83a804569c3f489088607c729485cdbd CSeq: 8963 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 322 v=0 o=- 3953552313 3953552313 IN IP4 192.168.1.75 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 12156 RTP/AVP 8 0 101 c=IN IP4 192.168.1.75 b=TIAS:64000 a=ssrc:1567952351 cname:73284f1717045a81 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:12157 2025/04/13 15:58:33.428169 2.8x.xx.xxx:59396 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.116:59396;rport;branch=z9hG4bKPj14c6f24b814e4d158014cc80b1fa5f8f Max-Forwards: 70 From: "6001" <sip:6005@192.168.1.75:5060>;tag=0397d2bdc3ef47f5b6e498126a360b0f To: <sip:100@192.168.1.75:5060> Contact: "6001" <sip:6005@192.168.1.116:59396;ob>;+sip.ice Call-ID: 83a804569c3f489088607c729485cdbd CSeq: 8964 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Authorization: Digest username="6005", realm="asterisk", nonce="1744559913/dab8894e3f31e038d7a969a6349a11c2", uri="sip:100@62.2x.2xx.xxx", response="2ce500d6a1583f05f6344bdf1f712fc7", algorithm=MD5, cnonce="808fc766135d40589dd68032bcaab5c6", opaque="2232aa9c42080f12", qop=auth, nc=00000001 Content-Type: application/sdp Content-Length: 537 v=0 o=- 3953552313 3953552313 IN IP4 192.168.1.116 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4032 RTP/AVP 8 0 101 c=IN IP4 192.168.1.116 b=TIAS:64000 a=rtcp:4017 IN IP4 192.168.1.116 a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:1567952351 cname:73284f1717045a81 a=ice-ufrag:37e51dc0 a=ice-pwd:49f7442b5078148140877b44 a=candidate:Hc0a80174 1 UDP 2130706431 192.168.1.116 4032 typ host a=candidate:Hc0a80174 2 UDP 2130706430 192.168.1.116 4017 typ host 2025/04/13 15:58:33.430593 192.168.1.75:5060 -> 2.8x.xx.xxx:59396 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 192.168.1.116:59396;rport=59396;branch=z9hG4bKPj14c6f24b814e4d158014cc80b1fa5f8f;received=2.8x.xx.xxx From: "6001" <sip:6005@192.168.1.75:5060>;tag=0397d2bdc3ef47f5b6e498126a360b0f To: <sip:100@192.168.1.75:5060> Call-ID: 83a804569c3f489088607c729485cdbd CSeq: 8964 INVITE Server: kamailio (5.7.4 (x86_64/linux)) Content-Length: 0 2025/04/13 15:58:33.461894 192.168.1.75:5060 -> 192.168.1.190:32210 INVITE sip:100@192.168.1.75 SIP/2.0 Via: SIP/2.0/UDP 62.2x.2xx.xxx:5060;branch=z9hG4bK3362.72f5db87deeeccee7fea924753af3da0.0 Via: SIP/2.0/UDP 192.168.1.116:59396;received=2.8x.xx.xxx;rport=59396;branch=z9hG4bKPj14c6f24b814e4d158014cc80b1fa5f8f Max-Forwards: 69 From: "6001" <sip:6005@192.168.1.75:5060>;tag=0397d2bdc3ef47f5b6e498126a360b0f To: <sip:100@192.168.1.75:5060> Contact: "6001" <sip:6005@2.8x.xx.xxx:59396;ob>;+sip.ice Call-ID: 83a804569c3f489088607c729485cdbd CSeq: 8964 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Authorization: Digest username="6005", realm="asterisk", nonce="1744559913/dab8894e3f31e038d7a969a6349a11c2", uri="sip:100@62.2x.2xx.xxx", response="2ce500d6a1583f05f6344bdf1f712fc7", algorithm=MD5, cnonce="808fc766135d40589dd68032bcaab5c6", opaque="2232aa9c42080f12", qop=auth, nc=00000001 Content-Type: application/sdp Content-Length: 322 v=0 o=- 3953552313 3953552313 IN IP4 192.168.1.75 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 12156 RTP/AVP 8 0 101 c=IN IP4 192.168.1.75 b=TIAS:64000 a=ssrc:1567952351 cname:73284f1717045a81 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:12157 Please Help me, Thank you.

4 8

TCP timeout
by Pyry Aaltonen 11 Apr '25

11 Apr '25

Hello, I´ve googled around about tcp timeout in kamailio tcp connections when the tcp connection is broken. Found this old question and to me it feels like I’m having that same situation as original question https://www.mail-archive.com/sr-users@lists.kamailio.org/msg15020.html Also found this https://kamailio.org/mailman3/hyperkitty/list/sr-dev@lists.kamailio.org/thr… and it seems to be the same description pretty much that I´m seeing. When the tcp connection (or tls) is interrupted in the network it takes around 15min for kamailio to reset the outgoing tcp connection. I see in the logs that when restarting kamailio process it logs 2025-03-27 12:25:18.697 { "level": "INFO", "module": "core", "file": "core/tcp_main.c", "line": 3282, "function": "tcp_init", "logprefix": "", "message": "Set TCP_USER_TIMEOUT=10000 ms" } So I think the fix from this https://github.com/kamailio/kamailio/commit/d893f3af1444c8c4c5db6cd53fb5777… is applied. This is tested with 5.8.5 and I have tested this by setting up with dispatcher tcp connection to external host Then with iptables drop traffic to that host, waiting kamailio to notice that destination is down, removing the iptables input and it takes around 15min to recover. (also restarting the kamailio helps and resolves the connection) And this is what kamailio prints during the test: Apr 4 08:29:15 kamailio[156947]: { "level": "ERROR", "module": "xlog", "file": "xlog.c", "line": 278, "function": "", "logprefix": "", "message": "Destination down: OPTIONS sip:ext-host;transport=tcp (<null>)" } Apr 4 08:44:43 kamailio[156957]: { "level": "ERROR", "module": "core", "file": "core/tcp_read.c", "line": 267, "function": "tcp_read_data", "logprefix": "", "message": "error reading: Connection timed out (110) ([]:5060 -> []:47492)" } Apr 4 08:44:43 kamailio[156957]: { "level": "ERROR", "module": "core", "file": "core/tcp_read.c", "line": 1524, "function": "tcp_read_req", "logprefix": "", "message": "error reading - c: 0x7f8625dea9b0 r: 0x7f8625deaad8 (-1)" } Apr 4 08:45:05 kamailio[156957]: { "level": "ERROR", "module": "xlog", "file": "xlog.c", "line": 278, "function": "", "logprefix": "Source:[ext-host]:5060, Call-id:4d0e1ccd315c817f-156947@int-host, CSeq:10", "message": "Destination up: OPTIONS sip:ext.host;transport=tcp (<null>)" } Any advice how to lower the timeout to be quicker in such event? -Pyry

5 6

leave
by Mihail D. 11 Apr '25

11 Apr '25

leave

1 0

STUN Server vs. NAT Configuration with Kamailio + RTPengine Setup
by Fernando Lopes 11 Apr '25

11 Apr '25

Previous Thread: https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… Hello everyone, Should I use a STUN server, or can I just configure NAT properly? Here’s my current setup: arduino Copy Edit Router (NAT device) ↓ Kamailio + RTPengine machine ↓ Virtual machine running Kubernetes ↓ Asterisk container Kamailio and RTPengine are sitting behind the NAT (the router), and they handle SIP and media. Do I need a STUN server in this case, or can I manage everything with NAT configuration alone? And what is the better approach? Any insights or best practices would be appreciated! Thank you.

2 1

IPv6 bind wrong IP. #4199
by vunm.allsign＠gmail.com 11 Apr '25

11 Apr '25

Hi guys, I opened issue on github: https://github.com/kamailio/kamailio/issues/4199 - Description: Kamailio (5.8.x): SIP proxy FreeSWITCH: Media - OS: Debian 12 gateway: aaaa:bbb:cccc:20::1 ipv6: aaaa:bbb:cccc:20::41e - kamailio.cfg: #!define ADDR_IPV4 xxx.xxx.xxx.xxx #!define ADDR_IPV6 [aaaa:bbb:cccc:20::41e] listen=ADDR_IPV4 listen=ADDR_IPV6 - I execute netstat -nlutp: tcp6 0 0 aaaa:bbb:cccc:20:::5060 :::* LISTEN 1691274/kamailio tcp6 0 0 aaaa:bbb:cccc:20:::5061 :::* LISTEN 1691274/kamailio udp6 0 0 aaaa:bbb:cccc:20:::5060 :::* 1691222/kamailio Why I set listen ip is aaaa:bbb:cccc:20::41e but kamailio stripped the last part of the address aaaa:bbb:cccc:20:: I have tried many ways but it does not work.Is there any additional configuration required regarding the Debian network interface? - Here is interfaces(of course i can ping from/to ipv6 address): # Additional interfaces, just in case we're using # multiple networks allow-hotplug eth1 iface eth1 inet6 static address aaaa:bbb:cccc:20::41e netmask 64 gateway aaaa:bbb:cccc:20::1 autoconf 0 Thank you.

2 1

Load multiple geoip2 databases (City + ASN)
by Joel Serrano 10 Apr '25

10 Apr '25

Hi guys, Is there a way to have multiple geoip2 databases loaded into Kamailio and then point the geoip2_match to them? If I understand correctly the docs I can only load one: https://www.kamailio.org/docs/modules/6.0.x/modules/geoip2.html#geoip2.p.pa… Is my assumption correct? Thanks, Joel.

3 5

Kamailio + RTP Engine question
by fernandolopes20003＠gmail.com 08 Apr '25

08 Apr '25

Hi everyone, I'm experiencing some issues with Kamailio and RTP Engine. Here's the setup: A user initiates a call, and the traffic goes through a router. The router forwards the traffic to a machine at 192.168.1.75, which runs Kamailio and RTP Engine. Kamailio uses a dispatcher to forward calls to 192.168.1.190, a Kubernetes node running an Asterisk container. The problem: When I'm inside the network, everything works fine — I can send and receive audio. But when I'm outside the network, the call connects, but there's no audio in either direction (no send or receive). Some Configs: Kamailio.conf: modparam("rtpengine", "rtpengine_sock", "udp:0.0.0.0:2223") listen=udp:192.168.1.75:5060 listen=tcp:192.168.1.75:5060 listen=udp:127.0.0.1:5060 # ----- dispatcher params ----- modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 2) modparam("dispatcher", "xavp_dst", "_dsdst_") modparam("dispatcher", "xavp_ctx", "_dsctx_") modparam("dispatcher", "ds_ping_from", "sip:proxy@kamailio.org") modparam("dispatcher", "ds_ping_interval", 60) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_timer_mode", 1) rtpengine.conf: interface = 192.168.1.75 listen-udp = 0.0.0.0:2223 port-min = 10000 port-max = 20000 Firewall: To Action From -- ------ ---- 22 ALLOW Anywhere 12222/udp ALLOW Anywhere 5060/udp ALLOW Anywhere 10000:20000/udp ALLOW Anywhere 22 (v6) ALLOW Anywhere (v6) 12222/udp (v6) ALLOW Anywhere (v6) 5060/udp (v6) ALLOW Anywhere (v6) 10000:20000/udp (v6) ALLOW Anywhere (v6) Also router has all this ports open Thank you.

5 6

Question: Kamailio + Rtpengine + NAT
by Fernando Lopes 08 Apr '25

08 Apr '25

Previous Thread: https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… I've followed some suggestions and got to check sip packets and got this. Change some configs, but couldn't get any NAT configuration to work, hoping to get a new opinion if it still, maybe it is a problem with NAT or maybe another thing. #-------------------------------------------------------------------------------------------------------# #-------------------------------------------------------------------------------------------------------# Called from "outside" and my microsip doesn't have STUN Server on. 2025/04/08 12:19:06.747644 2.81.7x.1xx:59562 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 2.81.7x.1xx:59562;rport;branch=z9hG4bKPj19931b6928594c3b90ba976acb74cd02 Max-Forwards: 70 From: "6002" <sip:6002@192.168.1.75:5060>;tag=7d887491eae24520b8b205a7dcdf569d To: <sip:100@192.168.1.75:5060> Contact: <sip:6002@2.81.7x.1xx:59562;ob>;+sip.ice Call-ID: fa30f64e6adb4b7e9719084b9d34b5b6 CSeq: 8949 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 536 v=0 o=- 3953107147 3953107147 IN IP4 192.168.1.116 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4030 RTP/AVP 8 0 101 c=IN IP4 192.168.1.116 b=TIAS:64000 a=rtcp:4029 IN IP4 192.168.1.116 a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:371808528 cname:7dd13e4d736d4043 a=ice-ufrag:69525f90 a=ice-pwd:16496df15af141bb26e901eb a=candidate:Hc0a80174 1 UDP 2130706431 192.168.1.116 4030 typ host a=candidate:Hc0a80174 2 UDP 2130706430 192.168.1.116 4029 typ host #-------------------------------------------------------------------------------------------------------# #-------------------------------------------------------------------------------------------------------# With STUN Server On -- Also get Register but still can't get any audio 2025/04/08 12:18:26.032585 2.81.7x.1xx:57124 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 2.81.7x.1xx:57124;rport;branch=z9hG4bKPjaf3ec8e03d52425eb67708c7e61457b1 Max-Forwards: 70 From: "6002" <sip:6002@192.168.1.75:5060>;tag=10bf4ad8533a4a45b478c900cb3242b1 To: <sip:100@192.168.1.75:5060> Contact: "6002" <sip:6002@2.81.7x.1xx:57124;ob>;+sip.ice Call-ID: 1e3dea0a3d2f4954b4232c624d37c9d8 CSeq: 7501 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 726 v=0 o=- 3953107106 3953107106 IN IP4 2.81.7x.1xx s=pjmedia b=AS:84 t=0 0 a=X-nat:1 m=audio 4033 RTP/AVP 8 0 101 c=IN IP4 2.81.7x.1xx b=TIAS:64000 a=rtcp:4035 IN IP4 2.81.7x.1xx a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:803428650 cname:24b959022cf70edd a=ice-ufrag:072851d1 a=ice-pwd:10d96c6c6ea14c665c5e6d4e a=candidate:Sc0a80174 1 UDP 1862270975 2.81.7x.1xx 4033 typ srflx raddr 192.168.1.116 rport 4033 a=candidate:Hc0a80174 1 UDP 1694498815 192.168.1.116 4033 typ host a=candidate:Sc0a80174 2 UDP 1862270974 2.81.7x.1xx 4035 typ srflx raddr 192.168.1.116 rport 4035 a=candidate:Hc0a80174 2 UDP 1694498814 192.168.1.116 4035 typ host Thank you Very much.

1 0

Question: Kamailio + Rtpengine + NAT
by Fernando Lopes 08 Apr '25

08 Apr '25

Previous Thread: https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… I've followed some suggestions and got to check sip packets and got this. Change some configs, but couldn't get any NAT configuration to work, hoping to get a new opinion if it still, maybe it is a problem with NAT or maybe another thing. #-------------------------------------------------------------------------------------------------------# #-------------------------------------------------------------------------------------------------------# Called from "outside" and my microsip doesn't have STUN Server on. 2025/04/08 12:19:06.747644 2.81.7x.1xx:59562 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 2.81.7x.1xx:59562;rport;branch=z9hG4bKPj19931b6928594c3b90ba976acb74cd02 Max-Forwards: 70 From: "6002" <sip:6002@192.168.1.75:5060>;tag=7d887491eae24520b8b205a7dcdf569d To: <sip:100@192.168.1.75:5060> Contact: <sip:6002@2.81.7x.1xx:59562;ob>;+sip.ice Call-ID: fa30f64e6adb4b7e9719084b9d34b5b6 CSeq: 8949 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 536 v=0 o=- 3953107147 3953107147 IN IP4 192.168.1.116 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4030 RTP/AVP 8 0 101 c=IN IP4 192.168.1.116 b=TIAS:64000 a=rtcp:4029 IN IP4 192.168.1.116 a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:371808528 cname:7dd13e4d736d4043 a=ice-ufrag:69525f90 a=ice-pwd:16496df15af141bb26e901eb a=candidate:Hc0a80174 1 UDP 2130706431 192.168.1.116 4030 typ host a=candidate:Hc0a80174 2 UDP 2130706430 192.168.1.116 4029 typ host #-------------------------------------------------------------------------------------------------------# #-------------------------------------------------------------------------------------------------------# With STUN Server On -- Also get Register but still can't get any audio 2025/04/08 12:18:26.032585 2.81.7x.1xx:57124 -> 192.168.1.75:5060 INVITE sip:100@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 2.81.7x.1xx:57124;rport;branch=z9hG4bKPjaf3ec8e03d52425eb67708c7e61457b1 Max-Forwards: 70 From: "6002" <sip:6002@192.168.1.75:5060>;tag=10bf4ad8533a4a45b478c900cb3242b1 To: <sip:100@192.168.1.75:5060> Contact: "6002" <sip:6002@2.81.7x.1xx:57124;ob>;+sip.ice Call-ID: 1e3dea0a3d2f4954b4232c624d37c9d8 CSeq: 7501 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.21.5 Content-Type: application/sdp Content-Length: 726 v=0 o=- 3953107106 3953107106 IN IP4 2.81.7x.1xx s=pjmedia b=AS:84 t=0 0 a=X-nat:1 m=audio 4033 RTP/AVP 8 0 101 c=IN IP4 2.81.7x.1xx b=TIAS:64000 a=rtcp:4035 IN IP4 2.81.7x.1xx a=sendrecv a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:803428650 cname:24b959022cf70edd a=ice-ufrag:072851d1 a=ice-pwd:10d96c6c6ea14c665c5e6d4e a=candidate:Sc0a80174 1 UDP 1862270975 2.81.7x.1xx 4033 typ srflx raddr 192.168.1.116 rport 4033 a=candidate:Hc0a80174 1 UDP 1694498815 192.168.1.116 4033 typ host a=candidate:Sc0a80174 2 UDP 1862270974 2.81.7x.1xx 4035 typ srflx raddr 192.168.1.116 rport 4035 a=candidate:Hc0a80174 2 UDP 1694498814 192.168.1.116 4035 typ host Thank you Very much.

1 0

Info: Donating To Kamailio Project
by Daniel-Constantin Mierla 07 Apr '25

07 Apr '25

Hello! Over the years, there have been discussions about what options could be made available to donate to Kamailio project in order to support its required infrastructure, administrative or development of complex components. Creating a foundation or using a crowdfunding platform have been explored, trying to take in consideration the needed man power and overhead, the transparency and accountability. To move forward on this matter, the Kamailio management team has decided to use Open Collective, with the fiscal host Open Collective Europe, as the platform for accepting and managing donations, more details, including the link where donations can be made, are published at: - https://www.kamailio.org/w/donations/ The donations should target either the support of project administration or the development of new feature, therefore before donating it is recommend to email to <management [at] lists.kamailio.org> providing some details about the scope of your donation. We also plan to discuss about it at the next Kamailio World Conference: May 12-13, 2025, organized again in Berlin, Germany, where many developers and members of the management board and our community get together, being a good opportunity to clarify and decide how to use the donations. More details about the event at: - https://www.kamailioworld.com Thanks for flying Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

How does drouting is_from_gw function works
by Samuel Moya Tinoco 02 Apr '25

02 Apr '25

Hi everyone, I'm trying to set my kamailio to route using is_from_gw function from drouting module. I'd like to know which SIP message headers does this function check in order to return true or false Thanks in advance for your help Samuel Moya Tinoco Departamento de Sistemas y Redes Móvil: (+34) 606985997 smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> ViveLibre C/ La Orotava 4 28660 Boadilla del Monte Madrid www.vivelibre.es<http://www.vivelibre.es/> [cid:image001.png@01DBA3D9.AABD8760] Soluciones inteligentes para la autonomía personal

1 0

Kamailio.org -issue with loading page
by Michal Hajek 01 Apr '25

01 Apr '25

Hello, does anyone know why kamailio.org is so slow to load from the EU (e.g. CZ, DE) michalhajek@MacBook-Pro ~ % wget -T 10 -v https://kamailio.org/w/ --2025-04-01 16:56:22-- https://kamailio.org/w/ Resolving kamailio.org (kamailio.org)... 2a00:d60:0:400::2, 193.22.119.66 Connecting to kamailio.org (kamailio.org)|2a00:d60:0:400::2|:443... connected. Unable to establish SSL connection. I test from different places - MacOS, Linux, Windows Thanks Michal

4 3

SIPtrace store database failed
by 17603019528＠163.com 01 Apr '25

01 Apr '25

Hello, I want to store the siptrace dialog in the database，but it gives an error. Is the configuration method incorrect? Kamailio version: ``` 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:51:23 Mar 31 2025 with gcc 4.8.5 ``` here is the log: ####### 8(3550) DEBUG: <core> [core/udp_server.c:731]: udp_rcv_loop(): probing packet received from 172.16.80.3 7935 2(3539) DEBUG: <core> [core/udp_server.c:708]: udp_rcv_loop(): received on udp socket: (106/100/956) [[INVITE sip:1002@172.16.4.113:5460 SIP/2.0 0D 0A Via: SIP/2.0/UDP 172.16.80.3:8798;branch=z9hG4bK-d87543-4]] 2(3539) DEBUG: <core> [core/receive.c:190]: ksr_evrt_received(): event route core:msg-received not defined 2(3539) DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 2(3539) DEBUG: <core> [core/parser/msg_parser.c:722]: parse_msg(): SIP Request: 2(3539) DEBUG: <core> [core/parser/msg_parser.c:724]: parse_msg(): method: <INVITE> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:726]: parse_msg(): uri: <sip:1002@172.16.4.113:5460> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:728]: parse_msg(): version: <SIP/2.0> 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Via] type 1 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d87543-4f7e02083f709d16-1--d87543->; state=6 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 2(3539) DEBUG: <core> [core/parser/parse_via.c:2663]: parse_via(): end of header reached, state=5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:592]: parse_headers(): Via found, flags=2 2(3539) DEBUG: <core> [core/parser/msg_parser.c:594]: parse_headers(): this is the first via 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Contact] type 7 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [To] type 3 2(3539) DEBUG: <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=10 2(3539) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [36]; uri=[sip:1002@172.16.4.113:5460] 2(3539) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (36)["1002"<sip:1002@172.16.4.113:5460> ], to tag (0)[] 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [From] type 4 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Call-ID] type 6 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [CSeq] type 5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <1> <INVITE> 2(3539) DEBUG: <core> [core/receive.c:397]: receive_msg(): --- received sip message - request - call-id: [NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.] - cseq: [1 INVITE] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:263]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:474]: receive_msg(): preparing to run routing scripts... 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=596 a=26 n=xlog 2(3539) INFO: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <script>: 172.16.80.3:8798|172.16.4.113:5460|udp|INVITE 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=605 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=707 a=67 n=set_rpl_no_connect 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=710 a=55 n=force_rport 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Allow] type 21 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Type] type 11 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [User-Agent] type 28 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=25 n=mf_process_maxfwd_header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=749 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=26 n=sanity_check 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:254]: check_ruri_sip_version(): check_ruri_sip_version entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:278]: check_ruri_sip_version(): check_ruri_sip_version passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:286]: check_ruri_scheme(): check_ruri_scheme entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:305]: check_ruri_scheme(): check_ruri_scheme passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:327]: check_required_headers(): check_required_headers entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Length] type 12 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=417 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:350]: check_required_headers(): check_required_headers passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:358]: check_via1_header(): check via1 header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:519]: check_cseq_method(): check_cseq_method entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:553]: check_cseq_method(): check_cseq_method passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:563]: check_cseq_value(): check_cseq_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:591]: check_cseq_value(): check_cseq_value passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:601]: check_cl(): check_cl entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:626]: check_cl(): check_cl passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:643]: check_expires_value(): check_expires_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:679]: check_expires_value(): no expires header found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:776]: check_parse_uris(): check_parse_uris entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:780]: check_parse_uris(): parsing ruri 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:793]: check_parse_uris(): looking up From header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=122cd223 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=29 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:808]: check_parse_uris(): looking up To header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:858]: check_parse_uris(): check_parse_uris passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity_mod.c:252]: w_sanity_check(): sanity checks result: 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=608 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=950 a=25 n=nat_uac_test 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=624 a=24 n=t_precheck_trans 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=24 n=t_check_trans 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1578]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=0/0 T start=0xffffffffffffffff 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:793]: t_lookup_request(): start searching: hash=30439, isACK=0 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:512]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-d87543-4f7e02083f709d16-1--d87543-] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:993]: t_lookup_request(): no transaction found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1650]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=1/3539 T end=(nil) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=757 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=24 n=has_totag 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siputils [checks.c:122]: has_totag(): no totag 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=637 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:742]: grep_sock_info(): checking if host==us: 12==12 && [172.16.4.113] == [172.16.4.113] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:745]: grep_sock_info(): checking if port 5460 (advertise 0) matches port 5460 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/forward.c:446]: check_self(): host (0:172.16.4.113:5460) == me 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=641 a=25 n=remove_hf 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=642 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=644 a=24 n=record_route 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| rr [record.c:490]: record_route(): inserted record route (r2: 1 - plen: 0) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=645 a=24 n=dlg_manage 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:907]: internal_get_dlg(): no dialog callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:975]: dlg_search(): dialog with callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' not found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:478]: build_new_dlg(): new dialog on hash 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:275]: populate_leg_info(): leg(0) route_set [], contact [sip:1003@172.16.80.3:8798], cseq [1] and bind_addr [udp:172.16.4.113:5460] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1040]: link_dlg(): linking dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1049]: link_dlg(): ref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:698]: get_dlg_timeout(): using default timeout 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_cb.c:227]: run_create_callbacks(): dialog=0x7ff07ff56f10 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2128]: trace_dialog(): Spiraled dialog! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2150]: trace_dialog(): trace_info xavp not registered! Probably incoming E2E CANCEL! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_profile.c:541]: set_current_dialog(): setting current dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:780]: dlg_lookup_mode(): ref dlg 0x7ff07ff56f10 with 1 -> 2 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:784]: dlg_lookup_mode(): dialog id=1302 found on entry 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:1927]: dlg_manage(): dialog created before transaction 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1088]: dlg_unref_helper(): unref op on 0x7ff07ff56f10 with 1 from dlg_hash.c:1106 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1092]: dlg_unref_helper(): unref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=658 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=648 a=25 n=sip_trace_mode 2(3539) BUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1917]: trace_add_info_xavp(): URI should be in raw format here 2(3539) ERROR: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1028]: sip_trace_helper(): failed to serialize siptrace info! Won't trace dialog! 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=649 a=24 n=sip_trace 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:618]: sip_trace_insert_db(): storing info - no user 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [db_query.c:72]: db_do_submit_query(): submitted query: insert into ###### here is my kamailio.cfg: ``` loadmodule "siptrace.so" modparam("siptrace", "db_url", DBURL) modparam("siptrace", "traced_user_avp", "$avp(user)") modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_init_mode", 0) ... route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE|REFER")) { record_route(); dlg_manage(); } if (is_method("INVITE")) { sip_trace_mode("d"); sip_trace(); } ```

1 0

SIPtrace store database failed
by 17603019528＠163.com 01 Apr '25

01 Apr '25

Hello, I want to store the siptrace dialog in the database，but it gives an error. Is the configuration method incorrect? Kamailio version: ``` 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:51:23 Mar 31 2025 with gcc 4.8.5 ``` here is the log: ####### 8(3550) DEBUG: <core> [core/udp_server.c:731]: udp_rcv_loop(): probing packet received from 172.16.80.3 7935 2(3539) DEBUG: <core> [core/udp_server.c:708]: udp_rcv_loop(): received on udp socket: (106/100/956) [[INVITE sip:1002@172.16.4.113:5460 SIP/2.0 0D 0A Via: SIP/2.0/UDP 172.16.80.3:8798;branch=z9hG4bK-d87543-4]] 2(3539) DEBUG: <core> [core/receive.c:190]: ksr_evrt_received(): event route core:msg-received not defined 2(3539) DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 2(3539) DEBUG: <core> [core/parser/msg_parser.c:722]: parse_msg(): SIP Request: 2(3539) DEBUG: <core> [core/parser/msg_parser.c:724]: parse_msg(): method: <INVITE> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:726]: parse_msg(): uri: <sip:1002@172.16.4.113:5460> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:728]: parse_msg(): version: <SIP/2.0> 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Via] type 1 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d87543-4f7e02083f709d16-1--d87543->; state=6 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 2(3539) DEBUG: <core> [core/parser/parse_via.c:2663]: parse_via(): end of header reached, state=5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:592]: parse_headers(): Via found, flags=2 2(3539) DEBUG: <core> [core/parser/msg_parser.c:594]: parse_headers(): this is the first via 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Contact] type 7 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [To] type 3 2(3539) DEBUG: <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=10 2(3539) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [36]; uri=[sip:1002@172.16.4.113:5460] 2(3539) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (36)["1002"<sip:1002@172.16.4.113:5460> ], to tag (0)[] 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [From] type 4 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Call-ID] type 6 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [CSeq] type 5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <1> <INVITE> 2(3539) DEBUG: <core> [core/receive.c:397]: receive_msg(): --- received sip message - request - call-id: [NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.] - cseq: [1 INVITE] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:263]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:474]: receive_msg(): preparing to run routing scripts... 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=596 a=26 n=xlog 2(3539) INFO: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <script>: 172.16.80.3:8798|172.16.4.113:5460|udp|INVITE 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=605 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=707 a=67 n=set_rpl_no_connect 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=710 a=55 n=force_rport 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Allow] type 21 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Type] type 11 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [User-Agent] type 28 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=25 n=mf_process_maxfwd_header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=749 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=26 n=sanity_check 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:254]: check_ruri_sip_version(): check_ruri_sip_version entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:278]: check_ruri_sip_version(): check_ruri_sip_version passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:286]: check_ruri_scheme(): check_ruri_scheme entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:305]: check_ruri_scheme(): check_ruri_scheme passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:327]: check_required_headers(): check_required_headers entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Length] type 12 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=417 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:350]: check_required_headers(): check_required_headers passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:358]: check_via1_header(): check via1 header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:519]: check_cseq_method(): check_cseq_method entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:553]: check_cseq_method(): check_cseq_method passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:563]: check_cseq_value(): check_cseq_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:591]: check_cseq_value(): check_cseq_value passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:601]: check_cl(): check_cl entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:626]: check_cl(): check_cl passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:643]: check_expires_value(): check_expires_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:679]: check_expires_value(): no expires header found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:776]: check_parse_uris(): check_parse_uris entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:780]: check_parse_uris(): parsing ruri 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:793]: check_parse_uris(): looking up From header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=122cd223 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=29 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:808]: check_parse_uris(): looking up To header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:858]: check_parse_uris(): check_parse_uris passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity_mod.c:252]: w_sanity_check(): sanity checks result: 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=608 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=950 a=25 n=nat_uac_test 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=624 a=24 n=t_precheck_trans 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=24 n=t_check_trans 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1578]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=0/0 T start=0xffffffffffffffff 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:793]: t_lookup_request(): start searching: hash=30439, isACK=0 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:512]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-d87543-4f7e02083f709d16-1--d87543-] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:993]: t_lookup_request(): no transaction found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1650]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=1/3539 T end=(nil) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=757 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=24 n=has_totag 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siputils [checks.c:122]: has_totag(): no totag 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=637 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:742]: grep_sock_info(): checking if host==us: 12==12 && [172.16.4.113] == [172.16.4.113] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:745]: grep_sock_info(): checking if port 5460 (advertise 0) matches port 5460 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/forward.c:446]: check_self(): host (0:172.16.4.113:5460) == me 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=641 a=25 n=remove_hf 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=642 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=644 a=24 n=record_route 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| rr [record.c:490]: record_route(): inserted record route (r2: 1 - plen: 0) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=645 a=24 n=dlg_manage 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:907]: internal_get_dlg(): no dialog callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:975]: dlg_search(): dialog with callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' not found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:478]: build_new_dlg(): new dialog on hash 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:275]: populate_leg_info(): leg(0) route_set [], contact [sip:1003@172.16.80.3:8798], cseq [1] and bind_addr [udp:172.16.4.113:5460] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1040]: link_dlg(): linking dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1049]: link_dlg(): ref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:698]: get_dlg_timeout(): using default timeout 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_cb.c:227]: run_create_callbacks(): dialog=0x7ff07ff56f10 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2128]: trace_dialog(): Spiraled dialog! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2150]: trace_dialog(): trace_info xavp not registered! Probably incoming E2E CANCEL! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_profile.c:541]: set_current_dialog(): setting current dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:780]: dlg_lookup_mode(): ref dlg 0x7ff07ff56f10 with 1 -> 2 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:784]: dlg_lookup_mode(): dialog id=1302 found on entry 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:1927]: dlg_manage(): dialog created before transaction 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1088]: dlg_unref_helper(): unref op on 0x7ff07ff56f10 with 1 from dlg_hash.c:1106 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1092]: dlg_unref_helper(): unref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=658 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=648 a=25 n=sip_trace_mode 2(3539) BUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1917]: trace_add_info_xavp(): URI should be in raw format here 2(3539) ERROR: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1028]: sip_trace_helper(): failed to serialize siptrace info! Won't trace dialog! 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=649 a=24 n=sip_trace 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:618]: sip_trace_insert_db(): storing info - no user 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [db_query.c:72]: db_do_submit_query(): submitted query: insert into ###### here is my kamailio.cfg: ``` loadmodule "siptrace.so" modparam("siptrace", "db_url", DBURL) modparam("siptrace", "traced_user_avp", "$avp(user)") modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_init_mode", 0) ... route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE|REFER")) { record_route(); dlg_manage(); } if (is_method("INVITE")) { sip_trace_mode("d"); sip_trace(); } ```

1 0

New direction for Kamailio under Russian military administration
by Alex Balashov 01 Apr '25

01 Apr '25

For immediate release: BERLIN, Germany (1 April 2025)--The newly appointed executive and political head of the Russian Military Administration of Kamailio (R-MAK), General Alexander Balashov, has issued a proclamation: diversity, equity and inclusion (DEI) initiatives in the Kamailio will be fiscally de-emphasised, 'woke' modules will be removed in future releases, and realist relations with other open-source projects and commercial stakeholders will be sought, based henceforth on the 'pragmatics' of relative strength and strategic advantage, calculated from the extrapolated monetary value of Github commits. To note, the Kamailio project came into the remit of Balashov and R-MAK following the dissolution of the post-war transatlantic alliance system and the capitulation of NATO in the first quarter of 2025. These events were followed by direct negotiations between US Vice President J.D. Vance and the Government of the Russian Federation on the future course of Kamailio and SIP real-time communications, in which it was quickly concluded by both parties that Kamailio fell into the Russian sphere of influence. In an interview with Balashov, our bright and patriotic staff here at 'Krasnaya Zvezda' pressed him to further articulate and clarify the 'new thinking', as the new R-MAK initiatives have been informally dubbed around the offices of Kamailio. What follows is a selection of his remarks. Our first question to Balashov was on the tip of many journalists' tongues: what are the most woke modules in Kamailio? 'How should I know? They are everywhere, lots of people sayink it', Balashov answered, gesturing airily at the ceiling. 'Our specialists lookink on case-by-the-case basis. But sometimes is obvious, for example the JavaScript modules, like app_jsdt. This is clearly to subsidise a certain kind of morally deficient person.' What kind of person? we inquired, to be met with a characteristic frosty reply: 'You know the kind.' Our next question concerned some confusion about where, exactly, DEI initiatives are found in Kamailio today: 'From what I know this? Like swamp, this source code. How to say it, "drainink?" Yes, yes, I want to do that with swamp. Zero-based budget approach. Do you know it?' Asked to clarify, Balashov added: 'It's new idea from good friend Elon and the very efficient Dozh. Is good. We remove all module, then we look: what is broken? For example from technical viewpoint or political? What is broken? Maybe nothing.' One could be forgiven for wondering what 'broken' means in this context. We asked Balashov: does it mean CI tests no longer passing? 'No, no, no, automated tests are vegan soy-boy agenda. If you automatically test, when will you ever write correct code? I will not, I know automatic test will catch. Lazy approach. This idea, "test test test", for small minds. Do you know history of CI/CD? Propaganda is that Americans came up with it, but did not. Is invented by people from countries of later-times accession to EU, they are be-ne-fi-ci-aries of Bruxelle redistributionink policy, social cohesions grants and regional economic development equalisation initiatives, like something from socialist bloc countries or maybe Mezzogiorno, without otherwise much work prospects, until suddenly: unemployed guy with idea! "I am now Directeur of Le Cloud DevOps!" What is DevOps? It is from nothing, but suddenly hearing this in cultured places, theatres, palaces, galleries. Where it comes from? Why nobody asks? This is the old political correctness, and now we must release this suffocation with fresh and original thinking.' When our team asked for a concrete example of R-MAK's zero-based module trimming process, Balashov did not hesitate to focus on a well-known preoccupation: 'The most obvious example of very much not-needed module is TM. I Snapchat good friend Elon and I say him, "is it needed?" He says "no". But maybe I don't trust, GRU say he is always with marijuana, likewise ketamine. I make FaceTime with Milei: "¿Vos querés TM?" He says, "¡Que se vaya a la mierda y también los izquierdistas!" I phone Donald, "what do you think about this TM?" He says, "I signed a tremendous executive order to ban it this morning". I bother Orban in the middle of the night: "I am awake, asking myself, asking my wife: who needs TM?", and he answers: "no man who is civilisationally compatible with European values". Now I go to public sector union subreddits and askink same, and there is much noise and raging and I lose the karma, downvote to negative 26. I WhatsApp the leftists and they squeal. I Microsoft Teams to Bill Clinton and he says "TM is a key component of the international Kamailio order, used in 95% of configurations worldwide". Great! The answer is more clear than Lake Baikal: TM, goodbye, and I never knew you!' What else is marked for deletion?, wondered a contributing staff writer. On this point, Balashov was coy, declining to reveal the full working draft of slated cuts. However, he was not wholly unwilling to preview the direction of travel for the fate of Kamailio's 250+ modules. 'The STIR-SHAKING stuff of course gone. Now you can saying again "master-slave replication", as nature wills, without guilt, for which to be forced to this fake apologetics, "primary-secondary replication". Cannot anymore "blacklist"? What this emotionally constipated style? And likewise freedom means free to make telemarket without performative rituals of atonement for the sins.' Balashov went on to cite President Donald Trump, who had remarked: 'Robocall mitigations are money grab by failing FCC and their Trump-hating Democrat croneys. People are saying they are issuing eighth report and order, they are believing the fake liberal news. It's going to stop, and it's going to stop right now.' Balashov also intimated that he did not hold dearly in his heart the 'carrierroute' module, which he linked, in the memorable words of Fox News' Laura Ingraham, to 'the chattering vaccinated classes': 'What gigahertz your immunology system vibrates at? Mine for example clean, not 5G.' Next, we posed a question from a reader: are these changes to Kamailio simply drafting in the slipstream of global realignment, anti-free trade momentum, backlash against progressive cultural totems, as well as, in the United States specifically, the inward turn, the withdrawal from internationalism, and the return to 19th century great power realism in international relations, under the new administration of Donald Trump? 'Da, sure, of course gettink along with fraternal peoples very important, but also some important difference from Anglo-Americans. In R-MAK we are constructing "reaction with European characteristics" and the goals are too broader, coalitions bigger.' For help in understanding where R-MAK's reimagined Kamailio stakes its claim in the shifting international order and in the contested claims of popular mandates and political legitimacy, we consulted the version control history. Our GitHub research broadly supports Balashov's taxonomy of the exceptional ways in which the new thinking in Kamailio caters to a larger variety of constituencies, beyond those of its more monolithic relative, MAGA, across the Atlantic. In addition to patches from a predictable crowd of well-known Eurosceptics and critics of the post-Cold War Western security architecture, the R-MAK branch of Kamailio has many commits from supporters of renewed and muscular state-guided moral interventionism. In particular, large diffs, likely bundles of commits squashed interactive rebasing, appear to come from Catholic corporatists of southern Europe. Static code analysis also revealed a distinctive trail of gremialist design patterns and algorithms in the coding style of Jaime Guzmán. While it can be arduous to interpret this braiding of intellectual influences into bottom-line policymaking, we asked Balashov if this was the broader coalition, or the ideological imprimatur of 'reaction with European characteristics', to which he alluded. 'Sure, okay, because leadink open-source project is for what, if user is the amoral agent, captaining only the flatulent steam-ship of his hedonism? Time has ended to be saying, "do whatever you want as long as GPL-compliant", "you are free to fork if you wish", "submit the PR of your dreams". Look at yourself! This is nihilism. It is like, as Americans say, "self-licking ice cream cone", da? If you look into repository clone long enough, it in turn look back into you, and what it sees? Kamailio is not enough just for clone; it must make you better man!' Added Balashov, emphatically: 'If open-source project regime is to matter, it must be PEDAGOGICAL!' Turning to questions of relations with neighbours, Balashov rather foreseeably merged into the flow of renovated international relations realism and the spirit of great power competition once again jostling the world. We asked Balashov if the new thinking in Kamailio implies an abandonment of prior global hegemonic claims vis-a-vis OpenSIPS: 'Who is abandonink? But we must live in peace. We have no quarrels with OpenSIPS if they want Bucharest or Amsterdam. For them they are havink their interests, and we are havink our too.' Notably, and somewhat surprisingly, however, Balashov added: 'But we are going to get Yate. It is historically correct. I take away no options from the table.' Lastly, we asked Balashov to touch on the delicate subject of IMS and 6G enthusiasts increasingly migrating into the ecology of Kamailio, and whether this has a place in the current of new thinking under R-MAK. 'I not know much about them. Many people sayink they are eating dogs, eating cats, right from the street in Berlin. What to say about such people?' -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

1 0

DMQ read message too large
by Calvin E. 31 Mar '25

31 Mar '25

We are seeing errors like this when synchronizing htables over DMQ: ERROR: <core> [core/udp_server.c:677]: udp_rcv_loop(): read message too large: 60793 We have no issues with other UDP fragments caused by STIR/SHAKEN headers. Our socket buffers are sufficiently large (SO_RCVBUF is initially 26214400). Does DMQ have a receive message size limit less than what it can send? Is DMQ intended for htables under a certain total size? We tried to configure DMQ to use a TCP listener with ;transport=tcp on the notification and server address, but the DMQ traffic was still sent as UDP. The example in the documentation shows TLS, but we haven't tried that. -Calvin E.

2 3

Intermediate CDRs
by Sergio Charrua 31 Mar '25

31 Mar '25

Hi all! I have been googling, and reading documentation, but I could not find any solution. How can I implement intermediate CDRs with Kamailio ACC module (or any other module) ? For example, on long duration calls, I 'm required to save call status on a CDR, resulting in intermediate CDR lines for the call (which will result in multiple CDR lines per long duration calls). Any clue on how to implement this? Did anyone achieved that with Kamailio ACC module? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

4 3

Multiple code modules
by David Cunningham 28 Mar '25

28 Mar '25

Hello, We have a requirement to load two code modules for use by kamailio.cfg, the reason being that we can't (won't, for business reasons) modify the first module and so need to add a second for our own code. Ideally we would load two Perl modules instead of the single module that's currently loaded like this: modparam( "app_perl", "filename", "/path/to/our/custom/Kamailio.pm" ) But I'm not sure how to load two modules like this. Otherwise, does anyone know if it's safe to load both a Perl module and a Python module? Then we could at least implement both required parts, one in Perl and one in Python. Thanks in advance for any help. -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

1 0

[ratelimit module] doubts about behavior
by juliofabian6385＠hotmail.es 26 Mar '25

26 Mar '25

I am reading https://kamailio.org/docs/modules/devel/modules/ratelimit.html and I want Kamailio, before an avalanche of calls (INVITE), to start discarding calls that exceed a threshold in 1 second, for example. So in summary I have prepared the module as follows: loadmodule "ratelimit.so" modparam("ratelimit", "timer_interval",1) modparam("ratelimit", "pipe", "1:TAILDROP:10") request_route { . . if (is_method("INVITE")) { if (!rl_check_pipe("1")) { sl_send_reply("503","Limiting"); exit; } } . . } As I understand from the documentation, this gives me a counter (one per INVITE) equal to 10, which resets after 1 second. In other words, if I receive 30 INVITES in 1 second, it will discard 20. From here, I have two questions between what I understand and what I see in the logs. FIRST QUESTION: I've made several SIPP calls in one second. I've run several tests, and the first reset of the counter always happens approximately timer_interval/2. From then on, the counter resets exactly every timer_interval. Am I doing something wrong? ########## RUNNING LOGS ########## 2025-03-26T18:59:20.509696381Z 0(1) DEBUG: <core> [core/cfg.y:2165]: yyparse(): loading module ratelimit.so 2025-03-26T18:59:20.509698675Z 0(1) DEBUG: <core> [core/sr_module.c:533]: ksr_locate_module(): found module to load </usr/lib/kamailio/modules/ratelimit.so> 2025-03-26T18:59:20.509702249Z 0(1) DEBUG: <core> [core/sr_module.c:587]: ksr_load_module(): trying to load </usr/lib/kamailio/modules/ratelimit.so> 2025-03-26T18:59:20.509704682Z 0(1) DEBUG: <core> [core/kemi.c:3463]: sr_kemi_modules_add(): adding module: ratelimit 2025-03-26T18:59:20.509707031Z 0(1) DEBUG: <core> [core/cfg.lex:2095]: pp_define(): defining id: MOD_ratelimit 2025-03-26T18:59:20.509815384Z 0(1) DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'ratelimit' matches module 'ratelimit' 2025-03-26T18:59:20.509817770Z 0(1) DEBUG: <core> [core/sr_module.c:850]: find_param_export(): found <timer_interval> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509820319Z 0(1) DEBUG: <core> [core/modparam.c:135]: set_mod_param_regex(): found <timer_interval> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509822755Z 0(1) DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'ratelimit' matches module 'ratelimit' 2025-03-26T18:59:20.509825068Z 0(1) DEBUG: <core> [core/sr_module.c:850]: find_param_export(): found <pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509827468Z 0(1) DEBUG: <core> [core/modparam.c:135]: set_mod_param_regex(): found <pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509829943Z 0(1) DEBUG: ratelimit [ratelimit.c:925]: parse_pipe_params(): pipe: [1|TAILDROP|10] 2025-03-26T18:59:20.510800378Z 0(1) DEBUG: <core> [core/sr_module.c:758]: find_mod_export_record(): found export of <rl_check_pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.519776933Z 0(1) DEBUG: <core> [core/sr_module.c:1031]: init_mod(): ratelimit ########## LOGS WHEN APPLY RATELIMIT ########## 2025-03-26T19:01:02.095676663Z 1(7) DEBUG: {1 1 INVITE 1-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.095679040Z 1(7) DEBUG: {1 1 INVITE 1-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=1 load=0.0 network_load=0 => ACCEPT . . 2025-03-26T19:01:02.272879226Z 2(8) DEBUG: {1 1 INVITE 10-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.272881671Z 2(8) DEBUG: {1 1 INVITE 10-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=10 load=0.0 network_load=0 => ACCEPT 2025-03-26T19:01:02.292599816Z 2(8) DEBUG: {1 1 INVITE 11-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.292602425Z 2(8) DEBUG: {1 1 INVITE 11-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=11 load=0.0 network_load=0 => DROP . . 2025-03-26T19:01:02.492680874Z 1(7) DEBUG: {1 1 INVITE 21-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.492694107Z 1(7) DEBUG: {1 1 INVITE 21-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=21 load=0.0 network_load=0 => DROP 2025-03-26T19:01:02.513079779Z 2(8) DEBUG: {1 1 INVITE 22-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.513088852Z 2(8) DEBUG: {1 1 INVITE 22-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=22 load=0.0 network_load=0 => DROP 2025-03-26T19:01:02.532804253Z 1(7) DEBUG: {1 1 INVITE 23-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.532808087Z 1(7) DEBUG: {1 1 INVITE 23-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=2 counter=1 load=0.1 network_load=0 => ACCEPT When the countdown restarts, it's "19:01:02.53" hours, and when it started, it was "19:01:02.09" hours. It doesn't reach the second. The drop system works well, but if my limit was 25 calls, I would have accepted the 22 I counted in the first second, plus the other 25 from the second number 2. Second question: There's a warning about a performance penalty in Kamailio when timer_interval is too small, so I've decided to set it to 2 just for practical purposes. So what should happen is that the counter would accept up to 10 calls in 2 seconds. But in the logs, what I see is the opposite: it accepts 20 calls in 2 seconds. Maybe it's supposed to work that way, and I'm misunderstanding the documentation? As optional information: Kamailio is running on a Google virtual machine, 12MB of RAM, 3 processors, 2 of which are dedicated. I'm using SIPP for load testing, and different call rates have been validated before testing the module. Sorry if my first post in this community was too long or is there more information missing :) . Thanks in advance

1 0

kamailio call redirect
by fabienbrou＠alcall.net 26 Mar '25

26 Mar '25

Hello everyone. I'm trying to redirect a call directly through kamailio by modifying the $ru variable. Just wondering if this is the right method or if there is a better way to do it. thanks

4 13

is possible empty actions?
by Sergey Safarov 26 Mar '25

26 Mar '25

I want to use contributions like route[PROXY_MEDIA] { if (is_method("BYE|CANCEL")) { # passing message for RTPengine processing } else if (!sdp_content()) { return; } # more instructions here ... rtpengine_manage(); } Now Kamailio cannot start because first if block has empty actions. How does nothing in the actions? I want to avoid not needed log messages and do not use constructions like if (!sdp_content() and ! is_method("BYE|CANCEL")) { return; }

3 2

Seeking advices on redesigning our VoIP system for scalability and manageability
by Francesco 26 Mar '25

26 Mar '25

Dear all, I hope this email finds you well. I am reaching out to gather insights and suggestions regarding a potential redesign of our VoIP system to improve scalability, ease of management, and upgradeability. *Current Setup:* - Our system is *not multi-tenant* and is based on *Kamailio and FreeSWITCH* in a distributed architecture (as example of distributed architecture, see: https://ufdcimages.uflib.ufl.edu/UF/E0/04/92/89/00001/THOMPSON_C.pdf). - Everything runs inside *LXC containers* across multiple nodes. - One of the challenges we face is *OS upgrades*, which are cumbersome and require significant manual intervention. - At the moment the code for voip is done with ansible Given these challenges, I am considering whether a *microservices-based architecture* could be a viable option. However, I have some concerns regarding: - *SIP and RTP handling with NATed containers* (e.g., Kubernetes, Docker Swarm) and potential issues with media traversal. - *Performance impact* when shifting real-time traffic handling to containerized environments. - *Upgrade and deployment strategies*—how to achieve smoother, rolling upgrades without service interruptions. - *Alternative approaches* that might be more effective, such as a hybrid model combining LXC with containerized microservices for specific functions. If anyone has experience transitioning a VoIP system to microservices or has insights on best practices for *scalable, maintainable VoIP architectures*, I would greatly appreciate your thoughts. What worked for you? What pitfalls should we be aware of?Do you have any documentation that I can check? Looking forward to learning from your experiences. Thank you. .: Francesco Colista .: Francesco Colista

3 2

TOPOS Issue with Response Handling on two different Interfaces
by Vinayak Makwana 25 Mar '25

25 Mar '25

Hello all, We are facing an issue while configuring TOPOS in Kamailio P-CSCF (running under Docker). Our objective is to strip Via, Record-Route, and Route headers for both INVITE and 180 Ringing responses. However, we observe unexpected behavior when handling the 180 Ringing/200 OK responses. Call Flow & Issue Description: Note: Public IP and Private IP mapping using the below configuration. listen=udp:Local_IP:5060 name "internal" listen=udp:Local_IP:6070 advertise Public_IP:6070 name "external" Call Flow (INVITE): A-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) --> Kamailio P-CSCF (Private IP) --> Kamailio P-CSCF (Public IP) --> B-Party For an incoming *INVITE* (A-Party → B-Party), TOPOS successfully strips the headers when the message flows through the P-CSCF, ensuring proper privacy of routing information. *Issue* : When B-Party sends a 180 Ringing, we observe that Kamailio P-CSCF (Private IP) adds a Record-Route header before forwarding the message to A-Party. Call Flow (180 Ringing): B-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) We need to ensure that the Record-Route and Via headers are stripped properly in both directions. Please guide us how to achieve and what we are doing wrong. TOPOS module is configured as follows: modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379") modparam("topos_redis", "serverid", "srv1") modparam("topos", "storage", "redis") modparam("topos", "contact_mode", 1) modparam("topos", "rr_update", 1) RR module is configured as follows: modparam("rr", "enable_full_lr", 1) modparam("rr", "append_fromtag", 1) configured the below event_route: event_route[topos:msg-outgoing] { xlog("L_INFO","[topos:msg-outgoing]"); if(is_request() and $sndto(ip)=="SCSCF_PRIVATE_IP") { xlog("L_INFO","[topos:msg-outgoing] TOPOS \n"); drop; } } Thanks, Vinayak Makwana -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

1 1

Running Kamailio in kubernetes
by sagar agarwal 25 Mar '25

25 Mar '25

Hi team, I am looking for some guidance to run Kamailio as part of our Kubernetes cluster. I don't see any official or well maintained helm chart out there to install Kamailio on K8s. If there is a recommendation from your side on a helm chart please let me know. Also would be interesting to know if you foresee any issues with running Kamailio on k8s or do you feel its better to stick with ec2 based installations. Regards Sagar Agarwal

4 3

Problem with ipsec setting of Via for outgoing message
by Minello, Loredana 24 Mar '25

24 Mar '25

Hello, I'm using Kamailio ver. 5.8.4. I configured the ims_ipsec_pcscf with modparam("ims_ipsec_pcscf", "ipsec_max_connections", 1) and call ipsec_forward with flag = IPSEC_FORWARD_FLAGS where : # - IPSEC_SEND_FORCE_SOCKET 1 # - IPSEC_FORWARD_USEVIA 256 #!define IPSEC_FORWARD_FLAGS 257 For the UE REGISTRATION I have the following flow UE PCSCF_GM_IMS REGISTER (32133) ------------------> (5060) 100 Trying (32133) <------------------ (5060) 401 Unauthorized (32133) <------------------ (5060) REGISTER (TCP) (PORT_UC) ------------------> (PORT_PS) 100 Trying (TCP) (PORT_UC) <------------------ (PORT_PS) 200 OK (TCP) (PORT_UC) <------------------ (PORT_PS) ------------------------------------------------------------------ SUBSCRIBE (UDP) (PORT_UC) ------------------> (PORT_PS) 200 Subscription (UDP) (PORT_US) <------------------ (PORT_PC) NOTIFY (UDP) (PORT_US) <------------------ (PORT_PC) 200 OK (UDP) (PORT_UC) ------------------> (PORT_PC) NOTIFY (UDP) (PORT_US) <------------------ (PORT_PC) 200 OK (UDP) (PORT_UC) ------------------> (PORT_PC) NOTIFY (UDP) (PORT_US) <------------------ (PORT_PC) 200 OK (UDP) (PORT_UC) ------------------> (PORT_PC) The SUBSCRIBE behavior is correct : PCSCF receives message on PORT_PS and sends on PORT_PC The NOTIFY behavior is wrong: PCSCF send from PORT_PC (correct), but UE respond towards PORT_PC, defined in the Via of the NOTIFY. I know I can use the set_advertised_port() function, and in this case can work, but the function is taking a constant as a parameter, not a variable. This is causing a problem when ipsec_max_connections > 1. In that case it won't be easy to pass the correct port. I was wondering if the ipsec module should properly set the VIA port to the correct PORT_PS, rather than leaving the setting of the correct port by the kamailio.cfg. Do you have any hints on that? Thanks

1 0

Re: send_fd(): sendmsg failed sending 55 on 52: Too many references: cannot splice (109)
by Mathias Schneuwly 24 Mar '25

24 Mar '25

Thank you, I've already changed the value, but that didn't solve my issue with the blocking Kamailio. I did some tests with an older Yocto image which contains Kamailio 5.5.4 and OpenSSL 1.1.1w. With this combination I was not able to reproduce the deadlock. Am Fr., 21. März 2025 um 16:49 Uhr schrieb Harald Kapper <hk(a)kapper.net>: > Hi > > fyi – in case you need this: > > systemctl edit kamailio.service > > > > add: > > ### Editing /etc/systemd/system/kamailio.service.d/override.conf > > ### Anything between here and the comment below will become the contents > of the drop-in file > > > > [Service] > > LimitNOFILE=40960 > > > > ### Edits below this comment will be discarded > > > > (or whatever number you’d like) > > saving saves the override for systemd into (like) > /etc/systemd/system/kamailio.service.d/override.conf > > > > Afterwards you have to restart the service (systemctl restart > kamailio.service) > > > > And you should be fine. > > > > Regards, hk > > > > *Von:* Henning Westerholt via sr-users <sr-users(a)lists.kamailio.org> > *Gesendet:* Donnerstag, 20. März 2025 14:25 > *An:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > *Cc:* Mathias Schneuwly <mathias(a)schneuwlys.ch>; Henning Westerholt < > hw(a)gilawa.com> > *Betreff:* [SR-Users] Re: send_fd(): sendmsg failed sending 55 on 52: Too > many references: cannot splice (109) > > > > Hello Mathias, > > > > yes, you can set the open files e.g. in the systemd unit file for Kamailio. > > > > Cheers, > > > > Henning > > > > *From:* Mathias Schneuwly via sr-users <sr-users(a)lists.kamailio.org> > *Sent:* Donnerstag, 20. März 2025 13:43 > *To:* sr-users(a)lists.kamailio.org > *Cc:* Mathias Schneuwly <mathias(a)schneuwlys.ch> > *Subject:* [SR-Users] Re: send_fd(): sendmsg failed sending 55 on 52: Too > many references: cannot splice (109) > > > > > I'll also give a try with 6.0.1 later. > > Meanwhile, I've tested 5.8.6 and 6.0.1 and both show the same issue. > > > > Am Do., 20. März 2025 um 10:21 Uhr schrieb Mathias Schneuwly < > mathias(a)schneuwlys.ch>: > > Hi Henning > > > > > Maybe also check the actual limits by “cat /proc/$kamailio-pid/limits” > Not 100% if its related, but if you are looking to scale this would be for > sure required. > > The limit was > > Max open files 1024 524288 files > > and I changed it now to > > Max open files 65536 65536 files > > > > Are there some recommendations for the limit? Would it make sense to > change that in the provided systemd file if you say that 1024 is not that > much? > > > > But anyway, it fails with 1024 and with 65536. > > > > I've also updated to 5.8.5 and it shows the same issue. I'll also give a > try with 6.0.1 later. > > > > > About the tls_thread_mode – you should use mode 2 if you are running > with openssl 3.x, otherwise you probably will observe random crashes. > > We are running OpenSSL 3.2.3 and tls_thread_mode is set to 2. But it still > blocks. > > > > Best regards > > Mathias > > > > Am Do., 20. März 2025 um 08:42 Uhr schrieb Henning Westerholt < > hw(a)gilawa.com>: > > Hello Mathias, > > > > 1024 open files are not that much, you should increase it for the kamailio > user. Maybe also check the actual limits by “cat > /proc/$kamailio-pid/limits” > > Not 100% if its related, but if you are looking to scale this would be for > sure required. > > > > About the tls_thread_mode – you should use mode 2 if you are running with > openssl 3.x, otherwise you probably will observe random crashes. > > > > If you are seeing the mentioned problem with 15 phones, this is clearly a > problem and should be further investigated. > > > > Cheers, > > > > Henning > > > > > > *From:* Mathias Schneuwly via sr-users <sr-users(a)lists.kamailio.org> > *Sent:* Donnerstag, 20. März 2025 08:07 > *To:* sr-users(a)lists.kamailio.org > *Cc:* Mathias Schneuwly <mathias(a)schneuwlys.ch> > *Subject:* [SR-Users] Re: send_fd(): sendmsg failed sending 55 on 52: Too > many references: cannot splice (109) > > > > Hi > > > > Thanks for the reply. We are using the following limits and I guess they > are the default values > > real-time non-blocking time (microseconds, -R) unlimited > core file size (blocks, -c) unlimited > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 15666 > max locked memory (kbytes, -l) 8192 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 15666 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > > > But to me, it looks more like a deadlock somewhere around SSL_accept. > According to the stack trace generated with "kamctl trap", all 8 TCP > receiver processes are waiting in "#1 0x00007fa14ca04830 in > pthread_rwlock_wrlock () from /usr/lib/libc.so.6". I guess the message "Too > many references: cannot splice (109)" is just the consequence as the main > process is no longer able to dispatch jobs to the child workers. > > > > Meanwhile, I'm able to reproduce the issue. It requires a bit of brute > force, but it deadlocks reliably after a few seconds. > > > > I'm flooding Kamailio with register messages using sipexer. I'm running > the following command 3 times in parallel and always after a few seconds, > Kamailio is completely blocked. > > watch -n 0.1 "./sipexer -register -vl 3 -co -com -ex 3600 -fu "2" -au "2" > -ap "test" -tk <path to key>.key -tc <path to cert>.cer -ti -sd -ru > sip:<domain> -cu sip:2@<domain> tls:<fqdn>:5061;sleep 0.1;./sipexer > -register -vl 3 -co -com -ex 0 -fu "2" -au "2" -ap "test" -tk <path to > key>.key -tc <path to cert>.cer -ti -sd -ru sip:<domain> -cu sip:2@<domain> > tls:<fqdn>:5061" > > > > I played a bit with the parameters "modparam("tls", "init_mode", 1)" and > "tls_threads_mode = 2", but it didn't seem to change anything. > > > > Please have in mind that we usually do not stress Kamailio that much. We > have seen the issue a couple of times with around 5 to 15 SIP phones > registered. But in this usual setup, the problem does not occur reliably. > > > > Best regards > > Mathias > > > > Am Di., 18. März 2025 um 21:53 Uhr schrieb Henning Westerholt < > hw(a)gilawa.com>: > > Hello, > > > > check the ulimit settings for the kamailio user and general resource usage > on that system. In development branch there is also a feature present to > print the actual ulimits on startup. > > > > Cheers, > > > > Henning > > > > *From:* Mathias Schneuwly via sr-users <sr-users(a)lists.kamailio.org> > *Sent:* Montag, 17. März 2025 13:41 > *To:* sr-users(a)lists.kamailio.org > *Cc:* Mathias Schneuwly <mathias(a)schneuwlys.ch> > *Subject:* [SR-Users] send_fd(): sendmsg failed sending 55 on 52: Too > many references: cannot splice (109) > > > > Hi > > > > We are using kamailio 5.8.4. > > > > Recently, we noticed, that after a few days, we see the following messages > from Kamailio `2025 Mar 17 10:22:11 ttel CRITICAL: <core> > [core/pass_fd.c:193]: send_fd(): sendmsg failed sending 55 on 52: Too many > references: cannot splice (109)`. > > > > When this happens, devices are no longer able to register. At the moment > we have no idea what might be wrong. > > > > Unfortunately, the internet does not reveal much information regarding > this issue. In one issue related to Kamailio ( > https://lists.kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio…), > I found the command `kamctl trap` and when I execute that, I see one issue, > which might be related, but I'm just guessing... > > > > ``` > > ---start 1782236 ----------------------------------------------------- > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/usr/lib/libthread_db.so.1". > 0x00007fa14c9fb1c6 in ?? () from /usr/lib/libc.so.6 > $1 = 26 > $2 = {pid = 1782236, unix_sock = 36, idx = 0, status = 1, rank = 17, desc > = "tcp receiver (generic) child=0", '\000' <repeats 97 times>} > #0 0x00007fa14c9fb1c6 in ?? () from /usr/lib/libc.so.6 > No symbol table info available. > #1 0x00007fa14ca04830 in pthread_rwlock_wrlock () from /usr/lib/libc.so.6 > No symbol table info available. > #2 0x00007fa14ac20b49 in CRYPTO_THREAD_write_lock () from > /usr/lib/libcrypto.so.3 > No symbol table info available. > #3 0x00007fa14adbd5da in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #4 0x00007fa14adbd9ca in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #5 0x00007fa14adbc907 in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #6 0x00007fa14adbd26c in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #7 0x00007fa14adbd68e in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #8 0x00007fa14abe75c6 in ?? () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #9 0x00007fa14abe840b in EVP_RAND_generate () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #10 0x00007fa14acf9282 in RAND_bytes_ex () from /usr/lib/libcrypto.so.3 > No symbol table info available. > #11 0x00007fa14b06cce8 in ?? () from /usr/lib/libssl.so.3 > No symbol table info available. > #12 0x00007fa14b05bdf7 in ?? () from /usr/lib/libssl.so.3 > No symbol table info available. > #13 0x00007fa14b0ef036 in tls_accept (c=c@entry=0x7fa1475c0dc0, > error=error@entry=0x7ffebd9443b8) at tls_server.c:457 > ret = <optimized out> > ssl = warning: could not convert 'ssl_st' from the host encoding > (ANSI_X3.4-1968) to UTF-32. > This normally should not happen, please file a bug report. > 0x7fa147668bd0 > cert = <optimized out> > tls_c = 0x7fa14768f490 > tls_log = <optimized out> > __func__ = "tls_accept" > #14 0x00007fa14b0f7540 in tls_h_read_f (c=0x7fa1475c0dc0, > flags=0x7ffebd9647d0) at tls_server.c:1153 > r = 0x7fa1475c0ee8 > bytes_free = 16383 > bytes_read = <optimized out> > read_size = <optimized out> > ssl_error = 0 > ssl_read = 0 > ssl = 0x7fa147668bd0 > rd_buf = > "\026\003\003\004\016\v\000\004\n\000\004\a\000\004\0040\202\004\0000\202\002\350\240\003\002\001\002\002\002\026\0270\r\006\t*\206H\206\367\r\001\001\v\005\0000b1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003U\004\b\f\004Bern1\r0\v\006\003U\004\a\f\004Bern1\r0\v\006\003U\004\n\f\004RUAG1\0200\016\006\003U\004\v\f\aDefence1\0240\022\006\003U\004\003\f\versaimfs.ch0\036\027\r230302163519Z\027\r291230163519Z0`1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003"... > wr_buf = > "\026\003\003\000A\002\000\000=\003\003\371\204\326\361\262-9\300\344gV\2316\373\235D\314\225u8\v}\215\254DOWNGRD\001\000\3000\000\000\025\377\001\000\001\000\000\v\000\004\003\000\001\002\000#\000\000\000\027\000\000\026\003\003\a\267\v\000\a\263\000\a\260\000\004\0040\202\004\0000\202\002\350\240\003\002\001\002\002\002\r>0\r\006\t*\206H\206\367\r\001\001\v\005\0000b1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003U\004\b\f\004Bern1\r0\v\006\003U\004\a\f\004Bern1\r0\v\006\003U\004\n\f\004RUAG1\0200\016\006\003U\004\v\f\aDefence1\0240\022\006"... > rd = {buf = 0x7ffebd944480 "\026\003\003\004\016\v", pos = 1405, > used = 1405, size = 65536} > wr = {buf = 0x7ffebd954480 "\026\003\003", pos = 0, used = 0, size > = 65536} > tls_c = 0x7fa14768f490 > enc_rd_buf = <optimized out> > n = 0 > flush_flags = 0 > err_src = <optimized out> > ip_buf = '\000' <repeats 63 times> > x = <optimized out> > tls_dbg = <optimized out> > __func__ = "tls_h_read_f" > redo_read = <optimized out> > continue_ssl_read = <optimized out> > __llevel = <optimized out> > __kld = <optimized out> > __llevel = <optimized out> > __kld = <optimized out> > #15 0x000055d2519871b4 in tcp_read_headers (c=c@entry=0x7fa1475c0dc0, > read_flags=read_flags@entry=0x7ffebd9647d0) at core/tcp_read.c:445 > bytes = <optimized out> > remaining = <optimized out> > p = <optimized out> > r = 0x7fa1475c0ee8 > mc = <optimized out> > body_len = <optimized out> > tvnow = {tv_sec = 1742100857, tv_usec = 944923} > tvdiff = <optimized out> > mfline = <optimized out> > mtransid = <optimized out> > __func__ = "tcp_read_headers" > #16 0x000055d251989cef in tcp_read_req (con=0x7fa1475c0dc0, > bytes_read=bytes_read@entry=0x7ffebd9647c8, read_flags=read_flags@entry=0x7ffebd9647d0) > at core/tcp_read.c:1509 > bytes = <optimized out> > total_bytes = 0 > resp = 1 > size = <optimized out> > req = 0x7fa1475c0ee8 > dst = {send_sock = 0x55d251a91020, to = {s = {sa_family = 52024, > sa_data = "\257Q\322U\000\000\002\000\000\000\376\177\000"}, sin = > {sin_family = 52024, sin_port = 20911, sin_addr = {s_addr = 21970}, > sin_zero = "\002\000\000\000\376\177\000"}, sin6 = {sin6_family = 52024, > sin6_port = 20911, sin6_flowinfo = 21970, sin6_addr = {__in6_u = > {__u6_addr8 = > "\002\000\000\000\376\177\000\000\030\000\000\000\000\000\000", __u6_addr16 > = {2, 0, 32766, 0, 24, 0, 0, 0}, __u6_addr32 = {2, 32766, 24, 0}}}, > sin6_scope_id = 0}, sas = {ss_family = 52024, __ss_padding = > "\257Q\322U\000\000\002\000\000\000\376\177\000\000\030", '\000' <repeats > 23 times>, > "\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\262+\226Q\001 > \000\000\200,5L\241\177\000\000 \020\251Q\322U\000\000 > \020\251Q\322U\000\000\200\303\257Q\322U\000\00009SG\241\177\000\000\330G\226\275\376\177\000\000\b\000\000\000\000\000\000", > __ss_align = 20}}, id = 1, send_flags = {f = 1, blst_imask = 0}, proto = 14 > '\016', proto_pad0 = 0 '\000', proto_pad1 = 0} > c = <optimized out> > ret = <optimized out> > again = <optimized out> > __func__ = "tcp_read_req" > #17 0x000055d25198ebec in handle_io (fm=fm@entry=0x7fa14c352c80, > events=events@entry=1, idx=idx@entry=-1) at core/tcp_read.c:1906 > ret = 8 > n = 0 > read_flags = RD_CONN_SHORT_READ > con = 0x7fa1475c0dc0 > s = 14 > resp = <optimized out> > t = <optimized out> > ee = 0x0 > __func__ = "handle_io" > error = <optimized out> > #18 0x000055d25199469b in io_wait_loop_epoll (repeat=repeat@entry=0, t=2, > h=0x55d251c49d60 <io_w>) at core/io_wait.h:1075 > n = 1 > r = 0 > fm = 0x7fa14c352c80 > revents = 1 > __func__ = "io_wait_loop_epoll" > #19 0x000055d251994e87 in tcp_receive_loop (unix_sock=<optimized out>) at > core/tcp_read.c:2026 > __func__ = "tcp_receive_loop" > #20 0x000055d25197e72c in tcp_init_children (woneinit=woneinit@entry=0x7ffebd964d1c) > at core/tcp_main.c:5391 > r = <optimized out> > i = <optimized out> > reader_fd_1 = 39 > pid = <optimized out> > si_desc = "tcp receiver > (generic)\000\000`M\226\275\376\177\000\000\001\000\000\000\000\000\000\000\210\035\223Q\322U\000\000 > \020\251Q\322U\000\000\220\315\257Q\322U\000\000\220\242/L\241\177\000\000\025\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000%\020\251Q\322U\000\000HU\257Q\322U\000\000e\005\000\000\000\000\000\000 > \020\251Q\322U\000\000\3750\235Q\322U\000" > si = <optimized out> > __func__ = "tcp_init_children" > error = <optimized out> > #21 0x000055d2517c6c7e in main_loop () at main.c:1950 > i = <optimized out> > pid = <optimized out> > si = <optimized out> > si_desc = "udp receiver child=7 sock=10.0.90.1:5060\000\000\000\000\322U\000\000?\342\017K\241\177\000\000\022\000\000\000\377\377\377\377\200\006\265L\241\177\000\000\253m\237L\241\177\000\000\361|\003\000\000\000\000\000\t\000\000\000\000\000\000\000Sat > Mar 15 05:25:32 2025\n\000\264L\241\177\000" > nrprocs = <optimized out> > woneinit = 1 > __func__ = "main_loop" > error = <optimized out> > #22 0x000055d2517bc151 in main (argc=<optimized out>, argv=<optimized > out>) at main.c:3256 > cfg_stream = <optimized out> > c = <optimized out> > r = <optimized out> > tmp = 0x7ffebd966e7f "" > tmp_len = 32673 > port = 5060 > proto = 0 > aproto = 0 > ahost = 0x0 > aport = 0 > options = 0x55d251aa74b8 > ":f:cm:M:dVIhEeb:B:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" > ret = -1 > seed = 3209119183 > rfd = <optimized out> > debug_save = <optimized out> > debug_flag = <optimized out> > dont_fork_cnt = 0 > n_lst = <optimized out> > p = <optimized out> > st = {st_dev = 24, st_ino = 46237, st_nlink = 2, st_mode = 16888, > st_uid = 899, st_gid = 899, __pad0 = 0, st_rdev = 0, st_size = 40, > st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1742012732, tv_nsec = > 217328715}, st_mtim = {tv_sec = 1742012732, tv_nsec = 217328715}, st_ctim = > {tv_sec = 1742012732, tv_nsec = 217328715}, __glibc_reserved = {0, 0, 0}} > l1 = <optimized out> > tbuf = '\000' <repeats 32 times>, > "\030\202\237\275\376\177\000\000@\002\000\000@\003\000\000\001", '\000' > <repeats 23 times>, "@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ > \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ > \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ > \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ > \003\000\000@\003\000\000@\003", '\000' <repeats 11 times>, "\001", > '\000' <repeats 118 times>... > option_index = 12 > long_options = {{name = 0x55d251a9230b "help", has_arg = 0, flag = > 0x0, val = 104}, {name = 0x55d251a937a4 "version", has_arg = 0, flag = 0x0, > val = 118}, {name = 0x55d251a9826a "alias", has_arg = 1, flag = 0x0, val = > 1024}, {name = 0x55d251a92310 "subst", has_arg = 1, flag = 0x0, val = > 1025}, {name = 0x55d251a92316 "substdef", has_arg = 1, flag = 0x0, val = > 1026}, {name = 0x55d251a9231f "substdefs", has_arg = 1, flag = 0x0, val = > 1027}, {name = 0x55d251a92329 "server-id", has_arg = 1, flag = 0x0, val = > 1028}, {name = 0x55d251a92333 "loadmodule", has_arg = 1, flag = 0x0, val = > 1029}, {name = 0x55d251a9233e "modparam", has_arg = 1, flag = 0x0, val = > 1030}, {name = 0x55d251a92347 "log-engine", has_arg = 1, flag = 0x0, val = > 1031}, {name = 0x55d251a938c1 "debug", has_arg = 1, flag = 0x0, val = > 1032}, {name = 0x55d251a92352 "cfg-print", has_arg = 0, flag = 0x0, val = > 1033}, {name = 0x55d251a9235c "atexit", has_arg = 1, flag = 0x0, val = > 1034}, {name = 0x55d251a92363 "all-errors", has_arg = 0, flag = 0x0, val = > 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} > __func__ = "main" > [Inferior 1 (process 1782236) detached] > ---end 1782236 ------------------------------------------------------- > > ``` > > > > Does anybody have an idea what this could be? I never saw that with > previous versions, and now we can see it on several instances, but we are > yet unable to reproduce. > > > > Not sure if this might be related, but we also see many messages like `Mar > 17 13:39:03 ttel /usr/sbin/kamailio[2882127]: CRITICAL: <core> > [core/tcp_main.c:5558]: tcp_timer_check_connections(): message processing > timeout on connection id: 402 (state: 0) - closing` > > > > Best regards > > Mathias > >

1 0

Dispatcher module resets URI parameters
by Marat Gareev 22 Mar '25

22 Mar '25

Hello, I encountered a problem that ds_select_domain function does not save URI parameters. I found workaround: if (!ds_select_domain( "1", 4, 3 )) { send_reply("502", "Bad Gateway"); exit; } if (!strempty($(ou{uri.params}))) { $ru = $ru+";"+$(ou{uri.params}); } But this can lead to duplicates if the URI in the dispatcher list contains the same parameter. Is there any other reliable way to keep original URI parameters while using the dispatcher? Thanks

2 1

send_fd(): sendmsg failed sending 55 on 52: Too many references: cannot splice (109)
by Mathias Schneuwly 20 Mar '25

20 Mar '25

Hi We are using kamailio 5.8.4. Recently, we noticed, that after a few days, we see the following messages from Kamailio `2025 Mar 17 10:22:11 ttel CRITICAL: <core> [core/pass_fd.c:193]: send_fd(): sendmsg failed sending 55 on 52: Too many references: cannot splice (109)`. When this happens, devices are no longer able to register. At the moment we have no idea what might be wrong. Unfortunately, the internet does not reveal much information regarding this issue. In one issue related to Kamailio ( https://lists.kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio…), I found the command `kamctl trap` and when I execute that, I see one issue, which might be related, but I'm just guessing... ``` ---start 1782236 ----------------------------------------------------- [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x00007fa14c9fb1c6 in ?? () from /usr/lib/libc.so.6 $1 = 26 $2 = {pid = 1782236, unix_sock = 36, idx = 0, status = 1, rank = 17, desc = "tcp receiver (generic) child=0", '\000' <repeats 97 times>} #0 0x00007fa14c9fb1c6 in ?? () from /usr/lib/libc.so.6 No symbol table info available. #1 0x00007fa14ca04830 in pthread_rwlock_wrlock () from /usr/lib/libc.so.6 No symbol table info available. #2 0x00007fa14ac20b49 in CRYPTO_THREAD_write_lock () from /usr/lib/libcrypto.so.3 No symbol table info available. #3 0x00007fa14adbd5da in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #4 0x00007fa14adbd9ca in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #5 0x00007fa14adbc907 in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #6 0x00007fa14adbd26c in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #7 0x00007fa14adbd68e in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #8 0x00007fa14abe75c6 in ?? () from /usr/lib/libcrypto.so.3 No symbol table info available. #9 0x00007fa14abe840b in EVP_RAND_generate () from /usr/lib/libcrypto.so.3 No symbol table info available. #10 0x00007fa14acf9282 in RAND_bytes_ex () from /usr/lib/libcrypto.so.3 No symbol table info available. #11 0x00007fa14b06cce8 in ?? () from /usr/lib/libssl.so.3 No symbol table info available. #12 0x00007fa14b05bdf7 in ?? () from /usr/lib/libssl.so.3 No symbol table info available. #13 0x00007fa14b0ef036 in tls_accept (c=c@entry=0x7fa1475c0dc0, error=error@entry=0x7ffebd9443b8) at tls_server.c:457 ret = <optimized out> ssl = warning: could not convert 'ssl_st' from the host encoding (ANSI_X3.4-1968) to UTF-32. This normally should not happen, please file a bug report. 0x7fa147668bd0 cert = <optimized out> tls_c = 0x7fa14768f490 tls_log = <optimized out> __func__ = "tls_accept" #14 0x00007fa14b0f7540 in tls_h_read_f (c=0x7fa1475c0dc0, flags=0x7ffebd9647d0) at tls_server.c:1153 r = 0x7fa1475c0ee8 bytes_free = 16383 bytes_read = <optimized out> read_size = <optimized out> ssl_error = 0 ssl_read = 0 ssl = 0x7fa147668bd0 rd_buf = "\026\003\003\004\016\v\000\004\n\000\004\a\000\004\0040\202\004\0000\202\002\350\240\003\002\001\002\002\002\026\0270\r\006\t*\206H\206\367\r\001\001\v\005\0000b1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003U\004\b\f\004Bern1\r0\v\006\003U\004\a\f\004Bern1\r0\v\006\003U\004\n\f\004RUAG1\0200\016\006\003U\004\v\f\aDefence1\0240\022\006\003U\004\003\f\versaimfs.ch0\036\027\r230302163519Z\027\r291230163519Z0`1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003"... wr_buf = "\026\003\003\000A\002\000\000=\003\003\371\204\326\361\262-9\300\344gV\2316\373\235D\314\225u8\v}\215\254DOWNGRD\001\000\3000\000\000\025\377\001\000\001\000\000\v\000\004\003\000\001\002\000#\000\000\000\027\000\000\026\003\003\a\267\v\000\a\263\000\a\260\000\004\0040\202\004\0000\202\002\350\240\003\002\001\002\002\002\r>0\r\006\t*\206H\206\367\r\001\001\v\005\0000b1\v0\t\006\003U\004\006\023\002CH1\r0\v\006\003U\004\b\f\004Bern1\r0\v\006\003U\004\a\f\004Bern1\r0\v\006\003U\004\n\f\004RUAG1\0200\016\006\003U\004\v\f\aDefence1\0240\022\006"... rd = {buf = 0x7ffebd944480 "\026\003\003\004\016\v", pos = 1405, used = 1405, size = 65536} wr = {buf = 0x7ffebd954480 "\026\003\003", pos = 0, used = 0, size = 65536} tls_c = 0x7fa14768f490 enc_rd_buf = <optimized out> n = 0 flush_flags = 0 err_src = <optimized out> ip_buf = '\000' <repeats 63 times> x = <optimized out> tls_dbg = <optimized out> __func__ = "tls_h_read_f" redo_read = <optimized out> continue_ssl_read = <optimized out> __llevel = <optimized out> __kld = <optimized out> __llevel = <optimized out> __kld = <optimized out> #15 0x000055d2519871b4 in tcp_read_headers (c=c@entry=0x7fa1475c0dc0, read_flags=read_flags@entry=0x7ffebd9647d0) at core/tcp_read.c:445 bytes = <optimized out> remaining = <optimized out> p = <optimized out> r = 0x7fa1475c0ee8 mc = <optimized out> body_len = <optimized out> tvnow = {tv_sec = 1742100857, tv_usec = 944923} tvdiff = <optimized out> mfline = <optimized out> mtransid = <optimized out> __func__ = "tcp_read_headers" #16 0x000055d251989cef in tcp_read_req (con=0x7fa1475c0dc0, bytes_read=bytes_read@entry=0x7ffebd9647c8, read_flags=read_flags@entry=0x7ffebd9647d0) at core/tcp_read.c:1509 bytes = <optimized out> total_bytes = 0 resp = 1 size = <optimized out> req = 0x7fa1475c0ee8 dst = {send_sock = 0x55d251a91020, to = {s = {sa_family = 52024, sa_data = "\257Q\322U\000\000\002\000\000\000\376\177\000"}, sin = {sin_family = 52024, sin_port = 20911, sin_addr = {s_addr = 21970}, sin_zero = "\002\000\000\000\376\177\000"}, sin6 = {sin6_family = 52024, sin6_port = 20911, sin6_flowinfo = 21970, sin6_addr = {__in6_u = {__u6_addr8 = "\002\000\000\000\376\177\000\000\030\000\000\000\000\000\000", __u6_addr16 = {2, 0, 32766, 0, 24, 0, 0, 0}, __u6_addr32 = {2, 32766, 24, 0}}}, sin6_scope_id = 0}, sas = {ss_family = 52024, __ss_padding = "\257Q\322U\000\000\002\000\000\000\376\177\000\000\030", '\000' <repeats 23 times>, "\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\262+\226Q\001 \000\000\200,5L\241\177\000\000 \020\251Q\322U\000\000 \020\251Q\322U\000\000\200\303\257Q\322U\000\00009SG\241\177\000\000\330G\226\275\376\177\000\000\b\000\000\000\000\000\000", __ss_align = 20}}, id = 1, send_flags = {f = 1, blst_imask = 0}, proto = 14 '\016', proto_pad0 = 0 '\000', proto_pad1 = 0} c = <optimized out> ret = <optimized out> again = <optimized out> __func__ = "tcp_read_req" #17 0x000055d25198ebec in handle_io (fm=fm@entry=0x7fa14c352c80, events=events@entry=1, idx=idx@entry=-1) at core/tcp_read.c:1906 ret = 8 n = 0 read_flags = RD_CONN_SHORT_READ con = 0x7fa1475c0dc0 s = 14 resp = <optimized out> t = <optimized out> ee = 0x0 __func__ = "handle_io" error = <optimized out> #18 0x000055d25199469b in io_wait_loop_epoll (repeat=repeat@entry=0, t=2, h=0x55d251c49d60 <io_w>) at core/io_wait.h:1075 n = 1 r = 0 fm = 0x7fa14c352c80 revents = 1 __func__ = "io_wait_loop_epoll" #19 0x000055d251994e87 in tcp_receive_loop (unix_sock=<optimized out>) at core/tcp_read.c:2026 __func__ = "tcp_receive_loop" #20 0x000055d25197e72c in tcp_init_children (woneinit=woneinit@entry=0x7ffebd964d1c) at core/tcp_main.c:5391 r = <optimized out> i = <optimized out> reader_fd_1 = 39 pid = <optimized out> si_desc = "tcp receiver (generic)\000\000`M\226\275\376\177\000\000\001\000\000\000\000\000\000\000\210\035\223Q\322U\000\000 \020\251Q\322U\000\000\220\315\257Q\322U\000\000\220\242/L\241\177\000\000\025\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000%\020\251Q\322U\000\000HU\257Q\322U\000\000e\005\000\000\000\000\000\000 \020\251Q\322U\000\000\3750\235Q\322U\000" si = <optimized out> __func__ = "tcp_init_children" error = <optimized out> #21 0x000055d2517c6c7e in main_loop () at main.c:1950 i = <optimized out> pid = <optimized out> si = <optimized out> si_desc = "udp receiver child=7 sock=10.0.90.1:5060\000\000\000\000\322U\000\000?\342\017K\241\177\000\000\022\000\000\000\377\377\377\377\200\006\265L\241\177\000\000\253m\237L\241\177\000\000\361|\003\000\000\000\000\000\t\000\000\000\000\000\000\000Sat Mar 15 05:25:32 2025\n\000\264L\241\177\000" nrprocs = <optimized out> woneinit = 1 __func__ = "main_loop" error = <optimized out> #22 0x000055d2517bc151 in main (argc=<optimized out>, argv=<optimized out>) at main.c:3256 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0x7ffebd966e7f "" tmp_len = 32673 port = 5060 proto = 0 aproto = 0 ahost = 0x0 aport = 0 options = 0x55d251aa74b8 ":f:cm:M:dVIhEeb:B:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 3209119183 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = 0 n_lst = <optimized out> p = <optimized out> st = {st_dev = 24, st_ino = 46237, st_nlink = 2, st_mode = 16888, st_uid = 899, st_gid = 899, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1742012732, tv_nsec = 217328715}, st_mtim = {tv_sec = 1742012732, tv_nsec = 217328715}, st_ctim = {tv_sec = 1742012732, tv_nsec = 217328715}, __glibc_reserved = {0, 0, 0}} l1 = <optimized out> tbuf = '\000' <repeats 32 times>, "\030\202\237\275\376\177\000\000@ \002\000\000@\003\000\000\001", '\000' <repeats 23 times>, "@\003\000\000@ \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@ \003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@\003", '\000' <repeats 11 times>, "\001", '\000' <repeats 118 times>... option_index = 12 long_options = {{name = 0x55d251a9230b "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x55d251a937a4 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x55d251a9826a "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x55d251a92310 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x55d251a92316 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x55d251a9231f "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x55d251a92329 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x55d251a92333 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x55d251a9233e "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x55d251a92347 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x55d251a938c1 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x55d251a92352 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x55d251a9235c "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x55d251a92363 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" [Inferior 1 (process 1782236) detached] ---end 1782236 ------------------------------------------------------- ``` Does anybody have an idea what this could be? I never saw that with previous versions, and now we can see it on several instances, but we are yet unable to reproduce. Not sure if this might be related, but we also see many messages like `Mar 17 13:39:03 ttel /usr/sbin/kamailio[2882127]: CRITICAL: <core> [core/tcp_main.c:5558]: tcp_timer_check_connections(): message processing timeout on connection id: 402 (state: 0) - closing` Best regards Mathias

2 6

Kamailio v5.8.6 Released
by Daniel-Constantin Mierla 20 Mar '25

20 Mar '25

Hello, Kamailio SIP Server v5.8.6 stable release is out. This is a maintenance release of the latest stable branch, 5.8, that includes fixes since the release of v5.8.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.8.x. Deployments running previous v5.8.x versions are strongly recommended to be upgraded to v5.8.6. For more details about version 5.8.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2025/03/kamailio-v5-8-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note that 5.8.x is currently the previous stable release series, the latest is 6.0.x and v6.0.1 was released on March 10, 2025. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

Releasing v5.8.6
by Daniel-Constantin Mierla 20 Mar '25

20 Mar '25

Hello, I am considering to release Kamailio v5.8.6 (out of branch 5.8) on Thursday, March 20, 2025. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. The most of the commits are backported, should any be found missing, reply to sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 1

Issue with async_cdp_callback() of MAR diameter message
by Minello, Loredana 18 Mar '25

18 Mar '25

Hello, I have an issue during the registration phase with the Diameter MAR procedure. The issue is as follows: 1. I perform a registration. 2. The MAR is correctly sent using the function: ims_www_challenge("REG_MAR_REPLY", "$var(auth_realm)"); 3. Upon receiving the MAA, after executing async_cdp_callback(), the execution does not return to the Kamailio reply route indicated (REG_MAR_REPLY). I tried replacing t_continue with t_continue_skip_timer in the async_cdp_callback() function of the MAR (see below), and everything works correctly. //tmb.t_continue(data->tindex, data->tlabel, data->act); tmb.t_continue_skip_timer(data->tindex, data->tlabel, data->act); free_saved_transaction_data(data); return; Note: When I send the SAR, I do not have this issue, but I noticed that in the corresponding async_cdp_callback(), the t_continue_skip_timer function is used. Do you think the modification I made to async_cdp_callback() for the MAR is correct? Why does t_continue not work? Thanks.

1 0

dispatcher not distributing well?
by David Villasmil 17 Mar '25

17 Mar '25

Hello guys, i have a kamilio with a dispatcher list in db like +------------------------------------------------+----------------------------------------------+----------------------------+ | id | setid | destination | flags | priority | attrs | description | register_datetime | +------+-------+---------------------+-------+----------+------------------------------+---------------+---------------------+ | 3239 | 430 | sip:gateway-08:5080 | 0 | 10 | duid=gateway-08;weight=50 | gateway-08 | 2023-03-21 00:19:44 | | 3246 | 430 | sip:gateway-11:5080 | 0 | 10 | duid=gateway-11;weight=50 | gateway-11 | 2023-05-15 23:00:28 | | 3247 | 430 | sip:gateway-12:5080 | 0 | 10 | duid=gateway-12;weight=50 | gateway-12 | 2023-05-15 23:06:57 | | 3249 | 430 | sip:gateway-14:5080 | 0 | 10 | duid=gateway-14;weight=50 | gateway-14 | 2023-05-15 23:24:44 | | 3276 | 430 | sip:gateway-15:5080 | 0 | 10 | duid=gateway-15;weight=50 | gateway-15 | 2024-05-01 19:43:19 | | 3277 | 430 | sip:gateway-16:5080 | 0 | 10 | duid=gateway-16;weight=50 | gateway-16 | 2024-05-01 19:51:16 | | 3278 | 430 | sip:gateway-1:5080 | 0 | 10 | duid=gateway-17;weight=50 | gateway-17 | 2024-05-01 19:58:13 | | 3279 | 430 | sip:gateway-17:5080 | 0 | 10 | duid=gateway-18;weight=50 | gateway-18 | 2024-05-01 20:06:44 | | 3280 | 430 | sip:gateway-3:5080 | 0 | 10 | duid=gateway-19;weight=50 | gateway-19 | 2024-05-01 20:14:50 | | 3281 | 430 | sip:gateway-2:5080 | 0 | 10 | duid=gateway-20;weight=50 | gateway-20 | 2024-05-01 20:23:25 | +------+-------+---------------------+-------+----------+------------------------------+---------------+---------------------+ and i'm dispatching with if(!ds_select_dst("$var(dispatcher_id)", "10")) { xlog("[DISPATCH]: ds_select_dst FAILED!'\n"); send_reply("404", "No destination"); exit; } still kamailio isn't distributing at all but for some reason is favoring high-description gateways: kamctl rpc dlg.list 5 gateway-20:5080;transport=udp" 2 gateway-19:5080;transport=udp" it's forwarding calls mostly to gateway-20, gateway-19, gateway-18, gateway-17... in descending order... Why is kamailio doing that? i'd expected it to distribute to all based on the call load on each gateway. Thanks all! Regards, David Villasmil email: david.villasmil.work(a)gmail.com

3 4

Recommendations for paid work
by Anthony Ford 14 Mar '25

14 Mar '25

Hi Can anyone recommend someone that can help us upgrade our 2 Kamailio servers please. After several failed attempts to do this ourselves, it is time to call in the professionals. 5.6.0-dev to the latest The current set up is 2 servers working in tandem, redis and mysql plus nebula. We do have a test server also attached, that can be used for testing. Thanks Tony

6 5

add_contact_alias modifies only one Contact address
by James Browne 13 Mar '25

13 Mar '25

- https://kamailio.org/docs/modules/5.8.x/modules/nathelper.html#nathelper.f.… This add_contact_alias() function changes only the first Contact address in a REGISTER request, even though it's normal (RFC3261, 10.2) for a REGISTER to have multiple Contact addresses. This seems to me to be a kamailio bug. For example, a user might remove one binding while adding a second, in a REGISTER request. If kamailio relays this while adding an alias to only the expires=0 binding, then the new binding may be stored incorrectly in the registrar. James

2 4

Server selecting TCP transport
by Jon Bonilla (Manwe) 13 Mar '25

13 Mar '25

Hi all Using 5.8.4 I have a trunk with a permanent registration created by rpc in the location table. It looks like this: kamcmd> ul.lookup location sbc.mydomain.com { AoR: sbc.mydomain.com Contacts: { Contact: { Address: sip:xxx@sbc.mydomain.com Expires: -102739 Q: 1 Call-ID: dfjrewr12386fd6-343(a)kamailio.rpc CSeq: 1 User-Agent: kamailio SIP Router - RPC Server Received: [not set] Path: <sip:192.168.255.202:5060;lr> State: CS_SYNC Flags: 0 CFlags: 0 Socket: [not set] Methods: 0 Ruid: ulcx-67c9e2ff-19f8-1 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 0 Last-Keepalive: 1741899218 KA-Roundtrip: 0 Last-Modified: 0 } } } In this situation the proxy sends the request to 192.168.255.202 which is a kamailio load balancer which is responsible for sending the call to the customer. The problem is that kamailio, when relaying this request, first performs TCP srv lookup and tries to send the request via TCP. There's no transport=tcp in the address. The lb's dns settings are: dns_try_ipv6=no dns_retr_time=1 dns_retr_no=1 dns_use_search_list=no use_dns_cache=on use_dns_failover=on dns_srv_lb=on dns_try_naptr=no dns_sctp_pref=1 dns_tcp_pref=1 dns_tls_pref=1 dns_udp_pref=1 Seems like this kamailio tries TCP SRV first, and then TLS and then UDP if the previous doesn't bring results. But no NAPTR is enabled. I don't know why it will choose TCP over UDP in this case. -- PekePBX, the multitenant PBX solution https://pekepbx.com

1 0

SDP Truncation When Relaying from WebSocket to UDP – Expected Behavior?
by Pavan Kumar 13 Mar '25

13 Mar '25

Hello Kamailio Community, I recently encountered an interesting behavior when using Kamailio to relay SIP messages from a WebSocket client to FreeSWITCH over UDP. *Observed Behavior:* - The WebSocket client sends an *INVITE* with a large SDP. - Kamailio forwards this request over UDP to FreeSWITCH. - Upon inspection, the *SDP in the relayed message appears truncated*. (Probably MTU limit) - *Surprisingly, the call still establishes successfully*, and there are no noticeable issues with audio or call setup. *My Questions:* 1. *Is this expected behavior?* Should Kamailio automatically truncate SDP when relaying from WebSocket to UDP? 2. *Could this be working accidentally?* For example, is FreeSWITCH handling the partial SDP gracefully by default? 3. *Should I be concerned about potential failures in different scenarios?* (e.g., ICE candidate loss, missing codec negotiation) I would appreciate any insights from the community on whether this is a known or expected behavior in Kamailio, or if it might be a configuration issue. Thanks in advance for your help! Best regards, Pavan Kumar

4 5

Need help using Kamailio IMS and Open5GS for 5G core
by Pete Kay 13 Mar '25

13 Mar '25

Hi I am able to compile Kamailio IMS and Open5GS. The instruction in https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ is for 4G using Diameter. For 5G, we need to use HTTP protocol. Does anyone know if there is any guide on how to configure Kamailio IMS and Open5GS on 5G core using HTTP protocol for PCRF ? Thanks for millions for all your help. Pete

2 1

Re: upgrading process
by Anthony Ford 12 Mar '25

12 Mar '25

Thanks Ben Really appreciate your response Tony From: Ben Kaufman via sr-users <sr-users(a)lists.kamailio.org> Reply to: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Date: Wednesday, 12 March 2025 at 16:20 To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Cc: Ben Kaufman <bkaufman(a)bcmone.com> Subject: [SR-Users] Re: upgrading process Luckily there usually aren't a lot of breaking changes in Kamailio updates, and config files are mostly back compatible. That doesn't mean that there are never changes, but it does mean that the number of issues to resolve is usually small. * wanted to know if I can run make install on every iteration i.e. 5.6.1, the 5.6.2 etc There shouldn't really be any changes needed to config for the patch/fix versions like that (third decimal place) so those should be fine (and is good practice if you're not able to quickly update to a supported version for any reason), but it shouldn't be necessary to touch every incremental version to upgrade Kamailio. Every major release has an upgrade guide from the pervious version, so in your case: * 5.6 to 5.7: https://www.kamailio.org/wikidocs/install/upgrade/5.6.x-to-5.7.0/ * 5.7 to 5.8: https://www.kamailio.org/wikidocs/install/upgrade/5.7.x-to-5.8.0/ * 5.8 to 6.0: https://www.kamailio.org/wikidocs/install/upgrade/5.8.x-to-6.0.0/ It still shouldn't be necessary to touch each individual version while upgrading. I'd recommend reading through these docs in order taking note of the following: * Look for potentially breaking changes in the core. I don't see any in those documents, but a good example would be if upgrading from 4.x to 5.x how fifo was deprecated. * Look for modules changes. Mostly you'll see things like new features which shouldn't be breaking. A few modules were deprecated/archived in 5.8 ( app_sqlang, and auth_identity). Sometimes modules have small breaking changes in them as well, for example in 6.0 the dialog module dropped support for the dlg_flag parameter. Check your kamailio configs to see if any of these listed changes will impact you. * Follow any DB upgrade changes. These are usually simple changes - things like adding an index to a column, or changing a varchar(n) datatype to be varchar(n+y) which won't break your existing config. Another reply correctly points out that you should watch for changes to the version table. This is possibly a situation where a conflict could arise: The version required for one table might be 1 in 5.6 and 2 in 6.0. It might be worth while to copy the existing version table to a new table (like version_60 for example), and use kamailio's version_table parameter to use the new version table on the updated config. (note: The upgrade guides don't show any table version changes, so you probably don't need to do this). Finally, as a recommendation, smoke test your config in docker. You might not have the container setup in a way to actually receive SIP messages, but "does the config file load correctly" is a nice thing to have resolved ahead of time. * Regards, Kaufman ________________________________ From: Anthony Ford via sr-users <sr-users(a)lists.kamailio.org> Sent: Wednesday, March 12, 2025 9:30 AM To: sr-users(a)lists.kamailio.org <sr-users(a)lists.kamailio.org> Cc: Anthony Ford <tony.ford(a)apalo.co.uk> Subject: [SR-Users] upgrading process CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi I need some help please. I am very inexperienced with Kamailio, and am trying to work out how to upgrade without rewriting any of the current config. I am going from 5.6.0 to 6.0.0 and wanted to know if I can run make install on every iteration i.e. 5.6.1, the 5.6.2 etc. until I need to make a bigger step, and may have to change tables etc. In the document for upgrading 5.6.x to 5.7.x it says make change to Watch table, but I have no watch table. Very confused. Thanks Tony

1 0

CANCEL suspension and forking
by Alex Balashov 12 Mar '25

12 Mar '25

Hi, When a CANCEL is received and matches a known INVITE transaction, it is forked to all existing branches of that INVITE transaction, at least with these settings: modparam("tm", "cancel_b_method", 2) modparam("tm", "failure_reply_mode", 3) I have a mobile endpoint that is slow to be pushed awake and reregister, tsilo-style, and by the time it finally appears on the scene, the underlying INVITE transaction has been terminated. Accordingly, that endpoint receives no CANCEL. You might ask why that's a problem, if it also didn't receive a forked INVITE. The problem is that Apple's CallKit requires interactive presentation of VoIP APNS notifications as though they are "calls", leading to the phenomenon of what might be called "ghost calls" extrinsically to the actual mobile application. Anyway, I am aware of numerous possible solutions to this problem in principle; most involve sending an out-of-band SIP message to signify an alternative cancellation of the call. However, wonder if I am missing some best-practical approach, perhaps through an overlooked TM facility, or some way of keeping the transaction alive longer than the CANCEL from the UAC would ordinarily require? I don't see how that would work, but thought better to ask. Thanks! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

3 4

upgrading process
by Anthony Ford 12 Mar '25

12 Mar '25

Hi I need some help please. I am very inexperienced with Kamailio, and am trying to work out how to upgrade without rewriting any of the current config. I am going from 5.6.0 to 6.0.0 and wanted to know if I can run make install on every iteration i.e. 5.6.1, the 5.6.2 etc. until I need to make a bigger step, and may have to change tables etc. In the document for upgrading 5.6.x to 5.7.x it says make change to Watch table, but I have no watch table. Very confused. Thanks Tony

3 3

Set TTL for skipped NAPTR record due to all IPs are unreachable
by Mathias Schneuwly 11 Mar '25

11 Mar '25

Hi I've a question regarding skipped NAPTR records. In our setup, we are using quite big DNS TTLs (860400). If there is an issue on the target server, the NAPTR record is marked as skipped "Mark to skip _sips._tcp.... NAPTR record due to all IPs are unreachable" until the TTL is expired. Since our TTLs are so big, the destination is no longer reachable during this time, even if the server is reachable again. I've seen that I can set "dns_cache_max_ttl" to reduce the time, but this is of course for all cached DNS records. Is there a way to set how long a NAPTR record is skipped or disable the feature at all? Or maybe skip the NAPTR only for the current dialog or transaction? Thanks for your help Best regards Mathias

2 7

Kamailio v6.0.1 Released
by Daniel-Constantin Mierla 10 Mar '25

10 Mar '25

Hello, Kamailio SIP Server v6.0.1 stable release is out. This is a maintenance release of the latest stable branch, 6.0, that includes fixes since the release of v6.0.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v6.0.x. Deployments running previous v6.0.x versions are strongly recommended to be upgraded to v6.0.1. For more details about version 6.0.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2025/03/kamailio-v6-0-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

Releasing v6.0.1
by Daniel-Constantin Mierla 10 Mar '25

10 Mar '25

Hello, I am considering to release Kamailio v6.0.1 (out of branch 60) on Monday, March 10, 2025. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 1

Kamailio with Presence Module and Publishing by Asterisk
by Ludovic GRANGE 05 Mar '25

05 Mar '25

Hi, I'm having a problem managing the presence between Kamailio and Asterisk. I have configured Kamailio as a presence server. Asterisk sends presence information via publishing sip request. My softphone which uses Kamailio as a presence server and as a proxy has 2 BLFs configured. On a first call, the presence status is displayed on the 2 keys. But for the 2nd call, only the extension receiving the call has its status changed on the BLF. Via sngrep, the Publishing requests arrive on Kamailio but the DB is not updated because the e-tag does not match. If I wait until the end of the expiry period (60s for the test), the DB is flushed and the 1st call works again. Could you please help me? Thank you Translated with DeepL.com (free version) -- Bien cordialement, Bande verticale Prosoluce Ludovic Grange Administrateur systèmes & réseaux Picto mailludovic.grange(a)prosoluce.fr <mailto:ludovic.grange@prosoluce.fr> Picto tél 05 31 61 62 25 <tel:+33531616225> Picto webwww.prosoluce.fr <https://www.prosoluce.fr> Logo Prosoluce

3 5

Best practices for proxy protocol and TLS offloading
by Alex Balashov 04 Mar '25

04 Mar '25

Hello, I am converting a Kamailio WSS/TLS gateway to pure TCP, with an external HAProxy handling TLS termination and emitting the proxied connection as plain TCP. I am using the PROXYv2 protocol, with `tcp_accept_haproxy=yes`, to convey the upstream network and transport-layer reachability info into Kamailio. I am trying to figure out best practices for mapping the contacts on those connections to the proxied connections themselves. For registrations, tcp_force_alias() (with `tcp_accept_aliases=yes`) works well, and inbound calls go to the right place. However, I'm not quite sure what to do with other flows, such as, for example, in-dialog requests on inbound calls going to the TLS endpoints. There are obviously a lot of possibilities, all or most of which I've tinkered with. These generally involve either {s.replace}-ing `;transport=tls` with `;transport=tcp` in the contacts received from the client, or using the traditional `nathelper` contact alias / RURI alias bag of tricks. However, I don't like the former solution because it leads to a non-compliant R-URI going to the endpoint (it's not the ;transport it sent in its contact), and I don't like the latter because it seems like there are too many moving parts. When tcp_force_alias() works so well for registrations, there must be some small linchpin I'm missing for normal request-reply flows. What is it? Thanks in advance! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 4

Topos Module Questions
by David Tek 04 Mar '25

04 Mar '25

Hello, I am trying to configure the Topos module and have some questions. # topos:msg-outgoing vs topos:msg-sending https://www.kamailio.org/docs/modules/5.8.x/modules/topos.html#topos.e.msg_… I am trying to understand the difference between these two event routes(beyond the content of the SIP message ). I notice that both are invoked when OPTIONS are generated by the local Kamailio server but only msg-sending is invoked for messages transiting the Kamailio( ie proxied, not locally generated). Is there some difference in how these event_routers are invoked beyond the content of the SIP message? # tops -> requests/replies When I am in event_route[topos:msg-sending] { and invoke 'drop', does this apply to the current message or does it apply to the transaction? I have a Kamailio node with devices on either side. Let's call side A untrusted and side B trusted. I want TOPOS happening against the untrusted device but not the trusted device. I have found that when I invoke 'drop' on a request coming from A to B, it disables TOPOS not only on that packet, but also the reply comes from B back to A, TOPOS isn't applied when the reply exits Kamailio towards A. So if I call 'drop' on the request coming from A to B, the reply coming from B to A has no TOPOS applied. How do I get TOPOS applied to all traffic facing a particular device while leaving that traffic un-stripped when the same traffic is interacting with other devices that are trusted? Thanks, David

2 2

Torso Sex Toy for Men & Women
by feifeiwangf＠uusextoy.com 04 Mar '25

04 Mar '25

The sex doll torso is a very light mini sex doll. Usually, its weight is 4kg to 20kg. These sex doll torsos are made of TPE or silicone. Of course, they are all very safe materials. https://www.sextorso.com/

3 2

SHA-256 HASH
by Social Boh 04 Mar '25

04 Mar '25

Hello list, is it possible create a user using sha-256 hash? My goal is Asterisk PBX Register ----- sha-256 digest authentication -> Kamailio Regards -- --- I'm SoCIaL, MayBe

2 3

KEMI logging function name output
by Dmitry Sytchev 28 Feb '25

28 Feb '25

Hi all! By default logging from KEMI with KSR.log() is prefixed with something like this: <core> [core/kemi.c:152]: sr_kemi_core_log(): Can we somehow disable this not to print it every time with every message? Thanks! [image: image.png] -- Best regards, Dmitry Sytchev

2 2

SNMP thresholds
by Sergio Charrua 27 Feb '25

27 Feb '25

Hi all! we have set SNMP stats on our production server. The server is only receiving 1% of the calls, less than 1 CAPS, but we are receiving some SNMP alarms that are a bit weird to us. [image: image.png] This is an example. As we were unsure about the thresholds to be set for Msg Queue, we set Minor to 20 and Major to 100, which resulted in some alarms when we exceeded the Major threshold. From our understanding, the Max Major MSG Queue threshold was 2176, which obviously generated an alarm. But we can't understand why when a Msg Queue depth of 1280 generated an Minor Threshold alarm when the threshold is 20!! Why not generate a Major Threshold alarm instead, as it did reach the Major Threshold ? Also, does anyone have a clue on how to estimate Major and Minor thresholds? How does this Msg Queue handler work? Is it Kamailio's level or on OS/Kernel level that it gets the statistics from? Apart from the official Kamailio SNMPStats docs, any doc or article one would share? greatly appreciated. ( I so much hate SNMP!!! :) ) Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

1 0

Tweaking TCP/TLS connection timers
by Ihor Olkhovskyi 27 Feb '25

27 Feb '25

Hello, I'm observing a bit strange behavoir of Kamailio, but maybe I'm wrong in my assumptions. In some cases Kamailio just closes absolutely valid TCP connection, as I see it in Wireshark [image: image.png] At the same time I do see in Kamailio logs a lots of lines with tcp_timer_check_connections(): message processing timeout on connection id: XXXXX (state: 0) - closing I see that many TCP connections are closing (and it's ok as we have mobile devices connected and loosing connections for them is ok) But for me this connection is perfectly ok looking on TCP keepalives, what can cause this behavoir? I have these TCP options tcp_connect_timeout=30 tcp_conn_wq_max=63536 tcp_crlf_ping=yes tcp_delayed_ack=yes tcp_fd_cache=yes tcp_keepalive=yes tcp_keepcnt=3 tcp_keepidle=30 tcp_keepintvl=10 tcp_linger2=30 Kamailio 5.8.3 Any hints are appreciated. -- Best regards, Ihor (Igor)

2 2

Kamailio and TLS-PSK Support
by Юрій Пивоваров 27 Feb '25

27 Feb '25

Dear Kamailio Community, I am currently exploring the possibility of configuring Kamailio to use TLS-PSK (Pre-Shared Key) for secure SIP signaling. Has anyone successfully configured Kamailio to work with TLS-PSK? If so, could you share any guidance, configuration examples, or relevant modules that need to be adjusted? In this setup, the SIP client will be a device with very limited resources, making it impossible to use certificates. This is why I am specifically looking into a TLS-PSK solution. I have also tried configuring stunnel as a proxy and set listen = tcp:127.0.0.1:5061 in kamailio config, but I haven't been able to get it working. Any suggestions on what might be missing or misconfigured? Thank you in advance for your help!

1 0

Drop RTP Flow and move to another point
by Social Boh 26 Feb '25

26 Feb '25

Hello List, before spending much time on solving this scenario, I'd like to know if this kind of operation can be done using some Kamailio function (maybe dlg_req_within?) or other method. The scenario is: a B2B-1 server call two different destinations, one is a SIP trunk and another is another B2B-2. Both calls go through Kamailio which uses RTPEngine for the media flow. The idea is to drop the first B2B from RTP Flow (leave for signaling) when both calls are answered and leave everything to Kamailio-RTPEngine, like: LegA: Kamailio-RTPEngine -> B2B-2 LegB: Kamailio-RTPEngine -> SIP trunk Thank you in Advance Regards --- I'm SoCIaL, MayBe

1 1

PRACK Retransmission and 408 Timeout Issue in Kamailio
by 高秉寬 26 Feb '25

26 Feb '25

Dear Kamailio Developers, I am using Kamailio as a SIP server to facilitate a phone call, but I am encountering an issue where the call cannot be established due to Kamailio sending a 408 Request Timeout to the caller. Issue Details: - A (Caller) sends an initial INVITE to Kamailio, which then forwards it to B (Callee). The INVITE contains the following Supported header: Supported: timer,100rel,replaces,precondition,from-change,histinfo,tdialog I suspect the *precondition* option may be relevant to the issue. - *B* responds with a *183 Session Progress* message, which includes: Require: 100rel,precondition Kamailio correctly forwards this response to *A.* - *A* then sends a *PRACK* request to Kamailio. However, this request contains: Require: sec-agree Supported: timer Notably, *precondition* is absent from both the *Require* and *Supported* headers. - Kamailio forwards this *PRACK* to *B*, and *B* responds with *200 OK*, including: Supported: 100rel,from-change,tdialog - However, Kamailio does not seem to acknowledge *B's 200 OK* and instead *keeps retransmitting the PRACK* to *B*. B responds with *200 OK* again, but the cycle repeats. - After three retransmissions of *PRACK*, Kamailio eventually sends *408 Request Timeout* to *A*, leading *A* to send a *CANCEL* request. Device Used: - *Caller (A):* Asus ROG Phone 5 - *Callee (B):* Asus ROG Phone 6 Both are commercially available mobile phones. Possible Cause: According to *3GPP TS 24.229, Subclause 5.1.3.1*, If the received response with an SDP body includes a Require header with > the "precondition" option-tag, the originating UE shall include a Require > header with the "precondition" option-tag in responses with an SDP body to > subsequent requests that include an SDP body and include the "precondition" > option-tag in either the Supported or Require header field received > in-dialog. In this case: - The *183 Session Progress* from *B* contains Require: *precondition*. - The subsequent *PRACK* from *A* does not include *precondition* in either *Require* or *Supported*. Could this mismatch be the reason Kamailio keeps retransmitting *PRACK* and ignoring *B's 200 OK*? Or could there be another factor causing Kamailio to behave this way? If additional details are needed, please let me know. Best regards, Ping Kuan Kao

3 4

Issue with registrations
by Anthony Ford 26 Feb '25

26 Feb '25

Hi Version = 5.6.0-dev0 We are seeking help to resolve an issue with registering devices to 3CX (All 3CX servers, have tried 8 different ones) . all the auth info including passwords etc are identical on the 3cx servers. We use Kamailio to register mobile sim cards to 3rd party sip servers i.e. 3CX. We send the normal Username, server addresses and auth details but are experiencing failures with 3CX rejecting the registration and return Proxy Auth failure 407. We have noticed in the pcaps from both sides that the expire value is changing from 180 as an example to 0. As an example In the uac reg_dump the values are : l_uuid: +447529135850<tel:+447529135850> l_username: +447529135850<tel:+447529135850> l_domain: sbc-mt.asim.apalo.io<http://sbc-mt.asim.apalo.io/>;transport=udp r_username: 1001 r_domain: egte.3cx.uk<http://egte.3cx.uk/> realm: <null string> auth_username: FdlHDC1IvA auth_password: extracted auth_ha1: none auth_proxy: sip:egte.3cx.uk:5060 expires: 60 flags: 0 diff_expires: -1738853736 timer_expires: 0 reg_init: 1738850836 reg_delay: 0 contact_addr: k01.asim.apalo.io<http://k01.asim.apalo.io/>;transport=tcp socket: <null string> [cid:image001.png@01DB86AB.2701F190] [cid:image002.png@01DB86AB.2701F190] [cid:image003.png@01DB86AB.2701F190] Looking forward to hearing from you. Many thanks Tony Ford

3 3

REG_MAR_REPLY never get executed
by stinktohighheaven＠gmail.com 26 Feb '25

26 Feb '25

Using Kamailio v5.3, based on the example for scscf found here: https://github.com/kamailio/kamailio/blob/master/misc/examples/ims/scscf/ka… after calling ims_www_challenge("REG_MAR_REPLY", "$var(realm)", "$var(alg)"); the control never goes to REG_MAR_REPLY route block, but it goes to the start of the requet_route block. here is the kamailio.cfg script: request_route { ....... /* Handle Registrations */ if (is_method("REGISTER")) { route(REGISTER); exit; } ...... } /** * Handling of REGISTER requests */ route[REGISTER] { ...... #!ifdef WITH_AUTH if (!ims_www_authenticate("$var(realm)")) { #!else if ($var(alg) == "3GPP-Digest" && !ims_www_authenticate("$var(realm)")) { #!endif if ($? == -2) { send_reply("403", "Authentication Failed"); exit; } else if ($? == -3) { send_reply("400", "Bad Request"); exit; } else if ($? == -9) { xdbg("Authentication re-sync requested\n"); ims_www_resync_auth("REGISTER_RESYNC_REPLY", "$var(realm)"); exit; } else { /* user has not been authenticated. Lets send a challenge via 401 Unauthorized */ xdbg("About to challenge! auth_ims\n"); ims_www_challenge("REG_MAR_REPLY", "$var(realm)", "$var(alg)"); exit; } } else { xdbg("Auth succeeded\n"); /* We need to check if this user is registered or not */ if (!impu_registered("location")) { save("PRE_REGISTER_SAR_REPLY", "location"); exit; } else { isc_match_filter_reg("1", "location"); save("REGISTER_SAR_REPLY", "location"); exit; } } } } /** * Handling of REGISTER MAR replies */ route[REG_MAR_REPLY] { xlog("L_DBG","maa_return code is $avp(s:maa_return_code)\n"); /* this is async so to know status we have to check the reply avp */ switch ($avp(s:maa_return_code)) { case 1: /* success */ xdbg("MAR success - 401/407 response sent from module\n"); break; case -1: /* failure */ xerr("MAR failure - error response sent from module\n"); break; case -2: /* error */ xerr("MAR error - sending error response now\n"); send_reply("503", "MAR failed"); break; default: xerr("Unknown return code from MAR, value is [$avp(s:maa_return_code)]\n"); send_reply("503", "Unknown response code from MAR"); break; } exit; } and here's the log: 12(18) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/usr/local/etc/kamailio/kamailio.cfg] l=757 a=27 n=ims_www_challenge 12(18) DEBUG: ims_auth [authorize.c:293]: challenge(): Looking for route block [REG_MAR_REPLY] 12(18) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [-2] 12(18) DEBUG: ims_auth [authorize.c:317]: challenge(): Need to challenge for realm [ims.mnc071.mcc432.3gppnetwork.org] 12(18) DEBUG: ims_auth [authorize.c:324]: challenge(): Checking if REGISTER is authorized for realm [ims.mnc071.mcc432.3gppnetwork.org]... 12(18) DEBUG: ims_auth [authorize.c:1449]: get_auth_userdata(): Searching auth_userdata for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 12(18) DEBUG: ims_auth [authorize.c:460]: challenge(): Suspending SIP TM transaction 12(18) DEBUG: ims_auth [authorize.c:1529]: multimedia_auth_request(): Sending MAR 12(18) DEBUG: ims_auth [cxdx_mar.c:574]: cxdx_send_mar(): Successfully sent async diameter 70(76) INFO: ims_auth [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp (avp_code = 297, vendor_id = 0) 70(76) DEBUG: ims_auth [authorize.c:1303]: new_auth_vector(): new auth-vector with ck [d2deb48b5b3b614ba9112396e3c036fe] with status 0 70(76) DEBUG: ims_auth [authorize.c:1560]: pack_challenge(): setting QOP str used is [, qop="auth"] 70(76) DEBUG: ims_auth [authorize.c:1562]: pack_challenge(): QOP str used is [, qop="auth"] 70(76) DEBUG: ims_auth [authorize.c:1449]: get_auth_userdata(): Searching auth_userdata for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 70(76) DEBUG: ims_auth [authorize.c:1458]: get_auth_userdata(): Found auth_userdata 70(76) DEBUG: ims_auth [authorize.c:1682]: add_auth_vector(): Adding auth_vector (status 1) for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org / IMPI 432710000010044(a)ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 70(76) DEBUG: ims_auth [cxdx_mar.c:486]: async_cdp_callback(): DBG:UAR Async CDP callback: ... Done resuming transaction 70(76) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [1] 70(76) ERROR: tm [t_suspend.c:197]: t_continue_helper(): active transaction not found 70(76) DEBUG: ims_auth [cxdx_mar.c:87]: free_saved_transaction_data(): Freeing saved transaction data: async 11(17) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=380 a=5 n=route

4 8

tm stats on prometheus
by Alexis Fidalgo 25 Feb '25

25 Feb '25

Hello all, i found that tm stats (kamcmd tm.stats) are not present in the response of xhttp_prom (prometheus), so in new configurations that we applied, we have no information/stats on reply codes. Is there a way to add this information to the xhttp_prom response? thanks in advance. regards

2 4

debug memory usage by AVP
by Sergey Safarov 25 Feb '25

25 Feb '25

In the "kamcmd mod.stats all shm" output i see to big value for "create_avp" metric Module: core { tcpconn_new(1205): 35104 counters_prefork_init(211): 61952 create_avp(178): 20737248 cfg_clone_str(132): 304 cfg_shmize(221): 1248 main_loop(1381): 16 Is possible to print AVP list and APV content without kamailio config change and restart?

1 0

Kamailio uses an ephemeral IP port instead of the port defined in $fs
by Leonid Fainshtein 24 Feb '25

24 Feb '25

Hi, I am using Kamailio v.5.8.4 on Ubuntu 24.04, kernel 6.8.0-51-generic In the configuration script I explicitly set $fs="udp:adrr:port". In normal situations, it works properly and I see that the UDP SIP requests are sent from the requested IP and port. Due to some reasons, free space on the server root filesystem was exhausted. I cleaned up the file system and everything looked good except the fact that Kamailio started to send messages from ephemeral IP ports instead of the port defined in $fs. Restart of Kamailio didn't solve the problem. But the server reboot fixed the issue. I don't understand how the lack of free disk space can cause such a problem and I'm afraid that there is another reason that I am missing. Has anybody seen such a problem? Best regards, Leonid

3 3

Outdated location information on deleted registrations
by Mathias Schneuwly 19 Feb '25

19 Feb '25

Hi I'm using Kamailio 5.8.4 and the python KEMI module. When I move the registration from one device to another, I can see for a while two entries with 'kamctl ul show' where the Expires parameter of the "old" registration is set to "deleted" and the "new" registration shows the seconds until the registration expires. "Address": "sips:200101@10.0.1.130:42323 ;transport=tls", "Expires": "deleted", -- "Address": "sips:200101@10.0.1.129:56374 ;transport=tls", "Expires": 3600, So far so good. When I try to fetch the actual registration address using "registrar.reg_fetch_contacts" or "registrar.lookup_xavp", I'm always getting the "old" deleted registration address instead of the new address as long as the deleted record is not removed. Feb 18 10:05:51 ttel /usr/sbin/kamailio[2356327]: WARNING: {1 511 INVITE 952600514-5060-52(a)BA.A.C.BCI} <core> [core/kemi.c:157]: sr_kemi_core_log(): reg_fetch_contacts: sips:200101@10.0.1.130:42323;transport=tls Feb 18 10:05:51 ttel /usr/sbin/kamailio[2356327]: WARNING: {1 511 INVITE 952600514-5060-52(a)BA.A.C.BCI} <core> [core/kemi.c:157]: sr_kemi_core_log(): lookup_xavp: aor=200101, uri=sips:200101@10.0.1.130:42323;transport=tls, socket=tls:10.0.1.1:5061, dsturi=None I also see that the database is only updated after the deleted entry is removed. Until then, the database still contains the old address. Btw, I'm using "modparam("usrloc", "db_mode", 2)", which would explain the delayed persisting into the database. 62|uloc-67b44aae-23f48e-2|200101||sips:200101@10.0.1.130:42323 ;transport=tls|||2460724.91858218|-1.0|482845299-5060-1(a)BA.A.B.BDA|2002|2460724.87691551|0|0|Grandstream GXV3350 1.0.3.52|tls:10.0.1.1:5061 |7135|<urn:uuid:00000000-0000-1000-8000-C074AD188038>|1|0|52|0|16 I'm asking myself whether the behavior is correct that "registrar.reg_fetch_contacts" and "registrar.lookup_xavp" are returning the deleted information instead of the "new" registration information? If yes, is there another way how I could get the "new" registration information? I'm not really interested in the old outdated information... Best regards Mathias

2 2

Info: maintenance work for kamailio.org server on Tuesday, Feb 18, 2025
by Daniel-Constantin Mierla 18 Feb '25

18 Feb '25

Hello, there is a planned mainenance work on the infrastructure for the server hosting kamailio.org services (among them: the main website, wiki, mailing lists) on next week, Tuesday, February 18, 2025, to start about 10:00am Berlin time (CET). Expect some intervals of unavailability, we hope they will be short and most of them not noticeable for the majority accessing these services during the day. Once the work is finished, an announcement will be sent out. The apt repository, github project and the matrix chat channels should not be affected, they can be accessed as usual and can be used a backup communication channels if anyone observes something that has to be addressed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 2

Asterisk ConfBridge behind Kamailio+Rtpengine
by Rahul mm 18 Feb '25

18 Feb '25

Dear all, Thanks for the amazing product ! I’m trying my hands on a scenario involving Asterisk for video_sfu and a bunch of webrtc and sip clients. The condition is that every call must essentially be a conference call for the participants to add more dynamically. I front ended asterisk with Kamailio and RTPEngine for ssl offloading, load balancing, and registrations. So when one user is present in the conference (his invite SDP containing one audio and one video line) i get local video and MoH back, but when another user joins in and a re-invite is send from asterisk containing two video lines - one for the sendrecv and other for send only, rtpengine doesn’t process the sendonly video line - keeps it as is RTP/AVP instead of making it *UDP/TLS/RTP/SAVPF.* *Is there a way to achieve that? or I’m on the wrong path ?* BR, RM

1 0

Kamailio - asterisk registration issue & transparent proxy
by Enzo Damato 17 Feb '25

17 Feb '25

Hi. I'm working on setting up kamailio as a load balancer for some asterisk instances. I've build a configuration that is working for the most part, but I am encountering issues with calls from the asterisk instances to users who's registrations were processed through the kamailio instance. When these users register, asterisk saves thier AOR as the address of the kamailio instance, and then subsequently tires to send invites to kamailio, instead of to the UAC. Since kamailio just proxied the registration, without actually registering the user, it doesn't know what to do with the invite, and the call fails. I would like to configure kamailio to rewrite the sip requests so that all traffic appears to be coming from the end user, rather than from the kamailio instance, essentially making the proxy transparent. Is this possible? Thank you, Enzo Damato

4 6

Prioritize specific codecs
by Temilolu Fayomi 17 Feb '25

17 Feb '25

Hello, I am working with inbound calls on kamailio (specifically fax), and was wondering if there was a way to re-prioritize the codecs found in the sdp of an invite. I've looked at using the sdpops module, but haven't been able to re-arrange the priority of the codecs listed. I've tried removing codecs to help incoming faxes switch over to t38 per my upstream providers instructions (calls will do a t38 re-invite if the g729a is the highest priority). I am just looking for which direction to go from here or if I misunderstand the nature of faxing and kamailio. Thank you in advance, Temilolu Fayomi

3 3

Constant crashes across versions
by Jon Bonilla (Manwe) 17 Feb '25

17 Feb '25

Hi all I have a setup of several proxies behind a load balancer and all of them have several coredumps every day. I've tried versions 5.3, 5.5 and 5.8 and all of them crash I didn't have dbgsym packages installed but now I've built a 5.8.4 version in one of them and can gdb the coredumps. Can't see anything particular and I'm wondering if I'm doing anything wrong. I'm descompressing the coredump with lz4cat. Sometimes I see that the system generates 3 coredumps at the same time. I've tried running gdb in one of them and exec "bt full" I usually see "can't access memory" in some of them but inb others I don't see anything relevant. I'm attaching one coredump. I don't even know if I'm doing it properly. Could you please guide me to how to debug what's going on? thanks

2 4

Info: sipexer v1.2.0 released
by Daniel-Constantin Mierla 11 Feb '25

11 Feb '25

Hello, a short note to announce that that sipexer v1.2.0 was released: - https://github.com/miconda/sipexer/releases/tag/v1.2.0 It is a modern and flexible SIP testing cli tool that can be used to send SIP signalling messages over UDP/TCP/TLS/WebSocket. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

DNS Unlinked Warnings
by John Larsen 10 Feb '25

10 Feb '25

Hi Everyone, We recently attempted an upgrade from kamailio 5.5.7 to 5.7.6. We immediately started to receive a log of warning logs similar to `dns_hash_put_shm_unsafe(): unlinked item 0x7f08799dcd90` The code shows that this warning log was added to the DNS cache in september 2023 - but its unclear what it means to have an unlinked item exactly? Is anyone able to shed any light on how DNS entries might become unlinked, and what the implications of it are? thanks John Larsen John Larsen Tech Lead EJohn.Larsen(a)symbio.global W symbio.global This communication is intended only for the person to whom it is addressed and may contain confidential material. If you received this communication in error, please inform the sender immediately and delete all copies. Please think of the environment before printing this email.

2 1

switch between "sips:" and "sip:" schema
by James Lipski 10 Feb '25

10 Feb '25

Hello, I have a kamailio installation where it's basically doing transport protocol translation. To go into more detail, I have a UA communicating over TLS towards kamailio/ and kamailio forwards the request to a freeswitch installation via UDP, so call-flow is as follows: UA <-- (TLS) --> Kamailio <-- (UDP) --> Freeswitch For the most part, this does work/ it's only when I use a UA that uses "sips:" as the schema instead of "sip:" where issues occur -- in my current topology, freeswitch has some weird behavior where it doesn't disconnect the call properly. At least based on my testing, I believe the issue is relating to the schema -- as the UA in question does have the ability to switch between schemas/ when using "sip:" instead of "sips:" over TLS, no issues with the same call-flow. In the event that I do come across a UA that doesn't have that ability, I was wondering if kamailio has the ability to switch schemas when it sends traffic over the UDP connection. I'm able to replace most aspects of the packet with "sip:" however the only header which contains the "sips:" schema is the contact header. With this alone, it propagates to the B-leg side (UDP side) of the call; and will cause freeswitch to not disconnect calls properly. I'm using the topos module to obfuscate my topology, not sure if that matters. -------- For example, on the A-leg side of the call, kamailio receives this: INVITE sips:12125551000@dev-sip.server.com:5061 SIP/2.0 Via: SIP/2.0/TLS 172.16.1.194:5061;branch=z9hG4bK236557042;rport;alias From: <sips:100000000@dev-sip.server.com>;tag=444048970 To: <sips:12125551000@dev-sip.server.com> Call-ID: 1326419916-5061-4(a)BHC.BG.B.BJE CSeq: 21 INVITE Contact: <sips:100000000@172.16.1.194:5061;transport=tls> Proxy-Authorization: Digest username="100000000", realm="dev-sip.server.com", nonce="Z6Ig0WeiH6Vdxtvej0I3XGCTUAEfh+0/", [uri="sips:12125551000@dev-sip.server.com](mailto:uri=)", response="43c1487d077db36a70fffdd1e25b3b52", algorithm=MD5 Max-Forwards: 70 User-Agent: Grandstream HT812 1.0.57.1 Supported: replaces, path, timer, eventlist Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Type: application/sdp Accept: application/sdp, application/dtmf-relay Content-Length: 1034 v=0 o=100000000 8000 8000 IN IP4 172.16.1.194 s=SIP Call c=IN IP4 172.16.1.194 t=0 0 m=audio 5004 RTP/SAVP 0 101 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=crypto:1 AEAD_AES_256_GCM inline:UlX3PAjNBP/aQwtwyf5ymsfJciB+VdFxMElO5zLVooUqmcEzZ8YyQQk9stI=|2^32 ------------------------------------------------------ On the B-leg side of the call, kamailio forwards the following to freeswitch: INVITE sip:12125551000@fs.server.com SIP/2.0 Via: SIP/2.0/UDP 10.64.52.113:5080;branch=z9hG4bK1552.89ec9666294034a5611f908f2a6a427e.0;i=f From: "Test" <sip:16461234567@dev-sip.server.com>;tag=444048970 To: <sip:12125551000@fs.server.com> Call-ID: 1326419916-5061-4(a)BHC.BG.B.BJE CSeq: 21 INVITE Max-Forwards: 15 Supported: replaces, path, timer, eventlist Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Type: application/sdp Accept: application/sdp, application/dtmf-relay Content-Length: 316 Contact: <sips:btpsh-67a21ca2-2dbe86-1@10.64.52.113:5080> v=0 o=100000000 8000 8000 IN IP4 10.64.52.113 s=SIP Call c=IN IP4 10.64.52.113 t=0 0 m=audio 13060 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=sendrecv a=ptime:20 -------------------------------------------------- As with the above, I was wondering if there is a way within kamailio to switch schemas on the b-leg side of this call example; specifically is there a way to update the contact header so it doesn't use the "sips:" schema when it traverses the UDP connection. Thank you for you time.

4 5

Auth_ephemeral module setup
by Anoop L 04 Feb '25

04 Feb '25

Hi, I'm trying to understand and setup Auth_ephemeral for authentication. My goal is to authenticate users dynamically using an web service for that I bumped into auth_ephemeral module. In the module how is a request made to the web service? Are username and password fetched from Pseudo-Variables variable? Is this module to be worked with xhttp module for http requests? Any help is much appreciated.

1 0

Auth_ephemeral Module Setup
by anoop96115＠outlook.com 04 Feb '25

04 Feb '25

Hi, I'm trying to understand and setup Auth_ephemeral for authentication. My goal is to authenticate users dynamically using an web service for that I bumped into auth_ephemeral module. In the module how is a request made to the web service? Are username and password fetched from Pseudo-Variables variable? Is this module to be worked with xhttp module for http requests? Any help is much appreciated.

1 0

Testing Kamailio IMS Modules with IPSec as P-CSCF
by Saeed Mogharian 03 Feb '25

03 Feb '25

Hi, I’m looking for suggestions on how to test Kamailio IMS modules, specifically for the IMS registration process over IPSec when Kamailio is configured as the P-CSCF node. Are there any scripts or IMS clients available that can help with this? Thanks in advance!

2 1

Kamailio 6.0 presentation at FOSDEM 2025
by Henning Westerholt 31 Jan '25

31 Jan '25

Hello, just a quick announcement, that tomorrow afternoon will be a presentation about Kamailio 6.0 at the FOSDEM conference in Brussels, Belgium [1]. Usually all the talks in this room are streamed online as well. I am happy also to meet during the conference to chat about Kamailio or other topics, just send me a (direct) message. Best regards, Henning [1] https://fosdem.org/2025/schedule/event/fosdem-2025-5978-kamailio-6-0-develo… -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 0

Strange memory stats
by Barry Flanagan 30 Jan '25

30 Jan '25

Hi, I have a 5.8.4 runing on Bookworm that after a while reports very strange memory stats like this: shmem.fragments: '729' shmem.free_size: '18446744009887078560' shmem.max_used_size: '67043934736' shmem.real_used_size: '67043698528' shmem.total_size: '3221225472' shmem.used_size: '67034971568' The settings are: SHM_MEMORY=3072 PKG_MEMORY=256 The shmem.free_size and max_used/max_size seem quite wrong. The output of "mod.stats all shm" shows the below: - 'Module: jsonrpcs' - Total: 0 - 'Module: core' - Total: 7891296 - 'Module: rr' - Total: 0 - 'Module: dialog' - Total: 146144 - 'Module: permissions' - Total: 130672 - 'Module: auth' - Total: 0 - 'Module: topoh' - Total: 0 - 'Module: sl' - Total: 14048 - 'Module: siptrace' - Total: 79184 - 'Module: sqlops' - Total: 0 - 'Module: acc' - Total: 0 - 'Module: xlog' - Total: 0 - 'Module: dmq' - Total: 1520 - 'Module: avpops' - Total: 0 - 'Module: rtpengine' - Total: 69328 - 'Module: db_mysql' - Total: 0 - 'Module: geoip2' - Total: 32 - 'Module: pv' - Total: 0 - 'Module: registrar' - Total: 0 - 'Module: textops' - Total: 0 - 'Module: htable' - Total: 6375584 - 'Module: tsilo' - Total: 74048 - 'Module: usrloc' - Total: 554240 - 'Module: tm' - Total: 6812224 - 'Module: websocket' - Total: 2551536 - 'Module: pike' - Total: 6880 - 'Module: tls' - Total: 5462960 - 'Module: tmx' - Total: 21968 - 'Module: kex' - Total: 3536 - 'Module: cfgutils' - Total: 128 - 'Module: sipdump' - Total: 32 - 'Module: domain' - Total: 5920 - 'Module: dispatcher' - Total: 20144 Thanks! -Barry

2 8

Kamailio v6.0.0 Released - new major version is out
by Daniel-Constantin Mierla 29 Jan '25

29 Jan '25

Kamailio v6.0.0 is out – it comes with 5 new modules and important updates to the core components and existing modules. The increment of the first version number reflects several important updates, among them: multi-threaded option for UDP receiving, option for specifying a range of ports to listen to, support for expressions with variables for most of the module functions parameters, internal libraries are directly inked to the core, support to use cmake to compile and install Kamailio. You can read a bit more detailed release notes at: * https://www.kamailio.org/w/kamailio-v6.0-0-release-notes/ Many thanks to all developers and community members that made possible this release. v6.0.0 brings more flexibility and optimizations across many existing components and modules, new parameters, functions, variables and transformations. Enjoy Kamailio v6.0.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

2 2

Releasing v5.8.5
by Daniel-Constantin Mierla 29 Jan '25

29 Jan '25

Hello, I am considering to release Kamailio v5.8.5 (out of branch 5.8) on Thursday, Jan 23, 2025. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 2

MS Teams BYE routing
by Barry Flanagan 28 Jan '25

28 Jan '25

Hi all, I have a Teams gw working apart from one issue., In a call originated in Teams,. if the called party hangs up, the BYE is sent to api-du-b-euwe.pstnhub.microsoft.com:443 which does not work. This is taken from the Contact header of the ACK I presume. Here is the ACK to the 200 OK: 28/01/2025 17:08:26.560 +00:00: 52.114.75.24:53728 -> 100.100.198.241:5061 ACK sip:9000@teams.domain.com:5061;transport=tls;tps=atpsh-67990f01-8ed8-1 SIP/2.0 FROM: "Teams User" <sip:+35314375362@sip.pstnhub.microsoft.com:5061;user=phone>;tag=c29cb7a79ddf40f9ba909f3f1034a770 TO: <sip:9000@teams.domain.com:5061>;user=phone;tag=as6e287620 CSEQ: 1 ACK CALL-ID: e49f7df631ee576286ecf159e81952fe MAX-FORWARDS: 70 VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK46d28f33 CONTACT: <sip:api-du-b-euwe.pstnhub.microsoft.com:443;x-i=0781e8a1-91e6-4f6a-bc4a-73d6890827d4;x-c=e49f7df631ee576286ecf159e81952fe/d/8/703117d8337e4975a8216a54f59035c2> CONTENT-LENGTH: 0 USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2025.1.20.11 i.EUWE.7 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY ..and here is the BYE. 28/01/2025 17:08:36.119 +00:00: 100.100.198.241:5060 -> 52.123.134.13:443 BYE sip:api-du-b-euwe.pstnhub.microsoft.com:443;x-i=0781e8a1-91e6-4f6a-bc4a-73d6890827d4;x-c=e49f7df631ee576286ecf159e81952fe/d/8/703117d8337e4975a8216a54f59035c2 SIP/2.0 Record-Route: <sip:teams.domain.com:5061;transport=tls;ftag=as6e287620;lr;r2=on> Record-Route: <sip:100.100.198.241:5060;ftag=as6e287620;lr;r2=on> Via: SIP/2.0/UDP 100.100.198.241;branch=z9hG4bKc89c.0c1cf04a771c30293432e5f1f59331c8.0 Via: SIP/2.0/UDP 102.102.139.182:5060;rport=5060;branch=z9hG4bK3c42c163 Max-Forwards: 69 From: <sip:9000@teams.domain.com:5061>;user=phone;tag=as6e287620 To: "Teams User"<sip:+35314375362@sip.pstnhub.microsoft.com:5061;user=phone>;tag=c29cb7a79ddf40f9ba909f3f1034a770 Call-ID: e49f7df631ee576286ecf159e81952fe CSeq: 102 BYE Content-Length: 0 How can I get around this? Using a pretty standard WITHINDLG route. I am using topos but not manipulating the Contact header. Thanks! -Barry

4 8

RTPengine module - pause/resume recording
by Who AmI 28 Jan '25

28 Jan '25

Hi list, I have been looking at the recording daemon in RTPengine with Kamailio controlling this via rtpengine_manage() flags: "record-call=on" in the initial Invite, or 200OK based on direction. I tested and this works brilliantly for the full calls, but when looking at pause/resume the module documentation is bare and I am a bit confused. It looks like the ngcp docs and Opensips module docs (for RTPengine) describe the pause/resume as just another start/stop flag. Use case is simple, all calls are recorded, but we want the option to pause, then resume once any private or personal information exchange has completed. My question is also simple - Is this the recommended way to pause and then resume recordings or have I missed something? The Kamailio documentation doesn't explicitly say this ( https://www.kamailio.org/docs/modules/stable/modules/rtpengine.html#rtpengi…) so just looking for advice if this is the best route to go. Thanks, John.

2 2

Re: [sr-dev] Re: Branching 6.0 series
by Daniel-Constantin Mierla 28 Jan '25

28 Jan '25

Hello, On 20.01.25 08:25, Daniel-Constantin Mierla via sr-dev wrote: > Hello, > > I think we should branch it on Wednesday, Jan 22, 2025, no matter on > what stage we are with cmake support. The old-Makefiles should be kept > anyhow (as they are or in a special folder with an easy way to recover > them), because there are many bits and pieces that can be discovered > later when more users. > > Because there were no many bugs reported to the C code specific to 6.0, > we can aim releasing on January 29, 2025, with old-Makefile still to be > used for tasks that are not yet covered by cmake. shall we still aim for releasing v6.0.0 on this upcoming Wednesday, January 29, 2025? We the old-Makefiles kept, it is doable, the wiki pages needs to be created for this release series, which I can do tomorrow, as I waited to see if how it should be the recommended method for compilation/installation. If the feeling is that we should wait, then probably the target date has to be shifted somewhere in the week starting on February 10, 2025, because Fosdem follows this weekend and then some countries have a week holiday break. If no other opinions and change of decision, the release will be done on Wednesday, with content using the old-Makefiles (to reuse existing tutorials) and reference to cmake variant when it is the case. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

2 1

defining configuration variables
by Sergio Charrua 27 Jan '25

27 Jan '25

Hello, just wondering if there is any way to define 2 constants as : # sets quarantine period the URL is set, in secs, after number of HTTP_RETRIES retries #!define SOME_VAR_1 60 # sets the configuration values for HTable module parameter #!define SOME_VAR_2 "some_configration_value" + SOME_VAR_1 I couldn't find anything in docs, and made several different ways without success. Any suggestions? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

2 2

UDP worker lock investigation
by Володимир Іванець 26 Jan '25

26 Jan '25

Hello everyone! I was wondering if it is possible to get information about a packet that is being possessed by the worker without increasing log level? I have an installation with Kamailio that is configured with two interfaces. Once in a while Kamailio stops accepting requests on one of the interfaces. It works fine for requests from other one. I think that worker processes might be locked while processing some requests. Enabling debug log is not an option because the traffic is quite high and the log file will not just be enormous, some lines will be missing. It looks like syslog will skip some of the log entries. So is it possible to check what packet worker process is currently processing? Or do I need to add some log entries with lower log level to trace requests manually? Thank you!

3 4

How to access registration contact user agent string in branch route after location lookup?
by Benoit Panizzon 24 Jan '25

24 Jan '25

Hi List I have some CPE which require special handling like removing 100rel and update from the supported methods because they misbehave. Previously, I was using reg_fetch_contacts and then appending the branches manually and stacking the UA in an AVP. With the branch index this allowed me to get the AVP containing the UA to which the call was branched in the branch route and perform filtering of methods based on UA, but it was complicated. Now I use the intended function lookup_to_dset() but now I miss how to access the register contact UA from within a branch route. Is there an intended way to access that information? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 7

Use local_identity or custom data to set callerID
by matu lopi 23 Jan '25

23 Jan '25

Hi team, Is it possible to use either local_identity or custom data properties to define the CallerID during the RTCSession lifecycle? Thank you.

2 1

Issue with ACK on INVITE
by Barry Flanagan 23 Jan '25

23 Jan '25

Hi folks, Trying to hook up a new endpoint but am having an issue. Kamailio is in front of an Asterisk box. They send an INVITE, we send 100, then 200 OK. However, when they send their ACK, the RURI is not set to the Contact of the 200, instead it is<number>@<proxy ip>. This causes the ACK to get routed to the proxy itself and the call fails. 82.160.190.100:5060 = Kamailio IP Port 198.201.240.242:5080 = Asterisk IP/Port 182.33.174.10:5060 = Provider endpoint The far endpoint say they cannot fix the RURI - should I be able to handle this ACK below? My understanding is the ACK's RURI should be the Contact of the 200 OK. 200 OK sent from us to the Provider (Contact shows correct URI) ========================================================= 2025/01/15 17:14:49.470634 82.160.190.100:5060 -> 182.33.174.10:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 182.33.174.10;branch=z9hG4bKefc7.ad07f2d3.0 Via: SIP/2.0/UDP 182.33.174.39:5060;received=182.33.174.39;branch=z9hG4bK5bbf9591;rport=5060 Record-Route: <sip:1800715080@82.160.190.100:5061;r2=on;lr=on;ftag=as0b42eef3;did=f2e.ade2;nat=yes> Record-Route: <sip:1800715080@82.160.190.100;r2=on;lr=on;ftag=as0b42eef3;did=f2e.ade2;nat=yes> Record-Route: <sip:182.33.174.10;lr;ftag=as0b42eef3> From: "0737965510" <sip:0737966610@182.33.174.39>;tag=as0b42eef3 To: <sip:1800715080@82.160.190.100>;tag=as4133584e Call-ID: 480dc17b3f88516f364778dc4b2528da@182.33.174.39:5060 CSeq: 102 INVITE Server: Asterisk PBX 18.9.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces *Contact: <sip:1800715080@198.201.240.242:5080>* Content-Type: application/sdp Content-Length: 314 , ACK Reply from Provider to Us (RURI points to Kamailio ip:port now =========================================================== 2025/01/15 17:14:49.478119 182.33.174.10:5060 -> 82.160.190.100:5060 *ACK sip:1800715080@82.160.190.100:5060 *SIP/2.0 Via: SIP/2.0/UDP 182.33.174.10;branch=z9hG4bKefc7.ad07f2d3.2 Via: SIP/2.0/UDP 182.33.174.39:5060;received=182.33.174.39;branch=z9hG4bK55656469;rport=5060 Route: <sip:1800715080@82.160.190.100;r2=on;lr=on;ftag=as0b42eef3;did=f2e.ade2;nat=yes>,sip:1800715080@82.160.190.100:5061;r2=on;lr=on;ftag=as0b42eef3;did=f2e.ade2;nat=yes> Max-Forwards: 69 From: "0737965510" <sip:0737966610@182.33.174.39>;tag=as0b42eef3 To: <sip:1800715080@82.160.190.100>;tag=as4133584e Contact: <sip:0737965510@182.33.174.39:5060> Call-ID: 480dc17b3f88516f364778dc4b2528da@182.33.174.39:5060 CSeq: 102 ACK Thanks -Barry

5 5

Kamailio v5.8.5 Released
by Daniel-Constantin Mierla 23 Jan '25

23 Jan '25

Hello, Kamailio SIP Server v5.8.5 stable release is out. This is a maintenance release of the latest stable branch, 5.8, that includes fixes since the release of v5.8.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.8.x. Deployments running previous v5.8.x versions are strongly recommended to be upgraded to v5.8.5. For more details about version 5.8.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2025/01/kamailio-v5-8-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

Getting headers from xhttp/websocket
by Barry Flanagan 23 Jan '25

23 Jan '25

Hi, I need to be able to pull in a header provided by a webrtc endpoint so I can use it in my request_route. I understand that I will need to use shm/htable to make it visible but I am unable to get the xhttp header using $header(x-p-push), or any header by name. In my event_route[xhttp:request] I have the following: if ($hdr(Upgrade) =~ "websocket" && $hdr(Connection) =~ "Upgrade" && $rm =~ "GET") { .... xlog("L_INFO", "BF x-p-push header is $hdr(x-p-push) Contact is $hdr(Contact)\n"); } The log shows both x-p-push and Contact header as null. sipdump shows the headers present in the request. Am I missing something? Running Kamailio 5.8.4 Thanks -Barry

3 3

Development is open for future release of v6.1.x series
by Daniel-Constantin Mierla 22 Jan '25

22 Jan '25

Hello, the branch 6.0 was created, therefore the master branch is open for adding new features, to be part of future release series v6.1.x. Any bug fix committed to master that applies to 6.0.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 6.0 or 5.8. Expect that v6.0.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v6.1.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime during the last part of 2025 or the beginning of 2026. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 0

Branch 6.0 has been created
by Daniel-Constantin Mierla 22 Jan '25

22 Jan '25

Hello, the branch 6.0 has been created, to be used for releasing v6.0.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-6.0 cd kamailio-6.0 git checkout -b 6.0 origin/6.0 Pushing commits in this branch: git push origin 6.0:6.0 Note that 6.0 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 6.0 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 6.0 will be out, respectively Kamailio v6.0.0. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

Not able to get the $TV(un) inside xhttp module
by kaseenadh111＠gmail.com 22 Jan '25

22 Jan '25

Hi, I am running Kamailio 5.7.* RHEL I need to log the latency of each XHTTP request (milli or microseconds precision) so I tried using $TV(un) which always gives a 0 value. Can we access $TV(un) under XHTTP routes? event_route[xhttp:request] { $var(tv_http_req_start_time) = $TV(un); xlog("L_INFO", "$$var(tv_http_req_start_time)= $var(tv_http_req_start_time) and actual $$TV(un)= $TV(un)"); .... } Output: Jan 22 16:18:20 VM-123************ kamailio[346535]: INFO: <script>: $var(tv_http_req_start_time)= 0 and actual $TV(un)= 0 $TS - I have tried this, it gives the Unix in seconds precision but I want milliseconds precision. Thanks Kasee

1 0

Re: [sr-dev] Re: Branching 6.0 series
by Daniel-Constantin Mierla 22 Jan '25

22 Jan '25

Hello, later today, in a few hours, I am going to create the branch 6.0. More details will be provided once it has been created. Cheers, Daniel On 20.01.25 08:25, Daniel-Constantin Mierla via sr-dev wrote: > Hello, > > I think we should branch it on Wednesday, Jan 22, 2025, no matter on > what stage we are with cmake support. The old-Makefiles should be kept > anyhow (as they are or in a special folder with an easy way to recover > them), because there are many bits and pieces that can be discovered > later when more users. > > Because there were no many bugs reported to the C code specific to 6.0, > we can aim releasing on January 29, 2025, with old-Makefile still to be > used for tasks that are not yet covered by cmake. > > Cheers, > Daniel > > On 15.01.25 11:16, Henning Westerholt via sr-dev wrote: >> Hello, >> >> yes, Xenofon is also waiting for a final reply from Sergey for the RPM packaging if now all is fine (was discussed as part of PR #4085). >> >> Cheers, >> >> Henning >> >>> -----Original Message----- >>> From: Victor Seva via sr-dev <sr-dev(a)lists.kamailio.org> >>> Sent: Mittwoch, 15. Januar 2025 10:59 >>> To: sr-dev(a)lists.kamailio.org >>> Cc: Victor Seva <linuxmaniac(a)torreviejawireless.org> >>> Subject: [sr-dev] Re: Branching 6.0 series >>> >>> Hi, >>> >>> please postpone. I didn't have time finalize the test of cmake builds on debian >>> packaging yet. >>> >>> On 15/1/25 7:18, Daniel-Constantin Mierla via sr-dev wrote: >>>> Hello, >>>> >>>> creating git branch 6.0 was planned for today and I wonder if it shall >>>> be done latter during the evening or it would be preferred to be >>>> postponed for two days or so, till end of the week/Friday, as I >>>> noticed yesterday some new work being done to cmake files for FreeBSD >>>> and maybe new commits are still coming. >>>> >>>> Of course, there is also the option to create the branch and then the >>>> new commits backported, but maybe postponing makes everything more >>>> convenient. >>>> >>>> In short, if anyone feels that postponing a bit creating the branch >>>> 6.0 simplifies their current work, let us know. If nobody ask for >>>> postponing, the branch will be created later towards the end of today. >>>> >>>> Cheers, >>>> Daniel >>> -- >>> ----------------------------------------------------------------- >>> | ⢀⣴⠾⠻⢶⣦⠀ Victor Seva | >>> | ⣾⠁⢠⠒⠀⣿⡁ linuxmaniac(a)torreviejawireless.org | >>> | ⢿⡄⠘⠷⠚⠋⠀PGP: 8F19 CADC D42A 42D4 5563 730C 51A0 9B18 CF5A >>> 5068 | >>> | ⠈⠳⣄⠀⠀⠀ Debian Developer | >>> ----------------------------------------------------------------- >> _______________________________________________ >> Kamailio - Development Mailing List -- sr-dev(a)lists.kamailio.org >> To unsubscribe send an email to sr-dev-leave(a)lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to the sender! > > -- > Daniel-Constantin Mierla (@ asipto.com) > twitter.com/miconda -- linkedin.com/in/miconda > Kamailio Consultancy, Training and Development Services -- asipto.com > > _______________________________________________ > Kamailio - Development Mailing List -- sr-dev(a)lists.kamailio.org > To unsubscribe send an email to sr-dev-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the sender! -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 1

Multi-line Via: rport added incorrectly
by James Browne 22 Jan '25

22 Jan '25

Hi I see that when kamailio adds rport to the Via header field of a request that has two Via values on the same line (comma-separated, of course), it adds the rport (and received) to the wrong value. I have this test kamailio.cfg for demonstration. children=1 loadmodule "sl" loadmodule "textops" loadmodule "nathelper" request_route { force_rport(); sl_send_reply(200, "OK"); } I send this OPTIONS (truncated) and get this response (truncated). The rport should be on the first Via value, not the second. OPTIONS sip:server SIP/2.0 Via: SIP/2.0/UDP 3.9.4.2:5060;branch=z9hG4bK503983089,SIP/2.0/UDP 1.3.4.1:5060;branch=z9hG4bK53805983059 From: <sip:client>;tag=LeonhardEuler To: <sip:server> SIP/2.0 200 OK Via: SIP/2.0/UDP 3.9.4.2:5060;branch=z9hG4bK503983089,SIP/2.0/UDP 1.3.4.1:5060;branch=z9hG4bK53805983059;rport=53805;received=127.0.0.1 From: <sip:client>;tag=LeonhardEuler To: <sip:server>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.49678e65 Server: kamailio (6.0.0-pre0 (x86_64/linux)) I've tested this with the latest commit (c994fb8) from kamailio. I can't think how this can be anything other than a bug. Should I log a bug report for this? James

2 4

Error when sending NOTIFYs to disconnected websocket clients
by Flavio Grossi 20 Jan '25

20 Jan '25

Hi, i have some SIP websocket clients (built using the SIP.js library) SUBSCRIBEd to other clients via kamailio v5.8.2. If one of the watchers suddenly disappears (e.g. the web page is reloaded), another connection is made and a new watcher appears in kamailio without the old one disappearing. For example: # kamctl rpc presence.watcher_list basic sip:1001@example.voismart.com { "jsonrpc": "2.0", "result": [ { "pres_uri": "sip:1001@example.com", "to_user": "1001", "watcher_user": "1000", "contact": "sip:1000@mfp0h2dhhmq2.invalid;transport=ws;alias=192.168.56.10~34166~5", "callid": "1o9b499kj6l65if0p30t", "user_agent": "sip.js/1.12.1", "expires": 1736422494, ... }, { "pres_uri": "sip:1001@example.com", "to_user": "1001", "watcher_user": "1000", "contact": "sip:1000@0j7qoabnv827.invalid;transport=ws;alias=192.168.56.10~34156~5", "callid": "8mjhrqifgm39up9t2qq3", "user_agent": "sip.js/1.12.1", "expires": 1736422492, ... } ], "id": 11753 } you can see the duplicated watcher in which the old connection is now invalid because the websocket client disappeared. In this situation, issuing a pres_refresh_watchers() call will fail to send any notify (even to the valid connection) because of this error: WARNING: <core> [core/msg_translator.c:3007]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found ERROR: tm [t_msgbuilder.c:1423]: assemble_via(): via building failed ERROR: tm [t_msgbuilder.c:1614]: build_uac_req(): error while assembling Via ERROR: tm [uac.c:552]: t_uac_prepare(): Error while building message ERROR: presence [notify.c:1734]: send_notify_request(): in function tm t_request_within() ERROR: presence [notify.c:1829]: notify(): sending Notify not successful ERROR: presence [notify.c:1585]: query_db_notify(): Could not send notify for [event]=dialog ERROR: presence [presence.c:739]: pres_refresh_watchers(): sending Notify requests in which the building of the notify message fails because it cannot find a valid connection when building the via header. Is this a wanted behaviour? shouldn't it just fail the sending of the single message? Is there anything i can do to fix this? Trying to reproduce the same problem with a regular tcp client, it seems that the other notifys are correctly sent and only a timeout error is sent for the single message: ERROR: <core> [core/tcp_main.c:4622]: handle_tcpconn_ev(): connect 192.168.56.10:21994 failed which i think is the correct behaviour. Related question: is it possible to remove active watchers when the connection goes down? Thanks for the help on this.

2 5

Performance issues with KEMI
by Daniel W. Graham 20 Jan '25

20 Jan '25

Testing out KEMI functionality and running into performance issues. If I exceed 150 calls per second the network receive queue grows and Kamailio is unable to keep up with requests and they begin dropping. KEMI script for testing is just doing a stateless reply to invites. Using python3s module. I've played with Kamailio child processes and memory allocations, but there is no impact. I've also attempted some buffer / memory tweaking at the OS level, again with no impact. Increasing CPU cores and even running the test on bare metal results in the same. Example of receive queue at 150 calls per second - Netid State Recv-Q Send-Q Local Address:Port udp UNCONN 337280 0 x.x.x.x:5060 Just wondering if anyone has experienced similar issues or has an example of the performance they are seeing before I continue down this path. Thanks, - dan

5 9

Need help with serial branching using: t_load_contacts(1)
by Benoît Panizzon 20 Jan '25

20 Jan '25

Hi Gang I guess, I don't completely understand who to properly perform serial branching. I did try to follow the examples from: https://www.kamailio.org/docs/modules/devel/modules/tm.html#tm.f.t_next_con… This is, stripped down, the relevant config used. modparam("tm", "contacts_avp", "tm_contacts") modparam("tm", "contact_flows_avp", "tm_contact_flows") route[LOCATION] { lookup_to_dset("location", "$var(lookupuri)"); if (!t_load_contacts(1)) { xlog("L_ERR", "$cfg(route): ######### load_contacts failed\n"); sl_send_reply("500", "Server Internal Error - Cannot load contacts"); exit; } xlog("L_INFO", "$cfg(route): Contacts loaded: $cnt($xavp(tm_contacts))\n"); => Confirms, there is more than one contact loaded. if (!t_next_contacts()) { send_reply("480", "Not registered"); } t_set_fr(5000,1500); # Set 5 second timeout for LAB testing to quickly try the next contact. t_on_branch("BR_TO_CUST"); t_on_branch_failure("BR_TO_CUST_FAILURE"); exit; } event_route[tm:branch-failure:BR_TO_CUST_FAILURE] { xlog("BRANCH FAILED $T_reply_code to $rm message\n"); t_on_branch("BR_TO_CUST"); t_on_branch_failure("BR_TO_CUST_FAILURE"); if (t_next_contact_flow()) { xlog("BRANCH FAILED, Try Next\n"); t_relay(); } else { xlog("L_INFO", "No more flows\n"); t_reply("408", "Branch Timeout"); exit; } } What happens is: INVITE is sent to the first contact, who is replying RINGING. After 5 seconds the timeout is reached and the branch-failure route engaged. Jan 17 15:01:15 dev-cpereg01 kamailio[3599432]: ERROR: <script>: BRANCH FAILED 408 to INVITE message Jan 17 15:01:15 dev-cpereg01 kamailio[3599432]: INFO: <script>: No more flows Jan 17 15:01:15 dev-cpereg01 kamailio[3599432]: CRITICAL: tm [tm.c:1554]: ki_t_reply(): w_t_reply entered in unsupported mode To my understanding, t_next_contact_flow() should have loaded the next ds, but this does not seem to happen. What am I missing? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 3

Kamailio IMS, used with IPv6?
by Valentin Christoph 16 Jan '25

16 Jan '25

Anybody experiences with Kamailio IMS modules (ims_registrar_scscf, ims_usrloc_scscf, ims_isc, ........) and the use of IPv6 addresses? Any pitfalls? DNS issues? Thanks, Christoph

2 2

Asynchttp failover
by Sergio Charrua 15 Jan '25

15 Jan '25

Hello all! just wondering if anyone knows a good way to failover with the HTTP Async module. The standard HTTP Client module (synchronous) does implement some nice functionalities for failover between URL addresses, but the HTTP Async doesn't have any failover functionality... I have implemented some functions (within kamailio.cfg) for failover upon HTTP requests, but despite it working fine, it would be better to have that functionality on the HTTP Async module, just like HTTP Client has... Any technical reason for HTTP Async module not having failover functionalities? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

2 2

Module snmpstats reporting inconsistent call success metrics on intense peaks of failed calls
by Igor Potjevlesch 15 Jan '25

15 Jan '25

Hello! We are plotting the call success rate on each of our proxies. Using the Kamailio snmpstats module, we try to obtain three counters to plot them on a graph: Total Calls Active Calls Error Calls Most of the time, everything works well, and we obtain sensible values: snmpwalk -c mycommunity -v 2c W.X.Y.Z 1.3.6.1.4.1.34352.3.1.3.1.3.2 -O n .1.3.6.1.4.1.34352.3.1.3.1.3.2.1.0 = Gauge32: 309 -> Total Calls .1.3.6.1.4.1.34352.3.1.3.1.3.2.2.0 = Gauge32: 95 -> Active Calls .1.3.6.1.4.1.34352.3.1.3.1.3.2.3.0 = Gauge32: 214 -> Error calls However, when our proxies are facing intense peaks of failed calls in a short time span, sometimes, the "Error Calls" counter returns a value higher than "Total Calls". As a result, "Active Calls" suddenly reaches a value close to the maximum of a Gauge32 (because T o t a l C a l l s − E r r o r C a l l s < 0 ). snmpwalk -c mycommunity -v 2c W.X.Y.Z 1.3.6.1.4.1.34352.3.1.3.1.3.2 -O n .1.3.6.1.4.1.34352.3.1.3.1.3.2.1.0 = Gauge32: 153 -> Total Calls .1.3.6.1.4.1.34352.3.1.3.1.3.2.2.0 = Gauge32: 4294967226 -> Active Calls .1.3.6.1.4.1.34352.3.1.3.1.3.2.3.0 = Gauge32: 223 -> Error calls As a result, our graphs make no more sense. We are currently running kamailio 5.6.4. Any idea if it's a bug or a configuration issue? Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

3 7

Branching 6.0 series
by Daniel-Constantin Mierla 15 Jan '25

15 Jan '25

Hello, I am trying to figure out what would be the best date to branch 6.0 in the git repo. To allow a bit of time after returning from the winter holidays to tune more the cmake and packaging, I would think that January 15, 2025 could be a good choice. If nobody comes with other opinions/suggestions, then we will go for it. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 1

kamcmd tls.reload issue
by Yuriy Nasida 14 Jan '25

14 Jan '25

Hello, I am using letsencrypt cert and key and do not want to restart kamailio every 3 months to load new ones. I know that there is: kamcmd tls.reload method but it has an error for me. error: 500 - Error while fixing TLS configuration (consult server log) I am checking the logs and see: kamailio[3865480]: INFO: tls [tls_domain.c:345]: ksr_tls_fill_missing(): TLSs<default>: tls_method=3 kamailio[3865480]: INFO: tls [tls_domain.c:357]: ksr_tls_fill_missing(): TLSs<default>: certificate='/etc/kamailio/certs/my_cert.crt' kamailio[3865480]: INFO: tls [tls_domain.c:364]: ksr_tls_fill_missing(): TLSs<default>: ca_list='(null)' kamailio[3865480]: INFO: tls [tls_domain.c:371]: ksr_tls_fill_missing(): TLSs<default>: ca_path='(null)' kamailio[3865480]: INFO: tls [tls_domain.c:378]: ksr_tls_fill_missing(): TLSs<default>: crl='(null)' kamailio[3865480]: INFO: tls [tls_domain.c:382]: ksr_tls_fill_missing(): TLSs<default>: require_certificate=0 kamailio[3865480]: INFO: tls [tls_domain.c:390]: ksr_tls_fill_missing(): TLSs<default>: cipher_list='(null)' kamailio[3865480]: INFO: tls [tls_domain.c:397]: ksr_tls_fill_missing(): TLSs<default>: private_key='/etc/kamailio/certs/private.key' kamailio[3865480]: INFO: tls [tls_domain.c:401]: ksr_tls_fill_missing(): TLSs<default>: verify_certificate=0 kamailio[3865480]: INFO: tls [tls_domain.c:406]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 kamailio[3865480]: INFO: tls [tls_domain.c:410]: ksr_tls_fill_missing(): TLSs<default>: verify_client=0 kamailio[3865480]: NOTICE: tls [tls_domain.c:1168]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... kamailio[3865480]: ERROR: tls [tls_domain.c:590]: load_cert(): TLSs<default>: Unable to load certificate file '/etc/kamailio/certs/my_cert.crt' kamailio[3865480]: ERROR: tls [tls_util.h:49]: tls_err_ret(): load_cert:error:03000072:digital envelope routines::decode error (sni: unknown) kamailio[3865480]: ERROR: tls [tls_util.h:49]: tls_err_ret(): load_cert:error:0A00018F:SSL routines::ee key too small (sni: unknown) Any advice ? It's interesting that there are not any errors in case I restart kamailio. I can make TLS calls without problems. deb 12.5 version: kamailio 5.7.4 (x86_64/linux)

4 5

FOSDEM VoIP Dinner
by Torrey Searle 14 Jan '25

14 Jan '25

Hello all, As in previous years, I'm organising the VoIP dinner for FOSDEM (1 Feb @ 19:00) However unlike previous years (since the restaurant got upset about splitting the bill 30 ways). I will ask everyone to order their meal and pay in advance. (and I will pay the bill to the restaurant with my card) If you are wanting to attend the dinner please fill out the following form and follow the instructions for payment. https://form.jotform.com/250012543310033 Contact details are also in the form if you want to reach out to me with any further questions. Kind regards Torrey

5 4

ims_diameter_server not freeing shared memory
by marpett365＠gmail.com 09 Jan '25

09 Jan '25

Hi, 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. have anyone ran into this issue and found a remedy or can give some pointers how to proceed? Following functions have been used for sending requests. diameter_request([peer], appid, commandcode, message) diameter_request_async([peer], appid, commandcode, message) 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"); } Shared memory after restart kamcmd mod.stats cdp shm Module: cdp { save_peer_applications(779): 144 make_send_pipe(126): 320 dp_add_pid(92): 216 AAAAddRequestHandler(69): 40 cb_add(183): 8 cb_add(177): 32 cdp_sessions_init(178): 8 cdp_sessions_init(173): 8 cdp_sessions_init(165): 1024 cdp_sessions_init(157): 3072 cdp_sessions_init(149): 8 cdp_trans_init(67): 8 cdp_trans_init(60): 24 add_timer(150): 24 add_timer(145): 144 new_peer(77): 16 new_peer(75): 16 new_peer(72): 16 new_peer(69): 80 new_peer(66): 96 new_peer(60): 384 peer_manager_init(84): 8 peer_manager_init(83): 8 peer_manager_init(82): 8 peer_manager_init(79): 8 peer_manager_init(76): 16 worker_init(101): 16 worker_init(94): 128 worker_init(89): 32 worker_init(87): 32 worker_init(84): 8 worker_init(82): 48 timer_cdp_init(182): 8 timer_cdp_init(179): 16 diameter_peer_init_real(137): 8 diameter_peer_init_real(131): 16 diameter_peer_init_real(122): 16 diameter_peer_init_real(115): 8 diameter_peer_init_real(108): 8 diameter_peer_init_real(101): 8 diameter_peer_init_real(94): 8 new_routing_entry(88): 64 parse_dp_config(447): 16 parse_dp_config(348): 8 parse_dp_config(340): 16 parse_dp_config(333): 40 parse_dp_config(326): 144 quote_trim_dup(96): 456 new_dp_config(52): 184 Total: 7024 } Shared memory after 10 diameter requests Module: cdp { save_peer_applications(779): 144 AAACreateAVP(137): 5072 AAATranslateMessage(500): 1320 do_receive(600): 7392 make_send_pipe(126): 320 dp_add_pid(92): 216 AAAAddRequestHandler(69): 40 cb_add(183): 8 cb_add(177): 32 cdp_sessions_init(178): 8 cdp_sessions_init(173): 8 cdp_sessions_init(165): 1024 cdp_sessions_init(157): 3072 cdp_sessions_init(149): 8 cdp_trans_init(67): 8 cdp_trans_init(60): 24 add_timer(150): 24 add_timer(145): 144 new_peer(77): 16 new_peer(75): 16 new_peer(72): 16 new_peer(69): 80 new_peer(66): 96 new_peer(60): 384 peer_manager_init(84): 8 peer_manager_init(83): 8 peer_manager_init(82): 8 peer_manager_init(79): 8 peer_manager_init(76): 16 worker_init(101): 16 worker_init(94): 128 worker_init(89): 32 worker_init(87): 32 worker_init(84): 8 worker_init(82): 48 timer_cdp_init(182): 8 timer_cdp_init(179): 16 diameter_peer_init_real(137): 8 diameter_peer_init_real(131): 16 diameter_peer_init_real(122): 16 diameter_peer_init_real(115): 8 diameter_peer_init_real(108): 8 diameter_peer_init_real(101): 8 diameter_peer_init_real(94): 8 new_routing_entry(88): 64 parse_dp_config(447): 16 parse_dp_config(348): 8 parse_dp_config(340): 16 parse_dp_config(333): 40 parse_dp_config(326): 144 quote_trim_dup(96): 456 new_dp_config(52): 184 Total: 20808 } Shared memory after 170k requests do_receive(600): 131363752 AAATranslateMessage(500): 32326656 AAACreateAVP(137): 110067152 Total: 273764840 Br Martin

2 5

evapi not processing received messages
by Sergio Charrua 09 Jan '25

09 Jan '25

Hi all! I have implemented evapi module on Kamailio 5.8.4, calling a python script. Python script is listening to a socket. It receives messages (JSON) from Kamailio, makes an HTTP request somewhere, and sends the response back to Kamailio. The Python script is working fine: it connects to Kamailio, sends HTTP requests, and forwards a response back to Kamailio: I have confirmed using TCPDump that, in fact, the data is received and forwarded back. However, despite showing messages that the Python client script is correctly connected to Kamailio, the event_route[evapi:message-received] is never executed. Probably there is some detail that I am missing, but the docs and online info for evapi are very rare, and they all show very similar configuration. And as I wrote, I have confirmed using TCPDump that the data is received from Python client script to Kamailio node. What am I missing? This is my Kamailio cfg: [loads modules] [sets modparams] modparam("evapi","bind_addr","10.20.20.1:8888") debug=2 children=16 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " disable_sctp = yes force_rport = yes rundir="/tmp" request_route { if ( is_method("ACK") ) { if ( t_check_trans() ) { t_relay(); } exit; } if(is_method("OPTIONS")){ sl_reply("200", "OK"); exit; } if(is_method("CANCEL")){ sl_reply("200","OK"); sl_reply("487","Request Terminated"); exit; } route(TOEVAPI); exit; } event_route[evapi:connection-new] { xlog("LINFO","new connection from [$evapi(srcaddr):$evapi(srcport)]\n"); if($evapi(srcaddr)!="10.20.0.1") { evapi_close(); exit; } } event_route[evapi:connection-closed] { xlog("LINFO","connection closed by $evapi(srcaddr):$evapi(srcport)\n"); } event_route[evapi:message-received] { xlog("LINFO","received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); jansson_get("t-index", "$evapi(msg)", "$var(t-index)"); jansson_get("t-label", "$evapi(msg)", "$var(t-label)"); $var(evmsg) = $evapi(msg); xlog("L_INFO", "preparing to resume transaction for processing: $var(tindex) / $var(tlabel)\n"); t_continue("$var(tindex)", "$var(tlabel)", "EVAPIRESPONSE"); } route[EVAPIRESPONSE] { xlog("L_INFO", "resumed transaction for processing: $T(id_index) / $T(id_label)\n"); [do stuff] } route[TOEVAPI]{ xlog("L_INFO", "suspended transaction: $T(id_index) / $T(id_label)\n"); evapi_async_relay( [some JSON string] ); exit; } Thanks in advance! Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

3 6

Kamailio and Faxing
by Temilolu Fayomi 09 Jan '25

09 Jan '25

Hello, I am having some issues ensuring t38 faxes are being received reliably. I am currently using kamailio as an inbound sbc with freepbx as the endpoint. I understand that potentially stripping other codecs except for g711a/u makes inbound faxes reliable, but beyond that I am having trouble determining how to ensure reliable faxing. Is this something kamailio can handle (such as an error correction mode or pass through setting or module?) I would appreciate any insight as I have hit a wall when it comes to this issue. Thank you, Temi

3 3

Re: WS and rtpengine_manage
by Knserbrave 08 Jan '25

08 Jan '25

test

2 4

deb-archive.kamailio.org unreachable
by Floimair Florian 08 Jan '25

08 Jan '25

Hi! It seems that deb-archive.kamailio.org is currently down. It resolves to IP 76.9.245.162 on my system Can someone with access to that please have a look. Thank you FLORIAN FLOIMAIR Software Development - Symphony Cloud Services Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria [signature_2459749227] commend.com LG Salzburg / FN 178618z

2 2

Kamailio crash
by Mitesh Thakkar 07 Jan '25

07 Jan '25

Hi, I have recently migrated from Kamailio 5.2.5 to Kamailio 5.5.7. After a migration, the Kamailio crashed. Find the details below. Thanks in advance. Back trace: ========= Core was generated by `/usr/local/sbin/kamailio -DD -E -m 1941 -M 970 -f /etc/kamailio/kamailio.cfg --'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f8e27a2be15 in OPENSSL_cleanse () from /lib/x86_64-linux-gnu/libcrypto.so.3 (gdb) bt #0 0x00007f8e27a2be15 in OPENSSL_cleanse () from /lib/x86_64-linux-gnu/libcrypto.so.3 #1 0x00007f8e278faa8a in CRYPTO_clear_free () from /lib/x86_64-linux-gnu/libcrypto.so.3 #2 0x00007f8e27838175 in BUF_MEM_free () from /lib/x86_64-linux-gnu/libcrypto.so.3 #3 0x00007f8e27bc0c98 in SSL_free () from /lib/x86_64-linux-gnu/libssl.so.3 #4 0x00007f8e27c8cd6e in tls_h_tcpconn_clean_f (c=0x7f8db0fa1e90) at tls_server.c:701 #5 0x000055f7f42cc6e1 in _tcpconn_free (c=0x7f8db0fa1e90) at core/tcp_main.c:1541 #6 0x000055f7f42e2f3c in tcpconn_put_destroy (tcpconn=0x7f8db0fa1e90) at core/tcp_main.c:3285 #7 0x000055f7f42e8759 in handle_tcp_child (tcp_c=0x7f8e27d88078, fd_i=-1) at core/tcp_main.c:3722 #8 0x000055f7f42f506f in handle_io (fm=0x7f8e27db1578, ev=1, idx=-1) at core/tcp_main.c:4539 #9 0x000055f7f42b6e49 in io_wait_loop_epoll (h=0x55f7f45ae240 <io_h>, t=5, repeat=0) at core/io_wait.h:1070 #10 0x000055f7f42f8bc3 in tcp_main_loop () at core/tcp_main.c:4824 #11 0x000055f7f4057fc2 in main_loop () at main.c:1856 #12 0x000055f7f4062670 in main (argc=10, argv=0x7ffc6d583528) at main.c:3052 OS: Ubuntu 22.04.5 LTS \n \l # kamailio --version version: kamailio 5.5.7 (x86_64/linux) 272fdd 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: 272fdd compiled on 14:21:35 Oct 21 2024 with gcc 11.4.0 # dpkg -l |grep openssl ii openssl 3.0.2-0ubuntu1.18 amd64 Secure Sockets Layer toolkit - cryptographic utility Regards.

3 3

children monitoring
by Sergey Safarov 06 Jan '25

06 Jan '25

If TCP children are busy, Please correct me if I am wrong if the remote IP is not responding via TCP protocol, this leads to a timeout and this child is busy. If many remote endpoints are not reachable via TCP this can lead to the case when half or more children are by timeout operations. I think required to monitor how many children are busy. Is it possible to get such info using kamcmd utility, statistics module, or xprom module. Sergey

4 7

Crash on dialog_publish.
by satyaprakash ch 06 Jan '25

06 Jan '25

Hi, The kamailio version we are using is "5.7.4", We are facing a kamailio crash recently and it has generated the core-dump. Below is the backtrace for the coredump. Could you please assist with this crash. *Bachtrace:* #0 0x00007fa6b051748a in dialog_publish (state=0x7fa6b0519505 "terminated", ruri=0x7069734030783532, entity=0x7ffcdfb16510, peer=0x7ffcdfb16520, callid=0x7fa5b0527cb8, initiator=1, lifetime=10, localtag=0x0, remotetag=0x0, localtarget=0x7fa5b0527ce8, remotetarget=0x7ffcdfb16500, do_pubruri_localcheck=0, uuid=0x7fa5b0527d18) at dialog_publish.c:302 body = 0x0 uri = {s = 0x0, len = 0} publ = 0x0 size = 0 content_type = {s = 0x0, len = -1288318368} ruri_uri = {user = {s = 0x0, len = 0}, passwd = {s = 0x0, len = 0}, host = {s = 0x0, len = 0}, port = {s = 0x0, len = 0}, params = {s = 0x0, len = 0}, sip_params = {s = 0x0, len = 0}, headers = {s = 0x0, len = 0}, port_no = 0, proto = 0, type = ERROR_URI_T, flags = (unknown: 0), transport = {s = 0x0, len = 0}, ttl = {s = 0x0, len = 0}, user_param = {s = 0x0, len = 0}, maddr = {s = 0x0, len = 0}, method = {s = 0x0, len = 0}, lr = {s = 0x0, len = 0}, r2 = {s = 0x0, len = 0}, gr = {s = 0x0, len = 0}, transport_val = {s = 0x0, len = 0}, ttl_val = {s = 0x0, len = 0}, user_param_val = {s = 0x0, len = 0}, maddr_val = {s = 0x0, len = 0}, method_val = {s = 0x0, len = 0}, lr_val = {s = 0x0, len = 0}, r2_val = {s = 0x0, len = 0}, gr_val = {s = 0x0, len = 0}} __func__ = "dialog_publish" #1 0x00007fa6b0518f89 in dialog_publish_multi (state=0x7fa6b0519505 "terminated", ruris=0x7069734030783532, entity=0x7ffcdfb16510, peer=0x7ffcdfb16520, callid=0x7fa5b0527cb8, initiator=1, lifetime=10, localtag=0x0, remotetag=0x0, localtarget=0x7fa5b0527ce8, remotetarget=0x7ffcdfb16500, do_pubruri_localcheck=0, uuid=0x7fa5b0527d18) at dialog_publish.c:412 __func__ = "dialog_publish_multi" #2 0x00007fa6b0506944 in __dialog_sendpublish (dlg=0x7fa5b046a850, type=64, _params=0x7fa6b0437620 <params>) at pua_dialoginfo.c:402 tag = {s = 0x0, len = 0} uri = { s = 0x7fa5b0527d41 "sip:+1248XXXXXXX@10.XXX.X.Xm6ka0542f9v0lmjjc4npkamailio954739148rdb2847sip :XXXXXX.com:5060sip:521XXXx0;tgrp=51;trunk-context=198.X.XXX.XXX@10.XXX.XX.XX:5060padi-6761ad46-154e-1560padi\300\300\300\300", len = 29} identity_local = { s = 0x7fa5b0527d28 "sip:413XXXx0@10.XXX.X.XXsip :+1248XXXXXXXX@10.XXX.X.XXm6ka0542f9v0lmjjc4npkamailio954739148rdb2847sip :XXXXXX.com:5060sip:415XXXx0;tgrp=51;trunk-context=198.X.XXX.XXX@10.XXX.XX.XX:5060padi-6761ad46-154e-"..., len = 25} target = {s = 0x0, len = 0} dlginfo = 0x7fa5b0527c90 request = 0x7fa6b3361b58 __func__ = "__dialog_sendpublish" Thanks.

1 2

record_route() adding wrong sips URI when transport is missing (defaulting to UDP)
by Benoit Panizzon 06 Jan '25

06 Jan '25

Hi Gang A quick search via google did not reveal any useful hits. Kamailio 5.7.6 CPE (TLS) => SBC (UDP) => Registrar (UDP) => Core CPE uses a sips contact URI to register, no transport attribute! sips:315996608@172.29.255.11:5061 SBC uses Path functionality. Situation: Call to CPE I see the registrar adding this Record-Route: Record-Route: <sips:registrar-ip;lr;ftag=6159862378> The SBC is adding a r2=on Record-Route to indicate the change between UDP and TLS. The Route-Set received by the CPE then is: INVITE sips:315996608@172.29.255.11:5061 SIP/2.0 Record-Route: <sips:sbc-ip:5061;transport=tls;r2=on;lr;ftag=6159862378> Record-Route: <sips:sbc-ip;r2=on;lr;ftag=6159862378> Record-Route: <sips:registrar-ip;lr;ftag=6159862378> Record-Route: <sip:core-ip;lr;ftag=6159862378> 180 Ringing req 100rel is making it back as the Via header look right. But when the remote side is sending a PRACK, is has to follow the Routeset which if I am not mistaking, is not making it back because because the CORE does not know how to send this via TLS to the Registrar. Core logging: prepare_new_uac(): can't fwd to af 2, proto 3 (no corresponding listening socket) IMHO already the 2nd Record-Route added by the Registrar should not contain a sips: URI but a sip: URI (reflecting the transport attribute not being present, defaulting to UDP) Is this a known issue? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

Guidance Required for Kamailio Load Balancer Behavior in Attended Transfer Scenarios
by Kotappa Gandudi 03 Jan '25

03 Jan '25

Dear Kamailio Team, I hope this email finds you well. I am currently working on a project where Kamailio is being utilized as a load balancer to distribute calls across multiple FreeSWITCH instances. I am using the round-robin technique for load distribution, and it is working perfectly for regular call scenarios. However, I am encountering an issue when handling attended transfer calls. Specifically, for a normal call, Kamailio assigns one FreeSWITCH instance, but during the attended transfer call, it assigns another FreeSWITCH instance. This behavior disrupts the continuity of the call handling. My requirement is for Kamailio to use the same FreeSWITCH instance for the entire call, including any attended transfers. I believe maintaining the same FreeSWITCH instance for the entire call flow would ensure consistency and avoid potential issues. Could you please guide me on how to configure Kamailio to achieve this behavior? I would greatly appreciate any suggestions, configurations, or modules that can help resolve this issue. Thank you for your time and assistance. Looking forward to your response. Best regards, Kotappa Y Gandudi

4 4

how to call loose_route() after adding route header without using msg_apply_changes?
by Benoît Panizzon 31 Dec '24

31 Dec '24

Hi List To handle CPE which can only handle a limited number of route header (PacketCable SIP specification), I need to store and restore the route header (limited topology hiding only affecting Route Header) to present the CPE only one Route or RR header. I pass the ID of the stored route-set via RR param. So when I get a message back from the CPE is: * Take ID from RR param and pull stored route set from cache. * remove_hf("Route"); * insert_hf("Route: $avp(stored-routeset)\r\n"); * msg_apply_changes(); * loose_route(); I found loose_route() only to be able to correctly determine the next hop, if I first did apply the changes. But after adding rtpengine to the mix, I got back into the known situation that calling rtpengine (on the branch route) after calling msg_apply_changes() results in duplicate SDP. Is there a way to get loose_route() to operate on freshly added header without calling msg_apply_changes? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

8 28

Async HTTP request is sent but response is incorrectly processed
by Sergio Charrua 30 Dec '24

30 Dec '24

Hi all! still struggling with Async HTTP Client ... My current configuration is very simple: #!define HTTP_API_ROUTING_ENDPOINT_MAIN " http://MY_HTTP_REST_API:18085/Endpoint" include_file "listen.cfg" loadmodule "pv" loadmodule "tm" loadmodule "http_async_client" loadmodule "xlog" loadmodule "tmx" loadmodule "sl" loadmodule "textops" loadmodule "cfgutils" loadmodule "siputils" loadmodule "rr" loadmodule "ctl" loadmodule "jsonrpcs.so" loadmodule "jansson.so" modparam("pv", "shvset", "http_async=i:8"); modparam("http_async_client", "workers", 1); modparam("http_async_client", "connection_timeout", 500) modparam("http_async_client", "curl_verbose", 1) # for debug purpose #modparam("tm", "fr_timer", 750) #modparam("tm", "fr_inv_timer", 20000) #modparam("tm", "remap_503_500", 0) modparam("tm", "failure_reply_mode", 3) modparam("tm", "max_inv_lifetime",5000) # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ modparam("jsonrpcs", "dgram_socket", "/tmp/kamailio_rpc.sock") debug=2 children=16 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " disable_sctp = yes force_rport = yes rundir="/tmp" request_route { $avp(REQUEST_URL) = HTTP_API_ROUTING_ENDPOINT_MAIN; if ( is_method("ACK") ) { if ( t_check_trans() ) { t_relay(); } exit; } if(is_method("OPTIONS")){ sl_reply("200", "OK"); exit; } if(is_method("CANCEL")){ sl_reply("200","OK"); sl_reply("487","Request Terminated"); exit; } jansson_set("string","from" , $hdr(From) , "$var(req)"); jansson_set("string","to" , $hdr(To) , "$var(req)"); jansson_set("string","r-uri" , $ru , "$var(req)"); jansson_set("string","contact" , $hdr(Contact) , "$var(req)"); jansson_set("string","call-id" , $ci , "$var(req)"); xinfo("MAIN-ROUTE - Setting From=$hdr(From) To=$hdr(To) Contact=$hdr(Contact) ci=$ci \n"); if ( is_present_hf("Identity") ) jansson_set("string","identity" , $hdr(Identity) , "$var(req)"); if ( is_present_hf("P-Identity-Bypass") ) jansson_set("string","p-identity-bypass" , $hdr(P-Identity-Bypass) , "$var(req)"); if ( is_present_hf("P-Asserted-Identity") ) jansson_set("string","p-asserted-identity" , $hdr(P-Asserted-Identity) , "$var(req)"); if ( is_present_hf("P-STSH-UC") ) jansson_set("string","p-stsh-uc" , $hdr(P-STSH-UC) , "$var(req)"); jansson_set("string", "request-time" , $avp(requestTime), "$var(req)"); ## Create transaction before http_async_query; if (is_method("INVITE")){ t_newtran(); xinfo("MAIN-ROUTE - Sending request [$var(req)]\n"); route(HTTP_ASYNC_REQUEST); } exit; } route[HTTP_ASYNC_REQUEST] { xinfo("HTTP_ASYNC_REQUEST - Sending request [$var(req)]\n"); $http_req(all) = $null; $http_req(suspend) = 1; $http_req(timeout) = 1500; # 1 second timeout $http_req(method) = "POST"; $http_req(hdr) = "Content-Type: application/json"; $http_req(body) = $var(req); if ( !http_async_query($avp(REQUEST_URL), "HTTP_REPLY") ) { xinfo("HTTP_ASYNC_REQUEST - http_async_query $ci FAILED. Return is [$rc]\n"); }else{ send_reply("503", "Server Error"); exit; } } route[HTTP_REPLY] { xinfo("HTTP_REPLY - Xphere Response Code $http_rs - $ci\n"); if ( $http_ok && $http_rs==200) { xinfo("HTTP_REPLY - $ci reply ok\n"); jansson_xdecode($http_rb, "json"); xinfo("HTTP_REPLY - HTTP JSON Response: $http_rb \n"); if ( $xavp(json=>sip-response-code) == 300 ){ remove_hf("Contact"); append_to_reply("Contact: $xavp(json=>contact)\r\n"); ## "touch" the ruri to add the contact header for 3xx: $ru = $ru; send_reply("300", "Multiple Choice"); exit; }else{ xinfo("HTTP_REPLY - $ci Error Replied $xavp(json=>sip-response-code) - $xavp(json=>sip-response-text) \n"); send_reply("$xavp(json=>sip-response-code)","$xavp(json=>sip-response-text)"); exit; } } else { xinfo("HTTP_REPLY - HTTP Response Code $ci - $http_rs and error $http_err \n"); if (!$http_ok){ sl_reply("503", "No Connection to HTTP"); exit; }else if ($http_rs>=500){ sl_reply("503", "HTTP Processing Error"); exit; } else{ sl_reply("503", "Cannot Connect to HTTP"); exit; } } exit; } The configuration is based on Ben Kaufman's kamailio_http_async <https://github.com/whosgonna/kamailio_http_async> example, but I have extended it a bit. Currently all the requests are being sent to the HTTP REST API. I can't find queue/buffering issues... What I am experiencing is that , using SNGREP, I get this flow: 10.240.12.209:5060 10.242.17.146:5060 ----------*---------- ----------*---------- 17:33:46.689852 x INVITE (SDP) x +0.000530 x --------------------------> x 17:33:46.690382 x 100 trying -- your call is x +1.499822 x <-------------------------- x 17:33:48.190204 x 503 No Connection to HTTP x +0.000029 x <-------------------------- x 17:33:48.190233 x 500 I'm terribly sorry, se x +0.002130 x <-------------------------- x 17:33:48.192363 x ACK x +0.485836 x --------------------------> x 17:33:48.678199 x 500 I'm terribly sorry, se x +0.004881 x <<<------------------------ x 17:33:48.683080 x ACK x +0.973295 x ------------------------>>> x 17:33:49.656375 x 500 I'm terribly sorry, se x +0.004105 x <<<------------------------ x 17:33:49.660480 x ACK x +1.995420 x ------------------------>>> x 17:33:51.655900 x 500 I'm terribly sorry, se x +0.005361 x <<<-------------------------x 17:33:51.661261 x ACK x x ------------------------>>> x I suspected issues with the HTTP REST service, but when using tcpdump, I can find the Request from Kamailio and a reply back from the REST API service, so doesn't seem to be a problem on the HTTP REST service So my questions are: - why is Kamailio sending a "SIP 500 I'm terribly sorry..." error after a 503 No Connection to HTTP is sent and an "exit" command is executed? - how can I get rid of these messages? - Why Kamailio keeps sending responses back to SBC after the ACK when it is set to just "exit"? - Why is Kamailio not processing the response from HTTP REST API when it is correctly received? Logs are also weird: - I find a lot of these warnings: "Dec 29 17:38:34 ire-nprod-sip1 /usr/local/sbin/kamailio[590864]: WARNING: http_async_client [http_async_client_mod.c:529]: ah_get_status(): an async variable was read after http error, use $http_ok to check the request's status" and "Dec 29 17:38:34 ire-nprod-sip1 /usr/local/sbin/kamailio[590864]: ERROR: http_async_client [http_multi.c:621]: check_multi_info(): handle 0x7f375f786b30 returned error 7:" (I am still not using EVAPI module, that will be my next step, after the holiday season) (I suspect, however, that the REST API is not being able to handle the load in this test environment (between 400 to 600 CAPS), but that is another matter.) In attach, TCPDUMP, if anyone wishes to analyse. Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

3 5

http sync / async final tests
by Alexis Fidalgo 26 Dec '24

26 Dec '24

Just to share, and thanks for your valuable help. My conclusion after tests (on my scenario) is http backend: is a golang http server with a 250ms delay to answer, and answering back a json, running in 10 replicas inside a K8 with 4 nodes. test (from kamailio perspective): receive INVITE send 100 call the http, get the result, get a key from the result and set it as the value of Contact header send 302 receive ACK (discard on sync scenario because it’s stateless, use it in async to end transaction) Kamailio host: 1vcpu kamailio 3.8.4 bookworm running inside containerd (with podman) 16GB RAM sipp: run from the K8 nodes hosts (directly from OS) (everything is LAN connected on 2 different physical servers, hypervisor is VMWare i guess 7.0.3) using http_client (sync with stateless): 8 children -M8 -m64 no more than 60 calls/sec (15cps on each sipp instance) until sipp start to retransmit the INVITES using async_http_client: 8 children -M8 -m2048 it’s been ~36 hours now at 250cps each sipp instance with 0 errors 0 retransmission and the kamailio host is userlab@sblb1:~$ vmstat 1 procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 4 0 0 10285460 364684 5444240 0 0 0 22 36 68 0 0 100 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5284 6822 27 14 58 0 0 4 0 0 10285460 364684 5444240 0 0 0 0 5306 6752 29 15 57 0 0 3 0 0 10285460 364684 5444240 0 0 0 0 5304 6823 26 16 57 0 0 2 0 0 10285460 364684 5444240 0 0 0 12 5287 6761 26 16 57 0 0 2 0 0 10285460 364684 5444240 0 0 0 0 5337 6838 27 14 58 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5101 6724 25 17 59 0 0 3 0 0 10285460 364684 5444240 0 0 0 0 5066 6650 26 14 60 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5306 6829 23 17 59 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5219 6725 23 19 58 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5274 6770 26 13 61 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5295 6756 26 18 56 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5235 6786 22 16 62 0 0 1 0 0 10285460 364684 5444240 0 0 0 0 5315 6833 21 20 59 0 0 at least for my scenario, it worths to pay the price of the memory tradeoff. again, Ben, Alex, Sergio, all, thanks for your help. regards

1 0

help on how to get ACK
by Alexis Fidalgo 24 Dec '24

24 Dec '24

Hello all, moving just a bit aside of the http and async_http. After all the real useful and interesting thread on that topic what helped me, im facing a problem i cant deal with and need a hint at least. Scenario INVITE -> Kamailio on request_route ... if(is_method("INVITE")){ t_newtran(); http_async_query("http://nuc:8080", "HTTP_REPLY"); } … Kamailio -> 100 - Trying then route[HTTP_REPLY] { if ($http_ok) { xlog("L_INFO", "route[HTTP_REPLY]: status $http_rs\n"); xlog("L_INFO", "route[HTTP_REPLY]: body $http_rb\n"); t_reply(302,"Redirect"); } else { xlog("L_INFO", "route[HTTP_REPLY]: error $http_err)\n"); } } Kamailio -> 302 Redirect ACK -> Kamailio This last ACK, how can i read it and use it to terminate the transaction? because Kamailio keeps transmitting the 302 message 3 more times until the transaction is finished by a timer 42(44) DEBUG: tm [t_reply.c:1723]: t_retransmit_reply(): reply retransmitted. buf=0x7f4c44f9d680: SIP/2.0 3..., shmem=0x7f4c3fce7900: SIP/2.0 3 42(44) DEBUG: tm [t_reply.c:1723]: t_retransmit_reply(): reply retransmitted. buf=0x7f4c44f9d680: SIP/2.0 3..., shmem=0x7f4c3fce7900: SIP/2.0 3 42(44) DEBUG: tm [t_reply.c:1723]: t_retransmit_reply(): reply retransmitted. buf=0x7f4c44f9d680: SIP/2.0 3..., shmem=0x7f4c3fce7900: SIP/2.0 3 42(44) DEBUG: tm [timer.c:642]: wait_handler(): finished transaction: 0x7f4c3fcd35a0 (p:0x7f4c3fad85d0/n:0x7f4c3fad85d0) 42(44) DEBUG: tm [h_table.c:133]: free_cell_helper(): freeing transaction 0x7f4c3fcd35a0 from timer.c:651 in request_route i have if(is_method("ACK")){ if(!t_check_trans()){ t_release(); } exit; }

4 26

append_branch
by Alexis Fidalgo 24 Dec '24

24 Dec '24

Hello all, how can avoid to append_branch do this call to call SIP/2.0 302 Redirect Via: SIP/2.0/UDP 192.168.86.250:5060;branch=z9hG4bK-65665-5-0 From: sipp <sip:sipp@192.168.86.250:5060>;tag=65665SIPpTag005 To: 123456 <sip:123456@192.168.86.128:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-deb8da2e Call-ID: 5-65665(a)192.168.86.250 CSeq: 1 INVITE Contact: <sip:4093823670@otherdomain.com>, <sip:8888576523@otherdomain.com>, <sip:9719533197@otherdomain.com>, <sip:5302579529@otherdomain.com>, <sip:4972010218@otherdomain.com> Server: kamailio (5.8.4 (x86_64/linux)) Content-Length: 0 What i mean with “avoid”, call to call, contact should have only 1 branch, no a stack of previous. thanks

2 1

Transactions help
by Alexis Fidalgo 24 Dec '24

24 Dec '24

Hello, after the discussion regarding http and http_async, I started some labs to make a comparison and see what’s the trade off and the associated cost. Main problem (to me) is im not clear on how transactions behave. Im running some fast tests now before I start to deploy the final scenarios and 1. A new transaction is created before the http_async call (as the module example shows for http_async_query function 2. The http_async_query call is executed, receives a response and the HTTP_REPLY route for http_async_query is executed. 3. As we need to redirect the call, im adding Contact information with append_to_reply and then calling t_reply(302,”Redirect) Up to here INVITE is received, a 100 is answered and then the 302 with the expected Contact information (collected and built from the http_async_query response), problem is that the 302 is retransmitted 3 more times. So, im not even sure that im doing the correct actions to process the call this way. Is there a document/book/reference I can read to understand transactions better? By now I can not handle the call to be processed correctly (without the retransmissions) and finish the transaction the correct way. Any help, link, guide, will be appreciated. Regards.

6 17

Kamailio not receiving packets on high CPS
by Sergio Charrua 23 Dec '24

23 Dec '24

Hello! for this ST/SH project, we are using Kamailio 5.8.4 in stateless mode, making HTTP requests to a REST API (Java Spring) that will reply with a JSON object, and then Kamailio replaces the Contact header and sends a SIP 300 Multiple Choice reply to the SBC that sent the initial INVITE. Kamailio is running on a VM with 4vCPUs and 4GB RAM and 2 NICs. On NIC ens224 there is a Virtual IP managed by Keepalived. Kamailio is listening on port 5060 on ens224 and set with 32 children process (tried with 8, 16, 24 and also 64, but with this value it was a lot worst). We are doing load performance tests on our PreProd environment. With the SBC we are sending 450 to 600 CAPS to Kamailio, and what we noticed is that above 450 CAPS, and after less than 1 minute, Kamailio only replies SIP 100 to some INVITEs. We also could figure out that Kamailio is not receiving all the INVITES, despite having proved that ALL invites are sent to the server. It seems to me that, for some reason, the OS is somehow not able to deliver *all* SIP packets to Kamailio, because: - sngrep does capture all the SIP packets and shows the flows - though the flow shows SIP invite coming from SBC to Kamailio Server, there is no SIP 100 replied back to SBC, even though this is the 1st thing kamailio does, so, for me, Kamailio did not received the SIP Invite - picking a call with reinvites, which after some seconds, SBC cancels, if I copy the Call-ID value and grep on kamailio's logs, I just do not find any content! I have read some "network tuning" articles, including Linux Tune Network Stack (Buffers Size) To Increase Networking Performance - nixCraft <https://www.cyberciti.biz/faq/linux-tcp-tuning/> and Tuning Kamailio for high throughput and performance | Evariste Systems Blog <https://blog.evaristesys.com/2016/02/15/tuning-kamailio-for-high-throughput…> and when running the following command I get: $ ss -4 -n -l | grep 5060 udp UNCONN 0 0 10.242.17.125:5060 0.0.0.0:* udp UNCONN 324224 0 10.242.17.146:5060 0.0.0.0:* According to the article, the 3rd column should be as near 0 as possible, ideally 0. While I am waiting for some sysadmin with root permissions to be available and modify some of the network parameters on this VM, I wonder if anyone has some tips to share on how to solve this behaviour. I'm not sure, either, what parameters to change or if they should be changed! The goal is to have a minimum 750 CAPS. Lastly, some parts of the code: Kamailio.cfg: > ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR > debug=1 > log_stderror=no > rundir="/tmp" > memdbg=5 > memlog=5 > log_facility=LOG_LOCAL0 > # configure the prefix for all log messages > log_prefix_mode = 1 > log_prefix="{$mt $hdr(CSeq) $ci} " > /* number of SIP routing processes */ > children=32 # ------------- ALREADY TRIED WITH 8,16,24... no results..... > /* uncomment the next line to disable TCP (default on) */ > disable_tcp=no > /* uncomment the next line to disable the auto discovery of local aliases > * based on reverse DNS on IPs (default on) */ > # auto_aliases=no > /* add local domain aliases */ > # alias="sip.mydomain.com" > ####### Custom Parameters ######### /* These parameters can be modified runtime via RPC interface * - see the documentation of 'cfg_rpc' module. * * Format: group.id = value 'desc' description * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */ ####### Modules Section ######## /* set paths to location of modules */ loadmodule "db_mysql.so" loadmodule "db_cluster.so" loadmodule "http_client.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "jansson.so" loadmodule "snmpstats.so" loadmodule "file_out.so" loadmodule "ctl.so" loadmodule "permissions.so" loadmodule "xhttp.so" loadmodule "xhttp_rpc.so" ####### Other Args and Env Vars ######### /* listen addresses */ include_file "listen.cfg" include_file "db_conn.cfg" # ----------------- setting module-specific parameters -------------- # --- DB Cluster params --- # minimum requirement is to have DBURL1 defined #!ifdef DBURL1 modparam("db_cluster", "connection" , DBURL1) #!endif #!ifdef DBURL2 modparam("db_cluster", "connection" , DBURL2) #!endif #!ifdef DBURL3 modparam("db_cluster", "connection" , DBURL3) #!endif #!ifdef DBURL4 modparam("db_cluster", "connection" , DBURL4) #!endif #!ifdef DBURL5 modparam("db_cluster", "connection" , DBURL5) #!endif modparam("db_cluster", "cluster", DBCLUSTER) # --- Permissions params --- modparam("permissions", "db_url", "cluster://k1") modparam("permissions", "db_mode", 1) #modparam("permissions", "reload_delta", 30) # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ modparam("jsonrpcs", "dgram_socket", "/tmp/kamailio_rpc.sock") modparam("jsonrpcs", "transport", 0) # ----- ctl params ----- /* set the path to RPC unix socket control file */ modparam("ctl", "binrpc", "unix:/tmp/kamailio_ctl") # ----- http_async_client params ----- modparam("http_client", "query_result", 0) modparam("http_client", "keep_connections", 0) modparam("http_client", "connection_timeout",2) modparam("http_client", "timeout_mode",2) modparam("http_client", "config_file", "/usr/local/etc/kamailio/http_client.cfg") # ---- SNMP Stats params ---- modparam("snmpstats", "sipEntityType", "proxyServer") modparam("snmpstats", "sipEntityType", "redirectServer") modparam("snmpstats", "sipEntityType", "other") modparam("snmpstats", "snmpgetPath", "/usr/bin/") modparam("snmpstats", "MsgQueueMinorThreshold", 20) modparam("snmpstats", "MsgQueueMajorThreshold", 100) modparam("snmpstats", "dlg_minor_threshold", 20) modparam("snmpstats", "dlg_major_threshold", 100) modparam("snmpstats", "snmpCommunity", "kamailio") # ---- File_Out params ---- modparam("file_out", "base_folder", "/data/sabire002/log/kamailio/") modparam("file_out", "file", "name=stsh_requests;interval=1440;extension=.log") modparam("file_out", "file", "name=cdr;interval=1440;extension=.log") modparam("file_out", "file", "name=http;interval=1440;extension=.log") ####### Routing Logic ######## include_file "includes/reqinit.cfg" include_file "includes/handle_options.cfg" include_file "includes/handle_cancel.cfg" include_file "includes/handle_stir_shaken_stateless.cfg" include_file "includes/handle_http_rpc.cfg" request_route { $avp(START_TIME)=$utimef(%Y-%m-%d %H:%M:%S); $avp(GROUPID) = allow_address_group($si, $sp); if ( $avp(GROUPID) == 100 || !allow_address_group($si, $sp) ) { xlog("L_INFO", "INIT - $si:$sp is not in the allowed ACL Group ID !\n"); #sl_reply("401", "Address not allowed"); exit; }; if (is_method("ACK") ) { #&& t_check_trans() ){ exit; } if (is_method("INVITE")) { file_out("cdr","$rm|$ft|$tt|$ci|$rs|$rr|$Ts|$avp(START_TIME)|$fU|$fd|$si|$tU|$rU|$rd|$utimef(%Y-%m-%d %H:%M:%S)"); send_reply("100","Trying"); } route(HANDLE_OPTIONS); route(REQINIT); xlog("L_INFO"," ********** Route START ***********"); # log the basic info regarding this call xlog("L_INFO","=================================================== \n"); xlog("L_INFO","New SIP message $rm with call-ID $ci received $pr request $rm $ou source $si:$sp from $fu to $tu \n"); xlog("L_INFO","=================================================== \n"); route(HANDLE_STIRSHAKEN); route(HANDLE_CANCEL); if (method == "INVITE"){ route(RELAY); } } route[RELAY] { # Sends a 300 Multiple Choices back to the proxy that requested the routing lookup xlog("L_INFO","RELAY - send reply \n"); file_out("cdr","RELAY|$ft|$tt|$ci|$rs|$rr|$Ts|$avp(START_TIME)|$fU|$fd|$si|$tU|$rU|$rd|$utimef(%Y-%m-%d %H:%M:%S)"); send_reply("300", "Multiple Choices"); exit; } As for the HANDLE_STIRSHAKEN route, where the main process is: route[HANDLE_STIRSHAKEN] { if (!is_method("INVITE")) { return; } $xavp(requestTime) = $utimef(%s); $var(post) = $null; // resets and makes sure the $var(post) variable is null before usage [.... get some header values ...] $var(res) = http_connect("api1", "/stsh", "application/json", "$var(post)", "$var(result)"); jansson_xdecode($var(result), "json"); if ( $xavp(json=>sip-response-code) == 300 ) { remove_hf("Contact"); append_to_reply("Contact: $xavp(json=>contact)\r\n"); } else { # add error message to reply sl_reply("$xavp(json=>sip-response-code)","$xavp(json=>sip-response-text)"); exit; } } Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

8 73

How to use @via[idx] ?
by Benoit Panizzon 23 Dec '24

23 Dec '24

Hi https://www.kamailio.org/wikidocs/cookbooks/5.7.x/pseudovariables/#selname-… https://www.kamailio.org/wikidocs/cookbooks/5.7.x/selects/#viaihost I'm trying to list all via hosts: $var(dooh) = @via[1].host; xlog("L_INFO","******** VIA HOST 1: $var(dooh) \n"); This above works as expected I get the 2nd entry. $var(i) = 0; while ($var(i) < $hflc(Via)) { $var(dooh) = @via[$var(i)].host; xlog("L_INFO","******** VIA HOST: $var(dooh) \n"); $var(i) = $var(i) + 1; } This fails with syntax error. How do I specify the index of the via header I want to extract the host from? I also attempted $sel(via[$var(i)].host) or via[$var(i)] or $sel(hfl(via[$var(i)])).host but I found no variant not throwing an error. PS: Is there maybe another nice function to figure out if we have already seen (and how many times we have) this same message? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 5

KAMI python3 and python3s not working / reloading
by trle.fuad＠gmail.com 20 Dec '24

20 Dec '24

Hello, I've started testing/learning KEMI and decide to use python3(s). I'm using default config with kamailio-basic-kemi-python3s.py (just deleted a couple of routes for simplicity). First thing I noticed is that reloading is not working. I've changed simple log line and did kamcmd app_python3s.reload. I'm compiling from source (inside Docker container, Debian bookworm as base), and have noticed it stopped working after thees commits for python3s: 62b4ee4a0d0b62b35c8bdf67e5daf9cbe9a28499 app_python3s: refactor GIL and thread state handling c81b2b3383c5900aba83672da024c812d8e6d89d app_python3s: initial support for free-threading Python And for python3 0ffe157bc13e7759ae1cee63a584fad4ac9eb38f app_python3: refactor GIL and thread state handling Am I missing some new parameter for module or compile flag? What I've noticed it's not only that it not reload, it also does not go through complete config file. While reloading, I see marking for reload. But nothing after that: 22(774) DEBUG: ctl [../../core/io_wait.h:368]: io_watch_add(): processing io_watch_add(0x748d1dfb83c0, 11, 3, 0x5f0adde454d0) - fd_no=1 22(774) DEBUG: ctl [io_listener.c:438]: handle_new_connect(): new connection (1) on /var/run/kamailio//kamailio_ctl 22(774) DEBUG: ctl [io_listener.c:499]: handle_stream_read(): bytes read: 29 22(774) INFO: app_python3s [apy3s_kemi.c:868]: app_python3s_rpc_reload(): marking for reload Python script file: /etc/kamailio/kamailio-basic-kemi-python3s.py (0 => 1) 22(774) DEBUG: ctl [io_listener.c:520]: handle_stream_read(): bytes processed: 29 22(774) DEBUG: ctl [io_listener.c:496]: handle_stream_read(): handle_stream read: eof on /var/run/kamailio//kamailio_ctl 22(774) DEBUG: ctl [../../core/io_wait.h:599]: io_watch_del(): DBG: io_watch_del (0x748d1dfb83c0, 11, -1, 0x10) fd_no=2 called

1 0

nethelper module - need clarification on how to handle uri alias on location contacts.
by Benoît Panizzon 20 Dec '24

20 Dec '24

Hi Gang When a CPE behind nat registers, I have the alias added to the AOR contact. It has format ip~port~transport Let's say: bob@1.2.3.4:5060;alias=5.6.7.8~7777~1 On an invite to that CPE behind nat, the contact is retrieved from the location record and I assumed I could call handle_ruri_alias in the branch route to that CPE and this would sent the call to that ip port via transport in the alias. I observe that the port is not taken into account. The INVITE to bob is sent to ip 5.6.7.8 but to port 5060 instead of 7777 In the example config, handle_ruri_alias() is only used for in dialog requests (has_totag). Have I misunderstood how CPE behind NAT should be registered and that registration resolved? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Request for Feedback on an Installation Script for Kamailio (from Source)
by BROU STEPHANE FABIEN 19 Dec '24

19 Dec '24

Dear Kamailio Community, I hope this message finds you well. I have recently developed an install.sh script aimed at simplifying the process of installing Kamailio directly from source. My goal is to streamline the installation process while adhering to best practices for Kamailio deployment. I would greatly appreciate your feedback, suggestions, or any corrections to help improve the script’s robustness and ensure it aligns with the community’s standards. You can find the script in my GitHub repository: https://github.com/AL-CALL-LLC/KamailioBuilder.git Feel free to test it, share your thoughts, or open issues on GitHub for any recommendations or areas that need refinement. Thank you in advance for your time and valuable expertise. I am more than happy to provide further details or engage in discussions if needed. Best regards, Fabien Brou Developer

1 0

[print_dset(): no r-uri or branches] when working with async worker
by elhar.mohamed＠gmail.com 18 Dec '24

18 Dec '24

Hello, I'm getting this warning WARNING: <core> [core/dset.c:690]: print_dset(): no r-uri or branches when working with async worker. here is below the code used: request_route { if (is_method("INVITE")) { append_to_reply("Contact: <sip:+1234;myparam=test@$si:$sp>\r\n"); send_reply("302", "Moved Temporarily"); exit; } } Can you please help?

2 2

Multiple Branches and 3xx Status Codes
by Christian Berger 17 Dec '24

17 Dec '24

Hi, we have the following situation: Multiple UAs are subscribed to the proxy and get INVITEd via parallel forking. Now one of the UAs sends us a 302 status, we would like to handle this like a failure. So we'd like to CANCEL all the other branches, and forward the 302 status to the original INVITE. We have tried t_reply("302", "$T(reply_reason)") in the response, which almost solves this, however we cannot pass the required headers form the 302 response in it. BTW, could there have been a change in the default behavior of Kamailio? We think it used to "just work" in the past. Thank you very much Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

3 3

Development for v6.0.x is frozen
by Daniel-Constantin Mierla 17 Dec '24

17 Dec '24

Hello, the formal notification that the development for the next major version 6.0.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 6.0 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, new pull requests can still be done, but they will be merged after branching 6.0. Can still be done commits with documentation improvements, enhancements to related tools (e.g., kamctl, kamcmd), merging exiting pull requests at this moment, exporting missing KEMI functions and completing the functionality of the new modules added for 6.0. Once the branch 6.0 is created, new features can be pushed again to master branch as usual. From that moment, the v6.0.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 6.0 is going to be built at: * https://www.kamailio.org/wikidocs/features/new-in-6.0.x/ Upgrade guidelines will be collected at: * https://www.kamailio.org/wikidocs/install/upgrade/5.8.x-to-6.0.0/ Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.8.x to 6.0.x. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

Freezing development for 6.0.x series
by Daniel-Constantin Mierla 16 Dec '24

16 Dec '24

Hello, I propose to aim freezing the development for 6.0.x series at the end of the 16th of December 2024 (Monday). New features that one wants to get in this release series have to be pushed to git repository or pull requests made for them. Afterwards usually follows a 4-6 weeks of testing till the first release 6.0.0. Unfreezing will happen earlier, after the first weeks of testing when the 6.0 branch will be created. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 1

ims_diameter_server: $diameter_response PV is null in the event_route[diameter:response]
by Grotti, Daniel 15 Dec '24

15 Dec '24

Hi list, I'm using kamailio 5.8 and playing with the ims_diameter_server module, by sending an async diameter request and trying to catch the reponse. Following the documentation, I'm sending the request with: route[SEND_ACR] { route(PREPARE_ACR); diameter_request_async("3", "271", "$var(json_acr)"); } route[PREPARE_ACR] { # here I build the AVP list in JSON $var(json_acr) = "[{"avpCode":277,"vendorId":0,"Flags":64,"int32":0},{...},{...}]"; } event_route[diameter:response] { xlog("Reply to diameter request is: '$diameter_response'\n"); } The ACR request is successfully sent and the the server is replying with ACA. The list of AVP are properly parsed, but when I enter the event_route to print the response, I get the $diameter_response = 'null': 2024-12-11T10:52:39.192951872+00:00 stderr F 11(19) DEBUG: cdp [worker.c:374]: worker_process(): worker_process(): [2] got task Q(2/2) 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP((nil) < 0x7ff827633810 >0x7ff8276338c0);code=263,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=52; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633810 < 0x7ff8276338c0 >0x7ff827633970);code=268,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=3;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff8276338c0 < 0x7ff827633970 >0x7ff827633a20);code=264,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=37; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633970 < 0x7ff827633a20 >0x7ff8276340b0);code=296,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=33; 2024-12-11T10:52:39.193124627+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633a20 < 0x7ff8276340b0 >0x7ff827634160);code=259,flags=40; 2024-12-11T10:52:39.193124627+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff8276340b0 < 0x7ff827634160 >0x7ff827634210);code=480,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827634160 < 0x7ff827634210 >0x7ff8276342c0);code=485,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827634210 < 0x7ff8276342c0 >(nil));code=85,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193612877+00:00 stderr F 11(19) INFO: <script>: [event_route]: Reply to diameter request is: '<null>' Is there something I miss to set/configure? Thanks, Daniel Daniel Grotti Development Team Leader, Private 5G daniel.grotti(a)hpe.com<mailto:daniel.grotti@hpe.com> Hewlett Packard Enterprise HPE.com [cid:803b85f7-01fe-4c9c-a069-74d14a9ea122]

3 9

How to remove rr param on a reply?
by Benoît Panizzon 13 Dec '24

13 Dec '24

Hi Is there a way to remove an param from the top most rr header? I add a rr param towards the B CPE to store some information which is sent back on the rr header of the reply from B. So far this is what is intended and I also get this param in subsequent route headers from messages created by B and as the route header are remove towards A, this works fine. Unfortunately, in a case of a reply, the parameter is passed to A which is then sending back the param in the route header which would make it somehow complicated to figure out which side sent that parameter. I'm only interested if sent from B. So I wonder, is there a way to delete a rr param on replies to make sure I don't get it back in the ACK to the reply? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

slot hongkong terbaik
by Womkevintanuwijaya＠gmail.com 13 Dec '24

13 Dec '24

<a href="https://slothongkong.pro/">slot hongkong</a> The best information from the world's largest number one blog!

1 0

registrar / usrloc / tm => 'load balanced' serial forking?
by Benoit Panizzon 13 Dec '24

13 Dec '24

Hi List With the dispatcher module, you can use different ways of load balanced and weighted serial or parallel forking. Is there a corresponding way to achieve load balanced serial forking to a destination set loaded from registered locations? Use case: Customer with a high availability set-up has two redundant PBX registered to the same AoR. Calls can not be sent in parallel as this would generate two concurrent calls to the end device but call should be distributed evenly between the two contacts registered with that AoR. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 8

HTTP_CLIENT timeout
by Sergio Charrua 13 Dec '24

13 Dec '24

Hello all! For a STSH project, kamailio is making HTTP requests to a middleware (REST API) using HTTP_CLIENT module. I have set the parameter "timeout" to 2 second, but this increases PDD to too high levels, so I have set it to 1 second. Problem is that 1sec is also too high! The parameter only accepts integer values, so no way to set this to 0.5sec. I thought of having a way for kamailio to be aware that HTTP node #1 is down, so next request it will use HTTP node #2 instead. And once in a while, say, every 60 seconds, kamailio would check status of HTTP node #1 and, if OK, then it will switch back to HTTP node #1 and failover to node #2 when required. The HTTP_CLIENT, as far as I know, doesn't do that. So the question is: what would be the best approach to have this feature on Kamailio? i thought about using HTable and have a flag with value of the HTTP connection to use by default. At worst, only the 1st failover request would take 1 or 2 seconds to timeout....then the subsequent HTTP requests would use node #2. Any ideas? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

4 5

How to inspect/dump a stacked xavp? / How to stack two xavp on each other?
by Benoit Panizzon 10 Dec '24

10 Dec '24

Hi List I'm trying to inspect the content of the $xavp(tm_contacts) to figure out how t_load_contacts exactly behaves when called multiple times. $var(k) = 0; while ($xavp(tm_contacts[$var(k)]) != $null) { $var(out) = "nothing"; xavp_params_implode("tm_contacts[$var(k)]", "$var(out)"); xlog("L_INFO", "$cfg(route): tm_contacts idx: $var(k) => $var(out)\n"); $var(k) = $var(k) + 1; } My stack contains multiple entries. Unfortunately I struggle to access the lower entries. xavp_params_implode("tm_contacts[$var(k)]", "$var(out)"); does nothing when $var(k) > 0 What is the best way to dump a complete xavp stack? I suspect t_load_contacts does flush the complete stack. Is there a way to stack an xavp on top of another one? Something like: xavp_rm("contact_stack"); # Initialize Stack lookup("location", "sip:alice@example.com"); t_load_contacts(0); $xavp(contact_stack) = $xavp(tm_contacts); lookup("location", "sip:bob@example.com"); t_load_contacts(0); $xavp(contact_stack) = $xavp(tm_contacts); # contact_stack now contains alice + bob lookup("location", "sip:carlie@example.com"); t_load_contacts(0); # $xavp(tm_contacts) now contains only charlie. $xavp(tm_contacts) = $xavp(contact_stack); # $xavp(tm_contacts) now contains only alice, bob + charlie. t_next_contacts(); # Push contacts to destination list creating branches. t_relay(); # Invite all contacts Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

6 10

segmentation fault when assigning xavp to another xavp (trying to stack them)
by Benoit Panizzon 10 Dec '24

10 Dec '24

Hi version: kamailio 5.7.6 (x86_64/linux) on Ubuntu from the: http://deb.kamailio.org/kamailio57 repository AOR alice has 4 contacts with q=0.5 AOR bob has 1 contact with q=0.5 I can reproduce a crash with this code snipplet: xavp_rm("contact_stack"); # Make sure XAVP does not exist. lookup("location", "sip:alice@example.com"); t_load_contacts(0); # after this, $xavp(tm_contacts) has four elements $xavp(contact_stack) = $xavp(tm_contacts); # Store the four elements on my stack # Verify, $xavp(contact_stack) now has four elements, copy successfull. lookup("location", "sip:bob@example.com"); # after this, $xavp(tm_contacts) has one element $xavp(tm_contacts) = $xavp(contact_stack); # Append the four previously saved contact with the one in $xavp(tm_contacts) if (!t_next_contacts()) { xlog("L_INFO", "$cfg(route): ERROR NO CONTACTS LOADED \n"); sl_send_reply("500", "Server Internal Error - Cannot get contacts"); } # Load contacts into destination set to parallel fork to five contacts. => segmentation fault! Shall I open an issue on github or am I performing a forbidden action? I'm doing some more test to find out where exactly the crash occurs. I'm not sure if it happens when adding to tm_contacts of when calling t_next_contacts. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

uneven load distribution after gw goes down?
by David Villasmil 09 Dec '24

09 Dec '24

Hello guys, I'm seeing the dispatcher module used with ds_select_dst($avp(dsdst), "0") is distributing the calls to a failing gw, to the next available gw instead of distributing it. When a gw fails and has been marked as inactive, shouldn't it be taken out of the list and the list recomputed? is this not the case? Thanks all Regards, David Villasmil email: david.villasmil.work(a)gmail.com

2 2

Updated: Online devel meeting on matrix - 15:00 UTC, Dec 9, 2024
by Daniel-Constantin Mierla 09 Dec '24

09 Dec '24

Hello, we should consider an online devel meeting sometime soon to summarize what was done at (and still needs to be done after) devel meeting in Dusseldorf and plan a bit the targets for next major release 6.0. If considered useful, I propose Dec 9, 2024 (Monday) at 15:00UTC (16:00 Berlin/Paris/Madrid/Rome), but we can also look for other dates as well. Topics to be discussed can be added at: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Pull requests can be made by users without git access. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 2

WS and rtpengine_manage
by Knserbrave 09 Dec '24

09 Dec '24

Hi Kamailio Community, When testing rtpengine_manage and websockets, I noticed that if the rtpengine table in the database is not used, a new websocket is created for every call for a given dialog. That is, when an INVITE is received, an offer is sent to rtpengine. When the 200 OK or 18[3|0] is received, an answer is sent. However, the WS identifier often changes and as a result the request is not sent over the same websocket. This is problematic particularly when using FQDNs in the Kamailio configuration. When a load balancer is used between Kamailio and rtpengine, the answer may arrive at a different rtpengine in the cluster. After tracing through the source, I could not find a configuration parameter or set of triggers that I could manipulate to fix this. It leads me to believe it is only possible to reuse the websocket when the rtpengine table is used. Does anybody have more experience than I in this area that may be able to point me in the right direction, making load balancers for rtpengine_manage calls possible?

3 2

Potential Bug in Kamailio: Base64 Decode Transformation Not Working in Lua but Works in kamailio.cfg
by Dirk Brouwers | CM.com 28 Nov '24

28 Nov '24

Dear Kamailio Developers, I am writing to report a potential bug in Kamailio's handling of base64 decoding when using the Lua scripting interface (app_lua). It appears that base64 decoding behaves inconsistently between Lua scripts and kamailio.cfg. When using `$(var(encoded_json){s.decode.base64t})` in kamailio.cfg, where $var(encoded_json) contains the encoded base64 string: `eyJmb28iOiJiYXIifQ` it decodes to the correct `{"foo":"bar"}`. But when using the same transformation in Lua `KSR.xlog.xinfo("Decoded in Lua: ".. KSR.pv.get("$(var(encoded_json){s.decode.base64t})"))` it logs a corrupted encoded base64 string: `Decoded in Lua: ..]..#035z{b.?...#036..-....` Thank you in advance for looking into this issue. Please let me know if you need additional details or test cases. Kind regards, Dbrcm

3 4

"Intermittent Issue: Kamailio Presence Server Not Generating NOTIFY Packets"
by satyaprakash ch 27 Nov '24

27 Nov '24

Hi We have FreeSWITCH and Kamailio presence servers set up. FreeSWITCH sends XML RPC messages to the Kamailio presence servers for PUBLISH operations, and we receive 200 OK responses in return. These responses include the SIP-ETag and Expires headers. However, the Kamailio presence server is not consistently generating NOTIFY packets. This issue seems to occur randomly. Can you please suggest this for presence servers. Thank you in advance.

1 0

record_route() adds empty route header if enable_double_rr is 1
by Benoit Panizzon 26 Nov '24

26 Nov '24

Hi Gang How is record_route() determining if it needs to add two RR Header? Kamailio 5.8.4 I'm attempting to perform route header hiding by by rebuilding some of the topos functionality with perl. So towards the CPE I'm removing all existing RR header and want to replace them with one header containing an attribute which the CPE is then sending back and allows me to restore the Route header. But I came across an issue which an empty RR header being created with this (simplified) script: modparam("rr", "enable_double_rr", 1) perl_exec("hide_route"); # Stores Route-Set and sets $avp(rrattr) as id remove_hf("Record-Route"); msg_apply_changes(); loose_route(); # Required for record_route()? add_rr_param(";rr=$avp(rrattr)"); # Add Param to identify saved route set record_route(); I end up with: Record-Route: <sip:;r2=on;lr;rr=id007> Record-Route: <sip:157.161.x.x;r2=on;lr;rr=id007> The first header missing the IP address, the message being dropped by the CPE There is no transport change. If I set enable_double_rr to 0 only the 2nd RR header is created and this works as expected but I am not sure if some situations would need double RR. What causes the double RR to be created in my case? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

app_perl add/remove HF?
by Benoît Panizzon 22 Nov '24

22 Nov '24

Hi List I'm looking into the perl module. Am I right, that I can not add or remove HF from an app_perl subroutine? I would need to pass an AVP from perl to tell Kamailio what to do? Goal is an attempt to re-build part of the topos functionality in perl but only handling RR and Route Header only on one leg, not on both. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

tcp_accept_haproxy option
by Wolter Eldering 22 Nov '24

22 Nov '24

Hi, I noticed that if I enable tcp_accept_haproxy kamailio still can accept connections without the PROXY-protocol header. The documentation on the wiki has the following note: "Please note that enabling this option will reject any inbound TCP connection that does not conform to the PROXY-protocol spec." https://www.kamailio.org/wiki/cookbooks/devel/core#tcp_accept_haproxy This could be true up until a specific version of kamalio but from 5.7.4+ this limitation is seems to be removed. Enabling tcp_accept_haproxy is breaking the outbound/rr module because it con’t find the socket based on the address and port from the flow token. The flow tokens created by a REGISTER on a connection without a PROXY header can be used. Flow tokens created from a connection with PROXY-protocol header will fail with "cannot find socket from flow-token” once loose_route is invoked. loose.c:561 /* First, force the local socket */ si = find_si(&rcv->dst_ip, rcv->dst_port, rcv->proto); if(si) set_force_socket(_m, si); else { LM_INFO("cannot find socket from flow-token\n"); return -1; } I’m not sure if the address and/or port values stored in the flow token are incorrect or the problem lies in the matiching in find_is(…). Wolter

1 0

RTC DevRoom at FOSDEM 2025
by Daniel-Constantin Mierla 21 Nov '24

21 Nov '24

Hello, FOSDEM'25 will host again a RTC DevRoom during the afternoon of February 1, 2025 (Saturday) -- more details and the call for presentation can be read at: - https://lists.fosdem.org/pipermail/fosdem/2024q4/003584.html I am not sure if I can participate (chances are more towards no, than to yes), but if anyone considers to go to the event, it will be good to submit a proposal to cover a bit Kamailio as well (it doesn't have to be entirely about Kamailio). Note that FOSDEM imposes a strict deadline this time for submissions (Dec 1, 2024), thus is no much time left. Should anyone in these groups plans to submit a proposal, let us know, so the others have an idea about it. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

TM-Module, ignoring
by Christian Berger 19 Nov '24

19 Nov '24

Hi, we would like to replicate a SIP-message ("REGISTER" in our case) to a set of nodes for further asynchronous processing. The message is already processed on the local Kamailio. We thought about using the tm-module in conjunction with the dispatcher module so we can reliably forward the message. This seems to work, however we get a new problem: Kamailio forwards the response it gets from those nodes. When we drop the response in the reply_route, it gets dropped before TM can see it. When we drop the response in the on_reply_route, it still will be forwarded. (adding or removing a header here works, however) $du is set to $null. Is there any clean way to suppress that response being forwarded back to the original requester? Best regards Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

2 2

Not able to use SRTP - from client to proxy
by Sajid Khan 18 Nov '24

18 Nov '24

Im using the module RTPengine. im having issues when ever i try to do a call using SRTP im using microsip i have checked the SDP everything ok. But when ever i place the call it gets rejected. if i disable SRTP then the calls work if (!rtpengine_offer("replace-origin replace-session-connection ICE=force RTP/SAVP RTP/AVP")) { I only need to encrypt client -> proxy from proxy -> asterisk should be plain rtp i hope someone can help me out thank you. The log in rtpengine shows this [1731055305.417896] ERR: [2a721ebf2c73414ab8e739d7bde912f9//1 port 14124]: [srtp] SRTP output wanted, but no crypto suite was negotiated

4 4

Kamailio 5.5.7 crash
by Mitesh Thakkar 18 Nov '24

18 Nov '24

Hi, I have recently migrated from Kamailio 5.2.5 to Kamailio 5.5.7. After a migration, the Kamailio crashed. Also, there were a lot of errors and warnings. Can someone help me to understand why this happened and what could be the solution? Logs (upside down): 18(397) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 2(381) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 30(409) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 8(387) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) OS: Ubuntu 22.04.5 LTS \n \l # kamailio --version version: kamailio 5.5.7 (x86_64/linux) 272fdd 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: 272fdd compiled on 14:21:35 Oct 21 2024 with gcc 11.4.0 # dpkg -l |grep openssl ii openssl 3.0.2-0ubuntu1.18 amd64 Secure Sockets Layer toolkit - cryptographic utility Regards, Miteshkumar Thakkar

2 1

Pua PUBLISH method over xmlrpc/jsonrpc
by dries＠degendt.com 18 Nov '24

18 Nov '24

Hi all I've installed a (pretty old) presence_dfks module that allows setting the presence using the following command: kamctl fifo pua_publish sip:1000@10.10.99.254 3600 as-feature-event application/x-as-feature-event+xml . . . "<?xml version='1.0' encoding='ISO-8859-1'?><ForwardingEvent><device><notKnown/></device><forwardingType>forwardImmediate</forwardingType><forwardStatus>true</forwardStatus><forwardTo>1234</forwardTo></ForwardingEvent>" The "pua_mi" module was however removed in Kamailio and jsonrpcs/xmlrpcs are supposed to be an alternative. I've tried both the following calls, but neither does recognize the pua_publish/pua.publish as a valid method. Attempt with jsonrpc: curl -H "Content-Type: application/json" -X POST -d '{"jsonrpc": "2.0", "method": "pua.publish", "params": [""], "id":1}' https://sbctest.tel.redacted.xx:5061/RPC/ ERROR: jsonrpcs [jsonrpcs_mod.c:1422]: ki_jsonrpcs_dispatch(): method callback not found [pua.publish] Attempt with xmlrpc: curl -H "Content-Type: text/xml" -X POST -d '<?xml version="1.0" ?><methodCall><methodName>pua_publish</methodName><params><param><value><string>sip:jh@sbctest.tel.redacted.xx</string></value></param><param><value><string>7776000</string></value></param><param><value><string>as-feature-event</string></value></param><param><value><string>application/as-feature-event</string></value></param><param><value><string>.</string></value></param><param><value><string>a.1481534683.13958.6.7</string></value></param><param><value><string>sip:127.0.0.1:5080;transport=tcp</string></value></param><param><value><string>P-Flags: 0</string></value></param><param><value><string>Messages-Waiting: yesMessage-Account: sip:jh@sbctest.tel.redacted.xxVoice-Message: 2/0 (0/0)</string></value></param></params></methodCall>' https://sbctest.tel.redacted.xx:5061/RPC/ <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>500</int></value> </member> <member> <name>faultString</name> <value><string>Method Not Found</string></value> </member> </struct> </value> </fault> Anyone who had some luck in this matter? Best regards, Dries

3 6

SIP NOTIFY over TLS fails
by dries＠degendt.com 15 Nov '24

15 Nov '24

Hi all I've installed a custom presence_dkfs module (https://github.com/tombeard/presence_dfks) in an effort to make our Grandstream devices (connected over TLS) display a server set callforward using Broadsoft's Device Feature Key Sync. The module was installed succesfully, but it appears that the NOTIFY upon SUBSCRIBE cannot be sent over TLS. This part seems to use the default presence module however so I'm taking my chances here to ask for some advice. I have already disabled verify_certificate in tls.cfg. The "dst addr: 193.19x.x.x:0" does seem to have an incorrect port as I should expect 5061? INFO: {1 600000 SUBSCRIBE 319937814-5062-3(a)BHC.DA.GB.CD} presence [notify.c:1744]: send_notify_request(): NOTIFY sip:544460@sbctest.tel.redacted.xx via sip:544460@172.30.61.23:5062;transport=tls on behalf of sip:544460@sbctest.tel.redacted.xx for event as-feature-event : 319937814-5062-3(a)BHC.DA.GB.CD ERROR: tls [tls_server.c:1312]: tls_h_read_f(): protocol level error ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS connect:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure (sni: unknown) ERROR: tls [tls_server.c:1316]: tls_h_read_f(): src addr: 172.30.61.23:5062 ERROR: tls [tls_server.c:1319]: tls_h_read_f(): dst addr: 193.19x.x.x:0 ERROR: <core> [core/tcp_read.c:1526]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f6d55b4b360 r: 0x7f6d55b4b488 (-1) Your advice is most appreciated! Cheers, Dries

4 7

dlq_req_within() usage for 3pcc-style reinvite media setup
by Alex Balashov 14 Nov '24

14 Nov '24

Hi, I am trying to use dlg_req_within() for a 3pcc-style call setup, to set up media via a reinvite: 1. Store original SDP offer from caller in $dlg_var()s; 2. Later, after e2e ACK is processed for initial INVITE transaction, send reinvite to callee using dlg_req_within(). I call rtpengine_offer() and feed it the original SDP offer (via read_sdp_pv modparam), and take the RTPEngine-transformed SDP and feed that to dlg_req_within(): dlg_req_within("callee", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); 3. I have found that event_route[tm:local-response] does not allow me to capture the 200 OK / SDP answer to this reinvite; it is internally absorbed. However, it is possible to arm an onreply_route in event_route[tm:local-request], to receive the 200 OK: event_route[tm:local-request] { if(method == "INVITE" && has_body("application/sdp")) t_on_reply("REINVITE_REPLY"); } 4. My intent is for this reinvite reply handler to set off a reinvite to the caller side: onreply_route[REINVITE_REPLY] { if(method == "INVITE" && has_body("application/sdp") && t_check_status("200")) { ... $var(rtpengine_use_this_sdp) = $rb; rtpengine_answer("..."); dlg_req_within("caller", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); } This ensures proper relay symmetry. Otherwise, the caller will continue to send RTP to the previous upstream endpoint of the call, prior to any reinvite. However, dlg_req_within() doesn't work in this later context, even though the documentation says it can be used from ANY_ROUTE. Kamailio doesn't complain, there is no error. It just doesn't initiate a reinvite to the caller. I considered the possibility that this may be because the calling scope is that of a pending reinvite transaction to the callee, but there is no obvious way to defer that into the future. If I send it to an async task worker, the transaction scope required for dlg_req_within() to know which dialog it's operating on will be lost. Any ideas appreciated, and thank you in advance! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 2

KEMI / Python Issues
by Daniel W. Graham 14 Nov '24

14 Nov '24

Experimenting with KEMI for the first time, I ran into a few issues and hoping someone has feedback. kamailio 5.8.3 In the following python example, 'if ksr.is_method("ACK"):' should never be reached. Below is debug. if not ksr.siputils.has_totag(): ksr.info("has to tag") sys.exit() if ksr.is_method("ACK"): if ksr.tm.t_check_trans(): ksr.relay() sys.exit) else: sys.exit() ksr.sl.send_reply(404, "Not here") sys,exit() ..... DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: siputils.has_totag DEBUG: siputils [checks.c:122]: has_totag(): no totag DEBUG: app_python3s [apy3s_kemi.c:368]: sr_apy_kemi_exec_func_ex(): execution of method: is_method DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 1 DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: sl.send_reply DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 2 DEBUG: sl [sl.c:306]: send_reply(): reply in stateless mode (sl) ..... Second, here are a couple errors I have seen a few times but havent been able to identify the underlying issue, mainly hoping for more context on the meaning of 'execution of route type 1 with no name returned -1'. ERROR: app_python3s [apy3s_kemi.c:146]: apy3s_exec_func(): error exception occurred DEBUG: app_python3s [apy3s_kemi.c:230]: sr_kemi_config_engine_python(): execution of route type 1 with no name returned -1 Any input is appreciated. * dan

2 7

WG: [External] RE: Question regarding error message "failed to add new socket to the fd list"
by Floimair Florian 14 Nov '24

14 Nov '24

Thank you Henning! Here are the configured limits for Kamailio Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 31543 31543 processes Max open files 16384 16384 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 31543 31543 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us This is what I know so far: There seems to be a problem with siptrace module (going via TCP to a heplify-server on another host), but I’m not sure if this is a coincidence or the cause of the problems. I see quite a bit of these before the actual problem arises: Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: <core> [core/tcp_main.c:630]: _wbufq_add(): (591 bytes): write queue full or timeout (32498, total 43196, last write 0 s ago) Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: siptrace [../../core/forward.h:261]: msg_send_buffer(): tcp_send failed Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/tcp_main.c:4023]: handle_ser_child(): received CON_ERROR for 0x7fe054f8ae10 (id 727321), refcnt 2, flags 0x3096 At some point then all things go south and the log is flooded with these messages Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd 2244, not in [0, 482) Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/tcp_main.c:4677]: handle_tcpconn_ev(): io_watch_del(3) failed: for 0x7fe054f8ae10, fd 2244 And then ultimately the above combined with the initially mentioned Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: CRITICAL: <core> [core/tcp_main.c:4264]: handle_ser_child(): failed to add new socket to the fd list And occasionally also something like this Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/io_wait.h:373]: io_watch_add(): trying to overwrite entry 2247 watched for 5 in the hash 0x5621dc404ee0 (fd:-601539712, type:22049, data:0x5621dc23c004) with (2247, 2, 0x7fe04f85c2a0) In total these add up to roughly 3600 lines per second (!!) in the log, so it is quickly flooded with these. Florian FLOIMAIR Software Development - Symphony Cloud Services (1568) Von: Henning Westerholt <hw(a)gilawa.com> Datum: Montag, 11. November 2024 um 19:52 An: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Floimair Florian <f.floimair(a)commend.com> Betreff: [External] RE: Question regarding error message "failed to add new socket to the fd list" CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello Florian, Any other error messages before that error happens, e.g. something about the memory. Otherwise, it could be indeed a ulimit issue. First step would be to check the actual configured limits for the kamailio user. Cheers, Henning From: Floimair Florian via sr-users <sr-users(a)lists.kamailio.org> Sent: Montag, 11. November 2024 17:45 To: sr-users(a)lists.kamailio.org Cc: Floimair Florian <f.floimair(a)commend.com> Subject: [SR-Users] Question regarding error message "failed to add new socket to the fd list" Hi! We have recently had issues with one of our Production Kamailios. When those happened, the log was filled with the following message: CRITICAL: <core> [core/tcp_main.c:4528]: handle_new_connect(): failed to add new socket to the fd list Now I wonder what the best approach is to prevent this. We are using TCP/TLS only and I think this might be related to the file ulimit, but I am not sure about that. Shared memory is set to 512MB Can you give me a hint on what to look for? Thank you very much! P.S.: Sorry, I accidentally replied to a previous post of a different topic before which is totally unrelated (I think I should stop working for today 😉) FLORIAN FLOIMAIR Software Development - Symphony Cloud Services Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria [signature_2072127332] commend.com LG Salzburg / FN 178618z

2 1

Tell topos to create 'duplicate' route header from rr header with same ip
by Benoit Panizzon 14 Nov '24

14 Nov '24

Hi Gang I'm having another go with a dedicated kamailio running topos to replace a B2BUA SBC. I came across this situation: Server Topology: Kamaiolio SBC (topos) <=> Kamailio Registrar <=> Kamailio Router (DLG + CDRS) Core IP Address 10.0.0.1 Registrar IP 10.0.0.2 Two different CPE are registered on Registrar via SBC One CPE is calling the other CPE So the path the call is taking is: CPE A => SBC => Registrar => Core => Registrar => SBC => CPE B Invite A => B goes through, no issue. 180 Ringing, required 100rel B => A requires the route to be recorded therefore contains 3 record route statements: Record Route: <sip:10.0.0.2;lr> Record Route: <sip:10.0.0.1;lr> Record Route: <sip:10.0.0.2;lr> To ensure answer will get route back to the registrar => core => registrar and then the contact pointing to the SBC with topos to restore the last hop. Ringing B => A works as expected and is answered by A with PRACK. topos would now need set Route: in this PRACK message, according to the received Record Route Header. Unfortunately I fear Topos 'removes' the routes with duplicate host ip. I only get: Route: <sip:10.0.0.2> Route: <sip:10.0.0.1> Causing the Core not to be able to route the PRACK back to the registrar. To test, which line is being dropped, I added an mark to each one and determined the 3rd Record Router is being dropped by topos, probably considered a duplicate. I found no setting of the 'do not perform record route header dupe detection'. Interestingly, when I look at the database field topos_d.b_rr all three entries are present in the correct order. Has anyone come over the same issue and found a solution? Maybe related to: https://github.com/kamailio/kamailio/issues/3778 ? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Kamailio Developers Meeting, Nov 19-20, 2024, in Dusseldorf
by Daniel-Constantin Mierla 14 Nov '24

14 Nov '24

Hello, Kamailio SIP Server project is organizing another meeting of its developers and community members during November 19-20, 2024 (Tue-Wed), hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and contributors in order to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join, developer or user interested in helping the project. Please note we have a limited capacity of seats in the meeting room, the main policy for accepting participants being first come first server. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 4

Kamailio v5.8.4 Released
by Daniel-Constantin Mierla 12 Nov '24

12 Nov '24

Hello, Kamailio SIP Server v5.8.4 stable release is out. This is a maintenance release of the latest stable branch, 5.8, that includes fixes since the release of v5.8.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.8.x. Deployments running previous v5.8.x versions are strongly recommended to be upgraded to v5.8.4. For more details about version 5.8.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2024/11/kamailio-v5-8-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

Releasing v5.8.4
by Daniel-Constantin Mierla 12 Nov '24

12 Nov '24

Hello, I am considering to release Kamailio v5.8.4 (out of branch 5.8) sometime next week, most likely on Tuesday, Nov 12, 2024. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

6 10

fail2ban complains about Kamailio syslog messages
by Juha Heinanen 12 Nov '24

12 Nov '24

When Kamailio message parser produces this kind of syslog message: 024-11-11T21:16:40.757364+02:00 box /usr/bin/sip-proxy[181398]: ERROR: <core> [core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg: message=<#026#003#001#006\340#001> fail2ban complains: Consider setting logencoding to appropriate encoding for this jail. Continuing to process line ignoring invalid characters: b'2024-11-11T21:06:15.347318+02:00 box /usr/bin/sip-proxy[181398]: ERROR: <core> [core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg: message=<#026#003#001#006\xc0#001>\n': 1 Time(s) Error decoding line from '/var/log/syslog' with 'UTF-8'.: 1 Time(s) Unable to retrieve Watch object associated to <_RawEvent cookie=0 mask=0x2 name='' wd=13 >: 3 Time(s) Would it be possible to somehow ensure that Kamailio syslog messages only contain valid UTF-8 characters? -- Juha

1 0

Last line of onreply_route (drops reply)
by James Browne 11 Nov '24

11 Nov '24

Hi all I noticed, in my config, that if the last line of the reply_route is a function that does not succeed, then the SIP response is not relayed and kamailio throws an error. I've searched documentation to indicate why this might be, but I can't find anything, so this looks to me like a bug. I use 5.8.1 for testing. Here's a sample config that shows what goes wrong. #################### #!KAMAILIO listen=udp:203.0.113.57:5060 debug=1 loadmodule "textops" request_route{exit;} reply_route{remove_hf_re("^X-Custom");} #################### Here's a sample SIP message that works. When I send this to udp:203.0.113.57:5060, kamailio relays it. #################### SIP/2.0 200 Testing Via: SIP/2.0/UDP 203.0.113.57:5060;branch=z9hG4bK-d8754z Via: SIP/2.0/UDP 198.18.0.157:5060;branch=z9hG4bK-d8754z T: <sip:c@s>;tag=676fbf45 F: <sip:c@s>;tag=676fbf45 X-Custom: lkjdfl i: testing-XXX CSeq: 1 INFO l: 0 #################### If I then remove the X-Custom header field from the SIP reply and try again, the message does not get relayed and I see this in the log. 5(1356) WARNING: <core> [core/receive.c:605]: receive_msg(): error while trying onreply script If I put a log command after the remove_hf_re(), then the message gets relayed. It looks like the reply_route always fails if the last function is not successful. Is this normal or is it a bug? James

3 5

Question regarding error message "failed to add new socket to the fd list"
by Floimair Florian 11 Nov '24

11 Nov '24

Hi! We have recently had issues with one of our Production Kamailios. When those happened, the log was filled with the following message: CRITICAL: <core> [core/tcp_main.c:4528]: handle_new_connect(): failed to add new socket to the fd list Now I wonder what the best approach is to prevent this. We are using TCP/TLS only and I think this might be related to the file ulimit, but I am not sure about that. Shared memory is set to 512MB Can you give me a hint on what to look for? Thank you very much! P.S.: Sorry, I accidentally replied to a previous post of a different topic before which is totally unrelated (I think I should stop working for today 😉) FLORIAN FLOIMAIR Software Development - Symphony Cloud Services Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria [signature_2072127332] commend.com LG Salzburg / FN 178618z

2 1

apt-key deprecation
by tom＠tomlynn.com 11 Nov '24

11 Nov '24

When I look at the debian repositories maintained by the project, there are instructions to import the public key of the repository for apt using this command: wget -O http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - which results in: Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). gpg: no valid OpenPGP data found. Is there an alternate method that can be posted in the repository that will get better results? Thank you, TL

5 5

Unable to get body in multipart body
by Anthony Blandin 08 Nov '24

08 Nov '24

Hello, I want to get a body for content-type "application/isup" but I have the following error: 4(16) DEBUG: textops [textops.c:3394]: ki_get_body_part_helper(): found content type application/isup 4(16) ERROR: textops [textops.c:3397]: ki_get_body_part_helper(): no CRLF found after content type Here is the INVITE sent: INVITE sip:+883390000010022@[remote_ip]:[remote_port];user=phone SIP/2.0 From: <sip:+883390000010007@[local_ip];user=phone>;tag=[call_number] To: <sip:+883390000010022@[remote_ip];user=phone> Max-Forwards: 70 Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch] Route: <sip:[local_ip]:[local_port];transport=udp;lr> Record-Route: <sip:[local_ip]:[local_port];transport=udp;lr> Call-ID: [call_id] CSeq: 1 INVITE P-Asserted-Identity: <sip:+883390000010007@[local_ip]:[local_port];user=phone> Accept: application/sdp,application/isup,multipart/mixed Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,PRACK,UPDATE P-Charging-Vector: icid-value=IBCF-1-161460836711652742337;icid-generated-at=BC00.QX00.ORANGE-MSS.FR;orig-ioi=ORANGE-MSS.FR Supported: 100rel Content-Type: multipart/mixed;boundary=unique-boundary-1 MIME-Version: 1.0 Contact: <sip:[local_ip]:[local_port];transport=udp> Content-Length:[len] --unique-boundary-1 Content-Type: application/sdp v=0 o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip] s=- c=IN IP[local_ip_type] [local_ip] t=0 0 a=sendrecv m=audio [media_port] RTP/AVP 8 96 b=RR:0 b=RS:0 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 a=maxptime:40 --unique-boundary-1 Content-Type: application/isup;version=spirou;base=itu-t92+ Content-Disposition: signal;handling=required \x01\x11\x20\x01\x0a\x00\x02\x0c\x0a\x04\x10\x88\x33\x09\x00\x00\x01\x20\xf2\x0a\x0a\x84\x13\x88\x33\x09\x00\x00\x01\x00\x07\x1d\x03\x80\x90\xa3\x3f\x07\x83\x97\x26\x87\x41\x00\x00\x39\x04\x34\xc0\x3f\xc0\x00 --unique-boundary-1-- CRLF is well added at the end of Content-Type header, is anybody could help me to solve this issue? Regards, Anthony

1 0

[db_unixodbc] how to specify the database with unixodbc？
by 17603019528＠163.com 08 Nov '24

08 Nov '24

Hi Dear Community, I want to use db_unixodbc to connect to the dm8 database. Although I use Opensips, I found that this module db_unixodbc, Kamailio and Opensips are the same. My question is how to specify the database with kamailio？ I add "Database = sbc" into odbc.ini, But nothing happened。 ###### cat /usr/local/etc/odbc.ini [DM8] Description = ODBC DRIVER FOR DM8 Driver = DM8 ODBC DRIVER SERVER = 172.16.7.131 TCP_PORT = 5230 odbcinst -j unixODBC 2.3.12 DRIVERS............: /usr/local/etc/odbcinst.ini SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources USER DATA SOURCES..: /root/.odbc.ini SQLULEN Size.......: 8 SQLLEN Size........: 8 SQLSETPOSIROW Size.: 8 ####### #################### modparam("usrloc", "db_url", "unixodbc://opensips:opensips#$@172.16.7.131:5230/dm8") #################### DBG:db_unixodbc:db_unixodbc_new_connection: opening connection: unixodbc://xxxx:xxxx@172.16.7.131/dm8 Nov 7 17:05:21 [145] DBG:db_unixodbc:db_unixodbc_new_connection: connection succeeded with reply <DSN=dm8;SERVER=172.16.7.131;UID=opensips;PWD=opensips#$;TCP_PORT=5230;> DBG:core:db_do_init: connection 0xfffd5bbbaf08 inserted in pool as 0xfffd5bbbb0e0 Nov 7 17:05:21 [145] ERROR:db_unixodbc:db_unixodbc_submit_query: rv=-1. Query= select table_version from version where table_name='dialog' Nov 7 17:05:21 [145] ERROR:db_unixodbc:db_unixodbc_extract_error: unixodbc:SQLExecDirect=42S02:1:-2106:Error in line: 1 ####################

2 1

Draining TCP/TLS SIP sessions from Kamailio and media sessions from RTPEngine
by Evgenii Buchnev 07 Nov '24

07 Nov '24

Hi Dear Community, Would appreciate your input into where to look further to explore my options and would be good to learn your experience with the following. There are many active-active kamailio nodes behind tcp load balancer. On the same VM with each Kamailio there is an instance of RTPEngine to manage Media/Transcoding/Etc for that Kamailio. This scales UP easily - new nodes just added behind tcp load balancer. To be able to scale down and/or update node configuration - I'd like to be able to drain sessions/calls properly and pass any active calls from current Kamailio and RTPEngine to other nodes. DMQ is not yet in place, although it's planned. What would be proper ways of migrating RTP sessions to other RTPEngines? Caveats? Also wonder how properly a tcp/tls based SIP session can be passed to another Kamailio? Thank you in advance for your input. Evgenii Buchnev

3 2

Roadmap to v6.0.0 - the next major release
by Daniel-Constantin Mierla 07 Nov '24

07 Nov '24

Hello, about 8 months since the last major release v5.8.x, therefore it is the time to plan a bit the next steps for getting v6.0.0 out. The Kamailio Developers Meeting is schedule in Dusseldorf, Germany during November 19-20, 2024, where we expect to push out a consistent number of updates. Then maybe we can wait for another 2 weeks or so to settle down/finish those updates. After that, if no other new features are planned by developers in short term, we can enter the testing phase, so the new major version can be released during the second part of January 2025 or first part of February 2025. Therefore, if you have new features under development that might require more than 1-1.5 months from now, and you want to get them in v6.0.0, let us know to plan properly. Other time lines suggestions to get to v6.0.0 are also welcome! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 1

Kamailio 5.5.7 alias not added to ACK
by Mitesh Thakkar 06 Nov '24

06 Nov '24

Hi, I was using kamailio 5.2.5. I have recently upgraded to kamailio 5.5.7. After upgrade, the alias is stop being add to the ACK of reinvite from upstream. Before upgrade, it was working fine. I’ll appreciate any help on this. Thank you. Regards, Miteshkumar Thakkar

1 0

SNMP setup
by Sergio Charrua 05 Nov '24

05 Nov '24

Hi all! I am having difficulties setting up SNMP, and mostly to figure out if what I have setup is correctly configured. This is what I have on Kamailio (5.8.2), which is set as stateless and as a redirect server (simply put, it receives INVITE from SBC, gets a route from routing services, modifies Contact header, and replies to SBC with 300 Multi Choice with new contact header): loadmodule "db_mysql.so" loadmodule "db_cluster.so" loadmodule "http_client.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "jansson.so" loadmodule "snmpstats.so" loadmodule "file_out.so" loadmodule "ctl.so" loadmodule "permissions.so" loadmodule "xhttp.so" loadmodule "xhttp_rpc.so" # ---- SNMP Stats params ---- modparam("snmpstats", "sipEntityType", "proxyServer") modparam("snmpstats", "sipEntityType", "redirectServer") modparam("snmpstats", "sipEntityType", "other") modparam("snmpstats", "snmpgetPath", "/usr/bin/") modparam("snmpstats", "MsgQueueMinorThreshold", 1) modparam("snmpstats", "MsgQueueMajorThreshold", 1) modparam("snmpstats", "dlg_minor_threshold", 1) modparam("snmpstats", "dlg_major_threshold", 1) modparam("snmpstats", "snmpCommunity", "kamailio") I have set the *_minor_threshold values to bear minimum. Should I add anything else? The logs show the following messages: DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 60) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 64) returns address 0x7f03af3bcc50 frag. 0x7f03af3bcc10 (size=64) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 20) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 32) returns address 0x7f03af3bcd00 frag. 0x7f03af3bccc0 (size=32) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcc50), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(464) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bcc10 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcd00), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(471) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bccc0 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 60) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 64) returns address 0x7f03af3bcc50 frag. 0x7f03af3bcc10 (size=64) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 20) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 32) returns address 0x7f03af3bcd00 frag. 0x7f03af3bccc0 (size=32) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcc50), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(464) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bcc10 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcd00), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(471) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bccc0 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) INFO: snmpstats [utilities.c:116]: get_statistic(): failed to retrieve statistics for active_dialogs INFO: snmpstats [utilities.c:116]: get_statistic(): failed to retrieve statistics for active_dialogs The SNMP daemon is set as follows: - /etc/snmp]$ cat snmptrapd.conf # Example configuration file for snmptrapd # # No traps are handled by default, you must edit this file! # # authCommunity log,execute,net public # traphandle SNMPv2-MIB::coldStart /usr/bin/bin/my_great_script cold and on /etc/snmp/snmpd.conf: ############################################################################### # Further Information # # See the snmpd.conf manual page, and the output of "snmpd -H". agentaddress udp:161 rocommunity kamailio master agentx agentXSocket tcp:localhost:705 trap2sink 10.X.Y.Z netcool 162 When running tcpdump and listening on port 162, no traffic is captured....it seems to me that Kamailio is not sending anything to SNMP Any clue, anyone? What am I doing wrong? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

3 3

Function sdp_get gets extra blank line (when MIME is used)
by James Browne 05 Nov '24

05 Nov '24

The sdp_get() function from sdpops returns an extra blank line sometimes, which looks like a bug to me. When I have an SDP that's in MIME, there's an extra newline at the end of the extracted SDP. Here's a sample config. I use 5.8.1 for testing. #################### #!KAMAILIO listen=udp:203.0.113.57:5060 debug=1 loadmodule "sdpops" loadmodule "pv" loadmodule "xlog" request_route{exit;} reply_route { sdp_get("$avp(sdp)"); xlog("L_NOTICE", "[$ci] The SDP is [$avp(sdp)].\n"); } #################### Here are two sample SIP-message bodies. #################### v=0 o=PCD 1730 1730 IN IP4 198.18.114.148 s=PCD c=IN IP4 198.18.114.148 t=0 0 m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 #################### #################### --e61e7a6a-16a2-46c0-adbb-a41ba86d32a2 Content-Type: application/sdp Content-Length: 130 v=0 o=PCD 1730 1730 IN IP4 198.18.114.148 s=PCD c=IN IP4 198.18.114.148 t=0 0 m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 --e61e7a6a-16a2-46c0-adbb-a41ba86d32a2-- #################### When the first body is received, the xlog correctly ends with this. m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] with length 130 When the second body is received, the xlog incorrectly ends with this, which has an extra newline in it. m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] with length 132 According to RFC2046, "The CRLF preceding the boundary delimiter line is conceptually attached to the boundary", but it looks like kamailio has a bug that incorrectly processes this. James

2 2

Simultaneous INVITE responses from multiple branches
by Anton Yabchinskiy 04 Nov '24

04 Nov '24

Hello, In our system we've encountered the following situation. There's a Kamailio proxy and a few REGISTER'ed devices behind the proxy. When there's an INVITE to these multiple devices, two of them simultaneously answer the call. Kamailio proxy accepts the first 200 OK from one of the devices and tries to CANCEL all other branches. But the second 200 OK device have already responded OK and doesn't acknowledge the CANCEL. So, there's now one established dialog with media, and another "established" one neither having media nor being correctly terminated. Looks like the similar scenario is described in section 3.1.2 of RFC 5407 (Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)). Is it possible to mitigate such scenarios in a Kamailio proxy? E.g., is it possible to send an additional BYE to these CANCEL'led branches? In current configuration, Kamailio proxy retrieves contacts with registrar:lookup() and does parallel forking with tm:t_relay().

2 2

Re: Dealing with flood of invalid SIP messages
by Juha Heinanen 04 Nov '24

04 Nov '24

I gave APIBAN a try. After a few days, no requests were banned by APIBAN, but during the same period, lots of request were banned by other checks in my config. That made me wonder if APIBAN really is effective. -- Juha

2 3

Error opening Kamailio's FIFO /run/kamailio/kamailio_rpc.fifo
by matilopi17＠gmail.com 01 Nov '24

01 Nov '24

Hello, This is kamailio version 5.8.2 and we`re having this issue every now and then. The error displayed is: ** ERROR: Error opening Kamailio's FIFO /run/kamailio/kamailio_rpc.fifo ** ERROR: Make sure you have loaded the jsonrpcs module and set FIFO transport parameters The problem is that the FIFO file /run/kamailio/kamailio_rpc.fifo doesn't exist, even though the "jsonrpc" module is in the Kamailio configuration, and the file is created when Kamailio service is restarted. But as mentioned, after few days the issue is repeated. I`ll appreciate any suggestion or advice of what I should check. Thank you!

4 5

Failed to parse the R-URI with topoh enabled
by Ale 29 Oct '24

29 Oct '24

Hi All, I think I have a problem with topoh, but I can't identify it. Kamailio 5.6.6, used as a stateless proxy, receives a 487 from a phone and propagates it correctly. Next comes the ack that should be forwarded back to the phone, but instead it doesn't forward it and produces the following error "pv_get_ruri(): failed to parse the R-URI" The error is generated by xlog("...$ru from $fu...\n"") as first line of request_route. If I disable topoh everything works perfectly.Topoh is only configured with mask_key only. Furthermore, not all phones generate this problem, at the moment there are some snoms. ACK sip:user@phone_ip:2048;line=kkqgarrj SIP/2.0 Via: SIP/2.0/UDP proxy_sip_ip;branch=z9hG4bK2ec.e7126a3134bef9d974f57dd43ebd4ea2.0 Route: <sip:kamailio_ip:5060;lr;received=sip:phone_ip:2048> Max-Forwards: 66 From: <sip:111111111@sip.example.com>;tag=pDc1BQ0B57Ujj To: <sip:user@sip.example.com>;tag=vslvowy4y2 Call-ID: 40a6c905-c0c8-4c20-b3f7-397b3fce58b6 CSeq: 90285584 ACK Content Length: 0 There is no difference between the ACK of the snom and other phones that work. The only difference I noticed is that the snom 487 contains Contact field in the header. Any suggestions? Thank you

3 5

How to handle e2e ACK with t_check_trans()
by Benoit Panizzon 28 Oct '24

28 Oct '24

Hi List To correctly route ACK belonging to a transaction (totag) the example code does: if ( is_method("ACK") ) { if ( t_check_trans() ) { route(RELAY); exit; } else { xlog("L_INFO", "$cfg(route): $rm NOT loose route NO transaction found DROP\n"); exit; } } Unfortunatels I fear that in a parallell forking scenario, the transaction is remove from memory as soon as the first 'negative' ACK is being processed so that the end 2 end ACK to the 200 OK of the branch that connected the call, never makes it through. I attempted to increase wt_timer to 10000 to have the transaction stay around 10 seconds but that does not solve the issue. I read that t_check_trans()'s result shall be considered more as a hint than as a confirmation of an existing transaction. Is there a clean / secure way to process e2e ACK and make sure they belong to a transaction? Or can I just safely remove the t_check_trans() call and route any ACK with a totag? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 3

Dealing with flood of invalid SIP messages
by mayamatakeshi 27 Oct '24

27 Oct '24

Hi, I was going through some old company tickets that I am assigned to and found a case when possibly an attacker flooded our kamailio server with invalid sip messages like this: 2019-04-27T20:14:05.533554+09:00 IPX051 /usr/local/src/git/sip-router/kamailio[1732]: ERROR: <core> [parser/msg_parser.c:714]: ERROR: parse_msg: message=<[F#016sD#026Z<8D>97<F8><B5>;<A9><E7>-<D2>(<E2><F6> v;/#021k\<CC>8<B1>λ<F4>#004M<B6><BE><EC>#035#003<94><E1>=<A0><FF><E3><AF>Kwzr<8B>A#036B<D7>#027#023cu<82>Y<D4>#037<FB><AC>S_<C4>Qg<AB><DE>F<88>I#006<8C><FA><F4>~#y3G<C7>H<80>b<BC><AD>#035<89>#002<DB><C8>#001U<9E>#007<CB><F9>nT<E5><EE><8E><F1>#0144> At that time we manually banned the IP. But it would be helpful to have this done automatically by fail2ban. So I was thinking this log should include the src IP address. I looked at the latest kamailio commit and core/parser/msg_parser.c does this log the same way so I was thinking in opening an issue for this. But maybe this should be dealt with differently. Any ideas?

4 6

Issue with Retrieving Kamailio Statistics: Missing FIFO File and Errors
by satyaprakash ch 25 Oct '24

25 Oct '24

Hi, I'm encountering an issue while trying to retrieve Kamailio statistics on the server using the command kamctl stats. Instead of the expected output, I am receiving the following errors: kamctl stats: -e \E[37;31mERROR: Error opening Kamailio's FIFO /run/kamailio/kamailio_rpc.fifo -e \E[37;31mERROR: Make sure you have loaded the jsonrpcs module and set FIFO transport parameters Additionally, the file /run/kamailio/kamailio_rpc.fifo does not exist. Could you please provide suggestions ?

3 4

Handeling error returned by rtpengine_manage(...)
by Wolter Eldering 23 Oct '24

23 Oct '24

Hello, I have a question about the rtpengine module and how to use it via KEMI/python. Will processing of the native script stop when rtpengine_manage returns with an error? Or will it continue and will the SDP be forwarded unchanged? #!ifdef WITH_RTPENGINE if(nat_uac_test("8")) { rtpengine_manage("SIP-source-address replace-origin replace-session-connection"); } else { rtpengine_manage("replace-origin replace-session-connection"); } #!else Regards, Wolter

3 4

Kamailio not deleteing rtp sessions
by Tihomir Culjaga 22 Oct '24

22 Oct '24

Hello, I'm using Kamailio + RTPEngine. Everything works well except one thing. I noticed rtp sessions are not being deleted after call termination. Instead, they remain lingering on RTPEngine waiting for a timeout. kamailio --version version: kamailio 5.5.2 (x86_64/linux) 55e232 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: 55e232 compiled on 14:13:04 Aug 25 2021 with gcc 8.4.1 rtpengine --version Version: 9.5.1.1-1.el8 rtpengine-ctl list totals tells me every session went to timeout :) --- snip --- Total statistics (does not include current running sessions): Uptime of rtpengine :914 seconds Total managed sessions :51 Total rejected sessions :0 Total timed-out sessions via TIMEOUT :51 Total timed-out sessions via SILENT_TIMEOUT :0 Total timed-out sessions via FINAL_TIMEOUT :0 Total timed-out sessions via OFFER_TIMEOUT :0 Total regular terminated sessions :0 Total forced terminated sessions :0 --- snip --- I'm using rtpengine_manage in two routes "route[RELAY]" and onreply_route[MANAGE_REPLY] . Do I need to add a specific rtpengine_delete somewhere ? route[RELAY] { ... $xavp(r=>$T_branch_idx) = "replace-origin replace-session-connection"; if (!nat_uac_test("8")) { $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " trust-address"; } if (!has_totag()) { xlog("L_INFO", "NEXIOS: proto = [$proto], ru = [$ru]"); if ($proto =~ "ws" && !($ru =~ "transport=ws")) { xlog("L_INFO", "####################### FROM WS to any ########################\n"); $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP direction=external direction=internal"; } else if (!($proto =~ "ws") && $ru =~ "transport=ws") { xlog("L_INFO", "####################### FROM any to WS ########################\n"); setbflag(FLB_TOWEBRTC); $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " rtcp-mux-offer generate-mid DTLS=active SDES-off ICE=force RTP/SAVPF direction=internal direction=external"; } else if (($proto =~ "udp") && $ru =~ "transport=udp" && $fs =~ "MY_IP2_ADDR") { xlog("L_INFO", "####################### FROM ?? to ?? $ru ########################\n"); } } # we engage RTPEngine if (has_body("application/sdp")) { xlog("L_INFO", "NEXIOS: # $xavp(r=>$T_branch_idx) #\n"); rtpengine_manage($xavp(r=>$T_branch_idx)); } if (!t_relay()) { sl_reply_error(); } exit; } onreply_route[MANAGE_REPLY] { ... $xavp(r=>$T_branch_idx) = "replace-origin replace-session-connection"; if (!nat_uac_test("8")) { $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " trust-address"; } if (has_totag()) { xlog("L_INFO", "onreply_route proto = [$proto], ru = [$ru]"); if ($proto =~ "ws" && !($ru =~ "transport=ws")) { xlog("L_INFO", "onreply_route ####################### FROM WS to any ########################\n"); $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP direction=external direction=internal"; } else if (!($proto =~ "ws") && $ru =~ "transport=ws") { xlog("L_INFO", "onreply_route ####################### FROM any to WS ########################\n"); setbflag(FLB_TOWEBRTC); $xavp(r=>$T_branch_idx) = $xavp(r=>$T_branch_idx) + " rtcp-mux-offer generate-mid DTLS=active SDES-off ICE=force RTP/SAVPF direction=internal direction=external"; } else if (($proto =~ "udp") && $ru =~ "transport=udp" && $fs =~ "MY_IP2_ADDR") { xlog("L_INFO", "onreply_route ####################### FROM ?? to ?? $ru ########################\n"); } } if (has_body("application/sdp")) { xlog("L_INFO", "onreply_route # $xavp(r=>$T_branch_idx) #\n"); rtpengine_manage($xavp(r=>$T_branch_idx)); } } Any ideas are appreciated. Regards, Tihomir.

4 6

parallel forking: how to fix 183 g711 then 200 ok g722?
by Benoit Panizzon 21 Oct '24

21 Oct '24

Hi Gang Parallel forking situation. A => B A => C A invites with g711,g722 which is forked to B and C B reports ringing by sending 183 + SDP g711 C report 180 ringing. C establishes connection 200 OK + SDP g722 https://www.rfc-editor.org/rfc/rfc3261.html#page-78 o If the initial offer is in an INVITE, the answer MUST be in a reliable non-failure message from UAS back to UAC which is correlated to that INVITE. For this specification, that is only the final 2xx response to that INVITE. That same exact answer MAY also be placed in any provisional responses sent prior to the answer. The UAC MUST treat the first session description it receives as the answer, and MUST ignore any session descriptions in subsequent responses to the initial INVITE. Now we run into the situation in which A received the 183 g711 and being RFC compliant, dropped the 2nd SDP from the 200 OK. => No audio! Has anyone encountered this situation and found a nice solution? Like generating an UPDATE or RE-INVITE towards A to change the codec in an RFC compliant way after the call is established? Or is the only solution to remove all codecs except the required g711a one when more than one contact are registered on an AOR? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 5

Statically Linking Multiple Modules Compile Error
by Steve Bezalel 21 Oct '24

21 Oct '24

Hello, I am trying to compile Kamailio with all its modules statically linked. How should I go about this? I followed through the installation documentation but could not find any information. I tried passing all the modules I want to statically link in the "static_modules" argument of `make` but it seems that definitions of modules clash as such. ``` make static_modules="siputils rr" ``` ``` /usr/bin/ld: modules/rr/rr_mod.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/rr/rr_mod.c:69: multiple definition of `module_version'; modules/siputils/siputils.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/siputils/siputils.c:78: first defined here /usr/bin/ld: modules/rr/rr_mod.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/rr/rr_mod.c:69: multiple definition of `module_flags'; modules/siputils/siputils.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/siputils/siputils.c:78: first defined here /usr/bin/ld: modules/rr/rr_mod.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/rr/rr_mod.c:69: multiple definition of `module_interface_ver'; modules/siputils/siputils.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/siputils/siputils.c:78: first defined here /usr/bin/ld: modules/rr/rr_mod.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/rr/rr_mod.c:166: multiple definition of `exports'; modules/siputils/siputils.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/siputils/siputils.c:241: first defined here /usr/bin/ld: modules/rr/rr_mod.o: in function `mod_register': /playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/rr/rr_mod.c:926: multiple definition of `mod_register'; modules/siputils/siputils.o:/playground/fuzzing-targets/sip/kamailio-dfsan/src/modules/siputils/siputils.c:817: first defined here ``` Any help would be appreciated. Thank you.

1 0

$hdr behaviour using jansson+http_connect
by Sergio Charrua 19 Oct '24

19 Oct '24

Hi all! My team and I are finalizing implementation of STIR/SHAKEN. The flow has been simplified and is something like: Call comes from SBC to Kamailio, Kamailio makes an HTTP request to a REST API, response is received by Kamailio (5.8.2) and depending on the response, it replies back to SBC with a SIP 300 Multiple Choice of a SIP 4xx error, denying the call. The INVITEs received by SBC may or may not contain the Identity header. On Kamailio side, the following code gets the required headers to build the JSON object sent to REST API: route[HANDLE_STIRSHAKEN] { if (!is_method("INVITE")) { return; } $var(requestTime) = $utimef(%s); $var(ruri) = "$ru"; #request URI $var(from) = "$hdr(From)"; #$fU From header $var(to) = "$hdr(To)"; #$tU; To header $var(contact) = "$hdr(Contact)"; #Contact header $var(callID) = "$ci"; # Call ID $var(identity) = "$hdr(Identity)"; # Identity header jansson_set("string","from" , $var(from) , "$var(post)"); jansson_set("string","to" , $var(to) , "$var(post)"); jansson_set("string","r-uri" , $var(ruri) , "$var(post)"); jansson_set("string","contact" , $var(contact) , "$var(post)"); jansson_set("string","call-id" , $var(callID) , "$var(post)"); jansson_set("string","identity" , $var(identity) , "$var(post)"); http_connect("api1", "/stsh", "application/json","$var(post)","$var(result)"); xlog("L_DEBUG", "HANDLE_STIRSHAKEN - Result = $var(result)\n"); [... do some other irrelevant stuff ...] } The usual INVITE is similar to this: INVITE sip:+33142XXXXXX@10.242.XXX.YYY:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.240.AAA.BBB:5064;branch=z9hG4bK+30f178b47ee25dd589f986ed7402b4eb3+sip+6+a64eb889 From: "+493XXXXXXX" <sip:+493XXXXXXX@10.240.AAA.BBB ;user=phone>;tag=10.240.AAA.BBB+6+ffe686f8+614d17a3 To: +33142XXXXXX <sip:+33142XXXXXX@10.242.XXX.YYY> CSeq: 1 INVITE Expires: 180 Content-Length: 234 Call-Info: <sip:10.240.AAA.BBB:5064>;method="NOTIFY;Event=telephone-event;Duration=2000" Supported: timer, 100rel Contact: <sip:+493XXXXXXX@10.240.AAA.BBB:5064;user=phone> Content-Type: application/sdp Call-ID: 0gQAAC8WAAACBAAALxYAAHRfFdrMLbnN/iMYu2NTT6kvhuhZAFl7MG1V2ozJLUcXg9dxbyQZ/PtoswtdHtcv9g--(a)10.240.AAA.BBB Min-SE: 90 Session-Expires: 90;refresher=uac X-dtmf: 5 P-Asserted-Identity: "+493XXXXXXX" <sip:+493XXXXXXX@10.240.AAA.BBB> Accept: application/sdp Accept: application/dtmf-relay Max-Forwards: 66 Allow: INVITE,CANCEL,BYE,ACK, INFO Identity: dGhpcyBpcyBzb21lIGR1bW15IGJhc2U2NCBlbmNvZGVkIElkZW50aXR5IGhlYWRlcg==.eW91IHdvdWxkIG5vdCBleHBlY3QgbWUgdG8gbGVhdmUgdGhlIHJlYWwgdmFsdWUgaGVyZSByaWdodD8=.dGhhbmtzIGZvciB5b3VyIGNvbXByZWhlbnNpb24=;info=< https://someURL.com/with/some/parameter;sc697295b.cer>;alg=ES256;ppt=shaken P-Origination-Id: 23A16F8B-F9AB-4536-9884-85C96EF3B964 P-Attestation-Indicator: C has-sdp: present [SDP stuff] (I have replaced some of the values for obvious reasons). - SBC is sending every 70 secs 2 automatically generated INVITEs to kamailio - 1st call contains the Identity header, the other call does not contain Identity header. - Both calls have different Call-IDs and different FROM and TO values, so they are different calls and can be perfectly found in logs as separated calls - Kamailio receives each call and extracts headers, as shown in code above, and sends the JSON request to HTTP REST API Here is the weird part.... every now and then, completely random, the JSON object request sent to the HTTP REST API contains an Identity value, supposedly extracted from the SIP header **but** the SIP message captured in SNGrep doesn't have **any* I*dentity header!! In fact, in the kamailio logs, where I sent the header values extracted from INVITE, the identity is empty! BUT the JSON object has the identity set with value. And the worst part is that, when this issue happens, the value of the Identity set in JSON belongs to a completely different call that was processed a few minutes before ! So I suspected about some Caching behaviour on the http_connect function and added the following lines before sending the JSON to REST API: if ( is_present_hf("Identity") ) { jansson_set("string","identity",* $var(identity),* "$var(post)"); } else jansson_set("string","identity", "", "$var(post)"); forcing the identity property of the JSON to an empty string, but this did not work either! I even added a new property which is the current timestamp making sure every request was unique, and that did not work either! The only way I could make it work was replacing the above lines using these lines: if ( is_present_hf("Identity") ) { jansson_set("string","identity", *(a)hf_value2.Identity*, "$var(post)"); } else jansson_set("string","identity", "", "$var(post)"); So, instead of using $hdr(Identity) , Kamailio extracts the Identity header using @hf_value2.Identity Question: why is this behaviour? Could this be a bug somewhere? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

3 3

Re: Dispatcher ping: "binding to source address X.X.X.X:XXXX failed: Address already in use" for TCP and TLS destinations
by Mirko Brankovic 15 Oct '24

15 Oct '24

Hi, Has anyone found how to safely suppress the warning? We see it on 5.7.4 Thanks, Mirko

2 2

kamailio - acc sqlite
by marek 14 Oct '24

14 Oct '24

hi, i'm trying setup kamailio for simple CDR logging versions - kamailio 5.7, rocky 9.4 i have configured and populate sqlite with "kamdbctl create" kamailio.cfg #CDR loadmodule "db_sqlite.so" loadmodule "acc.so" modparam("acc", "cdr_enable", 1) modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 2) modparam("acc", "db_url", "sqlite:///var/log/kamailio-cdr.sqlite") modparam("acc", "time_mode", 3) but i have this error ERROR: db_sqlite [dbase.c:232]: db_sqlite_submit_query(): failed to prepare statement: table acc has no column named time_attr any ideas where can i find acc schema update for time_attr column? bash# grep -Rni time_attr /usr/share/kamailio/db_sqlite/ shows nothing Marek

2 2

Getting the name of an already set onreply_route
by Denys Pozniak 14 Oct '24

14 Oct '24

Hello! Is it possible to find out the name of the onreply_route that was set before? Something like this: t_on_reply("MANAGE_REPLY"); ... if ( t_is_set("onreply_route") ) { get_onreply_route_name(); ... } -- BR, Denys Pozniak

3 5

Appending Branches Post Request Processing
by Knserbrave 08 Oct '24

08 Oct '24

Hi Community, Is it possible to append a branch to a transaction after the call is in a ringing state? Say a call comes in and an AOR only has two contacts. Branches are created to the contacts. A third comes in why the two are in the ringing state. Can we create a branch to the third?

2 3

TLS module crashes with FIPS OpenSSL
by Marat Gareev 08 Oct '24

08 Oct '24

Hello, I encountered a problem stopping Kamailio with FIPS OpenSSL: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3 Missing separate debuginfos, use: dnf debuginfo-install kamailio-5.7.3-4816.x86_64 (gdb) bt #0 0x00007ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3 #1 0x00007ff72914bf5b in conf_modules_finish_int () from /lib64/libcrypto.so.3 #2 0x00007ff72914c694 in CONF_modules_unload () from /lib64/libcrypto.so.3 #3 0x00007ff7291efff9 in OPENSSL_cleanup () from /lib64/libcrypto.so.3 #4 0x00007ff72954702b in ?? () #5 0x0000000100061c08 in ?? () #6 0x00007ff7190566c8 in ?? () #7 0x00007ffccf196a20 in ?? () #8 0x000000000071da8a in futex_release (lock=0x7ff729f08b50 <syslog>) at core/mem/../mem/../futexlock.h:134 #9 0x00000000006e9448 in destroy_tls () at core/tls_hooks.c:75 #10 0x000000000041f278 in cleanup (show_status=1) at main.c:594 #11 0x0000000000420af1 in shutdown_children (sig=15, show_status=1) at main.c:721 #12 0x0000000000421717 in handle_sigs () at main.c:752 #13 0x0000000000430c88 in main_loop () at main.c:1988 #14 0x0000000000439d13 in main (argc=14, argv=0x7ffccf1973f8) at main.c:3212 (gdb) Environment: Oracle Linux Server 9.3 Kamailio 5.7.3 yum list --installed | grep ssl openssl.x86_64 10:3.0.7-24.0.3.el9_fips @tools openssl-libs.x86_64 10:3.0.7-24.0.3.el9_fips @tools openssl-pkcs11.x86_64 0.4.11-7.el9 @anaconda xmlsec1-openssl.x86_64 1.2.29-9.el9 @AppStream What can I do for further investigation? Thanks

5 12

t_append_branches() and "dead" tcp connections
by Ihor Olkhovskyi 04 Oct '24

04 Oct '24

Hello, Recently encountered an issue with tsilo (that is using t_append_branches), but not sure found a root cause. So, I have a call, but aparently there are some "dead" TCP connections in a "location" table modparam("usrloc", "handle_lost_tcp", 0) On call initialtion, INVITE's are sent to "last seen" location, but aparently there is no answer and I assume it's in a state "trying to establish TCP connection" Obviously, there is no "100 Trying" answer on any outgoing INVITE. Than, a REGISTER comes from a contact, that is supposed to be called. Usual ts_append("location", "$tu"); is called, but in the logs I see [REGISTER] tm [t_append_branches.c:208]: t_append_branches(): failure to add branches (-1) If there is an active TCP connection, branches are added as expected. I'm getting this only in a case of trying to establish a call to a "dead" TCP connection. What am I missing here or it sounds like a bug? -- Best regards, Ihor (Igor)

2 9

kamailio sending from udp non-listening port
by David Villasmil 04 Oct '24

04 Oct '24

Hello guys, i'm seeing something weird, and i'm working if you can let me know. I have a kamailio in AWS with a private IP listening on several sockets: Listening on udp: 10.1.2.36:5070 udp: 10.1.2.36:5080 udp: 10.1.2.36:5160 advertise 4.3.2.1:5160 udp: 0.0.0.0:5066 tls: 10.1.2.36:443 advertise sip.something.com:443 tls: 10.1.2.36:444 advertise sip.something.com:444 tls: 10.1.2.36:5061 When forwarding a udp invite received on 10.1.2.36:5080 to a public ip provider say on 8.8.8.8:5060, i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160. But the outgoing invite does NOT use 5160, it uses some random port... Anybody knows why this might be? my problem is, that call goes to freeswitch... call is setup properly and connects fine. But 15 minutes later the end provider sends back a reINVITE, which freeswitch then sends TO THE RANDOM PORT kamailio used to send the INVITE... but by this time kamailio doesn't seem to even see the packet... help is greatly appreciated! David Regards, David Villasmil email: david.villasmil.work(a)gmail.com

4 9

relay to voip provider / sip trunk / path?
by Linux Admin 03 Oct '24

03 Oct '24

Hi. I am using https://github.com/havfo/WEBRTC-to-SIP to have a web sipcaller. it uses kamailio + rtpengine + web sipcaller (jssip) right now it is working using internal kamailo account and can call to another sip. But I need to use websipcaller to call to voip provider. I tried to register on my voip provider, and use just outbound websocket proxy, but it not working giving 401 the config I am using is https://github.com/havfo/WEBRTC-to-SIP/blob/master/etc/kamailio/kamailio.cfg Please help adopt it to relay anything to external sip provider. I don't know what I need, relay, sip trunk or path module. kamailio configs are very hard for me to understand. So I need it just as websocket proxy to my voip provider, that doesn't support websocket. thanks!

2 2

app_lua parse multiple files
by iliusha.md＠gmail.com 03 Oct '24

03 Oct '24

I have a Lua script which is split into multiple files, like: /etc/kamailio/routing/ ├── main.lua ├── logger.lua └── db.lua On restart, Kamailio fails to start with an error: main.lua:2: module 'logger' not found:\n\tno field package.preload If I set multiple files in the modparam parameter: modparam("app_lua", "load", "/etc/kamailio/routing/main.lua") modparam("app_lua", "load", "/etc/kamailio/routing/logger.lua") I'm getting the same error. Is it possible to load multiple files, or is this a limit to a single file currently?

4 3

Heads-up: Clean-up of legacy modules in app_python3
by Richard Chan 01 Oct '24

01 Oct '24

HI kamailio users, There is a WIP PR on master (and targeting 6.0) to clean-up legacy modules on app_python3. https://github.com/kamailio/kamailio/pull/3986/commits/a9eb4b35b67b58893772… If you rely on pre-KEMI features (Core / Router / Logger / Ranks) can you chime in here. This work is also in preparation to enable the Kamailio module to use free-threading builds of Python. Regards Richard

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users