sr-users

sr-users@lists.kamailio.org

29 participants
37478 discussions

rtpengine module does not detect new nodes in table
by David Cunningham 29 Apr '25

29 Apr '25

Hello, We are using Kamailio 5.8.2 with the rtpengine module on Ubuntu 22.04. The "rtpengine" table is used to define nodes, with a configuration like this: modparam( "rtpengine", "db_url", DB_URL ) modparam( "rtpengine", "table_name", "rtpengine" ) modparam( "rtpengine", "setid_default", 1 ) It works fine if Kamailio is restarted after entries in the "rtpengine" table are inserted or deleted, but new entries in the table aren't detected automatically. Is there a way to configure Kamailio to detect them? Thank you, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

4 6

OT: Client DNS resolver crashing on NAPTR lookup
by Benoit Panizzon 28 Apr '25

28 Apr '25

Hi List I hope it is OK to post a slightly off topic question. I have not found any similar reports via google. During testing of our development platform, I found two independent clients whose resolver process crashes randomly, when performing NAPTR lookups. Mitel/Aastra 68XXi Phones with Firmware >= 6.4 up to most recent. Inalp/Patton SNXX (Trinity OS) SIP Gateway with Firmware >= 3.14.X up to most recent. Both vendors reply they have no prior reports of this issue. The hostname used as registrar / proxy points to a NAPTR entry, which in turn points to 3 SRV entries für SIP+D2T, SIP+D2U, SIPS+D2T Each SRV entry then points to 4 IP Addresses (2x ipv4 and 2x ipv6) So quite a complex lookup and quite large replies. Anyone else observed this issue? When using a hostname that merely points to the A and AAAA records, no crashes. 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 ______________________________________________________

2 1

Kamailio Redis integration
by Timothy Delin 28 Apr '25

28 Apr '25

Hey team, I am facing an issue where my Kamailio and Redis are not integrated. I am using a VM with RHEL 9 OS, Kamailio in 5.4.7 version, and Redis DB in 7.2.7 version. Both my Kamailio and Redia are using Docker. We have installed the libhiredis and the ndb_redis in Kamailio When we tried to do a simple print "Hello World" from the Redis in Kamailio, we are receiving this error "ERROR: could not open module, missing loadmodule" even though we have confirmed in kamcmd Best regards, Timothy

3 2

Authentication qop auth-int
by 13715209697＠139.com 28 Apr '25

28 Apr '25

Hello! Kamailio 5.7.6 Debian 10.12 Here is my authentication route: ``` route[AUTH] { if (is_method("REGISTER") || from_uri==myself) { if (!auth_check("$fd", "subscriber", "0")) { auth_challenge("$fd", "2"); # flag not 0 exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } ... } ``` start eyebeam Version 1.5.14.4 ``` eyebeam --->REGISTER ----> kamailio <--401 (WWW-Authenticate: Digest realm="192.168.3.10", nonce=..., qop="auth-int") --->REGISTER (Authorization: Digest username="08001",realm="192.168.3.10",nonce=...,uri=...,response=...,cnonce=...,nc=00000001,qop=auth-int,algorithm=MD5) <--401 (auth_challenge() return -2 ) ``` OpenSIPS 3.4.12 register to kamailio, got the same result as eyebeam Any suggestions? Thanks!

4 8

Kamailio v6.0.1 and SUBSCRIBE processing
by Blair, Steve 26 Apr '25

26 Apr '25

I’m coming back to Kamailio after about a 10 year absence. I have v6.0.1 running handling registrations (unique devices) and inbound/outbound PSTN calling correctly. What I need is to process subscribe requests. I’m looking for direction on the correct configuration to 1. Authenticate subscribe messages. This appears to be working with following snippet. #eDevice: Need to authenticate subscribes before proceeding xlog("L_INFO", "eDevice: Start initial SUBSCRibe check. \n"); if (is_method("SUBSCRIBE")) { record_route(); if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); } # eDevice SUB Change consume_credentials(); route(PRESENCE); } 1. After authenticating forward any subscribe to an external presence server 2. Relay any response from external presence server to client device. Only the above authentication is working so direction on proper processing of subscribes when Kamailio is not the presence server will be appreciated. Thanks

1 0

Re: RTPengine media starts for intiating caller only
by airsay＠duck.com 23 Apr '25

23 Apr '25

Again, not super skilled yet with Kamailio/RTPEngine, but my first instinct is: "why you are advertising myproxyname.domain.net which is possibly a public IP". Your entire setup is in your LAN so you don't need to advertise any public IP. Look forward to others contributing and clarifying that Sent from my iPhone > On 23 Apr 2025, at 20:42, smh2017--- via sr-users <sr-users_at_lists.kamailio.org_airsay(a)duck.com> wrote: > > Hello, > > I have a problem with my basic Kamailio setup using RTPengine. I'm testing initially with two client UAs in the same LAN as the SIP server behind the firewall. The initiating UA starts the media proxy as soon as the receiving UA accepts the call, indicated by the call timer starting. But after accepting the call the receiving UA's timer doesn't start and after 10-15 secs hangs up with a NO ACK error message. > > I am using the kamailio default config file that comes with the Debian package and have made minimal changes recommended by various How-Tos for using Kamailio behind a firewall. Because the clients can successfully register over TLS, I'm assuming the problem is in the rtpengine configuration. The two rtp listen parameters I've tried are: > > interface = internal/192.168.1.100;external/192.168.1.100!myproxyname.domain.net > --or-- > interface = internal/192.168.1.100;external/myproxyname.domain.net > listen-ng = localhost:2223 > > I'm not sure why some example rtpengine configs list both the private and public addresses as external. > > Any suggestions where to start troubleshooting? > > Thanks, > > Steve > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the sender!

