sr-users May 2026

sr-users@lists.kamailio.org

21 participants
18 discussions

Postgres connections optimization #4342
by Stephane Savonitto 11 Jun '26

11 Jun '26

Hello, On P-CSCF when running we have 200+ permanent connection to postgres db, even if there is no traffic. Is there a way to manage connections dynamically using a pool like using PgBouncer ? Regards, Stéphane

5 9

Question on NAT usage and Record Route
by Martin Nyström 29 May '26

29 May '26

HI, Our outbound traffic from Kamailio pass via Amazon NAT Gateway. The issue is that the NAT Gateway provided by AWS clears its table after 350s. This causes INVITE refresh after 900s to fail because the PBX sends the SIP to the Amazon NAT Gateway source IP : port and it is dropped by the NAT Gateway since the session do no longer exists. It appears we cannot change the AWS NAT Gateway timeout, so we either need to drastically reduce the timer setting which I do not want, or find another way. Can we in the signalling tell the PBX to reply not to the source ip and port but instead directly to the Kamailio FQDN? I am thinking Record Route would solve this, but before I start fiddling with it I’d like some feedback from the experts if that is the way. We’re using Kamailio 6.1 with 5061/TLS. /M

1 2

pull request planned for htable module
by Valentin Christoph 29 May '26

29 May '26

Hi all, We have implemented a few improvements/additions around the htable RPC commands for our own purposes, mainly to support runtime configuration, export/import and persistence handling for htable data. Most of the changes are: • New ‘htable.help’ command • Support for dumping htable content to a file – via ‘htable.dump <table> [path]’ • New ‘htable.load_from_file’ command to load htable entries from a file • Support for ‘htable.store all’ and ‘htable.store all force’ Since the changes are relatively large and require some documentation updates, we wanted to ensure first whether these kinds of changes are wanted for Kamailio. Any hint is welcome. Kind regards, Christoph

3 4

6.1.2 content of $avp being zapped after setting $sht
by Benoît Panizzon 28 May '26

28 May '26

Hi Gang Just updated our dev plattform from 5.8 to 6.1 Now I have $avp variables loosing their content. xlog("L_INFO", "$cfg(route): 4 DEST: $avp(destination_e164) \n"); $sht(custprof=>$var(get_custprofileid)) = $var(xcustprof); xlog("L_INFO", "$cfg(route): 5 DEST: $avp(destination_e164) \n"); 2026-05-22T15:43:25.346183+00:00 dev-core01 kamailio[7543]: INFO: [1 044400xxxx SDc1pa001-4e1ed786dd4928cd90b8b72f465d372a-tc8lgn3 10198 INVITE]<script>: GET_CUST_PROFILE: 4 DEST: +41800800800 2026-05-22T15:43:25.346221+00:00 dev-core01 kamailio[7543]: INFO: [1 044400xxxx SDc1pa001-4e1ed786dd4928cd90b8b72f465d372a-tc8lgn3 10198 INVITE]<script>: GET_CUST_PROFILE: 5 DEST: <null> Did I perhaps miss something during upgrade? I consulted: https://www.kamailio.org/wikidocs/install/upgrade/ -- 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 9

Kamailio v6.1.3 Released
by Daniel-Constantin Mierla 27 May '26

27 May '26

Hello, Kamailio SIP Server v6.1.3 stable release is out. This is a maintenance release of the latest stable branch, 6.1, that includes fixes since the release of v6.1.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v6.1.x. Deployments running previous v6.1.x versions are strongly recommended to be upgraded to v6.1.3. For more details about version 6.1.3 (including links and guidelines to download the tarball or from GIT repository), visit: - https://www.kamailio.org/w/2026/05/kamailio-v6-1-3-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 v6.1.3
by Daniel-Constantin Mierla 27 May '26

27 May '26

Hello, the release of Kamailio v6.1.3 (out of branch 6.1) is considered to be done on Wednesday (May 27) or Thursday (May 28), 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 World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

2 2

uac_replace_to() generates double angle brackets in To header when display name is used in kamailio 6.1.2
by descartin＠bts.io 27 May '26

27 May '26

