sr-users

sr-users@lists.kamailio.org

25 participants
37379 discussions

Unable to use db_alias_lookup to call multiple extensions
by Merul Patel, PhD 01 Dec '23

01 Dec '23

Hi, Kamailio newby here. Having some trouble with using alias_db to forward an incoming call to two extensions. Thanks in advance for any help. I've tried using the Ubuntu Jammy ARM64 packages, as well as compiling the source for version 5.7.3. In both cases, I've added three extensions, and calls directly between them work fine with the vanilla kamailio.cfg. However, I then wanted to add an alias so that when called it would dial two extensions, but only the first extension is ever called. My kamailio.cfg only differs in a few places: $ diff kamailio.cfg kamailio.cfg.original 3,6d2 < #!define WITH_AUTH 1 < #!define WITH_DEBUG 1 < #!define WITH_ALIASDB 1 < # 268,270d263 < loadmodule "db_sqlite.so" < #!define DBURL "sqlite:///usr/local/kamailio-devel/etc/kamailio/kamailio.sqlite" < 367c360 < modparam("tm", "failure_reply_mode", 0) --- > modparam("tm", "failure_reply_mode", 3) 450d442 < modparam("alias_db", "append_branches", 1) I can see from the log that when dialling the desired alias (5000) an alias_db query is performed: Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [0] is [sip:6002@merrivale.localdomain] Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [1] is [sip:6001@merrivale.localdomain] But only the first result is called. I've changed the order of the aliases in the sqlite db and just the first result is called. What am I missing? Merul

1 0

How to use: kamcmd ul.db_users?
by Benoit Panizzon 01 Dec '23

01 Dec '23

Hi List I want to find a way to check how many users are regsitered. https://www.kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.r.db… But no matter how I try, I get a 500 error... # kamcmd ul.db_users location And yes, the table is called 'location'. I did try to find out how kamctl ul show --brief pulls that information, but did not succeed. Also that command takes way too long how that we have several thousand registered users. Or would I need to query this directly from the database? 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 2

Info: RTC Devroom at FOSDEM 2024
by Daniel-Constantin Mierla 01 Dec '23

01 Dec '23

Hello, another edition of FOSDEM is approaching and it will include again a Real Time Communications devroom. If anyone wants to share their interesting applications or experiences in the field, consider to submit a presentation proposal. The CfP is available at: - https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html It does not have to be about Kamailio, all RTC topics are welcome, just think to be something useful for developers, as the event is targeting them. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

No access to variables within timer route
by dries＠degendt.com 30 Nov '23

30 Nov '23

Hi, I have a timer which is called each 5 seconds: modparam("timer", "declare_timer", "REFRESH_CALLSTATE_TIMER=REFRESH_CALLSTATE_TIMER,5000,slow"); I'm enabling setting the variable "testvar" and enabling the timer when an INVITE is received: if (is_method("INVITE|ACK|UPDATE|CANCEL|BYE")) { $var(testvar) = "blablabla"; timer_enable("REFRESH_CALLSTATE_TIMER", "1"); ... route[REFRESH_CALLSTATE_TIMER] { xlog("L_INFO", "Testvariable: $var(test)\n"); } However, the variable is always 0: INFO: <script>: Testvariable: 0 I've also tried printing pseudovariables like $ci, $du but nothinh seems accessible. Is there a workaround for this? Best regards, Dries

3 6

kamailio t_on_failure tcp timeout
by Julien Chavanton 29 Nov '23

29 Nov '23

Hi, I would like to catch TCP timeouts when I use a socket that was not closed. In this example I am sending SIP MESSAGE ... t_on_reply("ON_REPLY_MESSAGE"); t_on_failure("FAILURE_MESSAGE"); if (!t_relay()) sl_reply_error();

1 2

Evapi Async - suspend transaction for a limited time
by Ilie Soltanici 29 Nov '23

29 Nov '23

Hello, I'm trying to use the evapi_async_relay function from the evapi module, however,I don't want the transaction to be suspended for more than 1 second. For instance, if there's no response from the external application within this time frame, I want the script to continue and remove that transaction from memory. One potential approach I am considering is to add suspended transactions to a hash table with a timestamp value. Then, using rtimer module, I could periodically parse this table every second and process the results, but I'm not sure how efficient is that. Maybe you know other alternative, more efficient solutions (from a performance point of view) that could achieve the same goal? Any insights or recommendations would be greatly appreciated. Thank you.

3 6

