sr-users July 2025

sr-users@lists.kamailio.org

44 participants
33 discussions

Basic Configuration
by smh2017＠zoho.com 23 Jul '25

23 Jul '25

I am trying to set up a very basic SIP server. I can only establish external-to-internal calls using the following parameters with the default configuration files: RTP Engine Config File interface=server_local_ip!public_domain_name Kamailio Config File alias="public_domain_name" listen=server_local_ip:5061 adverise public_domain_name:5061 I cannot establish internal-to-external calls nor external-to-external calls with the above configuration settings. In these failed calls, the answering external callee UA sends 200-OK, but the caller UA does not ACK. In looking at the sip trace messages, no alias for the public ip address is appended to the Contact header of the external UA's 200-OK SIP message. So perhaps the caller doesn't know where to send the ACK. The network setup has the local UAs and the Kamailio server behind a port-forwarded NAT routher. External (internet) UAs are also behind NAT routers. Is there a change or addition to the above config snippets that would solve the problem, or do I need to add some instruction to the routing section? Finally, does anyone sell or otherwise offer basic Kamailio/RTPEngine configuration files that work more or less "out-of-the box" for the described setup? Thanks, Steve Hamilton

2 3

Error: different number of preprocessor directives
by Fernando Lopes 23 Jul '25

23 Jul '25

Hello everyone, I'm having an issue with my Kamailio config where I'm getting the following error: ERROR: bad config file (0 errors) (parsing code: 0) 0(2) ERROR: <core> [core/ppcfg.c:276]: pp_ifdef_level_error(): different number of preprocessor directives: 1 more #!if[n]def as #!endif I've gone through the config up and down so many times and can't seem to find the problem. I have a definitions.cfg file where I define all the variables, and I’ve made sure that every #!ifdef WITH_SOMETHING has a corresponding definition. I also ran this command (recommended by GPT): grep -E '#!ifn?def|#!endif' /usr/local/etc/kamailio/kamailio.cfg It shows matching numbers of #!ifdef and #!endif, and I’ve checked it manually several times — everything looks fine. Any tips for debuging or finding the problem. #!ifdef WITH_CDRS #!endif #!ifdef WITH_DEBUG #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_FAIL2BAN #!ifdef WITH_ANTIFLOOD #!endif #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_RESPONSE_STATS #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_CDRS #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_HTTP #!endif #!ifdef WITH_WEBSOCKETS #!endif #!ifdef WITH_NAT #!ifdef WITH_RTPENGINE #!endif #!endif #!ifdef WITH_TLS #!endif #!ifdef WITH_ANTIFLOOD #!endif #!ifdef WITH_FAIL2BAN #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_CDRS #!endif #!ifdef WITH_FAIL2BAN #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_HOMER #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_ANTIFLOOD #!endif #!ifdef WITH_NATSIPPING #!endif #!ifdef WITH_NOAUTH_PRIVATE_NET #!endif #!ifdef WITH_AUTH #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_NAT #!endif #!ifdef WITH_RTPENGINE #!endif #!ifdef WITH_DISPATCHER #!endif #!ifdef WITH_WEBSOCKETS #!endif #!ifdef WITH_HTTP #!ifdef WITH_WEBSOCKETS #!endif #!endif #!ifdef WITH_RTPENGINE #!endif Thank you.

5 4

kamailio 5.8.6 sanity problem
by ale Gural 23 Jul '25

23 Jul '25

