sr-users

sr-users@lists.kamailio.org

50 participants
37556 discussions

Re: [SR-Users] Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration
by Rhys Hanrahan 03 Apr '19

03 Apr '19

Hi All, I managed to solve my need to re-write NOTIFY packets with help from this thread: https://www.mail-archive.com/sr-users@lists.kamailio.org/msg08088.html This seems to work well. I am re-writing the packets as shown below… I guess my only question is, is this relatively safe/smart to do? I basically copied what our standalone Asterisk PBXes are doing in my captures, so I guess so? But I’m not confident enough to say it won’t cause some weird edge case issues. I can only say it works … [View More]fine with the Snom and Yealink handsets I am testing with. I’m just concerned because it feels a bit like a hack. For SUBSCRIBE I re-write: * Request URI and To header from 101@ sent by the handset to tenant101@ (to match the SIP username of the handset - tenant101@) For NOTIFY I re-write: * From and Contact header to remove the tenant prefix, to go back to 101@ to match the BLF key configuration on the handsets. Any advice would be appreciated on if this is a bad idea, and there’s a better way. Thanks! 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 From: sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of Rhys Hanrahan <rhys(a)nexusone.com.au> Reply-To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Date: Tuesday, 26 March 2019 at 8:56 pm To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration 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] [View Less]

1 0

uac_replace_from/to, msg_apply_changes and Re-INVITE
by Henning Westerholt 03 Apr '19

03 Apr '19

Hello, I am currently debugging a strange issue related to the usage of uac_replace_from/to() after msg_apply_changes(). It works all fine, but in a Re-INVITE case it inserts the wrong headers for the 100 - Trying case. The calle side gets then a reply with wrong From/To. This happens all the time with this particular cfg. I already checked for the usual issues: - msg_apply_changes() called several times - msg_apply_changes() called after transactions created/async processing etc.. Any … [View More]

3 8

TOPOS Call-ID masking
by Cinthia Leung 02 Apr '19

02 Apr '19

Greetings, Call-ID masking is not available, although the modparam is there. Just wondering if there are any plans to get that in soon. Thanks. Cindy

2 2

ENUM for CNAM dips
by Spencer Thomason 02 Apr '19

02 Apr '19

Hi all, I’m interested in extending the ENUM module to add support for draft-ietf-enum-cnam-08 CNAM queries using ENUM. I’m looking for high level guidance as to the best way to implement this and any feedback on naming of exported functions and parameters. Maybe something like enum_cnam_query("pvar", "destination", [,"suffix" [,"service"]]) ? Best regards, Spencer

2 1

Info: Kamailio World 2019 – Participation Grants
by Daniel-Constantin Mierla 02 Apr '19

02 Apr '19

Hello, we continue our tradition to give away 3 free passes to students and underrepresented people at Kamailio World Conference (www.kamailioworld.com) – thanks to the sponsors, we are able to offer them in 2019 as well. The passes cover the entire registration fee for all three days and the social networking events – costs with travel and accommodation have to be covered by the participants. Anyone enrolled in an academic activity (including master and PhD programs) as well as … [View More]

1 0

Port 5060 omitted in Record-Route
by Lợi Đặng 02 Apr '19

02 Apr '19

