hello is there a cleaner/fastest way to update PAI header user part other than using subst
i come up with
subst('/^P-Asserted-Identity:(.*)(sip|sips|tel|tels):([^@]*)@([a-zA-Z0-9.]+)(.*)$/P-Asserted-Identity:\1\2:$var(newPAIUser)@\4\5/ig');
Thanks.
Hi Gang
Next question.
I have some broken CPE which do not set a=ptime despite using 20ms which
then causes the call to get rejected in certain destinations, because
ptime header is missing.
So I would like to match the user-agents in question and add back
a=ptime:20
Google searches found an user with the exact same problem almost 10
years ago and Daniel replying that indeed a function to add a body line
would be handy.
https://www.kamailio.org/docs/modules/devel/modules/textops.html
How could this be accomplished? I don't see a add_body_line or other
function which does not 'replace' a body line.
--
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
______________________________________________________
Hi
I have a setup where Kamailio is connected to several telephony providers using different IP addresses to communicate with them.
So I have a socket per provider.
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
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
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
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
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
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
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
