sr-users May 2024

sr-users@lists.kamailio.org

50 participants
64 discussions

Via header force change protocol to TLS?
by Anthony Alba 30 May '24

30 May '24

I have kamailio behind a TLS termination proxy so the sockets are correctly deduced to be TCP. However the clients only talk TLS to the proxy and are confused when the top Via header added by Kamailio is TCP. Is there a way for Kamailio to forcibly pretend its protocol is TLS? Like advertised_address but "advertised_protocol" instead. (With pjsip testing: it has a flag use_tls which ignores TCP from Kamailio and continues to use the persistent TLS transport to proxy. Linphone fails because it tries to honor TCP in Via and is unable to establish TCP transport). BTW I am using t_relay_to_tcp so Kamailio will return traffic to the proxy as TCP even though the contact addresses specify transport=TLS.

4 10

libstirshaken installation issues
by tfayomi＠untangledtechnology.com 30 May '24

30 May '24

Hi All, I am attempting to install the stirshaken module for kamailio and I ran into a couple issues installing the open source c library for libstirshaken. When I use the make command, I'm getting this error: src/stir_shaken.c: In function 'stir_shaken_is_key_trusted': src/stir_shaken.c:726:9: error: 'EVP_PKEY_cmp' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 726 | if (!EVP_PKEY_cmp(pkey, candidate_pkey)) { | ^~ In file included from /usr/include/openssl/x509.h:29, from /usr/include/openssl/ssl.h:31, from /usr/include/libks2/libks/ks_ssl.h:25, from /usr/include/libks2/libks/ks.h:80, from include/stir_shaken.h:15, from src/stir_shaken.c:1: /usr/include/openssl/evp.h:1418:5: note: declared here 1418 | int EVP_PKEY_cmp(const EVP_PKEY *a, const EVP_PKEY *b); | ^~~~~~~~~~~~ At top level: cc1: note: unrecognized command-line option '-Wno-gnu-zero-variadic-macro-arguments' may have been intended to silence earlier diagnostics cc1: all warnings being treated as errors make: *** [Makefile:1337: src/stir_shaken.lo] Error 1 I tried going into the stir_shaken file and changing EVP_PKEY_cmp to EVP_PKEY_eq, but it just brings up more deprecation errors. I also tried rolling back the openssl version on my machine to openssl version 1.1 and changing EVP_PKEY_eq back to EVP_PKEY_cmp, but the same error persists. Is there any way to resolve this error, or is there another library that can be used to get the stirshaken module for kamailio? Thanks in advance, Temi

6 7

Is udp_mtu and udp_mtu_try_proto broken in kamailio v5.8
by Supreeth Herle 30 May '24

30 May '24

Hello, I have a dockerized IMS setup using kamailio from git commit id 4fb8accc6747ad56fec3dc84d70cb2b8bbd7316e (tag 5.8.x), where I am seeing an issue faced by one of the users of the dockerized IMS. The issue is that the SIP request (in UDP) even though it exceed the MTU of 1300 (udp_mtu=1300 and udp_mtu_try_proto=TCP) the SIP request from P-CSCF is not sent out as a TCP. The pcap and P-CSCF logs in debug can be found in the github issue - https://github.com/herlesupreeth/docker_open5gs/issues/316#issuecomment-213… IP of the containers are follows: P-CSCF - 172.22.0.21 S-CSCF - 172.22.0.20 SIP Client - 192.168.101.x P-CSCF is configured with udp_mtu=1300 and udp_mtu_try_proto=TCP In the pcap you can notice that the SIP NOTIFY originating from S-CSCF is forwarded to P-CSCF (packet no. 698) and packet length is 2716. At this point P-CSCF should have tried to convey the SIP packet to SIP client via TCP. But I dont see any TCP connection establishment either and eventually request times out (packet 1147). [image: image.png] Any help or insights would be highly appreciated. Thanks and Regards, Supreeth

1 0

Re: Failover with dialog dmq while dialog state 2
by Björn Klasen 27 May '24

27 May '24

