June 2025 - sr-users - kamailio.org

Dispatcher sets IP flag on servers even though SIP OPTIONS receive 200 OK
by Pablo Oliver 26 Jun '25

26 Jun '25

Hi there, I'm new to Kamailio, and maybe this is a silly question. I’ve set up Kamailio as a SIP proxy with two Asterisk servers acting as media services. This is my configuration for the dispatcher module: loadmodule "dispatcher.so" modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_threshold", 5) modparam("dispatcher", "ds_inactive_threshold", 5) modparam("dispatcher", "ds_ping_latency_stats", 1) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") modparam("dispatcher", "ds_ping_from", SIPCALL) I can see the SIP OPTIONS requests going from Kamailio to Asterisk and receiving 200 OK responses. However, the dispatcher is still setting the IP (Inactive Probing) flag on the servers: kamcmd dispatcher.list { NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip:172.16.254.21:5060 FLAGS: IP PRIORITY: 0 LATENCY: { AVG: 0 STD: 0 EST: 0 MAX: 0 TIMEOUT: 183 } } DEST: { URI: sip:172.16.254.20:5060 FLAGS: IP PRIORITY: 0 LATENCY: { AVG: 0 STD: 0 EST: 0 MAX: 0 TIMEOUT: 183 } } } } } } So when I try to use ds_select_dst("1", "4"), it always fails. Did I miss something in my configuration? Thanks! Regards, Pablo.

3 6

Context of t_continue
by johannes.westhuis＠auerswald.de 25 Jun '25

25 Jun '25

Hi, we are using kamailio 5.8 with t_suspend to suspend calls until a push notification wakes up the phone. The phone will then send an NOTIFY with information, so that t_continue can be called. This works well, but currently we are facing issues with rtpengine, and looking at the logs, there is something suspicious: we are calling: t_continue("$sht(vtp=>id_index::$hdr(X-Resume))", "$sht(vtp=>id_label::$hdr(X-Resume))", "RESUME"); ... route[RESUME] { xdbgl("[RESUME] rm=$rm ru=$ru du=$du \n"); ... after the call to t_continue i can see the log mentioned above: Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} <script>: 486:[RESUME] rm=INVITE ru=sip:<URI_REDACTED> I wondered why the log call still logs the context as the NOTIFY context and not the INVITE context, and if that might lead to issues? currently we get problems with rtpengine_manage when we try to call it in the route[RESUME] Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke We are currently checking, if we can work around this issue, but i am hoping to getting a bit of insight from you. Best Regards JWes

4 4

Kamailio v6.0.2 Released
by Daniel-Constantin Mierla 25 Jun '25

25 Jun '25

Hello, Kamailio SIP Server v6.0.2 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.2. 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.2. For more details about version 6.0.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2025/06/kamailio-v6-0-2-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

multihoming & BYEs
by Dustin Marquess 25 Jun '25

25 Jun '25

All, I've tried searching and have found similar posts before, but I have yet to find a real 'solution'. I'm running Kamailio 6.0.1 & RTPEngine 13.3.1.7 (on a Linux VM) as a "SBC" (at home) using the config from: https://github.com/voiceboys/sbcOS/blob/version_2.0/var/www/html/alpine/con… Except that I've added the following: mhomed=1 modparam("rr", "force_send_socket", 1) The SBC is dual-homed: one interface on the local LAN and another interface directly on the Internet/WAN (real public IP). Everything works fine, EXCEPT if the remote end (the side on the WAN/Internet) hangs up first. If they do, the BYE never makes it past Kamailio to the local PBX and/or phone. https://users.openser.narkive.com/1aK7n8Il/sr-multihomed-kamailio-and-enabl… suggests to use $sht to save the information needed, but I have no clue where in the config to put that. Any help would be greatly appreciated. Thanks! -Dustin

4 4

Re: kamailio tls module not loading
by Jonathan Aquilina 25 Jun '25

25 Jun '25

