sr-users June 2022

sr-users@lists.kamailio.org

53 participants
57 discussions

Siremis startup helper service for systemd

by Joseph Goettgens

Hi, I had some difficulties getting Siremis 5.3 to run under Debian 11 Bullseye. It turned out that the problem was the creation of the Siremis socket: <UnixSockLocal name="unixsocklocal" address="/run/siremis/siremis_rpc.sock" timeout="3.0"/> There is a warning in siremisJRCommands.xml that points out that systemd has to be reconfigured as sockets in /tmp are no longer shared (PrivateTmp setting). By the same token, /run/siremis/siremis_rpc.sock cannot be created as the httpd server is not allowed to write to /run, i.e. it can neither create the socket nor the siremis directory. The permanent creation of the siremis directory with suitable access rights is also not possible, since /run is mounted as tmpfs in the default configuration. At least the directory has to be created at boot time, which can be done with a small helper service. This is working for me (siremis-helper.service): [Unit] Description=Siremis Helper Service After=network.target [Service] Type=oneshot ExecStartPre=/usr/bin/mkdir /var/run/siremis ExecStart=/usr/bin/chown www-data:www-data /var/run/siremis [Install] WantedBy=multi-user.target It is enabled the usual way with systemctl "systemctl start --now siremis-helper". Siremis now works with jsonrpc commands and the procedure would mean that installing Siremis on a newer Debian system would definitely require some attention. Does anyone have any objections to the above procedure?

1 year, 10 months

Re-establishment of a closed TCP connection

by Vitalii Krutsitskyi

Hello General overview of the infrastructure: Client (Cisco Hardware) ---> AWS NLB ---> Kamailio Instances The client has a time limit for the opened TCP connections - 10 minutes. This is a hardcoded value that can't not be changed. Regardless of the traffic that flows through the connection, it is closed after 10 minutes. Problem: in case of long-running calls above 10 minutes it is not possible for Kamailio to send back SIP traffic back to the client using the original TCP connection. The client has been asked to either increase the time limit or send SIP reinvites - none of that is possible due to some client's infrastructure limitations. Question: is it possible to force Kamailio to open a new TCP connection and associate it with the call? Client has a 5060 port always opened which can accept incoming connections.

1 year, 10 months

ipops dns_query not working using Kemi

by Thomas de Rooij | CM.com

Hi all, We are trying to do a DNS query using Kemi: KSR.ipops.dns_query(domain, "xyz") The result is always -3. This is returned here: https://github.com/kamailio/kamailio/blob/5.5.4/src/modules/ipops/ipops_pv.… It seems weird to me that the error code is returned because the same non-Kemi code works just fine. Could it be related to this issue: https://github.com/kamailio/kamailio/issues/2052 Thanks. Kind regards, Thomas

1 year, 10 months

remove headers with less than 5 characters with textops

by Patrick Karton

Hello im trying to textops module to remove headers with name length less than 5 characters with regular expression but it seems impossible or the module does not handle $ char remove_hf_re("^.{1,5}$")

1 year, 10 months

Siremis JSONRPC problem on Bullseye

by Joseph Goettgens

Hi, I seem to have a problem setting up Siremis 5.3 on a Debian 11 box using the Kamailio 5.6.0 release (installed from repo). When I enter something like core.uptime into the JSONRPC Command Panel, I get a "System Internal Error" alert. The Apache error log then says: [Mon Jun 06 10:48:41.459377 2022] [php7:notice] [pid 22322] [client 192.168.xxx.xxx:45030] socket bind failed: No such file or directory, referer: http://deb11srv1-kamailio/siremis/sipadmin/jrcmds The path siremis/sipadmin/jrcmds obviously does not seem to exist and I assume that one needs some internal adjustments for some paths. As far as the socket is concerned, siremis/modules/sipadmin/service/siremisJRCommands.xml has the definition: UnixSockRemote name="unixsockremote" address="/var/run/kamailio/kamailio_rpc.sock" timeout="3.0"/> and the corresponding definition in /etc/kamailio/kamailio.cfg is: modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") modparam("jsonrpcs", "dgram_mode", 0666) which looks fine to me. I also checked for the existence of the socket and its access rights. Any suggestions?

1 year, 10 months

t_cancel_callid - doesn't insert Reason header, if called from branch 0

by Pavel Veselovsky

