sr-users March 2024

sr-users@lists.kamailio.org

44 participants
45 discussions

RFC: move app_lua_sr to kamailio-archive

by Victor Seva

Hi, I would like to move app_lua_sr to kamailio-archive but I would like to hear if anyone out there has a solid reason not to do it. Since we have app_lua as KEMI for a long time I think is time to retire the old remains of app_lua Cheers -- ----------------------------------------------------------------- | ,''`. Victor Seva | | : :' : linuxmaniac(a)torreviejawireless.org | | `. `' PGP: 8F19 CADC D42A 42D4 5563 730C 51A0 9B18 CF5A 5068 | | `- Debian Developer | -----------------------------------------------------------------

8 months

Dialog and DMQ on restart

by Björn Klasen

Hi everybody, I'm just testing Kamailio 5.4.1 with dialog replication over DMQ. This seems to work very good. Dialogs are replicated without problems. When I'm restarting one node I would have expected, that all dialogs are synced again, just like in dmq_usrloc. But this does not happen. After a restart the nodes dialog-list is empty. Did I miss somethin? Is there a special parameter that I have to set? BR, Björn -- Björn Klasen, Specialist TNG Stadtnetz GmbH, Network Management (VoIP) Projensdorfer Straße 324 24106 Kiel Germany T +49 431/ 530530 F +49 431/ 7097-555 mailto: bklasen(a)tng.de http://www.tng.de Register: Amtsgericht Kiel HRB 6002 KI Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg, Sven Schade, Carsten Tolkmit, Dr. Sven Willert Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428

8 months

RTP Engine with Kamailio

by Vishal Pai

Hello Everyone. I am looking for documentation to have multiple RTP Engine servers connected with kamailio using db url and balance the load accordingly. Thanks

8 months

Kamailio to aid in seamless data center migration?

by Brad

I need to move a few dozen FreePBXen with some commercial modules running in individual VMs to a new data center. I’m trying to work out a plan to move the PBXes to the new data center in a way that will be transparent to the endpoints, or at the very least with the absolute minimum of downtime. Some of the installations are rather old, and there’s a handful of peculiarities on each, so the typical FreePBX backup/restore process hasn’t gone smoothly, at least in our tests. My current train of thought is to put a clone the VMs in the new data center and use Kamailio to route the SIP traffic to the new servers/IPs. I’ve never used it before, so I may be barking up the wrong tree, but it /appears/ to do what I’m suggesting. If so, I’m thinking I can install Kamailio on each VM, point it to the local asterisk/FreePBX initially, and clone the VM. Then, after the new instance is up and running, point Kamailio on the original VM to the cloned VM's asterisk, after which I can make appropriate DNS changes. Another option would be to stand up a single Kamailio server and redirect SIP traffic destined for individual asterisk servers to it at the router. Endpoints are mostly Yealink, and I’m not sure if they’ll feel the need to restart when the registration/SIP server’s IP changes, but a quick bounce when not in use isn’t the end of the world. I’d very much like to avoid having to send an update to each phone manually, but I can script a SIP NOTIFY if required. Anything stupid, wrong, ignorant, or just smelly about this tactic? Or, for that matter, any other suggestions?

8 months

RFC5626 Keep-Alive with CRLF

by Ihor Olkhovskyi

Hello, A bit generic question, does Kamailio supports CRLF keepalive per https://www.rfc-editor.org/rfc/rfc5626#section-4.4.1 ? It's more for tracking TCP connection states, as seems tcp_keepalive_enable is not super reliable especially in mobile networks. -- Best regards, Ihor (Igor)

8 months

Branch Route trigger for Withindialog calls?

by Benoit Panizzon

Hi List I am just wondering... When I am sending the initial INVITE to a customer CPE, this goes throug the whole location lookup and through a branch route in which I make some last adjustments to the headers, like removing header the customer shall not get (like P-Asserted-Identity which would reveal the caller identity on a callerid restricted call). On a Re-Invite (session timer refresh) the call is being routed by loose_route() and immediately sent to RELAY. uac_replace and uac_restore seem to work fine for stuff like To and From Header. But how do I prevent unwanted header to disclose information to the customer which should ne be disclosed? Do I need to re-arm the branch trigger also for within dialog calls? 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 ______________________________________________________

8 months

loose_route false when using topos? At which point in the call flow, does topos restore the Route header?

by Benoit Panizzon

Hi https://lists.kamailio.org/pipermail/sr-users/2020-July/109801.html I have the exact same issue. When the B side is starting a new transaction (UPDATE to refresh the session in my case) without topos enabled, that transaction contains one or multiple route header and a to_tag. Therefore loose_route() is true and the call is more or less sent to route(RELAY) immediately without further checks. If topos is enabled, all record-route header are removed and only one Via sent to the CPE. So when the CPE replies, there is no Route header. Therefore loose_route returns false. This makes me wonder, at which stage is topos restoring the route headers? Shouldn't that happen before loose_route is evaluated? 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 ______________________________________________________

8 months

No 408 generated by tm module on fr_timer when redis crashes

by Patrick Karton

8 months

Wrong documentation for module 'Userblacklist'

by Björn Klasen

Hi everybody, I'm a little bit confused about the documentation of the Userblacklist module as I think it has to be Userblocklist since version 5.x. Also some of the commands and some column names in the database have changed. I can remember that the documentation was right at some point, but the it has been changed back to Userblacklist. I wonder if nobody noticed that because the old commands do not work. BR, Björn -- Björn Klasen, Senior Specialist (VoIP) TNG Stadtnetz GmbH, TNG-Technik Gerhard-Fröhler-Straße 12 24106 Kiel・Deutschland T +49 431 7097-10 F +49 431 7097-555 bklasen(a)tng.de https://www.tng.de Executive board (Geschäftsführer): Dr. Sven Willert (CEO/Vorsitz), Gunnar Peter, Sven Schade, Carsten Tolkmit, Bernd Sontheimer Amtsgericht Kiel HRB 6002 KI USt-ID: DE225201428 Die Information über die Verarbeitung Ihrer Daten gemäß Artikel 12 DSGVO können Sie unter https://www.tng.de/datenschutz/ abrufen. ______________________________________________________________________

8 months

Bug in htable in 5.8.0

by Brooks Bridges

We have some scripts that are setting values in an htable for various things, one of which is to disable options replies to take a system “out of service”. We discovered today upon deploying 5.8.0 that the “htable.seti” command appears to be broken. [root@ip-10-52-42-102 ~]# kamcmd htable.seti system_settings option_pings_off 1 error: 500 - Not enough parameters (htable name, key name and value) however if we do htable.sets it works fine (although not an integer so it’s breaking our shutdown scripts). [root@ip-10-52-42-102 ~]# kamcmd htable.sets system_settings option_pings_off 1 Ok. Key set to new value. [root@ip-10-52-42-102 ~]# I’ve looked through the commit history for htable and haven’t found anything that really stands out as a possible issue, so can the gurus please take a look? Thanks! Brooks Bridges Sr. Developer [https://files.skyetel.com/logo.png] Direct: (888) 444‑1111 Office: (561) 453‑4085 Email: bbridges(a)skyetel.com 902 Clint Moore Road Suite 206 Boca Raton, FL 33487 www.skyetel.com Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

8 months, 1 week

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 2024