sr-users March 2019

sr-users@lists.kamailio.org

78 participants
104 discussions

Uri's user part parameters
by Duarte Rocha 27 Mar '19

27 Mar '19

Greetings, Does Kamailio have a way of identifying the user-part parameters of an URI? I have situations where i have sip:user;parameter=yes@host. Best Regards, Duarte Rocha

2 1

Manipulating User Agent header in dispatcher OPTIONS
by Andrew White 27 Mar '19

27 Mar '19

Hi all, I’ve set the server_header variable in my primary config, and I’ve got a catch in the default reply route to modify headers where required. I’m masking this value for security reasons, and filling it with my own value for vanity reasons :). I’ve noticed that the OPTIONS packet that is send via the dispatcher module when probing mode is on contains a User-Agent field which has the full version and OS type. Unfortunately I don’t necessarily have trust of the end destination being dispatcher to, nor the packet switchers in-between. How can I catch this OPTIONS packet to manipulate the value? It doesn’t appear to go through the REQUEST route or the ONSEND route. Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 2

accounting and db_redis
by Daniel Tryba 27 Mar '19

27 Mar '19

Under https://www.kamailio.org/docs/modules/5.2.x/modules/db_redis.html#db_redis.… there is an example for using db_redis for accounting. This doesn't appear to work (5.2.2) modparam("db_redis", "keys", "acc=entry:callid,time_hires&cid:callid") results in: db_redis [redis_dbase.c:1886]: db_redis_insert(): inserting to prefix (table) 'acc' db_redis [redis_dbase.c:382]: db_redis_build_entry_keys(): build entry keys db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of ent db_redis [redis_dbase.c:306]: db_redis_find_query_key(): found key in entry key db_redis [redis_dbase.c:133]: db_redis_val2str(): converting str value '1db9c0bc57291e db_redis [redis_dbase.c:338]: db_redis_find_query_key(): entry key so far is 'acc:entr db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of entry key 'time_hires' in query db_redis [redis_dbase.c:346]: db_redis_find_query_key(): key 'time_hires' for type 'entry' not found, unable to use this type db_redis [redis_dbase.c:405]: db_redis_build_entry_keys(): Failed to create direct entry key, no matching key definition db_redis [redis_dbase.c:1892]: db_redis_insert(): failed to build entry keys db_redis [redis_dbase.c:1976]: db_redis_insert(): failed to do the insert What does work is "time" instead of "time_hires". Since I have no idea what values are available (I guess the table names?) and time only has a 1 sec resolution, what is a correct version of time_hires?

1 2

DBText does not exists!
by Andrew White 27 Mar '19

27 Mar '19

Hi all, I’m currently playing with the UAC module to hand off remote registrations with trunks to Kamailio. I want to keep Kamailio’s external connections low, so I’m planning to use db_text to load the UAC info, and populate the flat file via other methods. When attempting to load my UAC DB via db_text however, I get the following: Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: db_text [dbt_lib.c:143]: dbt_cache_get_db(): database [/etc/kamailio/uac.db] does not exists! Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31902]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/31902 Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: db_text [dbt_base.c:102]: dbt_init(): cannot get the link to database Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: uac [uac_reg.c:1318]: uac_reg_load_db(): failed to connect to the database When running using WITH_DEBUG flag, it does not appear to attempt on normal start. A kamcmd uac.reg_reload yields: Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read: new connection (1) on /var/run/kamailio//kamailio_ctl Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: <core> [core/sr_module.c:632]: find_mod_export_record(): found export of <db_bind_api> in module db_text [/usr/local/lib64/kamailio/modules/db_text.so] Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: <core> [db.c:210]: db_bind_mod(): using db bind api for db_text Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: db_text [dbt_base.c:55]: dbt_init(): initializing for db url: [text:///etc/kamailio/uac.db] Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: db_text [dbt_lib.c:125]: dbt_cache_get_db(): looking for db /etc/kamailio/uac.db! Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: db_text [dbt_lib.c:143]: dbt_cache_get_db(): database [/etc/kamailio/uac.db] does not exists! Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: db_text [dbt_base.c:102]: dbt_init(): cannot get the link to database Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: uac [uac_reg.c:1318]: uac_reg_load_db(): failed to connect to the database Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: ctl [io_listener.c:495]: handle_stream_read(): handle_stream read: eof on /var/run/kamailio//kamailio_ctl The file of course does exist, and has fine permissions (Kamailio runs as root in this case): -rw-r--r-- 1 root root 169 Mar 26 04:49 /etc/kamailio/uac.db Contents of file: l_uuid(str) l_username(str) l_domain(str) r_username(str) r_domain(str) realm(str) auth_username(str) auth_password(str) auth_proxy(str) expires(int) flags(int) reg_delay(int) 123:test:test.com:test:test.com:test.com:user:pass:10.0.0.100:600:: (At this stage I just want to see the reg packet in Wireshark). 1) Is this the correct method to do UAC? Load credentials, then Kamailio will handle the registration and renewal? I’ve struggled a bit to understand the documentation, hence the testing 2) Why is my db_text failing to load the file? Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