Hi Henning, thank you for your reply. I did a lot testings during the past days and I think I found a solution that is working, although it's very dirty... I found out it is possible to send a manual KDMQ-Message to all Proxy-Nodes including the one that it sending die KDMQ-Message. So I create a dialog state 4 message on ACK and indeed the Dialog on all Peers are Updated correctly to state 4. I also tried this for state 3 on 200 OK, but this does not work. I haven't had a look into the code yet but my experiments shows, that there is never is state 3 update via DMQ, so I think it's not implemented. Interestingly the TM-Timer still times out after 300 seconds but in normal circumstances this doesn't bother, because either the failed Kamailio will not trigger this, because the Software or the Server crashed, or it tries to send a CANCEL that is denied because we are in dialog state 4. The only thing is your really have to be careful about your hash tables. You have to delete them at the correct point. I really need to test a lot at this point, but till now, billing seems to be OK even on failover scenarios. This is why I really like Kamailio :) BR, Björn Am 09.05.24 um 20:57 schrieb Henning Westerholt: Hello, thanks for the detailed e-mail. As also indicated in the module documentation, the dialog module DMQ replication will not replicate everything, its main use-case is for profile data sharing. https://kamailio.org/docs/modules/5.8.x/modules/dialog.html#dialog.p.enable… In the past months there have been some other discussions on the users lists about similar scenarios (I think related to billing/accounting) and dialog with DMQ, which might be interesting for you in this regard. If you find issues where the DMQ synchronisation is lacking some functionality in the dialog module, you can create a feature request in our issue tracker. There is of course no guarantee that this limitation is also timely addressed. Regarding the INVITE and CANCEL scenario, this is usually not related to dialog but to the tm module. As you also mentioned, there is no replication of transaction state in tm. Cheers, Henning -- 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<mailto:bklasen@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. ______________________________________________________________________

2 3

I'm looking for an get_rr_param() usage example
by Benoit Panizzon 27 May '24

27 May '24

Hi Gang To process spiraling calls without the dialog module. I'm trying to use a rr param to identify in which iteration I am. So when I have a call spiraling through the same instance 3 times, every time I process an invite I would do something like: add_rr_param(";sp-count=$avp(sp-count)"); But to initialize that counter, I need to be able to read what is in there beforehand. if (check_route_param("sp-count=") { get_route_param(msg, "sp-count", $avp(sp-count)) $avp(sp-count) = $avp(sp-count) + 1; add_rr_param(";sp-count=$avp(sp-count)"); } else { add_rr_param(";sp-count=1"); } But what do I pass as msg parameter? Is it the PV $msg(hdrs) ? PS: I need this to append this to the call ID for rtpengine so I hopefully can match new transactions no matter from which side they are initiated to the correct rtp stream. 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 ______________________________________________________

1 0

Is there any funtion to route based on source phone number
by SAMUEL MOYA TINOCO 27 May '24

27 May '24

Hi everyone, I have a kamailio configured to send invites from different phone numbers registered in kamailio to different endpoints. The configuration that I have right now is a big if chain with the phone numbers that then sends the invite using dispatcher module. Example: If (phone number in invite = phone number X) { dispatcher sends to endpoint X} If (phone number in invite = phone number Y) { dispatcher sends to endpoint Y} If (phone number in invite = phone number Z) { dispatcher sends to endpoint Z} Im not sure if this is the correct way of doing this or if there is any module that can do this allowing me to configure it using BBDD instead of kamailio configuration. I started doing it like this on our test environment while I was learning how to use kamailio and I'd like to know if this is the right way to do it or if I should do it with other methods Thank you in advance

7 7

Fwd: rtpengine timestamp jumps
by Jeff Brower 26 May '24

26 May '24

