sr-users

sr-users@lists.kamailio.org

21 participants
37376 discussions

app_perl add/remove HF?
by Benoît Panizzon 22 Nov '24

22 Nov '24

Hi List I'm looking into the perl module. Am I right, that I can not add or remove HF from an app_perl subroutine? I would need to pass an AVP from perl to tell Kamailio what to do? Goal is an attempt to re-build part of the topos functionality in perl but only handling RR and Route Header only on one leg, not on both. -- 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

tcp_accept_haproxy option
by Wolter Eldering 22 Nov '24

22 Nov '24

Hi, I noticed that if I enable tcp_accept_haproxy kamailio still can accept connections without the PROXY-protocol header. The documentation on the wiki has the following note: "Please note that enabling this option will reject any inbound TCP connection that does not conform to the PROXY-protocol spec." https://www.kamailio.org/wiki/cookbooks/devel/core#tcp_accept_haproxy This could be true up until a specific version of kamalio but from 5.7.4+ this limitation is seems to be removed. Enabling tcp_accept_haproxy is breaking the outbound/rr module because it con’t find the socket based on the address and port from the flow token. The flow tokens created by a REGISTER on a connection without a PROXY header can be used. Flow tokens created from a connection with PROXY-protocol header will fail with "cannot find socket from flow-token” once loose_route is invoked. loose.c:561 /* First, force the local socket */ si = find_si(&rcv->dst_ip, rcv->dst_port, rcv->proto); if(si) set_force_socket(_m, si); else { LM_INFO("cannot find socket from flow-token\n"); return -1; } I’m not sure if the address and/or port values stored in the flow token are incorrect or the problem lies in the matiching in find_is(…). Wolter

1 0

RTC DevRoom at FOSDEM 2025
by Daniel-Constantin Mierla 21 Nov '24

21 Nov '24

Hello, FOSDEM'25 will host again a RTC DevRoom during the afternoon of February 1, 2025 (Saturday) -- more details and the call for presentation can be read at: - https://lists.fosdem.org/pipermail/fosdem/2024q4/003584.html I am not sure if I can participate (chances are more towards no, than to yes), but if anyone considers to go to the event, it will be good to submit a proposal to cover a bit Kamailio as well (it doesn't have to be entirely about Kamailio). Note that FOSDEM imposes a strict deadline this time for submissions (Dec 1, 2024), thus is no much time left. Should anyone in these groups plans to submit a proposal, let us know, so the others have an idea about it. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

TM-Module, ignoring
by Christian Berger 19 Nov '24

19 Nov '24

Hi, we would like to replicate a SIP-message ("REGISTER" in our case) to a set of nodes for further asynchronous processing. The message is already processed on the local Kamailio. We thought about using the tm-module in conjunction with the dispatcher module so we can reliably forward the message. This seems to work, however we get a new problem: Kamailio forwards the response it gets from those nodes. When we drop the response in the reply_route, it gets dropped before TM can see it. When we drop the response in the on_reply_route, it still will be forwarded. (adding or removing a header here works, however) $du is set to $null. Is there any clean way to suppress that response being forwarded back to the original requester? Best regards Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

2 2

Not able to use SRTP - from client to proxy
by Sajid Khan 18 Nov '24

18 Nov '24

