sr-users

sr-users@lists.kamailio.org

34 participants
37388 discussions

Fatal Python error: failed releasing import lock after fork
by Nigel Daniels 06 Jun '22

06 Jun '22

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

2 3

SNMP, export concurrent calls count
by ZZ Wave 30 May '22

30 May '22

Hello. Debian 10, Kamailio 5.2.1 I want to monitor concurrent calls in/out per every trunk connected to this proxy (it's done with dialog profiles), and export this to Zabbix. But I can't find in snmpstats documentation how to export user-defined variables. Help me please. Maybe SNMP isn't the best solution for that...

2 1

Centos kamailio.repo file is not updated
by Patrick Wakano 30 May '22

30 May '22

Hello ist, I've noticed some of the latest releases do not have their repo mentioned in the https://rpm.kamailio.org/centos/kamailio.repo The repos are there, it is just the kamailio.repo file missing some of the newer versions like 5.4.7, 4.5.8, 5.5.4, 5.6.0... Cheers, Patrick

3 3

Fedora RPMs
by Tim Anderson 30 May '22

30 May '22

Hi, I can't find any RPMs for Fedora 35 or 36. Have they moved somewhere other than rpm.kamailio.org? Regards, Tim

3 2

DNS Failover try next destination on receiving code other than 503
by Patrick Karton 30 May '22

30 May '22

Hello, im using DNS Failover and everything works well except i would like to try other resolved ips when i receive a 408 from the previous ones As far as i know only a received 503 will trigger next destinations and there is no config parameters in tm module to handle that behaviour. so how can i implement it ? set a failure route before relay and just call t_relay() after again ? also is there a way in failure route to know how many destinations are left to exit failure route. Thanks for help.

2 3

KEMI Python Syntax
by Olivier Roy 30 May '22

30 May '22

Hello, I am writing some Kamailio scripts using app_python3. I understand that the KSR module is automatically generated by Kamailio. So when I import KSR from KSR I don't get any syntax from my IDE since it doesn't know where KSR is. My question: is there a way to generate a KSR.py file that can be used for autocompletion and syntax highlighting? Thanks. Olivier

2 1

get and store destination ip address and port that the request will be sent to
by Patrick Karton 30 May '22

30 May '22

Hello is there a way or pseudo var to get ip address & port that the request will be sent to and save it in to another variable. i want a way to get it to store it. im not able to save it with to_ip and to_port of the onsend_route. TThanks.

2 1

Find Values in User part of Diversion URI
by Lewis Hutchinson 30 May '22

30 May '22

Sorry if this is a super basic ask but I can't seem to work it out, I have got a work around but for my own sanity wanted to post the question on here. In Kamailio Native 5.5.2 I want to be able to look into this field $(di{uri.user}) and "find" or see if it "contains" a value i.e Diversion: "TEST" sip:112233445566@xxx.xxx.xxx.xxx;user=phone; find 234 or contains 234 I know how to do this in in KEMI Python but for the life of me cant get my head around it in Native. 2ndly is there an opposite to {s.numeric} Removes all non-numeric parts of string. I want the ability to strip all numeric parts. Keep us the good work. Lewis

3 4

TLS connection failure. Not sure if system behavior is correct.
by Володимир Іванець 27 May '22

27 May '22

Hello all! My test Kamailio setup (now updated to version 5.5.4) that was working with MS Teams some time ago, now stopped :) I was wondering if someone could tell me if the current behavior is correct or if there is a problem? Here is a screenshot of the packet capture: [image: image.png] I thought that after MS Teams side sent Change Cipher Spec request, Kamailio should respond with ACK. But instead it just starts sending data (I believe it sends OPTIONS request. sipdump module captured it). Is this correct? There seems to be no issues in the Kamailio debug log: May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0xae9560, 24, 0x1, 0xffffffff) fd_no=20 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xae9560, 25, -1, 0x0) fd_no=20 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4471]: handle_tcpconn_ev(): sending to child, events 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4144]: send2child(): selected tcp worker idx:1 proc:11 pid:28972 for activity on [tls:172.16.30.206:5062], 0x7fad6a70f6c8 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7fad6a70f6c8, fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2720]: tcpconn_do_send(): sending... May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2753]: tcpconn_do_send(): after real write: c= 0x7fad6a70f6c8 n=2279 fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2754]: tcpconn_do_send(): buf= May 20 15:29:05 server kamailio[28961]: 7 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0xb555c0, 6, 2, 0x7fad6a70f6c8) - fd_no=1 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:794]: sr_ssl_ctx_info_callback(): SSL disable renegotiation May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:542]: tls_connect(): TLS connect successful May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:549]: tls_connect(): tls_connect: new connection to 52.114.132.46:5061 using TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384 256 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:552]: tls_connect(): tls_connect: sending socket: 172.16.30.206:0 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:418]: tls_dump_cert_info(): tls_connect: server certificate subject:/CN=sip.pstnhub.microsoft.com May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:422]: tls_dump_cert_info(): tls_connect: server certificate issuer:/C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2720]: tcpconn_do_send(): sending... May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2753]: tcpconn_do_send(): after real write: c= 0x7fad6a70f6c8 n=509 fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2754]: tcpconn_do_send(): buf= May 20 15:29:05 server kamailio[28961]: ▒4▒▒▒▒.▒2T$-▒▒ o▒w)▒(▒▒^▒D▒U{xn9▒' ▒&▒t▒▒)▒▒?▒d▒=g▒▒?▒▒▒4/▒▒▒▒-R+▒tR▒H,▒o▒D2r ▒5Q?m▒▒9▒▒#▒O▒▒▒\eϣ▒݄"▒z=▒U▒? May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xae9560, 24, -1, 0x0) fd_no=19 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4471]: handle_tcpconn_ev(): sending to child, events 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4144]: send2child(): selected tcp worker idx:2 proc:12 pid:28973 for activity on [tls:172.16.30.206:5062], 0x7fad6a6f25a0 May 20 15:29:05 server kamailio[28961]: 12(28973) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7fad6a6f25a0, fd=6 May 20 15:29:05 server kamailio[28961]: 12(28973) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:304]: tcp_read_data(): EOF on connection 0x7fad6a70f6c8 (state: 0, flags: 18) - FD 6, bytes 0, rd-flags 10000 ([52.114.132.46]:5061 -> [52.114.132.46]:0)11(28972) DEBUG: <coreTCP closed event creation triggered (reason: 0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:192]: tcp_emit_closed_event(): no callback registering for handling TCP closed event May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1503]: tcp_read_req(): EOF May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xb555c0, 6, -1, 0x10) fd_no=2 called May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1878]: handle_io(): removing from list 0x7fad6a70f6c8 id 2 fd 6, state 2, flags 18, main fd 25, refcnt 2 ([52.114.132.46]:5061 -> [52.114.132.46]:0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1659]: release_tcpconn(): releasing con 0x7fad6a70f6c8, state -1, fd=6, id=2 ([52.114.132.46]:5061 -> [52.114.132.46]:0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1660]: release_tcpconn(): extra_data 0x7fad6a70f008 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:3574]: handle_tcp_child(): reader response= 7fad6a70f6c8, -1 from 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: tls [tls_server.c:729]: tls_h_tcpconn_close_f(): Closing SSL connection 0x7fad6a70f008 Thank you!

1 1

Debian: Kamailio: -> FIN - SYN -> on new port
by Kevin Browne 26 May '22

26 May '22

Hi, am looking for some specific Kamailio help i cant seem to find anywhere ( # running Kamailio on Debian/buster ... ## after receipt of tcp FIN, port is closed. when signaling is required again from Kamailio side. Kam is attempting SYN on FINd (closed) port. this is rejected RST. How to change SYN to re-establish tcp on new ephemeral port? ## another description, same problem: FIN received from (external) cisco (call owner) due to port recycling, not to keep port open after x minutes. everything is as expected re ACKs and such. When Kam wants to send REFER to cisco after the FIN, tcp attempts a SYN (as we'd expect) but sends SYN on old closed port. ## Where to change this Kam/OS/other is where i'm attempting to identify, then figure how to change. Thank you.

2 1

Jump to page:

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