Rtpengine support- I am re-posting again, as I noticed on the SR-USERs web page no HTML or inline images are showing (https://lists.kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio…). The Wireshark screencap that demonstrates the issue is uploaded at: https://www.signalogic.com/images/rtpengine_wireshark_capture_timestamp_jum… all other info remains the same. Thanks, Jeff ----- Forwarded message from Jeff Brower <jbrower(a)signalogic.com> ----- Date: Fri, 17 May 2024 17:10:10 +0000 From: Jeff Brower <jbrower(a)signalogic.com> Subject: Fwd: [SR-Users] rtpengine timestamp jumps To: sr-users(a)lists.kamailio.org Reposting this. If there is an issue with HTML format and/or wireshark screen cap and I need to upload that separately somewhere else, please let me know. Thanks. -Jeff ----- Forwarded message from Jeff Brower <jbrower(a)signalogic.com> ----- Date: Thu, 09 May 2024 05:32:27 +0000 From: Jeff Brower <jbrower(a)signalogic.com> Subject: [SR-Users] rtpengine timestamp jumps To: sr-users(a)lists.kamailio.org Hi rtpengine experts, We have some customers processing long multi-party call pcaps using mediaMin who are reporting large amounts of packets with timestamp jumps but no packet loss (for instance 10% of packets over a 1 hr 45 min call). For example, in the Wireshark excerpt shown below, packets 6 and 8 sent by rtpengine show a timestamp increment of 640, but sequence number increment of 1: [screencap link at https://www.signalogic.com/images/wireshark_capture_timestamp_jump.png] In the mediaMin output packet log we typically see sections similar to: : : Seq num 98584 timestamp = 3902252372, rtp pyld len = 33 media-R Seq num 98585 timestamp = 3902252692, rtp pyld len = 33 media Seq num 98586 timestamp = 3902253012, rtp pyld len = 33 media-R Seq num 98587 timestamp = 3902253332, rtp pyld len = 33 media Seq num 98588 timestamp = 3902253652, rtp pyld len = 33 media-R Seq num 98589 timestamp = 3902253972, rtp pyld len = 33 media Seq num 98590 timestamp = 3902254292, rtp pyld len = 33 media Seq num 98591 timestamp = 3902254612, rtp pyld len = 33 media-R Seq num 98592 timestamp = 3902254932, rtp pyld len = 33 media Seq num 98593 timestamp = 3902255252, rtp pyld len = 33 media Seq num 98594 timestamp = 3902255572, rtp pyld len = 33 media-R Seq num 98595 timestamp = 3902255892, rtp pyld len = 33 media Seq num 98596 timestamp = 3902256212, rtp pyld len = 33 media Seq num 98597 timestamp = 3902256532, rtp pyld len = 33 media Seq num 98598 timestamp = 3902256852, rtp pyld len = 33 media-R Seq num 98599 timestamp = 3902257172, rtp pyld len = 33 media Seq num 98600 timestamp = 3902257492, rtp pyld len = 33 media-R Seq num 98601 timestamp = 3902257812, rtp pyld len = 33 media Seq num 98602 timestamp = 3902258132, rtp pyld len = 33 media Seq num 98603 timestamp = 3902258452, rtp pyld len = 33 media Seq num 98604 timestamp = 3902258772, rtp pyld len = 33 media-R Seq num 98605 timestamp = 3902259092, rtp pyld len = 33 media : : where media-R packets are timestamp gap repairs (i.e. frame loss concealment). The behavior tends to be bursty, but once it gets going it goes for a while and seems relatively consistent. Is this expected behavior for rtpengine ? If so is rptengine in turn dealing with some type of "slow packet rate" issue from a remote sender ? Thanks, Jeff ----- End forwarded message ----- ----- End forwarded message -----

2 4

core children setting
by Alexis Fidalgo 24 May '24

24 May '24

Hello all, im not clear on the children setting, currently we’re listening in a single UDP port, i do understand that children are how many forks per listener ip:port, but i have this question, is this value tied on how many requests are received? In our case every requests takes an average of 80ms to be processed (there are a few external queries executed per request), so, example which value for children should i use if i have 200req/s, 300, 400? Right now im using 16 but i can see some cpu peaks in high traffic hours. thanks

2 2

"Contact does not exist in PCSCF usrloc" error in log
by Shantanu K Roy 23 May '24

23 May '24

Hello, We are trying to integrate Kamailio as the IMS server with our 5G core emulator by following the steps listed out at https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. In our case, we have our own 5G core emulator instead of the Open5GS core. We are using sipp scripts to generate the SIP calls. The PCRF component of the 5G core is emulated by us and is capable of handling Diamater calls from Kamailio over the Rx interface. We have got the setup working to the point where the SIP Register calls are landing on the PCSCF which in turn is sending out AA Requests to PCRF and the PCRF is responding. However there is an internal error in the Kamailio log "4(3682133) ERROR: ims_qos [ims_qos_mod.c:1305]: w_rx_aar_register(): This contact does not exist in PCSCF usrloc - error in cfg file" Please help us in identifying if we are missing anything in the Kamailio set up. The packet capture and syslog excerpts from the VM where Kamailio is running are attached; here we are trying to perform SIP Registration for three SIP endpoints 001010123456791, 001010123456792 and 001010123456793. If there is any additional information required, please let us know. Regards, Shantanu

1 0

VoLTE/IMS third party registration issues
by ruben.iniguez＠vodafone.com 23 May '24

23 May '24

Checking Kamailio in a VoLTE environment we are finding issues to make it work. First issues arise when getting AS to extract the required info from third party registration, primarily IMPUs. Third party registration is sent to AS with IMPI in To header, preventing the AS from extracting the IMPU from the most obvious place, the To header, according to 3GPP 24.229: "Notification of Application Servers about registration status [...] the To header field, which shall contain a non-barred public user identity belonging to the service profile of the processed Filter Criteria. It may be either a public user identity as contained in the REGISTER request received from the UE or one of the implicitly registered public user identities in the service profile, as configured by the operator;" On the other hand, the third party registration can only embed in its body either the original request or the original response but not both (notice mutually exclusive "else if" statements in third_party_reg.c). Both are needed to extract Feature-Caps (from original request) and IMPUs (for instance from P-Associated-URI in original response). Therefore to extract that info the AS should subscribe to the reg info in S-CSCF, but such SUBSCRIBE is rejected with 403. From Registrar IMS SCSCF documenation it looks like this is not supported: "This function checks to see that a SUBSCRIBE request is authorised to subscribe to the particular identity. Only 3 entities can subscribe: The user agent to its own state The P-CSCF specified in the path header for that user Application Server (AS) not yet implemented" Therefore question to the community is how these limitations are overcome in existing VoLTE deployments with Kamailio? Any advice?

1 0

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