Im using the module RTPengine. im having issues when ever i try to do a call using SRTP im using microsip i have checked the SDP everything ok. But when ever i place the call it gets rejected. if i disable SRTP then the calls work if (!rtpengine_offer("replace-origin replace-session-connection ICE=force RTP/SAVP RTP/AVP")) { I only need to encrypt client -> proxy from proxy -> asterisk should be plain rtp i hope someone can help me out thank you. The log in rtpengine shows this [1731055305.417896] ERR: [2a721ebf2c73414ab8e739d7bde912f9//1 port 14124]: [srtp] SRTP output wanted, but no crypto suite was negotiated

4 4

Kamailio 5.5.7 crash
by Mitesh Thakkar 18 Nov '24

18 Nov '24

Hi, I have recently migrated from Kamailio 5.2.5 to Kamailio 5.5.7. After a migration, the Kamailio crashed. Also, there were a lot of errors and warnings. Can someone help me to understand why this happened and what could be the solution? Logs (upside down): 18(397) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 2(381) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 30(409) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 8(387) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) OS: Ubuntu 22.04.5 LTS \n \l # kamailio --version version: kamailio 5.5.7 (x86_64/linux) 272fdd 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: 272fdd compiled on 14:21:35 Oct 21 2024 with gcc 11.4.0 # dpkg -l |grep openssl ii openssl 3.0.2-0ubuntu1.18 amd64 Secure Sockets Layer toolkit - cryptographic utility Regards, Miteshkumar Thakkar

2 1

Pua PUBLISH method over xmlrpc/jsonrpc
by dries＠degendt.com 18 Nov '24

18 Nov '24

Hi all I've installed a (pretty old) presence_dfks module that allows setting the presence using the following command: kamctl fifo pua_publish sip:1000@10.10.99.254 3600 as-feature-event application/x-as-feature-event+xml . . . "<?xml version='1.0' encoding='ISO-8859-1'?><ForwardingEvent><device><notKnown/></device><forwardingType>forwardImmediate</forwardingType><forwardStatus>true</forwardStatus><forwardTo>1234</forwardTo></ForwardingEvent>" The "pua_mi" module was however removed in Kamailio and jsonrpcs/xmlrpcs are supposed to be an alternative. I've tried both the following calls, but neither does recognize the pua_publish/pua.publish as a valid method. Attempt with jsonrpc: curl -H "Content-Type: application/json" -X POST -d '{"jsonrpc": "2.0", "method": "pua.publish", "params": [""], "id":1}' https://sbctest.tel.redacted.xx:5061/RPC/ ERROR: jsonrpcs [jsonrpcs_mod.c:1422]: ki_jsonrpcs_dispatch(): method callback not found [pua.publish] Attempt with xmlrpc: curl -H "Content-Type: text/xml" -X POST -d '<?xml version="1.0" ?><methodCall><methodName>pua_publish</methodName><params><param><value><string>sip:jh@sbctest.tel.redacted.xx</string></value></param><param><value><string>7776000</string></value></param><param><value><string>as-feature-event</string></value></param><param><value><string>application/as-feature-event</string></value></param><param><value><string>.</string></value></param><param><value><string>a.1481534683.13958.6.7</string></value></param><param><value><string>sip:127.0.0.1:5080;transport=tcp</string></value></param><param><value><string>P-Flags: 0</string></value></param><param><value><string>Messages-Waiting: yesMessage-Account: sip:jh@sbctest.tel.redacted.xxVoice-Message: 2/0 (0/0)</string></value></param></params></methodCall>' https://sbctest.tel.redacted.xx:5061/RPC/ <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>500</int></value> </member> <member> <name>faultString</name> <value><string>Method Not Found</string></value> </member> </struct> </value> </fault> Anyone who had some luck in this matter? Best regards, Dries

3 6

SIP NOTIFY over TLS fails
by dries＠degendt.com 15 Nov '24

15 Nov '24

Hi all I've installed a custom presence_dkfs module (https://github.com/tombeard/presence_dfks) in an effort to make our Grandstream devices (connected over TLS) display a server set callforward using Broadsoft's Device Feature Key Sync. The module was installed succesfully, but it appears that the NOTIFY upon SUBSCRIBE cannot be sent over TLS. This part seems to use the default presence module however so I'm taking my chances here to ask for some advice. I have already disabled verify_certificate in tls.cfg. The "dst addr: 193.19x.x.x:0" does seem to have an incorrect port as I should expect 5061? INFO: {1 600000 SUBSCRIBE 319937814-5062-3(a)BHC.DA.GB.CD} presence [notify.c:1744]: send_notify_request(): NOTIFY sip:544460@sbctest.tel.redacted.xx via sip:544460@172.30.61.23:5062;transport=tls on behalf of sip:544460@sbctest.tel.redacted.xx for event as-feature-event : 319937814-5062-3(a)BHC.DA.GB.CD ERROR: tls [tls_server.c:1312]: tls_h_read_f(): protocol level error ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS connect:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure (sni: unknown) ERROR: tls [tls_server.c:1316]: tls_h_read_f(): src addr: 172.30.61.23:5062 ERROR: tls [tls_server.c:1319]: tls_h_read_f(): dst addr: 193.19x.x.x:0 ERROR: <core> [core/tcp_read.c:1526]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f6d55b4b360 r: 0x7f6d55b4b488 (-1) Your advice is most appreciated! Cheers, Dries

4 7

dlq_req_within() usage for 3pcc-style reinvite media setup
by Alex Balashov 14 Nov '24

14 Nov '24

Hi, I am trying to use dlg_req_within() for a 3pcc-style call setup, to set up media via a reinvite: 1. Store original SDP offer from caller in $dlg_var()s; 2. Later, after e2e ACK is processed for initial INVITE transaction, send reinvite to callee using dlg_req_within(). I call rtpengine_offer() and feed it the original SDP offer (via read_sdp_pv modparam), and take the RTPEngine-transformed SDP and feed that to dlg_req_within(): dlg_req_within("callee", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); 3. I have found that event_route[tm:local-response] does not allow me to capture the 200 OK / SDP answer to this reinvite; it is internally absorbed. However, it is possible to arm an onreply_route in event_route[tm:local-request], to receive the 200 OK: event_route[tm:local-request] { if(method == "INVITE" && has_body("application/sdp")) t_on_reply("REINVITE_REPLY"); } 4. My intent is for this reinvite reply handler to set off a reinvite to the caller side: onreply_route[REINVITE_REPLY] { if(method == "INVITE" && has_body("application/sdp") && t_check_status("200")) { ... $var(rtpengine_use_this_sdp) = $rb; rtpengine_answer("..."); dlg_req_within("caller", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); } This ensures proper relay symmetry. Otherwise, the caller will continue to send RTP to the previous upstream endpoint of the call, prior to any reinvite. However, dlg_req_within() doesn't work in this later context, even though the documentation says it can be used from ANY_ROUTE. Kamailio doesn't complain, there is no error. It just doesn't initiate a reinvite to the caller. I considered the possibility that this may be because the calling scope is that of a pending reinvite transaction to the callee, but there is no obvious way to defer that into the future. If I send it to an async task worker, the transaction scope required for dlg_req_within() to know which dialog it's operating on will be lost. Any ideas appreciated, and thank you in advance! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 2

KEMI / Python Issues
by Daniel W. Graham 14 Nov '24

14 Nov '24

Experimenting with KEMI for the first time, I ran into a few issues and hoping someone has feedback. kamailio 5.8.3 In the following python example, 'if ksr.is_method("ACK"):' should never be reached. Below is debug. if not ksr.siputils.has_totag(): ksr.info("has to tag") sys.exit() if ksr.is_method("ACK"): if ksr.tm.t_check_trans(): ksr.relay() sys.exit) else: sys.exit() ksr.sl.send_reply(404, "Not here") sys,exit() ..... DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: siputils.has_totag DEBUG: siputils [checks.c:122]: has_totag(): no totag DEBUG: app_python3s [apy3s_kemi.c:368]: sr_apy_kemi_exec_func_ex(): execution of method: is_method DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 1 DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: sl.send_reply DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 2 DEBUG: sl [sl.c:306]: send_reply(): reply in stateless mode (sl) ..... Second, here are a couple errors I have seen a few times but havent been able to identify the underlying issue, mainly hoping for more context on the meaning of 'execution of route type 1 with no name returned -1'. ERROR: app_python3s [apy3s_kemi.c:146]: apy3s_exec_func(): error exception occurred DEBUG: app_python3s [apy3s_kemi.c:230]: sr_kemi_config_engine_python(): execution of route type 1 with no name returned -1 Any input is appreciated. * dan

2 7

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