sr-users December 2022

sr-users@lists.kamailio.org

54 participants
67 discussions

outbound Edge Proxy
by Giovanni Iamonte 06 Dec '22

06 Dec '22

Dear List In the last week I try to figure out how I can put in place a configuration that use an edge proxy and a register by using kamailio 5.6, but i am facing some issues. Scenario: We are using on ubuntu 20.04, HAproxy and Kamailio 5.6. We have configured a Kamailio register that, in the following case, perfectly works. ______ __ __________ TLS | | TLS | | Client ------------------ > | NAT |-----------> | Kamalio | in |_HAProxy | out in | Register | |_________| | | |________ _| Now we want to put a kamailio edge proxy before the kamailio Register, please take a look to the below picture ______ ______ __ _________ ___________ TLS | | TLS | | TCP | | Client ------------------ > | NAT |-----------> | Kamalio | -------------> | Kamailio | in |_HAProxy | out in | Edge | out in | Register | |_________| | Proxy | | | |_________| |___________| HAproxy -> sip-test.example.com Kamailio edge proxy -> 192.168.58.1 Kamailio Register -> 192.168.58.15 The kamailio Edge has been configured as indicated in the outbound module example. When a transaction such as REGISTER or SUBSCRIBE reach the "Kamailio Register" the Record-Route and Via headers are correct and it works. When the transaction such as MESSAGE or INVITE reach the "Kamailio Register" it does not work and below you can see the message and the error. Note that the Record-Route and Via headers are the same as the previous message REGISTER and SUBSCRIBE. Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: INFO: {1 40742 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <script>: SIPMessage-in-request = 192.168.58.1:53606-sip:s-user.02@sip-dev.example.com-MESSAGE sip:s-user.02@sip-dev.example.com SIP/2.0 Record-Route: <sip:192.168.58.1:15006;transport=tcp;r2=on;lr> Record-Route: <sip:sip-test.example.com:16005;transport=tls;r2=on;lr> Via: SIP/2.0/TCP 192.168.58.1:15006;branch=z9hG4bKa257.add27f134dd83c78aef13ca7798f87ca.0;i=6 Via: SIP/2.0/TLS 192.168.58.1:39592;received=192.168.58.1;rport=39592;branch=z9hG4bKPjajkY.0NlW2AFuz3.BRaKH4EdvdmQTs9L;alias Max-Forwards: 69 From: <sip:s-user.03@sip-dev.example.com>;tag=VnOekkKsq4tLhFAywXzbxLXxIesWscn3 To: <sip:s-user.02@sip-dev.example.com> Call-ID: YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET CSeq: 40742 MESSAGE Accept: text/plain, application/im-iscomposing+xml Content-Type: text/plain Content-Length: 59 ################## MESSAGE ################### Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: INFO: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <script>: SIPMessage-in-request = 192.168.58.1:53606-sip:s-user.02@sip-dev.example.com-MESSAGE sip:s-user.02@sip-dev.example.com SIP/2.0 Record-Route: <sip:192.168.58.1:15006;transport=tcp;r2=on;lr> Record-Route: <sip:sip-test.example.com:16005;transport=tls;r2=on;lr> Via: SIP/2.0/TCP 192.168.58.1:15006;branch=z9hG4bKb257.83b972054df1675806975159ae1f1e43.0;i=6 Via: SIP/2.0/TLS 192.168.58.1:39592;received=192.168.58.1;rport=39592;branch=z9hG4bKPjfan-Tte.vtL8brkWb20wm.5b8iuVEtQV;alias Max-Forwards: 69 From: <sip:s-user.03@sip-dev.example.com>;tag=VnOekkKsq4tLhFAywXzbxLXxIesWscn3 To: <sip:s-user.02@sip-dev.example.com> Call-ID: YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET CSeq: 40743 MESSAGE Accept: text/plain, application/im-iscomposing+xml Proxy-Authorization: Digest username="s-user.03", realm="sip-dev.example.com", nonce="Y48hMWOPIAW7JeSQ7/a+cuJ1gKwT8hrC", uri="sip:s-user.02@sip-dev.example.com", response="3b7c34476443e5f1125fa460a4981180", cnonce="3AT-ZMwyfpgaMwlulh5cq5vJHi75-wnz", qop=auth, nc=00000001 Content-Type: text/plain Content-Length: 59 Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: WARNING: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <core> [core/forward.c:228]: get_send_socket2(): protocol/port mismatch (forced tcp:192.168.58.15:15006, to tls:192.168.58.1:60982) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [ut.h:315]: uri2dst2(): no corresponding socket found for "192.168.58.1" af 2 (tls:192.168.58.1:60982) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [t_fwd.c:471]: prepare_new_uac(): can't fwd to af 2, proto 3 (no corresponding listening socket) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [t_fwd.c:1754]: t_forward_nonack(): failure to add branches Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (7/SL) based on what we have understood in the message headers "Via" and Record-Route" there are the right information to reach back the proxy Edge, but looking to the error message it seems that the kamailio register try to reach back the proxy edge through the TLS instead of using the TCP. Could someone put me in the right direction. Thanks Regards -- ------------------------------------------------------------------------ Ing. Giovanni Iamonte Developments and technologies area Quintetto Srl Via Monte Navale, 1 10015 - Ivrea (TO)  mobile: +39 393 9196310  tel: +39 0165 1845290  e-mail: giovanni.iamonte(a)quintetto.it  web: www.quintetto.it

2 4

Packet processing order
by Jawaid Bazyar 06 Dec '22

06 Dec '22

Hi, I have experienced out of order packet processing when testing a simple Kamailio config. The configuration is as follows, basically: request_route{ record_route(); enum_query(); xlog("INVITE ENUM query - To URI $tU"); forward(); } I saw this thread from 2020: https://www.mail-archive.com/sr-users@lists.kamailio.org/msg11786.html The issue seems to be that kamailio process scheduling is naïve – i.e., incoming SIP packets are processed without regard to whether packets received before this one, are currently being processed. This means any packets after the initial INVITE that require more processing, can get reordered. In my test lab I have: SIPp – UAC Kamailio Proxy SIPp – UAS The proxy uses enum NAPR lookups to route calls to +13038151000 to the UAS. Now, if I do SIPp UAC o SIPp UAS directly, I have no problems – no out of order packets. It is only when I introduce Kamailio in the middle that I get OOO packets. See the images attached: uac-to-proxy, proxy, and proxy-to-uas. In this example, Kamailio OOO causes SIPp UAC to fail to “generate audio” – because UAC does not see packets in the correct order, I never turns on the simulated audio. Calls that have in-order dialogs, work fine, and SIPP UAC “pauses” 10 seconds to simulate a phone call. So far, the error rate runs from 1/1000 to around 1/200 – pretty bad. In the thread, a few things were suggested. Have fewer kamailio processes than cores: Did not resolve issue. Try route_locks_size = 256 Did not resolve issue. Though, it did alter it somewhat. But, it is not clear to me how this works – would this setting restrict the number of open calls to 256? Have only one kamailio process: (“children=1”) This works. “Works”, I should say, because this would greatly restrict total platform scalability to a point where it is probably useless for my application. I saw the same issue discussed in the OpenSIPS mailing list from 2010, and the response was “this is not a bug”. Well, I respectfully beg to differ with both OpenSIPS and Kamailio – it IS a bug. I don’t think a proxy should reorder packets involved in a call in a non-deterministic way. In the Kamailio list thread, Alex Balashov discusses the contortions he has to go through to avoid repercussions from this issue. Kamailio as-is probably works fine for relatively low-volume operations. And a lot of the feedback is “why are out of order packets a problem?” OK, sure, in the very specific example given in the 2020 thread, maybe who cares. But in my thinking, there is absolutely nothing preventing Kamailio from generating much more serious OOO scenarios that would cause calls to fail. In my example, Kamailio OOO causes SIPp to fail to “generate audio”. Who knows how other SIP stacks will behave? But the more one will try to scale Kamailio, the more significantly this out of order processing issue will become. The solution to this seems very simple and straightforward – put packets to be processed into a queue PER Call-ID, or something along those lines. In short, the parallelism should be by call, not by packet. What say ye? Have I misunderstood something here? Cheers, Jawaid

4 11

Database Failure Detection at runtime
by Waqar 40 06 Dec '22

06 Dec '22

Hello Everyone, I am using Kamailio sqlops module to write to a remote database which is not the database of Kamailio. It is working fine. But for redundancy purpose, if this database goes down, I want the Kamailio to detect the failure at runtime and write the data to another database (standby database). Is it possible? Can anybody please guide me on this asap? Regards, Vicky

3 3

ds_is_from_list not matching dispatcher listed with hostname
by Benoît Panizzon 03 Dec '22

03 Dec '22

Hi On our devevelpment system, we have this dispatcher list: 3200 sip:reg1.dev.example.com:5060 0 0 name="Registrar01"; 3200 sip:reg2.dev.example.com:5060 0 0 name="Registrar02"; The names or course are in the DNS: A,AAAA and PTR. ds_is_from_list() returns the groupId 3200 Now I have started building the production system... 3200 sip:reg1.prod.example.com:5060 0 0 name="Registrar01"; 3200 sip:reg2.prod.example.com:5060 0 0 name="Registrar02"; DNS ist set up the same. I have double-checked: Names and IP addresses do resolve as they should. ds_is_from_list() returns nothing. I have also sniffed the connection. The ip addresses in the packets are the ones I expect. modparam("dispatcher", "ds_ping_from", "sip:survivability@sip.example.com") pings the machines and is getting answers. What else could cause this not to match? -- 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

imc sends all messages with Content-Type: text/plain
by Joey Golan 02 Dec '22

02 Dec '22

Hello, I'm checking the imc module and it appears that imc sends all messages with hard-coded content type header so if client sends an application/im-iscomposing+xml message, other clients receives the message with content-type text/plain which is very confusing. I think the right behavior is to take the content-type header from the original message and use it in the messages imc sends. Is there a workaround that might help me achieve that?

3 3

RLS is not sending Notify on resource list updated
by Lewis Hutchinson 01 Dec '22

01 Dec '22

Have you confirmed if the NOTIFY is sent? Attempted to be sent? Noticed you said "but no NOTIFY is received" -----Original Message----- From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of sr-users-request(a)lists.kamailio.org Sent: 19 November 2022 11:00 To: sr-users(a)lists.kamailio.org Subject: sr-users Digest, Vol 210, Issue 19 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.kam… or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. RLS is not sending Notify on resource list updated (Joey Golan) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Nov 2022 21:33:29 +0200 From: Joey Golan <joeygo(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] RLS is not sending Notify on resource list updated Message-ID: <CAAOPBYfHikYXKSRga5Mnf+fgUisrDk5PgHoCZ7anMgqqAmnU-w(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, I'm using Kamailio v5.6.2 with presence, presence_xml, xcap_server, and rls modules. I pushed 2 documents to the xcap server: 1. urn:ietf:params:xml:ns:resource-lists <?xml version="1.0" encoding="UTF-8" standalone="no"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list name="friends"> <entry uri="sip:1001@example.com"> <display-name>1001</display-name> </entry> <entry uri="sip:1002@example.com"> <display-name>1002</display-name> </entry> </list> </resource-lists> 2. urn:ietf:params:xml:ns:rls-services <?xml version="1.0" encoding="UTF-8" standalone="no"?> <rls-services xmlns="urn:ietf:params:xml:ns:rls-services" xmlns:rl="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org…"> <service uri="sip:1000+presence@example.com"> <resource-list> https://kamailio:5061/xcap-root/resource-lists/users/sip:1000@example.com/i… "friends"]</resource-list> <packages> <package>presence</package> </packages> </service> </rls-services> I'm subscribing to presence event on rls-service SUBSCRIBE sip:1000+presence@example.com SIP/2.0 Via: SIP/2.0/TLS 10.255.0.3:33883 ;rport;branch=z9hG4bKPjbe079f60-d0e0-4f1e-9f93-b18e467be5e8;alias Max-Forwards: 70 From: "1000" <sip:1000@example.com>;tag=97ef0748-da39-442f-9a02-468b67134ad6 To: <sip:1000+presence@example.com> Contact: <sip:20416583@10.255.0.3:5061;transport=tls> Call-ID: 9773a68c-b001-49f0-9ffa-093beb3d8e36 CSeq: 18636 SUBSCRIBE Event: presence Expires: 600 Supported: 100rel, replaces, norefersub, gruu Accept: multipart/related, application/rlmi+xml, application/pidf+xml Allow-Events: presence Supported: eventlist User-Agent: sipsimple 5.2.6 Content-Length: 0 The RLS sends a NOTIFY immediately upon accepting the subscription according to RFC 4662 and also the RLS is virtually subscribing to the presence event on the 2 resources in the friends list NOTIFY sip:20416583@10.255.0.3:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS joey-local-proxy.example.com:5061 ;branch=z9hG4bKa93d.b63e0697000000000000000000000000.0 To: <sip:1000@example.com>;tag=97ef0748-da39-442f-9a02-468b67134ad6 From: <sip:1000+presence@example.com >;tag=e02a02cb113b2bdb8ebdb022d767e6d2-a1677c19 CSeq: 1 NOTIFY Call-ID: 9773a68c-b001-49f0-9ffa-093beb3d8e36 Content-Length: 468 Max-Forwards: 70 Event: presence Contact: <sip:kamailio@example.com:5060> Subscription-State: active;expires=600 Require: eventlist Content-Type: multipart/related;type="application/rlmi+xml";start="<1668755827.sip:1000+presence@example.com.1700642067 >";boundary="1W1NaaaIIq6dOtLRXODFwqmC" --1W1NaaaIIq6dOtLRXODFwqmC Content-Transfer-Encoding: binary Content-ID: <1668755827.sip:1000+presence@example.com.1700642067> Content-Type: application/rlmi+xml;charset="UTF-8" <?xml version="1.0"?> <list uri="sip:1000+presence@example.com" xmlns="urn:ietf:params:xml:ns:rlmi" version="1" fullState="true"> <resource uri="sip:1001@example.com"/> <resource uri="sip:1002@example.com"/> </list> --1W1NaaaIIq6dOtLRXODFwqmC-- Now I?m changing the resource list using XCAP. I?m sending a PUT request with a new document and I see that the change is pushed to the DB but user 1000 is not receiving a NOTIFY with the updated list. This is the updated document: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list name="friends"> <entry uri="sip:1001@example.com"> <display-name>1001</display-name> </entry> <entry uri="sip:1002@example.com"> <display-name>1002</display-name> </entry> <entry uri="sip:1003@example.com"> <display-name>1003</display-name> </entry> </list> </resource-lists> I see that Kamailio is virtually subscribing on 1003 (The newly added user) but NOTIFY is not received. Also tried to subscribe on xcap-diff event, and the subscription was accepted successfully but no NOTIFY is received. Am I missing something? Thanks, Joey

1 0

Unable to install kamailio-mysql on CentOS 9
by Shailendra Paliwal 01 Dec '22

01 Dec '22

Hello, I'm trying to set up kamailio on a Cent OS 9 server but I'm unable to install the kamailio-mysql module. Can someone suggest any possible solutions here, Tried to setup kamdbctl after changing the configuration to use mysql, ➜ ~ kamdbctl create ERROR: could not load the script in /usr/lib64/kamailio//kamctl/kamdbctl.mysql for database engine MYSQL ERROR: database engine not loaded - tried 'MYSQL' Contents of /usr/lib64/kamailio/kamctl/, I'm not sure why there's a double slash in the message above ➜ ~ ls /usr/lib64/kamailio/kamctl/ dbtextdb kamctl.base kamctl.ctlbase kamctl.dbtext kamctl.rpcfifo kamctl.ser kamctl.sqlbase kamdbctl.base kamdbctl.dbtext I'm unable to install kamailio-mysql ➜ ~ dnf install kamailio-mysql Last metadata expiration check: 0:00:23 ago on Thursday 01 December 2022 03:53:45 AM. Error: Problem: conflicting requests - nothing provides libmysqlclient.so.21()(64bit) needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 - nothing provides mysql-libs needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) I've checked that I do have the following repolists, ➜ kamctl dnf repolist repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS epel Extra Packages for Enterprise Linux 9 - x86_64 epel-next Extra Packages for Enterprise Linux 9 - Next - x86_64 extras-common CentOS Stream 9 - Extras packages kamailio Kamailio - latest - Packages for the Kamailio latest release mariadb-main MariaDB Server mariadb-maxscale MariaDB MaxScale mariadb-tools MariaDB Tools tailscale-stable Tailscale stable This is after a fresh installation of CentOS 9. I believe that I might have a missing repolist or probably have something incorrect in the configuration.

5 7

2026

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 December 2022