sr-users December 2023

sr-users@lists.kamailio.org

33 participants
29 discussions

kemi python3s - module 'KSR' has no attribute 'nathelper'

by marek

hi, trying kamailio 5.7.3 with KEMI pythons3s sample from https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili… trying simple register with sipsak sipsak -U --sip-uri "sip:cervajs@kamailio.example.com" -u cervajs -a top_secret 4(28805) ERROR: PY8 {REGISTER}: app_python3s [apy3s_kemi.c:141]: apy3s_exec_func(): error exception occurred 4(28805) ERROR: PY8 {REGISTER}: app_python3s [apy3s_exception.c:167]: apy3s_handle_exception(): apy3s_exec_func: ksr_request_route((null)): Unhandled exception in the Python code: Traceback (most recent call last): File "/etc/kamailio/kamailio.py", line 31, in ksr_request_route if ksr_route_natdetect()==-255 : File "/etc/kamailio/kamailio.py", line 238, in ksr_route_natdetect if KSR.nathelper.nat_uac_test(19)>0 : AttributeError: module 'KSR' has no attribute 'nathelper' i see nat_uac_test in doc https://kamailio.org/docs/tutorials/5.7.x/kamailio-kemi-framework/modules/#… any tips/ideas? happy christmas Marek

11 months, 1 week

Errors with TLS

by SAMUEL MOYA TINOCO

Hi everyone, All my environment was working properly. But a few days ago I've started to have problems with my websocket connectios. Everytime I try to register my websocket Kamailio log this Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1330]: tls_h_read_f(): protocol level error Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS accept:error:0A000416:SSL routines::sslv3 alert certificate unknown (sni: unknown) Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1334]: tls_h_read_f(): src addr: IP_webclient:61423 Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1337]: tls_h_read_f(): dst addr: IP_Kamailio:8443 Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: <core> [core/tcp_read.c:1476]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fbc423053b0 r: 0x7fbc423054d8 (-1) My tls.cfg: [server:default] method = TLSv1.2+ verify_certificate = no require_certificate = yes private_key = /etc/kamailio/cert/clave_SSL.key certificate = /etc/kamailio/cert/certificado.pem Kamailio version: root@prod-kamailio:/etc/kamailio# kamailio -v version: kamailio 5.6.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 12.2.0 I don't know why it stopped working. And I'm not sure what to do or what to check. Has anyone faced this problem? Any help would be appreciated Thanks in advance Samuel Moya Tinoco Departamento de Sistemas y Redes Móvil: (+34) 606985997 smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> [cid:image001.png@01DA33E6.D2D833D0] Soluciones inteligentes para la autonomía personal

11 months, 1 week

How to hang up the call in xhttp routing

by mm e

event_route[xhttp:request] { if ($hu =~ "hangupCall"){ $var(body) = $rb; xhttp_reply("200", "OK", "",""); jansson_get_field($var(body), "callid", "$var(callid)"); jansson_get_field($var(body), "cseq", "$var(cseq)"); if (t_cancel_callid("$var(callid)", "$var(cseq)", "22")) { xlog("L_NOTICE", "t_cancel_callid============"); } exit; } xhttp_reply("404", "Not Found", "",""); exit; } According to this route, the answered call cannot be hung up。How should I hang up the answered call in xhttp routing, similar to freeswitch's uuid_kill。

11 months, 1 week

Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

by faisal.jamil.khan＠gmail.com

Hi Team, I am trying to setup Kamailio with MS Teams Direct Routing and after resolving TLS issues now I am getting this at my dispatcher flags. Possible suggestions required. kamcmd dispatcher.list | egrep "URI|FLAGS" URI: sip:sip.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP URI: sip:sip2.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP URI: sip:sip3.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP Dec 14 20:23:27 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKd9f6.c2e7d2f4000000000000000000000000.0 To: <sip:sip.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-c7b52d5e CSeq: 10 OPTIONS Call-ID: 23b2dc436850e949-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux)) Dec 14 20:23:28 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip2.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKccf6.53fea6f0000000000000000000000000.0 To: <sip:sip2.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-7a126c3a CSeq: 10 OPTIONS Call-ID: 23b2dc436850e94a-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux)) Dec 14 20:23:28 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip3.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKdcf6.5a4f89e6000000000000000000000000.0 To: <sip:sip3.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-992aa610 CSeq: 10 OPTIONS Call-ID: 23b2dc436850e94b-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux))

11 months, 1 week

Info: Next Kamailio World Conference - April 18-19, 2024, Berlin, Germany

by Daniel-Constantin Mierla

Hello, a short announcement to inform that the dates for next Kamailio World Conference have been set to April 18-19, 2024, the event to take place again in Berlin, Germany. It will be a different venue than the past editions, that one not being available. A pre-conference day is considered on April 17, 2024, but it is not yet known in what form and where. The conference is scheduled a bit earlier than the usual in the year because Germany hosts the Euro 2024 football championship during June-July 2024, making May very busy and harder to find adequate conferencing space in Berlin. The website and more details will be published soon. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

11 months, 1 week

Regretfully we were unable to process the URI

by Gavin Baumanis

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;

11 months, 1 week

Encoded Call-ID - Topoh module

by Vanderlei Torres Batistela

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

11 months, 2 weeks

{uri.duri} not working

by hanxiaofang＠x-y-t.cn

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"); } } ```

11 months, 2 weeks

Proxy Inactivity and Kamailio Log Disruption Issue.

by satyaprakash ch

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?

11 months, 2 weeks

usrloc ka_mode - Flooding OPTIONS at same time?

by Benoit Panizzon

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 ______________________________________________________

11 months, 2 weeks

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