Hello, when kamailio 5.8.6 got the follow SIP message. INVITE sip:026774800@kamnet:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.25.206.73:5060;branch=z9hG4bK6204h710copg0h2s34a0.1 From: <sip:506555021@kamnet :5060;transport=UDP;user=phone>;tag=BN-1778920881-1-1752995491-343935404 To: <urn:service:sos.police@kamnet> Call-ID: 5f6d530-13f3cbf9-fb215-7f1546651f58-4d0f660a-13c4-764 CSeq: 1 INVITE X-SessionId: -1778920881 User-Agent: BN4000-3.9.2-706 Max-Forwards: 60 Supported: norefersub,timer,100rel,199 P-Asserted-Identity: <sip:506555021@hotmobile.co.il:5060 ;transport=UDP;user=phone> P-Asserted-Identity: <tel:506555021;phone-context=+972> Contact: <sip:10.25.206.73:5060;yop=00.00.84CE62D9.0000.7009;transport=udp> P-Early-Media: supported P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=425074efe02c6a01 Content-Disposition: session;handling=required Allow: INVITE,CANCEL,ACK,BYE,OPTIONS,INFO,PRACK,UPDATE,REFER,NOTIFY Content-Type: application/sdp Content-Length: 207 v=0 o=BN4000 0 0 IN IP4 10.9.21.56 s=- c=IN IP4 10.9.21.56 t=0 0 m=audio 54732 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=maxptime:20 a=ptime:20 the TO To: <urn:service:sos.police@kamnet>, the problem is kamailio 5.8.6 response with 400 bad to header but kamailio 5.7.5 continue with normal call. here you can see the sanity log for both kamailio: kamailio 5.8.6 Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:254]: check_ruri_sip_version(): check_ruri_sip_version entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:278]: check_ruri_sip_version(): check_ruri_sip_version passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:286]: check_ruri_scheme(): check_ruri_scheme entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:305]: check_ruri_scheme(): check_ruri_scheme passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:327]: check_required_headers(): check_required_headers entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:350]: check_required_headers(): check_required_headers passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:519]: check_cseq_method(): check_cseq_method entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:553]: check_cseq_method(): check_cseq_method passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:563]: check_cseq_value(): check_cseq_value entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:591]: check_cseq_value(): check_cseq_value passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:601]: check_cl(): check_cl entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:626]: check_cl(): check_cl passed Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:643]: check_expires_value(): check_expires_value entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:679]: check_expires_value(): no expires header found Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:776]: check_parse_uris(): check_parse_uris entered Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:780]: check_parse_uris(): parsing ruri Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:793]: check_parse_uris(): looking up From header Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: sanity [sanity.c:808]: check_parse_uris(): looking up To header Jul 20 17:08:15 vm-tkamprov-n 671587 DEBUG: <core> [core/parser/parse_uri.c:1369]: parse_uri(): bad char '@' in state 5 parsed: <urn:service:sos.police> (22) / <urn:service:sos.police@kamnet> (29) Jul 20 17:08:15 vm-tkamprov-n 671587 ERROR: <core> [core/parser/parse_to.c:81]: parse_to_uri(): failed to parse To uri Jul 20 17:08:15 vm-tkamprov-n 671587 WARNING: sanity [sanity.c:810]: check_parse_uris(): invalid To header or uri kamailio 5.7.5 Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:253]: check_ruri_sip_version(): check_ruri_sip_version entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:277]: check_ruri_sip_version(): check_ruri_sip_version passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:285]: check_ruri_scheme(): check_ruri_scheme entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:304]: check_ruri_scheme(): check_ruri_scheme passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:326]: check_required_headers(): check_required_headers entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:349]: check_required_headers(): check_required_headers passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:518]: check_cseq_method(): check_cseq_method entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:552]: check_cseq_method(): check_cseq_method passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:562]: check_cseq_value(): check_cseq_value entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:590]: check_cseq_value(): check_cseq_value passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:600]: check_cl(): check_cl entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:625]: check_cl(): check_cl passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:638]: check_expires_value(): check_expires_value entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:674]: check_expires_value(): no expires header found Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:771]: check_parse_uris(): check_parse_uris entered Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:775]: check_parse_uris(): parsing ruri Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:788]: check_parse_uris(): looking up From header Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:803]: check_parse_uris(): looking up To header Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity.c:853]: check_parse_uris(): check_parse_uris passed Jul 20 17:00:51 vm-tkamprov-n 662105 DEBUG: sanity [sanity_mod.c:252]: w_sanity_check(): sanity checks result: 1 Thanks

3 3

Configure TLS 1.3 cipher suites
by caique.cornelio＠mitel.com 22 Jul '25