Hi Timothy, Have you checked to see there is no firewall blocking traffic? Regards, Jonathan From: Timothy Delin <timothy.delin(a)singtel.com> Sent: 25 June 2025 05:53 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Who AmI <myfriendjohn1(a)gmail.com>; Jonathan Aquilina <jaquilina(a)eagleeyet.net> Subject: RE: [SR-Users] Re: kamailio tls module not loading Hey Jonathan, I can confirm that this IP address is only used for the Kamailio TLS listener based on the netstat command. /usr/src/kamailio # netstat -tuln | grep 5063 tcp 0 0 192.168.254.19:5063 0.0.0.0:* LISTEN I am not sure if I should have a separate listener and outgoing port for listener. Best regards, Timothy From: Jonathan Aquilina <jaquilina(a)eagleeyet.net<mailto:jaquilina@eagleeyet.net>> Sent: Wednesday, June 25, 2025 11:41 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>>; Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>> Subject: RE: [SR-Users] Re: kamailio tls module not loading [CAUTION: External email] Do not click links or open attachments unless you recognize the sender and know the content is safe. ___ Hi Timothy, This line is the give all tell all here: 0(1) DEBUG: <core> [core/tcp_main.c:1305]: find_listening_sock_info(): binding to source address 192.168.254.19:5061 failed: [Address in ue] [98] Address in use im guessing that should say. Can you confirm there are no ip conflicts with another container using the same ip address? Regards, Jonathan From: Timothy Delin via sr-users <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Sent: 25 June 2025 03:40 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>>; Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>> Subject: [SR-Users] Re: kamailio tls module not loading Hey John, Apologies on the late reply, was away for the whole week. All your questions have been checked and ruled out. However, I still not able to resolve it. Hence, I decided to approach it differently with manual loadparam loadmodule "tls.so" #modparam("tls", "config", "/etc/kamailio/tls/tls.cfg") modparam("tls", "tls_method", "TLSv1.2+") # Force TLS 1.2+ for all connections modparam("tls","require_certificate",1) modparam("tls","verify_certificate",1) modparam("tls","verify_depth",9) modparam("tls","certificate","/etc/kamailio/tls/certificate.pem") modparam("tls","private_key","/etc/kamailio/tls/private_key.pem") modparam("tls","ca_list","/etc/kamailio/tls/server_cas.pem") Now it is showing that the TLS connectivity exist, but I know can't let the Kamailio docker run properly and I keep receiving this log message 0(1) DEBUG: <core> [core/tcp_main.c:1305]: find_listening_sock_info(): binding to source address 192.168.254.19:5061 failed: [Address in ue] [98] 0(1) DEBUG: tls [tls_server.c:242]: tls_complete_init(): completing tls connection initialization 0(1) DEBUG: tls [tls_server.c:204]: tls_get_connect_server_name(): xavp with outbound server name not found 0(1) DEBUG: tls [tls_server.c:178]: tls_get_connect_server_id(): xavp with outbound server id not found 0(1) DEBUG: tls [tls_server.c:185]: tls_get_connect_server_id(): outbound server id not set Just to confirm, does it mean that I cant be using the TLS listen port and output port the same? Best regards, Timothy From: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>> Sent: Monday, June 16, 2025 6:31 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc: Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>> Subject: Re: [SR-Users] kamailio tls module not loading [CAUTION: External email] Do not click links or open attachments unless you recognize the sender and know the content is safe. ___ Hi there, A few quick questions just to rule out the simple stuff. - I don't see it, but I assume you have added "loadmodule "tls.so"" to the cfg? - In the file: /etc/kamailio/modules/tls.cfg - this points to the path where the certs are - is that path accessible by the kamailio process for read access? (0600 with owner kamailio or 644 with owner root etc) - Correctly named path and cert name as well in the above file? Hope this helps. John. On Mon, 16 Jun 2025 at 10:30, Timothy Delin via sr-users <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> wrote: Hi everyone, I am facing an issue where I cannot load the TLS module in my Kamailio server. I keep receiving this error message "0(1) ERROR: <core> [core/sr_module.c:529]: ksr_locate_module(): could not find module <tls> in </usr/local/lib64/kamailio/modules> 0(1) CRITICAL: <core> [core/cfg.y:4015]: yyerror_at(): parse error in config file /etc/kamailio/modules/tls.cfg, line 1, column 12-19: failed to load module" The Kamailio that I run has this configuration version: kamailio 5.8.6 (x86_64/linux) 6c71d5 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: 6c71d5 compiled on 04:12:34 Jun 6 2025 with gcc 12.2.1 ------------------------------------------------------------------- #global.cfg debug=2 log_stderror=no memdbg=5 memlog=5 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " /* number of SIP routing processes */ children=2 /* Defining interfaces */ #!substdef "!PUBLICIP!$env(PUBLICIP)!" #!substdef "!UDPPORT!$env(UDPPORT)!" #!substdef "!PUBLIC_UDP_SOCKET!udp:PUBLICIP:UDPPORT!" /* Need for TLS Support */ #!substdef "!PUBLIC_TLS_SOCKET!TLS:PUBLICIP:5061!" #!substdef "!COREIP!$env(COREIP)!" #!substdef "!UDPPORT!$env(UDPPORT)!" #!substdef "!CORE_UDP_SOCKET!udp:COREIP:UDPPORT!" #!substdefs "!CORESUBNET!$env(CORESUBNET)!" /* listen addresses */ listen=PUBLIC_UDP_SOCKET listen=CORE_UDP_SOCKET /* Need for TLS Support */ listen=tls:0.0.0.0:5061<https://link.edgepilot.com/s/79616226/8h-IjRzlmUan51PlxuZR2Q?u=http://0.0.0…> #!substdef "!DBUSERNAME!$env(DBUSERNAME)!" #!substdef "!DBPASSWORD!$env(DBPASSWORD)!" #!substdef "!DBHOST!$env(DBHOST)!" #!substdef "!DBNAME!$env(DBNAME)!" #!define DBURL "mysql://DBUSERNAME:DBPASSWORD@DBHOST/DBNAME" #!define HTTP_API_ROUTING_ENDPOINT "https://link.edgepilot.com/s/47dca7bc/8tV4cYQp4UOpnHFQ2B1E6A?u=http://172.1…" ---------------------------------------------------------------- #kamailio.cfg ####### Enable TLS ######## enable_tls=yes ####### Core Modules Section ######## include_file "/etc/kamailio/modules-core.cfg" ####### Global Parameters ######### include_file "/etc/kamailio/globals.cfg" ####### Other Modules Section ######## include_file "/etc/kamailio/modules.cfg" ####### Custom Parameters ######### /* These parameters can be modified runtime via RPC interface * - see the documentation of 'cfg_rpc' module. * * Format: group.id<https://link.edgepilot.com/s/46e1218e/fSZaVF1GX0mM6LO8mQoqWA?u=http://group…> = value 'desc' description * Access: $sel(cfg_get.group.id<https://link.edgepilot.com/s/c2c005e4/uslHdtRDQE6btKKfMLeGzQ?u=http://cfg_g…>) or @cfg_get.group.id<https://link.edgepilot.com/s/c2c005e4/uslHdtRDQE6btKKfMLeGzQ?u=http://cfg_g…> */ ####### Routing Logic ######## include_file "/etc/kamailio/routes.cfg" __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.