Hi all, i was using kamailio 4.2.1 located in 2 networks > listen = tcp:MY_ADDR:5060 advertise MY_ADDR:5060 > listen = tls:MY_ADDR:5061 advertise PUBLIC_NAT_ADDR:5061 when the call made from the inside network to out side, running `record_route()` resulted in 2 Record-Route headers added (enable_double_rr=1) Record-Route: PUBLIC_NAT_ADDR:5061;transport=tls;lr > Record-Route: MY_ADDR;transport=tcp;lr That was totally fine omitting the port in the first Record-Route when using tcp (… [View More]

3 5

Compressing SIP messages
by Igor Olhovskiy 01 Apr '19

01 Apr '19

Hi! Was looking on some way to compress SIP signalling between internal servers. But found out, there are no some pre-defined or recommended mechanism of doing this. Yes, I found gzcompress module, but it will help only in case of big body, but not whole message itself. Like in some cases you can have 4-5 RR headers, which is already a lot of info. What I googled is SigComp Compact Header form As I found, SigComp is really not widely-used method and it support along opensource SIP servers/… [View More]

8 11

presence_dialoginfo module not sending publish on dialogue change
by Richard Nunley 01 Apr '19

01 Apr '19

To whom can be of assistance, I’m am working towards enabling presence on my Kamailio proxy but have hit a bit of a brick wall. I’m seeing dialogues being created and persisted to the database, subscriptions are being handled and rows are being written to the active_watchers table but no PUBLISH is ever being received by the server to kickoff the sending of NOTIFY to the active watchers. Further, I’m never seeing a row in the watchers table though I don’t know that this isn’t expect behavior. … [View More]

3 2

Use Kamailio as forward proxy between two networks
by Lauritz 01 Apr '19

01 Apr '19

Hello, I am trying to implement the following network setup using Kamailio and RTPProxy, but was not able to find any recent documentation or blog posts with hints: > local_net1 : local_net2 > 10.250.10.* : 10.250.11.* > : > (1) (2) : > +-------------+ +--------------+ +--------------+ > ! !.11 .12 ! Proxy !.21 ! Debian Host !.22 > ! Starface !---------------! + Kamailio !<<--------------! + Linphone !.23 > ! ! ! + RTPProxy ! ! ! > +-------------+ +-----------… [View More]

2 1

Kamailio Managed Cloud
by Alex Balashov 01 Apr '19

01 Apr '19

For immediate release: ATLANTA, GA (1 April 2019)--Following its long tradition of forward-thinking innovation in open-source Real-Time Communications (RTC), the leadership of the Kamailio SIP server project (formerly known as OpenSER) has launched the Kamailio Managed Cloud (KMC). Alex Balashov of Evariste Systems and Fred Posner of The Palner Group were among several key North American stakeholders on hand to discuss it further. As Posner told us, "Kamailio Managed Cloud is a new, best-of-… [View More]breed managed Kamailio hosting environment. We provide elasticity by leveraging human capital. Using our patent-pending Orchestration Turk system, our managed cloud technicians will purchase your SuperMicro bare-metal server, known as a KamBox, drive to the data centre, and rack-and-stack it on demand -- all in response to a SOAP API call! And when you want to remove your on-demand KamBox, just issue a 'delete' operation and we will decommission the hardware -- live!" "Dedicated KamBox colocation really puts the Management in Managed Cloud," emphasised Balashov. "But that doesn't mean we keep the customer out of the loop. We are using the most modern XMLHttpRequest and 'AJAX' techniques to provide a real-time dashboard with KamBox status to all users, though it will not work with Internet Explorer 6 -- we're addressing that." "Anyway, there are numerous other cloud platforms out there, many of which rely on virtualisation and automated orchestration and the like. It really takes the human touch out of the equation and gives the short shrift to quality, while also taking away jobs. And besides, how can a so-called 'virtual' machine be truly carrier-grade?" Kamailio Managed Cloud launched in two principal regions today -- US-EAST-1, located in Jacksonville, Florida, USA, and EU-CENTRAL-1, based in the booming tech hub of central Europe and birthplace of OpenSER: Berlin, Germany. Unnamed sources tell us that strategic expansion is planned for several other regions, including Flint, Michigan, USA. The mechanics of Kamailio Managed Cloud have invited questions about how other elastic cloud resources are managed, more especially elastic storage. According to KMC senior management, storage is provided via a mechanism developed by ASIPTO StorageWorks. ASIPTO chief Daniel-Constantin Mierla was on hand at the KMC launch to explain: "It's very easy. When a customer requests more space with a simple and lightweight SOAP call with just a little custom XML namespaces, then depending on the region, Fred or I receive an SMS on our smartphones from our advanced PHP backend and drive to the data centre to insert another hard drive into one of the KamBox's several drive bays. We are using the latest in advanced mobile communications, SMS, to ensure fastest response time. Of course our service level is comprehensive and includes Managed Partition Table Labelling and Managed LVM Insertion. Also there is optional Managed Filesystem Formatting for a complete portfolio of managed services. ASIPTO StorageWorks moves at the speed of global e-business. Just text us your desired filesystem layout and partitioning scheme. It is really that easy!" When asked about business focus, marketing turnaround veteran Henning Westerholt, Executive Vice President of Business Development for KMC responded: "Our target customer is a socially conscious Millennial-run corporation or start-up who see value in the unique blend of managed services and an artisanal, hand-crafted, organic approach that is compatible with social justice and takes a people-centric view." Asked to elaborate upon his vision of social justice, Westerholt added: "Virtualisation, orchestration and auto-scaling take the people out of the equation, and Kamailio is, in the end, about people, as communication in general is about people. What would it be without the people? Moreover, these mechanisms take away gainful opportunities from hard-working university graduates. Kubernetes, Docker Swarm, VMWare, and KVM contravene the social policy objective of full employment." At press time, Posner, who also heads up KMC Labs North America, was said to be lending his pioneering business vision and knack for seeing around technology trend corners to intensive work on next-generation, bleeding-edge functionality for KMC. While Posner was tight-lipped about the specifics, he did state that the 'dispatcher' module is slated to be deprecated in favour of a "human load-balancing approach to SIP requests that is both cloud-native and eco-conscious". Industry analysts agree that protocol-aware load-balancing strategies are complicated and that the application of human judgment to the problem represents a fertile field for dynamic innovation and investment. Reports from regional press confirm that KMC Labs are in the process of building a fullfilment centre for this innovative offering, said to be branded "Central Switchboard", at an undisclosed site in Bangladesh, where thousands of "Load Balance Operator" jobs have been advertised in and around the Dhaka market. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ [View Less]

1 0

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