Hallo all, I defined branch_failure routing block via t_on_branch_failure() In the branch_failure route, in case of "408 Request timeout" I am sending CANCEL with reason "t_cancel_callid("$ci", "$cs", "22", "408")". If the t_cancel_callid("$ci", "$cs", "22", "408") is called in branch_failure for branch idx 0, the CANCEL is sent, but Reason header is missing there. Why? (I expect that t_cancel_callid() should insert Reason header regardless of branch it is called from) If the t_cancel_callid is called in branch idx !=0, the CANCEL contains Reason header with cause as expected. Thanks for clarification of this behavior, Pavel. P.S. code snipset: event_route[tm:branch-failure:primary] { if ($T(reply_code) == "408") { if ($avp(branch_idx) == $T_branch_idx) { if (t_cancel_callid("$ci", "$cs", "22", "408")) { xlog("L_INFO", "CANCEL sent ci:$ci, cs:$cs 408"); } else { xlog("L_INFO", "CANCEL not sent ... ci:$ci, cs:$cs 408"); } $var(_palotmp_) = "sip:" + $avp(replaced_cfnry_target_number) + "@" + $dd + ":" + $dp + ";user=phone"; append_branch($var(_palotmp_),"1.0"); t_relay(); return; } } }

1 year, 10 months

Fatal Python error: failed releasing import lock after fork

by Nigel Daniels

The logs appear as follows: Fatal Python error: failed releasing import lock after fork Current thread 0x 7(13) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [srid-62930e67-d-] (0 / 16) kamailio | 00007fe8fb8a4180 (most recent call first): kamailio | <no Python frame> kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tm [ctl handler] kamailio | 7(13) DEBUG: tm [callid.c:136]: child_init_callid(): callid: '06d932e436730fa0-13(a)10.10.0.4' kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tmx [ctl handler] kamailio | 7(13) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: sl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: ctl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: debugger [ctl handler] kamailio | 7(13) DEBUG: debugger [debugger_mod.c:224]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: app_python3 [ctl handler] kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:234]: sr_apy_kemi_exec_func_ex(): execution of method: .info kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:266]: sr_apy_kemi_exec_func_ex(): param[1] for: info is str: ===== kamailio.child_init(-2) kamailio | kamailio | 7(13) INFO: <core> [core/kemi.c:106]: sr_kemi_core_info(): ===== kamailio.child_init(-2) kamailio | 7(13) DEBUG: ctl [ctl.c:329]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x556774893180 kamailio | 7(13) DEBUG: ctl [ctl.c:336]: mod_child(): ctl: 0 io_listen_loop(1, 0x556774893180) kamailio | 7(13) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) kamailio | 7(13) DEBUG: ctl [io_listener.c:245]: io_listen_loop(): io_listen_loop: adding socket 8, type 2, transport 3 (/var/run/kamailio//kamailio_ctl) kamailio | 7(13) DEBUG: ctl [../../core/io_wait.h:374]: io_watch_add(): processing io_watch_add(0x7fe8f9aef380, 8, 2, 0x556774893180) - fd_no=0 Running python 3.8.10 using the suggested. # ----------------- setting module-specific parameters --------------- # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) ####### Routing Logic ######## modparam("app_python3", "load", "/opt/kamailio/etc/kamailio.py") cfgengine "python"a import sys import KSR as KSR def dumpObj(obj): for attr in dir(obj): KSR.info("obj.%s = %s\n" % (attr, getattr(obj, attr))) def mod_init(): KSR.info("===== from Python mod init\n") dumpObj(KSR) return kamailio() class kamailio: def __init__(self): KSR.info('===== kamailio.__init__\n') def child_init(self, rank): KSR.info('===== kamailio.child_init(%d)\n' % rank) return 0 def ksr_request_route(self, msg): KSR.info("===== request - from kamailio python script\n") KSR.setdsturi("sip:alice@127.0.0.1:5080") KSR.tm.t_on_branch("ksr_branch_route_one") KSR.tm.t_on_reply("ksr_onreply_route_one") KSR.tm.t_on_failure("ksr_failure_route_one") KSR.sl.send_reply(100, "Trying") if KSR.tm.t_relay() < 0 : KSR.sl.send_reply(500, "Server error") return 1 def ksr_reply_route(self, msg): KSR.info("===== response - from kamailio python script\n") return 1 def ksr_onsend_route(self, msg): KSR.info("===== onsend route - from kamailio python script\n") return 1 def ksr_branch_route_one(self, msg): KSR.info("===== branch route - from kamailio python script\n") return 1 def ksr_onreply_route_one(self, msg): KSR.info("===== onreply route - from kamailio python script\n") return 1 def ksr_failure_route_one(self, msg): KSR.info("===== failure route - from kamailio python script\n") return 1 Any help is appreciated, thanks. -- - Nigel

1 year, 10 months

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 June 2022