sr-users December 2023

sr-users@lists.kamailio.org

33 participants
34 discussions

Regretfully we were unable to process the URI
by Gavin Baumanis 18 Dec '23

18 Dec '23

Hi Everyone, Very new to SIP And to Kamailio Configuration / administration. I have a working AWS instance with Kamailio installed on it - and it works fine. We are creating a whole new environment and I have cloned the existing AWS EC2 instances. I have edited all the configs to ensure that they are using the correct DNS names and / or IP addresses. Otherwise the "configs" are identical. While attempting to call a SIP number, I get the following message, returned to the soft phone I am using (microSIP) *Regretfully we were unable to process the URI (479/SL)* I can also see the same error message in the console of the Kamailio server. I am hoping that this might mean something to someone enough - to suggest some troubleshooting steps, please. Thanks;

3 3

Encoded Call-ID - Topoh module
by Vanderlei Torres Batistela 15 Dec '23

15 Dec '23

Hello all, How can I get the encoded Call-Id generated by TOPOH module to store in the CDR ? Regards, Vanderlei

2 1

{uri.duri} not working
by hanxiaofang＠x-y-t.cn 13 Dec '23

13 Dec '23

Hi Kamailio experts, OS: Debian11 Kamailio ver: 5.7.3 {uri.duri} doesn't seem to work The following script can be reproduced: ``` debug=2 log_stderror=yes # mpath="/usr/local/lib/kamailio/modules/" loadmodule "tm.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "ctl.so" loadmodule "htable.so" modparam("tm", "failure_reply_mode", 3) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 120000) request_route { xinfo("*** $sel(msg)\n"); sl_send_reply("404", "Not here"); exit; } event_route[htable:mod-init] { $var(ouri) = "sip:alice@server.com:5060;nat=yes;transport=tcp;line=xyz"; $var(duri) = $(var(ouri){uri.duri}); # => "sip:server.com:5060;transport=tcp" xinfo("ouri = $var(ouri)\n"); xinfo("duri = $var(duri)\n"); if ($var(duri) == "sip:server.com:5060;transport=tcp" ) { xinfo("uri.duri work well\n"); } else { xerr("something is wrong\n"); } } ```

2 4

Proxy Inactivity and Kamailio Log Disruption Issue.
by satyaprakash ch 12 Dec '23

12 Dec '23

HI, Scenario: We possess 2 proxies and 2 registrar servers equipped with dmq functionality. Unexpectedly, one of the Proxy IP addresses was marked as inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease responding. Simultaneously, Kamailio logs stopped recording any activity. Upon restarting the Kamailio service, the problem was resolved, and the proxy resumed normal operation, with the Flag changing back to AP (ACTIVE). The sudden occurrence of this issue is not clear, and due to the cessation of logs during the incident, we lack information for the investigation. Any suggestions on how to address this issue would be appreciated. And is this scenario happened to any one in your experience?

2 3

usrloc ka_mode - Flooding OPTIONS at same time?
by Benoit Panizzon 12 Dec '23

12 Dec '23

Hi We have reached 20000 registered CPE and start facing issues. Am I observing correctly that when ka_mode 4 is enabled, OPTIONS are send simultaneously to all registered CPE and not spread over the interval? They could be the cause very high pps peaks on network equipment? If so, is there a way to spread the ka options over time so they don't cause such high peaks? Or even better, is there a way to enable them for only some customers via a variable? 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 ______________________________________________________

4 5

is_method_f(): cannot parse cseq header in xhttp:request event route?
by Benoît Panizzon 12 Dec '23

12 Dec '23

Hi all I use event_route[xhttp:request] on Kamailio 5.5 Every time a xhttp request is processed I get this log entry: ERROR: textops [textops.c:3541]: is_method_f(): cannot parse cseq header Almost identical config on Kamailio 5.6 does not show this error. Is that something that got fixed in 5.6? I see a change in the documentation, While 5.5 does not state $rm can be accessed, 5.6 states $rm contains the HTTP method. Or do I somehow leak the http request to somewhere I call is_method() on it after terminating the event route? How should the event_route[xhttp:request] properly be terminated? With 'return' or with 'exit'? -- 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

Upgrade Minor versions
by Gavin Baumanis 11 Dec '23

11 Dec '23

Hi there, I have taken over a project that uses Kamailio. I am aware of what we use it for - I am just not sure on the how... apart from what I have read in the docs. We're currently running 5.4.2 and I'd like to upgrade to (at least) the latest 5.4 offering - as that seems as if it would be the easiest and safest option. So I am hoping I might get some direction, please - on the way forward for an upgrade. The documentation seems OK if you're upgrading minor versions... but I couldn;t find anything about upgrading patch versions. Thanks!

2 2

Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023
by Daniel-Constantin Mierla 05 Dec '23

05 Dec '23

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 (5.8 or 6.0)? If considered useful, I propose Dec 5 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 PS: Previous announcement indicated the start time 14:30 UTC, this message changes it to 15:00 UTC - 30min later due to a constraint in availability of one of the Kamailio developers. -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 3

stats.get_statistucs dialog: counter over/underrun?
by Benoit Panizzon 05 Dec '23

05 Dec '23

Hi List Kamailio 5.5 # kamcmd stats.get_statistics dialog: dialog:active_dialogs = 17 dialog:early_dialogs = 18446744073709551615 dialog:expired_dialogs = 0 dialog:failed_dialogs = 31198 dialog:processed_dialogs = 107519 Where could this early_dialog value come from? 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

Setting up Kamailio as SIP Proxy
by Saul Ibarra 04 Dec '23

04 Dec '23

Hi, I am needing some help setting up kamailio as a sip proxy between a provider(trunk) and a test pbx The trunk requires username&password and i would like to add that information to the request within the Kamailio proxy, so that the PBX can authenticate directly by IP (without username&password) through the Kamailio proxy. As a programmer with a limited background in SIP (currently learning), I am keen on understanding the intricacies of this setup at the SIP level. Could you please direct me to resources or documentation that covers scenarios similar to mine? Any help or guidance you could provide would be greatly appreciated. Thanks

4 8

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 December 2023