2 1

RTPengine media starts for intiating caller only
by smh2017＠zoho.com 23 Apr '25

23 Apr '25

Hello, I have a problem with my basic Kamailio setup using RTPengine. I'm testing initially with two client UAs in the same LAN as the SIP server behind the firewall. The initiating UA starts the media proxy as soon as the receiving UA accepts the call, indicated by the call timer starting. But after accepting the call the receiving UA's timer doesn't start and after 10-15 secs hangs up with a NO ACK error message. I am using the kamailio default config file that comes with the Debian package and have made minimal changes recommended by various How-Tos for using Kamailio behind a firewall. Because the clients can successfully register over TLS, I'm assuming the problem is in the rtpengine configuration. The two rtp listen parameters I've tried are: interface = internal/192.168.1.100;external/192.168.1.100!myproxyname.domain.net --or-- interface = internal/192.168.1.100;external/myproxyname.domain.net listen-ng = localhost:2223 I'm not sure why some example rtpengine configs list both the private and public addresses as external. Any suggestions where to start troubleshooting? Thanks, Steve

1 0

404 sent from Kamailio NOT from the script
by Richard Robson 23 Apr '25

23 Apr '25

I have a problem where a call comes in and causing a 404 Not Found to be replied. the script does not have a 404 reply set in it anywhere unfortunately I cannot get the script to produce logs, hence my other post. But its making it tricky to find the source of the 404. following the script it should not be producing a 404, but doing a relay. I suspect there is something wrong with the tm or its not getting a result it needs. It looks like the transaction module is triggering thge 404 somehow and Its showing up in debug below. Does anyone have any ideas why i'm getting a 404? version 5.6.6 Regards, Richard Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=3/28700 T start=0xffffffffffffffff Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430] Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:703]: t_lookup_request(): no transaction found Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1172]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T end=(nil) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1394]: t_newtran(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T start=(nil) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430] Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:703]: t_lookup_request(): no transaction found Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 8336) called from tm: h_table.c: build_cell(336) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_hooks.c:342]: run_reqin_callbacks_internal(): trans=0x7faf932f42c0, callback type 1, id 0 entered Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 40) called from tm: t_hooks.c: insert_tmcb(134) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global id=4/28700 T start=0x7faf932f42c0 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_lookup.c:1176]: t_check_msg(): T (0x7faf932f42c0) already found for msg (0x7faf977b64b0)! Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 626) called from tm: t_reply.c: _reply_light(488) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:1768]: cleanup_uac_timers(): RETR/FR timers reset Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_hooks.c:252]: run_trans_callbacks_internal(): DBG: trans=0x7faf932f42c0, callback type 512, id 0 entered Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} acc [acc_logic.c:721]: tmcb_func(): acc callback called for t(0x7faf932f42c0) event type 512, reply code 404 Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:625]: _reply_light(): reply sent out - buf=0x7faf977bf7f8: SIP/2.0 404 Not Foun... shmem=0x7faf932f0468: SIP/2.0 404 Not Foun Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_funcs.c:122]: put_on_wait(): put T [0x7faf932f42c0] on wait Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> [core/mem/q_malloc.c:495]: qm_free(): qm_free(0x7faf976b5010, 0x7faf977bf7f8), called from tm: t_reply.c: _reply_light(635) Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm [t_reply.c:636]: _reply_light(): finished Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} sl [sl.c:288]: send_reply(): reply in stateful mode (tm)

4 7

Kamailio docker with missing modules
by Martin Nyström 23 Apr '25

23 Apr '25

Hi, I’m using the docker ghcr.io/kamailio/kamailio:5.8.6-xenial but it appears to be missing the app_python modules. How can I add it, together with other missing modules? /M

1 2

Behaviour of suspended transactions
by Alex Balashov 18 Apr '25

18 Apr '25

Hello! Two questions about suspended transactions: 1) What is the lifetime of a suspended INVITE transaction? Can I change it? 2) While a transaction is suspended, its event hooks (e.g. onreply_route, failure_route) do not run, of course, even if replies that match the transaction are received. Is there a way to intercept these replies externally and resume the transaction upon the receipt of the reply, and prior to the processing of the reply? For example, can the replies be captured in a stateless route, and mapped Call-ID => index/label to t_continue() the transaction, then have the transaction state machine process that very same reply too? t_is_retr_async_reply() seems to hint at this intention, but its scope is more narrow, if I understood the documentation correctly: it seems to deal with retransmissions only. The code path I'm interested in is more akin to a t_is_reply_to_async() function. As you might guess, the driver for this inquiry is a mobile workflow where, in the vast majority of cases, one is contacting a stale registration and should just suspend the transaction, but where occasionally, in a small minority of cases, the endpoint does respond on the existing contact. The standard tsilo workflow of trickling parallel branches into a pending transaction doesn't work here because of the behaviour of Apple's CallKit; we have to try the existing contact _before_ we send a push notification. -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

3 2

← Newer
1
2
3
4
5
6
7
...
3748
Older →

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