sr-users

sr-users@lists.kamailio.org

54 participants
37560 discussions

Testers wanted for new TLS transport based on wolfSSL
by Richard Chan 24 Jun '22

24 Jun '22

Hello Kamailio users, I would like testers to try out a new module tls_wolfssl, an alternate TLS transport based on wolfSSL. Why another TLS transport implementation? The travails of using OpenSSL >= 1.1.1 in Kamailio’s multi-process paradigm has been documented by OpenSIPS (and that sister project has implemented tls_wolfssl). Essentially, OpenSSL makes no concessions to the multi-process use case and in fact has implementation details that work against global shared memory structures. As a result Kamailio contains some tricky code * a pthread polyfill in core * duplicated SSL_CTX per worker * atexit workaround How to test? The code is currently in master and can be built in the usual way. Debian has 5.2.0 libwolfssl-dev needed; for some RPM distros (el8, el9, fc36) I have created a Copr repository https://copr.fedorainfracloud.org/coprs/beaveryoga/wolfSSL/ Known limitations The current state can be considered as identical to tls+OpenSSL 1.1.1/3.0.x. Old TLS protocols < 1.2 and cipher list configuration don’t work, i.e., only TLS 1.2 and 1.3 work with the default cipher list. In your configuration just replace loadmodule “tls.so” with loadmodule “tls_wolfssl.so” The rest of the TLS configuration can remain unchanged unless you are using a funky protocol version/cipher list combination. Thanks! S-P

3 3

Kamailio Procedure
by Suporte 24 Jun '22

24 Jun '22

Hi Does anyone have the procedure model for Kamailio_cdrs, I'm trying to implement the model from the book, but the syntax error always appears. Thanks for the support. Adriano Vieira

3 2

problem getting the rtp packet source port
by hamed r 23 Jun '22

23 Jun '22

hello i have problem on receive source port rtp packet client-ip = 5.202.105.250 server-ip = 194.5.205.33 client2-ip = 188.212.241.46 In the 200 ok packet from client2 ,The value 4002 is set in the audio port [image: photo_2022-06-12_17-44-37.jpg] I expect rtp packets to be sent to me from source port 4002, but these packets are sent to me from another source , which is port 55755 in the image below, and I just opened this port(4002) in the firewall. If I turn on my firewall service, all packets will be dropped. I have to have this firewall [image: photo_2022-06-12_17-44-48.jpg] thanks for help me

3 2

Possibility of mirroring the rpm/deb.kamailio.org repos efficiently via rsync?
by Malte Schmidt 23 Jun '22

23 Jun '22

Hello, is there an rsync endpoint available or is there a possiblity of setting this up? Creating a mirror via HTTP is a rather quick and dirty solution and while the deb-repo can be mirrored using debmirror, the rpm repo is hard to sync to a non-CentOS-based machine due to missing dependencies such as yum and reposync in latest Debian-based systems. Would be great to get some input in regards to this topic. Cheers

3 3

What is the alignment of shm_malloc and friends?
by Richard Chan 22 Jun '22

22 Jun '22

Hi Daniel and kamailio users, In my integration adventure of wolfSSL and kamailio I have encountered an alignment issue sometime causing segfaults. May I enquire what is the alignment of shm_malloc and friends? The wolfSSL library integration requires that ser_malloc and ser_realloc return values aligned on alignof(_max_align_t) which in the case of x86_64 is 16. Thank you Shih-Ping

2 3

5.6 Package for Ubuntu 22.04 LTS?
by Mark Boyce 21 Jun '22

21 Jun '22

Hi all Any chance of Ubuntu 22.04 LTS "Jammy Jellyfish” being added to the Jenkins package builder for kamailio 5.6? Ubuntu native repo seems to have 5.5 in it. Thanks Mark

1 0

Finding advertised address of socket
by Tor Petterson 21 Jun '22

21 Jun '22

Hi I have a setup where Kamailio is connected to several telephony providers using different IP addresses to communicate with them. I am using the dispatcher module to route calls to the different providers. My question is if there is a way to get the advertised address of the socket chosen by dispatcher? I have a socket pointer in the XAVP but I can't figure out if it is possible to get the advertised address from it somehow. Thanks in advance. Tor

2 1

Record-Route advertised per branch
by Ilie Soltanici 17 Jun '22

17 Jun '22

Hello, Is there any way to advertise a different IP Address in the Record-Route header individually per branch? I have a setup here - where Kamailio is listening on 2 different interfaces: Local IP and External IP. At the moment if the packet is coming through the internal interface - I'm checking where is it going to and based on that I'm setting the Record-Route header accordingly - and everything works well, except when I have multiple branches: one going through the internal interface and another one through the external one, so in this case, I have to add a different record-route header per branch, by doing this in the branch_route - it's not working and getting the error: w_record_route_advertised_address(): Double attempt to record-route. What would be another way to accomplish this?

4 7

RTPengine in Debian
by Richard Fuchs 17 Jun '22

17 Jun '22

HI all, Just a quick heads up that RTPengine is now available in Debian sid/unstable mainline repositories. Big thanks to our own Victor Seva and Guillem Jover for making this possible. Cheers

4 4

set/add_contact_alias() difference
by ZZ Wave 17 Jun '22

17 Jun '22

Playing around with WSS support: if (nat_uac_test(64)) { force_rport(); ...... if (!add_contact_alias()) { xinfo("Error aliasing contact <$ct>\n"); sl_send_reply("400", "Bad Request"); exit; } set_contact_alias() throws this error on ACK without Contact, add_contact_alias() doesn't (and thats OK). Is this the expected behavior?

2 1

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