sr-users February 2024

sr-users@lists.kamailio.org

49 participants
43 discussions

best approach to setup SIP Session sharing between servers
by Sergio Charrua 28 Feb '24

28 Feb '24

Hi all! I am having some difficulties/doubts on what would be the best approach to let multiple Kamailio servers share their SIP sessions between each other. The goal is to have HA on Kamailio cluster such that if a call is received and initiated on Kamailio #1, and during any moment of the call (before or while established) if the server #1 goes down or Kamailio stops working for any reason, the call can be processed by Kamailio server #n available in the cluster. I do not want to mess with Virtual IPs or DNS, that is not the point, but instead need to get a proper way to share SIP sessions between Kamailio servers such that any server could continue the call without issue. I have checked the Dialog and DMQ module, but I am not sure if that is the way to go.... Could any one share a solution for this? Greatly appreciated. Cheers, *Sérgio Charrua* *www.voip.pt <http://www.voip.pt/>*

8 11

Clarification on pv_www_authenticate
by James Lipski 28 Feb '24

28 Feb '24

Hello, I would like get further information on the "pv_www_authenticate" function from auth module. For the response code "-1", which is listed as "generic error", what exactly is covered when this function returns this? Is it just everything else that isn't listed reason (invalid password, nonce expired, no credentials, etc...). On my production system, I'm seeing this as a response code on some registration requests, and just want to know what is causing this (enabling full verbose logging is a bit difficult on my production system, and want to try to replicate it on my test environment, however just need clarification on what this covers). Thank you.

2 1

Topos methods_nocontact parameter
by Benoit Panizzon 27 Feb '24

27 Feb '24

Hi I'm having another go at topos trying to solve an issue of sip messages getting to big for certain clients to process. Unfortunately some methods (ACK/PRACK/BYE probably CANCEL) do not contain a contact header, therefore the topology is still revealed (and potentially a lot of via header inserted increasing message size). Is it safe to set methods_nocontact to an empty string to force creation of a Contact header for every SIP method? Is there another way to completely hide topology aka keeping header small? 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 ______________________________________________________

3 7

How to keep SIP messages small, possibly below fragmentation limit?
by Benoît Panizzon 26 Feb '24

26 Feb '24

Hi In the process of getting rid of our commercial B2Bua SBC and handling all clients directly via Kamailio... We have come across some (unfortunately many we have in use) CPE which have an issue with fragmented packets or which simply do not allocate enough memory to parse or create messages of a certain size. Their SIP stack just crashes with errors like 'message to large for send buffer' and similar. This affects messages with containing as little as 5 via and 4 record-route header and a couple of codec in the SDP. Is there a recipe for trying to keep packets as small as possible? I would like to avoid using the topos module as I issues with this module completely failing in certain situations. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- 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

Development is open for future release of v5.9.x series
by Daniel-Constantin Mierla 23 Feb '24

23 Feb '24

Hello, the branch 5.8 was created, therefore the master branch is open for adding new features, to be part of future release series v5.9.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.8.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.8 or 5.7. Expect that v5.8.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.9.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime during the last part of 2024 or the beginning of 2025. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

1 0

Branch 5.8 has been created
by Daniel-Constantin Mierla 23 Feb '24

23 Feb '24

Hello, the branch 5.8 has been created, to be used for releasing v5.8.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.8 cd kamailio-5.8 git checkout -b 5.8 origin/5.8 Pushing commits in this branch: git push origin 5.8:5.8 Note that 5.8 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.8 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.8 will be out, respectively Kamailio v5.8.0. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

1 0

Building Debian packages for further modules
by Christian Berger 22 Feb '24

22 Feb '24

Hi, for our workflow we build our own Debian packages for kamailio. We are currently trying and failing to create a package for the kafka modules. What we have tried so far: Adding the "Build-Depends:" entries for librdkafka-dev in debian/control Adding a "Package" in debian/control Adding kafka to the PACKAGE_GROUPS in debian/rules So far it seems to build the module and a package for it, but the package only contains metadata, but no .so file. We are currently running out of ideas. What else can we do? Best wishes Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

2 2

Kemi questions
by Stefan-Cristian Mititelu 21 Feb '24

21 Feb '24

Hello, When writing kemi cfg (python in my case), is there any way to get rid of standard cfg shared variables and use kemi cfg variables instead? E.g. Instead of $shv(blabla) (in standard config) can I use some global python var called 'blabla'? Is it seen and shared by all kamailio processes? Or I still need to use KSR.pv.get/set("$shv(blabla)") ? Thank you, Stefan

2 3

Freeswitch and Kamailio Integration.
by jayapal＠ring4.com 21 Feb '24

21 Feb '24

Greetings, I am new to Kamailio and seeking assistance. I have installed FreeSWITCH version 1.10.11 and Kamailio version 5.6.5. I have two inquiries: I aim to configure FreeSWITCH with Kamailio. Could someone kindly guide me on achieving this integration? I am curious about the storage location of Kamailio's log files. Could someone please provide information regarding this? Thank you in advance for your help and guidance.

4 4

htable write access state
by Patrick Karton 21 Feb '24

21 Feb '24

Hello are htable protected for multiple write access? can i safely update htable from one process and be sure another process will access it for write operation ? if yes is the lock on all the htable or only on the bucket where the key belongs ? Thanks.

2 1

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 February 2024