5.6.4 debian htable dbmode=1 not writing at shutdown
by Bernd Krueger-Knauber 29 Nov '23

29 Nov '23

Hi, I have still the problem that my htables are not written into a sqlite db when I shutdown kamailio. Manual writing via: kamcmd htable.store ... is working. As I can see in the logs with highest loglevel, the function destroy() is never called. ht_db_url.len is > 0 ht_db_init_con() should work, else nothing would work with the db. But I can not see the debug messages from ht_db_open_con() Any ideas? Best regards, Bernd

5 5

Incompatibility of the DMQ htable protocol with older Kamailio versions
by Denys Pozniak 29 Nov '23

29 Nov '23

Hello! I noticed that there are differences in the DMQ htable replication protocol for the old version of Kamailio 5.2 and the new 5.7. For example, the new version uses action 2 when updating values and action 4 to remove. The old Kamailio version uses the values 1 and 3 respectively. Well, as a result, the htable data is not shared between such nodes, plus there are errors in the syslog of the old version: ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action It would probably be worth introducing some kind of DMQ htable protocol versioning to maintain compatibility? And is there any option to make them work together (I wouldn’t really want to change the action number in sip/sdp/json on the fly)? Kamialio 5.2 {"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":3,"htname":"shared","cname":"user","mode":0} Kamailio 5.7 {"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":4,"htname":"shared","cname":"user","mode":0} -- BR, Denys Pozniak

2 2

tps_storage_fill_contact(): no r-uri user
by Denys Pozniak 28 Nov '23

28 Nov '23

Hello! My topology is like this: PBX -> Kamailio Topos -> User When calling the user, PBX does not add the user part in the Contact URI, something like: Contact: <sip:10.10.10.10:5080;transport=udp> When the customer sends a reinvite, the topos turns off for this transaction and the sip partially breaks down with error: topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user topos [tps_storage.c:615]: tps_storage_record(): failed to store As far as I understand, the RFC allows the absence of the user part in the URI and this occurs quite often. I can provide the pcap file and debug log in a private message if this helps identify the essence of the problem. # kamailio -v version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty -- BR, Denys Pozniak

3 5

Kamailio ver 5.7.3 - source installation warnings
by Muhammad Danish Moosa 28 Nov '23

28 Nov '23

Hi, I am planning to upgrade Kamailio to version 5.7.3 to manage some memory leaks issues. I am installing from source and came across these warnings, just wanted to be sure if they are safe to be ignored. cr_func.c: In function ‘set_next_domain_on_rule’: cr_func.c:160:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:160:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘actually_rewrite’: cr_func.c:348:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:348:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘ki_cr_load_user_carrier_helper’: cr_func.c:782:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ -- LD (gcc) [M p_usrloc.so] p_usrloc.so CC (gcc) [M evrexec.so] evrexec_mod.o evrexec_mod.c:64:1: warning: missing braces around initializer [-Wmissing-braces] static evrexec_info_t _evrexec_info = {0}; ^ evrexec_mod.c:64:1: warning: (near initialization for ‘_evrexec_info.data’) [-Wmissing-braces] LD (gcc) [M evrexec.so] evrexec.so CC (gcc) [M avp.so] avp.o LD (gcc) [M avp.so] avp.so CC (gcc) [M acc_diameter.so] diam_message.o CC (gcc) [M acc_diameter.so] acc_diameter_mod.o CC (gcc) [M acc_diameter.so] diam_avp.o CC (gcc) [M acc_diameter.so] diam_tcp.o LD (gcc) [M acc_diameter.so] acc_diameter.so CC (gcc) [M dmq.so] bind_dmq.o CC (gcc) [M dmq.so] message.o CC (gcc) [M dmq.so] dmq_funcs.o dmq_funcs.c: In function ‘ki_dmq_send_message’: dmq_funcs.c:304:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:304:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] dmq_funcs.c: In function ‘ki_dmq_bcast_message’: dmq_funcs.c:374:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:374:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] CC (gcc) [M dmq.so] notification_peer.o CC (gcc) [M dmq.so] dmq.o dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces] sip_uri_t dmq_server_uri = {0}; ^ dmq.c:61:1: warning: (near initialization for ‘dmq_server_uri.user’) [-Wmissing-braces] dmq.c:67:1: warning: missing braces around initializer [-Wmissing-braces] static sip_uri_t dmq_notification_uri = {0}; ^ dmq.c:67:1: warning: (near initialization for ‘dmq_notification_uri.user’) [-Wmissing-braces] Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

2 2

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