3 6

Extract URI from Headers
by Duarte Rocha 27 Mar '19

27 Mar '19

Greetings, In my SBC i usually have to do operations on P-Asserted-Identity and Contact header. For those operations i usually have to get the user part, domain, etc. For that i'm using the URI Transformations provided by Kamailio. However, in order to do this i have to trim the header value by hand in order to remove brackets, display infos, etc. Does Kamailio have a method for extracting the URI from those kinds of headers? Best Regards, Duarte Rocha

3 3

Disable Dispatcher GW from DB
by Patrick Wakano 26 Mar '19

26 Mar '19

Hello list, Hope you are all doing well! I am looking for a way to disable a Dispatcher GW from the DB. I know I can disable it using the "kamcmd dispatcher.set_state d ..."command, but in case I do a reload or restart after that, the disabled GW will be back as active. Of course I could also delete the GW from DB, but for CDR purposes I want to keep the entry but mark as permanently disabled, so Kamailio won't try to use it nor ping it anymore. Does anyone how can I do that in the DB? I am looking for the exact same behavior the "kamcmd dispatcher.set_state d" does but from some change in the DB. Thanks, Kind regards, Patrick Wakano

3 5

Presence module. How to update contact DB record after re-SUBSCRIBE ?
by Denys Pozniak 26 Mar '19

26 Mar '19

Hello! We are using Presence module with MySQL with parameters below. And looks like module does not update contact DB record in case of re-SUBSCRIBE. So we have a case when NAT router periodically changes the outgoing port, but NOTIFY from Kamailio goes to port from initial SUBSCRIBE. Is this normal module behavior or we missed something? modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0) # kamailio -v version: kamailio 4.4.2 (x86_64/linux) 892ad6 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 892ad6 compiled on 14:45:42 Sep 26 2017 with gcc 4.8.5 -- BR, Denys Pozniak

1 0

Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration
by Rhys Hanrahan 26 Mar '19

26 Mar '19