22 Jul '25

Is the removal of a specific TLS 1.3 cipher supported as today? I am working on making the ciphers accepted configurable and i know it is possible with TLS <1.2, wondering if it is the same case with 1.3.

3 2

Best Book Recommendation for Learning SIP/VoIP
by Fernando Lopes 22 Jul '25

22 Jul '25

Hi everyone, I'm not new but also not a professional to the world of SIP and VoIP but feeling lost, and I'm looking to get a solid foundational understanding. I was wondering if anyone could recommend a good book that explains SIP in a clear and practical way? Whether it's a textbook, a practical guide, or even an eBook, I’d really appreciate your recommendations! Thanks in advance!

4 3

Setting Via IP inside script logic
by Nick Jones 22 Jul '25

22 Jul '25

G'day all, I'm working on a scenario with a Kamailio box with a private IP, with a public IP 1:1 NATed to it (but the VM does not see the public IP on the NICs). When forwarding requests to some hosts I want to set the Via address to be the public IP, but when forwarding requests to other hosts I want to leave the Via address to the internal IP address. If I set the `Advertise` parameter in the bind config, this sets the Via to the advertised IP, but I'm seeing that address used even when communicating with hosts on the private IP. Of course if the IP was on the VM itself I could use $fs or force_send_socket, but that only works if I've got the public IP bound, which I can't do. Is there a simple way to set / override what IP gets baked into the Via header? Cheers, Nick

3 3

Kamailio as a Stateless Smart SIP Proxy
by Antonio 19 Jul '25

19 Jul '25

Hi everyone, Do we have a ready-to-use Kamailio role or configuration for: *“Kamailio as a Stateless Smart SIP Proxy”*, Specifically one that uses *Contact Header Encoding*? That is — a proxy where Kamailio does not store registration state, but encodes the client’s IP and port into the Contact header during REGISTER , and later decodes it from the INVITE to forward the call back to the client. Thanks in advance! -- *Antony* satskiy.a(a)gmail.com

4 7

TLS certificates kamailio & Asterisk
by Fernando Lopes 18 Jul '25

18 Jul '25

Hello everyone, I have a quick question. I'm working on a local project where Kamailio acts as a proxy and Asterisk handles the media. Both are running in separate Docker containers. For tls communication between the two, should I generate a separate TLS certificate for each container, or create only one certificate and use it for both? Thanks in advance!

2 1

cannot clone xavi from non existing parsed_pv_headers
by Mathias Schneuwly 18 Jul '25

18 Jul '25

Hi I'm getting the error "Jul 15 15:15:54 ttel /usr/sbin/kamailio[812316]: ERROR: {1 382 BYE 860005579-5060-39(a)BA.A.B.BCJ} pv_headers [pvh_xavp.c:485]: pvh_clone_branch_xavi(): cannot clone xavi from non existing parsed_pv_headers" on BYE messages. Interestingly, only on the first attempt to read the from user. I have the following snippet in my `ksr_branch_manage` KSR.log('notice', f'ksr_branch_manage: 1') KSR.log('notice', f'ksr_branch_manage: 2: {KSR.pv.get('$x_fU')}') KSR.log('notice', f'ksr_branch_manage: 3: {KSR.pv.get('$x_fU')}') The result in the log is Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE 1640171511-5060-41(a)BA.A.B.BCJ} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 1 Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: ERROR: {1 402 BYE 1640171511-5060-41(a)BA.A.B.BCJ} pv_headers [pvh_xavp.c:485]: pvh_clone_branch_xavi(): cannot clone xavi from non existing parsed_pv_headers Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE 1640171511-5060-41(a)BA.A.B.BCJ} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 2: 200102 Jul 15 15:25:03 ttel /usr/sbin/kamailio[816424]: NOTICE: {1 402 BYE 1640171511-5060-41(a)BA.A.B.BCJ} <core> [core/kemi.c:155]: sr_kemi_core_log(): ksr_branch_manage: 3: 200102 Even if there is an ERROR, it seems to be able to read the from user from pv_headers. Is this error just informative and uses the wrong severity, or what does it mean? I have no modparam for pv_headers. It uses the default configuration and I'm on 5.8.6. Regards Mathias