Hello, I am seeing a possible issue with `uac_replace_to()` in Kamailio 6.1.2. Version: ```text kamailio 6.1.2 (x86_64/linux) 1b2dad-dirty ``` I am calling `uac_replace_to()` passing both a display name and a To URI. ```text DEBUG: uac [uac.c:588]: ki_replace_to(): dsp=0x7ffca81777a0 (len=15) , uri=0x7ffca81777b0 (len=41) DEBUG: uac [replace.c:341]: replace_uri(): adding new display ["+818067029073"] DEBUG: uac [replace.c:368]: replace_uri(): uri to replace [sip:818067029073@10.100.10.19:5065] DEBUG: uac [replace.c:369]: replace_uri(): replacement uri is [sip:+818067029073@10.100.10.91;user=phone] DEBUG: uac [replace.c:434]: replace_uri(): Stored <_uac_to> var in dialog with value sip:818067029073@10.100.10.19:5065 DEBUG: uac [replace.c:454]: replace_uri(): Stored <_uac_tonew> var in dialog with value sip:+818067029073@10.100.10.91;user=phone DEBUG: uac [replace.c:468]: replace_uri(): Stored <_uac_tdp> var in dialog with value DEBUG: uac [replace.c:483]: replace_uri(): Stored <_uac_tdpne> var in dialog with value "+818067029073" ``` The replacement seems to work internally, but the outgoing INVITE sent to the callee contains double angle brackets in the `To` header. The resulting header is: ```text To: "+818067029073" <<sip:+818067029073@10.100.10.91;user=phone>> ``` And I get the folloing error when processing the response from UAS ``` May 19 03:42:19 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[3562]: ERROR: <core> [core/parser/parse_addr_spec.c:754]: parse_addr_spec(): unexpected char [</60] in status 5: [+818067029073 <] . May 19 03:42:19 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[3562]: ERROR: <core> [core/parser/parse_to.c:56]: parse_to_body(): bad to header May 19 03:42:19 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[3562]: ERROR: <core> [core/parser/msg_parser.c:342]: parse_headers(): bad header field [To: +818067029073 <<sip:+818067029073@10.100.10.91;user=phone>>;tag=1803SIPpTag011 May 19 03:42:19 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[3562]: ERROR: <core> [core/receive.c:398]: receive_msg(): parsing relevant headers failed May 19 03:42:19 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[3562]: ERROR: <core> [core/receive.c:558]: receive_msg(): required headers not found in reply ``` If a pass the replace uri enclosed in brackets (<sip:+818067029073@10.100.10.91;user=phone>), then i obtain a To header with triple <....> and I get the folowing error processing the response from callee ```text May 19 03:43:31 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[4136]: ERROR: <core> [core/parser/parse_to.c:56]: parse_to_body(): bad to header May 19 03:43:31 ip-10-100-10-19 /usr/local/kamailio/sbin/kamailio[4136]: ERROR: <core> [core/parser/msg_parser.c:342]: parse_headers(): bad header field [To: +818067029073 <<<sip:+818067029073@10.100.10.91;user=phone>>>;tag=1803SIPpTag012 ``` Is this a known issue in 6.1.2, or am I passing the URI/display name in the wrong format? From the debug logs, the replacement URI appears to be stored without angle brackets, but the final generated `To` header contains: ```text <<sip:+818067029073@10.100.10.91;user=phone>> ``` Thanks in advance. David Escartín

2 4

Re: uac_replace_to() generates double angle brackets in To header when display name is used in kamailio 6.1.2
by David Escartín 27 May '26

27 May '26

Hi, I think I found the reason for the double angle brackets issue I reported. From what I can see, starting with Kamailio 6.1, uac_replace_to() seems to handle the To URI as a name-addr and automatically wraps the URI in angle brackets when needed. So, for example, if the original header does not contain a display name: To: sip:1234@example.com and I call something like: uac_replace_to("sip:5678@example.com"); Kamailio 6.1 generates the expected result: To: <sip:5678@example.com> This means that we no longer need to force a display name before calling uac_replace_to() just to make the header use the <sip:...> format. The double angle brackets I was seeing were caused by my own configuration in one of our AWS test machines. I had a workaround there that manually added < > around the URI for cases where the To header had no display name. With Kamailio 6.1, uac_replace_to() was then adding the brackets again, resulting in: To: <<sip:5678@example.com>> Sorry for the noise, and thanks for the help. Best regards, David David Escartín Vice President Systems Programming bts.io | LinkedIn+34 976214883 Edificio Tecnológico Cines Goya. C. Josefa Amar y Borbón 10, Planta 3, Zaragoza

1 0

Change of email
by Jonathan Aquilina 22 May '26

22 May '26

Good Morning, What do I need to do in order to change my email address that is subscribed to this list with. Regards, Jonathan

2 1

Predictable nat keepalive OPTIONS from server
by Jon Bonilla (Manwe) 22 May '26

22 May '26

Hi I'm experiencing an issue when trying to keep open the natted registrations of the phones. It happens since upgraded from 5.6 to 6.0 The modparams in 5.6: modparam("usrloc", "timer_interval", 30) modparam("nathelper", "natping_interval", 0) The modparams are these in 6.0: modparam("usrloc", "timer_interval", 30) modparam("usrloc", "ka_interval", 20) modparam("usrloc", "ka_randomize", 5) modparam("nathelper", "natping_interval", 0) I let the ursloc ka system to send the keepalives. It does send them every 30 seconds with that configuration but the first one after the REGISTER can take a minute and by that time some routers have closed the port and the OPTIONS don't make it to the phone. Is there a way to ensure that the first OPTIONS is sent before 30 seconds have elapsed since the REGISTER? Should I keep both ka and nathelper mechanisms? cheers, Jon

3 3

2026

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 May 2026