sr-users March 2019

sr-users@lists.kamailio.org

78 participants
100 discussions

by Duarte Rocha

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

5 years, 8 months

Disable Dispatcher GW from DB

by Patrick Wakano

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

5 years, 8 months

Presence module. How to update contact DB record after re-SUBSCRIBE ?

by Denys Pozniak

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

5 years, 8 months

Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration

by Rhys Hanrahan

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]

5 years, 8 months

kamcmd error

by Zhong, Alec (NSB - CN/Qingdao)

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

5 years, 8 months

FW: add script counter.

by Zhong, Alec (NSB - CN/Qingdao)

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]

5 years, 8 months

User part on contact header

by Duarte Rocha

Greetings, On an INVITE the user part in the Contact header mandatory? Can't seem to find info on this. Best regards, Duarte Rocha

5 years, 8 months

Default port interference in TLS conneciton

by Dalibor Zeman

Hello, I am running Kamailio v. 5.1.2 with typical configuration for wss connections (default config + tls, websocket, nathelper modules), quite everything is running as should, but I am quite concerned about what I got on Homer server. My Kamailio is listening on port 4443 for TLS. Opening dialog runs as should, then UPDATE and BYE messages are received on 4443, but sent out on 5060. When I don't set up default port, 403 reply comes on a call. I'd like to know whether it is something defined by standard or it has a meaning and I should leave it as it is, or I should correct it somehow and then how. Also, if it has a meaning, then what it is. Thanks for your answer, Dalibor Zeman.

5 years, 8 months

Modifying NOTIFY of presence_dialoginfo

by Kevin Olbrich

Hi! I need to customize the content of the NOTIFY sent by presence_dialoginfo. How can I change the message before it is sent? Kind regards Kevin

5 years, 8 months

KEMI Ruby - exit from within function

by Andrew White

Hi all, I know ruby is pretty new to KEMI, so I understand this might not be supported. I’ve been able to build a functional basic configuration using KEMI based app_ruby. However the function KSR::x.exit is not exposed to the interpreter. Reading up on the function (https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/kemimods/… <https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/kemimods/…>) I can see either a native `exit` or a return from the request_route is recommended. The latter of these works fine, however the former throws the following error when called either within the request_route function or any others: Mar 22 03:40:46 guest /usr/sbin/kamailio[17474]: ERROR: {1 19731 BYE 8u6We4ReU01GuU-zoa7VuqC.qWwwg29S} app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: exit Mar 22 03:40:46 guest /usr/sbin/kamailio[17474]: ERROR: {1 19731 BYE 8u6We4ReU01GuU-zoa7VuqC.qWwwg29S} app_ruby [app_ruby_api.c:1078]: app_ruby_run_ex(): ruby exception (6) on callback for: ksr_request_route (res type: 17) It appears the app_ruby wrapper is seeing an exit as an exception and throwing an error. I’m unsure if this is affecting my actual flow (still building the config), but the error in the logs is certainly annoying. Returning from the request_route function works fine, however this is obviously harder to do from within a sub function. Any direction on how to correctly exit in similar ways to native or other KEMI implementations would be appreciated. By the way, thanks Daniel for writing this module! This makes Kamailio significantly more accessible for myself and others like me! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

5 years, 8 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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