1 1

TOPOS module routing loop with rogue Route headers
by David Tek 17 Jul '25

17 Jul '25

Hello, Setup: I activated the TOPOS module in my setup that looks something like this: SIP Device ---> Proxy1(w/ topos) ---> Proxy2(no topos) ---> ??? ---> Freeswitch. I am using Kamailio 6.0.1 (or 6.0.2, not sure). Both my proxies and the other nodes I don't control in ??? part all add Record-Route/Route headers for in-dialog requests. So an INVITE coming from the SIP Device will go through these proxies, on the 200 OK there are 3+ Record-Route headers which are consumed by TOPOS on Proxy1. With my baresip and Yealink phones, the phones send a 200 OK with NO Route headers and the Route headers are readded by the TOPOS module before it hits the routes in kamailio. Problem: Some SIP devices(I used an older Aastra device to reproduce the issue) like to add a Route header with the target proxy, and so Kamailio receives something like this(some headers stripped for brevity): ACK sip:atpsh-68769b30-2b-1@192.168.0.25 SIP/2.0 Via: SIP/2.0/UDP 192.168.34.122:5060;branch=z9hG4bKe3a6fe355f721ae5b Route: <sip:banana.mydomain.tld;lr> From: "12015550000" <sip:12015550000@banana.mydomain.tld>;tag=ba05cb9826 To: <sip:13105550000@banana.mydomain.tld:5060;user=phone>;tag=1SvNyXFeQjUaN Call-ID: 149a3a344dda2a1c CSeq: 12259 ACK With this, Kamailio receives the packet, internally somewhere runs the myself check and sees banana.mydomain.tld isn't a local domain. So it routes to that domain, which happens to resolve to this same Kamailio. So Kamailio routes the packet to itself until Max-Forwards hits 0 and fails. Solutions I tried: So I thought maybe alias_subdomains would help here: loadmodule "corex.so" modparam("corex", "alias_subdomains", "mydomain.tld") I ran this and found that it fixed the routing loop on the ACK, but then I got a routing loop on the BYE instead. So then I thought, maybe I can squeeze this out earlier: event_route[topos:msg-incoming] { if ( proto != TLS || !$tls_peer_verified || $Rp != "5061" ) { xlog("L_NOTICE", "=======> User packet this one $rm\n"); remove_hf("Route"); } else{ xlog("L_NOTICE", "=======> Server packet this one $rm\n"); } This didn't work, it only ever is invoked for SIP OPTIONS. So I tried with event_route[topos:msg-receiving] and saw messages like this: 16(1347) CRITICAL: <core> [core/ip_addr.c:234]: ip_addr2sbuf(): unknown address family 0 I guess $Rp isn't available in this event route. and $proto is always null. If I disable TOPOS completely, the Aastra phone will load the ACK with the Route headers defined by the Record-Route headers in the 200 OK and the call completes normally. I added this to the top of my request_route: xlog("L_NOTICE","$si - $rm - $hfl(Route) $hfl(Via)\n"); and the only route header that appeared for the ACK packet was the single route header. It would seem TOPOS can be 'defeated' by a rogue Route header. I started reading through the source code on this but could not pinpoint any code that would 'not restore TOPOS stripped headers when a rogue Route header appears because the Route header doesn't match the myself condition of Kamailio'. I even tried adding to topos:msg-sending: append_hf("Route: <sip:invalid.tld>\r\n"); To trick the phone into something that is predictable so I can strip it before TOPOS parses the headers. I'm not sure what to do next, I don't want to go back to TOPOH because I need the packet size savings(some users have issues with big packets ). I've seen other user-agents in the wild beyond these Aastras add Route headers in unexpected places, so this is not a single issue. I even went so far as to ask AI some help, but it just hallucinated the entire time. (AI says this should say 'I also explored AI assistance but didn't find relevant solutions for this specific scenario.' ). Any suggestions on what to do next ? Thanks, David

1 1

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 July 2025