2 1

about http server
by mm e 25 Jun '25

25 Jun '25

In kamailio-6.0.x version, there are multiple http servers, such as: XHTTP MICROHTTPD NGHTTP2, which module has the best performance?

2 2

Releasing v6.0.2
by Daniel-Constantin Mierla 25 Jun '25

25 Jun '25

Hello, I am considering to release Kamailio v6.0.2 (out of branch 6.0) on Wednesday, June 25, 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

2 2

kamailio tls module not loading
by Timothy Delin 25 Jun '25

25 Jun '25

Hi everyone, I am facing an issue where I cannot load the TLS module in my Kamailio server. I keep receiving this error message "0(1) ERROR: <core> [core/sr_module.c:529]: ksr_locate_module(): could not find module <tls> in </usr/local/lib64/kamailio/modules> 0(1) CRITICAL: <core> [core/cfg.y:4015]: yyerror_at(): parse error in config file /etc/kamailio/modules/tls.cfg, line 1, column 12-19: failed to load module" The Kamailio that I run has this configuration version: kamailio 5.8.6 (x86_64/linux) 6c71d5 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: 6c71d5 compiled on 04:12:34 Jun 6 2025 with gcc 12.2.1 ------------------------------------------------------------------- #global.cfg debug=2 log_stderror=no memdbg=5 memlog=5 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " /* number of SIP routing processes */ children=2 /* Defining interfaces */ #!substdef "!PUBLICIP!$env(PUBLICIP)!" #!substdef "!UDPPORT!$env(UDPPORT)!" #!substdef "!PUBLIC_UDP_SOCKET!udp:PUBLICIP:UDPPORT!" /* Need for TLS Support */ #!substdef "!PUBLIC_TLS_SOCKET!TLS:PUBLICIP:5061!" #!substdef "!COREIP!$env(COREIP)!" #!substdef "!UDPPORT!$env(UDPPORT)!" #!substdef "!CORE_UDP_SOCKET!udp:COREIP:UDPPORT!" #!substdefs "!CORESUBNET!$env(CORESUBNET)!" /* listen addresses */ listen=PUBLIC_UDP_SOCKET listen=CORE_UDP_SOCKET /* Need for TLS Support */ listen=tls:0.0.0.0:5061 #!substdef "!DBUSERNAME!$env(DBUSERNAME)!" #!substdef "!DBPASSWORD!$env(DBPASSWORD)!" #!substdef "!DBHOST!$env(DBHOST)!" #!substdef "!DBNAME!$env(DBNAME)!" #!define DBURL "mysql://DBUSERNAME:DBPASSWORD@DBHOST/DBNAME" #!define HTTP_API_ROUTING_ENDPOINT "http://172.16.254.30:5000/api/routing" ---------------------------------------------------------------- #kamailio.cfg ####### Enable TLS ######## enable_tls=yes ####### Core Modules Section ######## include_file "/etc/kamailio/modules-core.cfg" ####### Global Parameters ######### include_file "/etc/kamailio/globals.cfg" ####### Other Modules Section ######## include_file "/etc/kamailio/modules.cfg" ####### 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 */ ####### Routing Logic ######## include_file "/etc/kamailio/routes.cfg"