Hi Everyone, I’ve recently just started working with Kamailio – thanks everyone for this amazing software. Like many people, I’m in the process of trying to put Kamailio in-front of Asterisk to allow it to scale out, and my plan is for Kamailio to take over registrations, usrloc and presence/dialoginfo, as we’ve had issues where handsets are failing to get BLF updates/notifys, so I am hoping a couple of Kamailio boxes can scale better in this regard. DMQ is particularly exciting in how it will allow me to build a truly distributed platform. But I’m struggling to get presence to work the way I need it to. Our environment is multi-tenanted, but we do not (and can’t really) use multi-domains. Instead, we prefix the SIP usernames with the “tenant name” such as tenanta101 and tenantb101. My problem is that all the BLFs are configured for 101@PBX with no tenant name in the User part of the URI so that internal dialing and call pickup will work. Because in Asterisk we use “subscribecontext” this hasn’t been a problem in the past – Asterisk knows for subscriptions coming from that handset that it belongs to that tenant’s context in the dialplan and they are “isolated”, so having handsets subscribe as 101@ in their request URI was never a problem. Of course, with Kamailio I don’t have subscribecontext, and my main issue is that the “presentity_uri” being stored is 101@ while each of the SIP accounts of the handsets are registered as tenenata101@, and as such, no NOTIFYs are sent by Kamailio because it thinks that there are no watchers for the presentity_uri. If I change the SIP account username to 101 to match the BLF key, NOTIFYs are sent as expected. But then this breaks call pickup and internal dialing using the BLF keys. I would rather handle this in Kamailio than in Asterisk and having to re-configure the BLF keys for hundreds of handsets. I need to do something like: * When a SUBSCRIBE comes in, I need to prefix presentity_uri with the tenant name so the subscription changes from 101@ to tenanta101@ in the active_watchers table. * When Kamailio generates a NOTIFY, the notify would be built based on presentity_uri and would come out as tenanta101@, but the phone’s BLFs are configured for 101@ so I would need to *remove* the tenant prefix before sending out the notify. Is there a good, or recommended way to handle this scenario? Maybe something entirely different to changing the presentity_uri? I’ve written the following config to re-write the request URI and To field in any incoming subscribe requests, and successfully got the active_watchers table to store a presentity_uri containing my tenant prefix. But the problem I am having is that I can’t figure out how to modify the NOTIFY packets before they are sent – and looking at cfgtrace, it seems I might not be able to? My “standard” presence + dialoginfo configuration was taken from here as a starting point: https://kb.asipto.com/kamailio:presence:k43-blf Here is what I have so far in terms of trying to make my modifications – any guidance would be greatly appreciated. It feels like there’s probably a better way to do this than re-writing critical headers like To and Request URI? @@ -466,6 +467,8 @@ request_route { # authentication route(AUTH); + route(REWRITE_PRESENCE); + # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); # Presence server processing route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; if(is_method("SUBSCRIBE") && $hdr(Event)=="message-summary") { # Asterisk is our voicemail route(TOASTERISK); # returns here if no voicemail server is configured sl_send_reply("404", "No voicemail service"); exit; } #!ifdef WITH_PRESENCE if (!t_newtran()) { sl_reply_error(); exit; } if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if(is_method("SUBSCRIBE")) { # See REWRITE_PRESENCE - this should have been executed before we get here. handle_subscribe(); t_release(); } exit; #!endif +route[REWRITE_PRESENCE] { + if (is_method("SUBSCRIBE")) { + xlog("Re-writing subscribe to include tenant prefix\n"); + # The default presentity_uri needs to be prefixed with + # the tenant name + # So re-write the To header + route(TENANTINFO); + # Now grab the tenant name. + $var(subscribe_ru) = "sip:" + $var(tenant_name) + $rU + "@" + $rd; + xlog("Re-writing SUBSCRIBE To header as: $var(subscribe_ru)\n"); + insert_hf("To: $var(subscribe_ru)\r\n", "From"); + $ru = $var(subscribe_ru); + # Force change immediately: + # http://www.kamailio.org/wiki/tutorials/faq/main#why_changes_made_to_headers… + msg_apply_changes(); + } else if (is_method("NOTIFY")) { + xlog("Re-writing NOTIFY to remove tenant prefix\n"); # This code block does not get executed right now. + # We are storing the presentity_uri with a tenant prefix + # handsets do not expect this, only 101@, 102@ etc... In their BLF configs + # So this tenant prefix must be removed when building the reply. + route(TENANTINFO); + $var(notify_ru) = "sip:" + $(rU{s.substr,$(var(tenant_name){s.len}),0}) + "@" + $rd; + xlog("Re-writng NOTIFY to use: $var(notify_ru)\n"); + insert_hf("To: $var(notify_ru)\r\n", "From"); + $ru = $var(notify_ru); + # Force change immediately: + # http://www.kamailio.org/wiki/tutorials/faq/main#why_changes_made_to_headers… + msg_apply_changes(); + } +} Thanks for your time. Rhys Hanrahan Chief Information Officer Nexus One Pty Ltd E: support(a)nexusone.com.au<mailto:support@nexusone.com.au> P: +61 2 9191 0606 W: http://www.nexusone.com.au/ M: PO Box 127, Royal Exchange NSW 1225 A: Level 12 227 Elizabeth St, Sydney NSW 2000 [ttp://quintus.nexusone.com.au/~rhys/nexus1-email-sig.jpg]

1 0

kamcmd error
by Zhong, Alec (NSB - CN/Qingdao) 26 Mar '19

26 Mar '19

Hello Could you please help check below error? I encountered below error when to use kamcmd to get the value of one script_counter. [cid:image001.png@01D4E3EB.98F9BB70] BR, Alec

1 0

FW: add script counter.
by Zhong, Alec (NSB - CN/Qingdao) 26 Mar '19

26 Mar '19

Hello, Could you please help check below error for counters module? BR, Alec From: Zhong, Alec (NSB - CN/Qingdao) Sent: 2019年3月26日 10:56 To: 'sr-dev(a)lists.kamailio.org' <sr-dev(a)lists.kamailio.org> Subject: add script counter. Hello, Could you please help check below error? I would like to add a script counter to count the number of received message by kamailio. Anything wrong to use counters module? Should counters.so be loaded? Thank you in advance. Kamailio.cfg change [cid:image001.png@01D4E3C2.32E8DFB0] Kamailo log [cid:image002.png@01D4E3C2.8237E9D0]

1 0

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

2026

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 March 2019