4 7

Dispatcher vs Keepalive
by Sergio Charrua 23 Jun '25

23 Jun '25

Hello all, Just wondering your opinions on this.... The project I'm in uses a REST API to get the routes to relay the call to, and one of the main requirements is whenever an egress gateway is down, inform the REST API about its status, and the same once the gateway is up again. So I was reading the modules docs and was stuck with a question: what would be the best solution to keep track of egress gateways availability? 1 - using Keepalive with DRouting to ping each endpoint's address:port , even though the solution is going to use RTJson with the JSON route list returned from a REST API which makes DRouting virtually useless, unless for using the list of gateways to send OPTIONS too. There is no event:routes to execute every time a gateway is down or up.... 2 - using Dispatcher module to "watch" for each endpoint's availability, and make use of the event:route of the Dispatcher module to inform REST API that the endpoint is down or back up once again. Again, RTJson with the JSON route list returned from the REST API would be used to manage routing. I've done a few tests with Dispatcher, and it was really easy to setup the endpoint "watching" mode as well as the event:routes, but I might give a try on Keepalive if it is the better bet. Would greatly appreciate your opinions and expertise on this. Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

2 2

Fwd: RFC3261 rules
by Sergey Safarov 22 Jun '25

22 Jun '25

Could you look at the attached PCAP with OPTIONS message. When OPTIONS message is received, then Kamailio generates error logs like dropping insane message from 10.140.6.38:60083 After checking the PCAP, I see extra %x00 characters after the OPTIONS message in the same UDP frame. Example [image: image.png] I have checked RFC3261 and do not see a definition of "x00" chars. Also in the same RFC, present a reference to the RFC2234 <https://datatracker.ietf.org/doc/html/rfc2234> where is described "space chars", "white space". According to RFC2223, char %x00 cannot be treated as "space" and should be treated as control (CTL) char. Also, RFC3261 does not use "CTL" chars. Using these two RFC, I can conclude, OPTIONS in the attached PCAP breaks RFC requirements, and we can request partner fix this issue on their equipment. Is anything else in the RFC can be used to justify that the given examples of OPTIONS messages violate RFCs? Sergey

7 10