sr-users November 2022

sr-users@lists.kamailio.org

42 participants
56 discussions

Turn off transaction accouting but keep dialog cdr accounting?

by Benoit Panizzon

Hi Team Inserts require resources, especially on high load situations and if there are a couple of indexes on the table. As I use the dialogue module to create CDR, I would like to disable the normal transaction based accounting. I have attempted by not calling: setflag(FLT_ACC) setflag(FLT_ACCFAILED) but I still get both, CDR and Transaction entries created in the corresponding database tables. How could I turn off transaction accounting? 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 year, 4 months

Regex not capturing as required for subst_hf

by Salvinder Parhar

Hi, I'm trying to capture and substitute the host IP of contact header using the subst_hf but it's not working as expected. I tested my regex in a tester and it works fine there but not in Kamailio config. *Regex:* @(.+?)> *Substitution:* @PUBLIC_IP:5060> *Three contact headers that I'm trying to match;* Contact:<sip:0065*7766@199.48.100.166:5060 >;methods="INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER" Contact: <sip:0065*7788@172.16.1.216 ;transport=udp>;expires=3600;reg-id=1;+sip.instance="<urn:uuid:03660bc5-bb70-4784-8ac5-000413B108BA>" Contact: <sip:0925*0007@199.48.100.166:5060> *Outcome I'm expecting for the three contact headers;* Contact:<sip:0065*7766*@PUBLIC_IP:5060>* ;methods="INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER" Contact: <sip:0065*7788*@PUBLIC_IP:5060>* ;expires=3600;reg-id=1;+sip.instance="<urn:uuid:03660bc5-bb70-4784-8ac5-000413B108BA>" Contact: <sip:0925*0007*@PUBLIC_IP:5060>* This regex in Kamailio works fine for the first and third contact header but for the second contact header it matches all the way to the end of the contact header excluding the quote (") sign. I've tried so many other combinations [like *(a)(.+?)>;?* ] of regex but nothing seems to work. Is there a way to accomplish this with one regex? Thanks, Sal

1 year, 4 months

Re: [SR-Users] To stop automatic creation of RabbitMQ queues by kazoo module

by Luis Azedo

your expectation is wrong, that's how it works, all channels are bi-directional and for that they use a queue. > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 Nov 2022 12:48:58 +0530 > From: Sharmila Sundar <sharmila.sundar(a)ecosmob.com> > To: sr-users(a)lists.kamailio.org > Subject: [SR-Users] To stop automatic creation of RabbitMQ queues by > kazoo module > Message-ID: > <CACcTecP1CfjuKdu33jEvZWUK2bE5ZSK37m-6xE1iEB= > 9XwUCgg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello Team, > > I run into a problem with Kazoo module. > > We noticed that , amqp_max_channels parameter creates automatic queues in > Rabbitmq-server based on the channel number provided. > Expecting that , it should create only channels not queues. > > This is the modparam I added > modparam("kazoo", "amqp_max_channels", 12) > > Can any one help on this issue as why the kazoo module creates an automatic > queue based on amqp_max_channels param ? > > Please find the screenshot attached from rabbitmq server > > Regards > SharmilaS > >

1 year, 5 months

db_extra fields cannot be integer

by Jose Figueroa

Hello everyone, According to this old thread, the db_extra fields in the acc module cannot be integer: https://lists.kamailio.org/pipermail/sr-users/2015-February/087053.html Does this answer is still valid or is there another form to represent an integer? since in my acc table I added an integer value field. -- Jose Figueroa

1 year, 5 months

kamcmd autocompletion

by Antoine DEBARRE

Hi, I just installed kamailio v5.5 via deb.kamailio.org packages (debian 11). Seems that kamcmd autocompletion doesn't work at all. It is OK for v5.4 via official debian packages (packages.debian.org/bullseye/kamailio) Best regards, -- <https://app.livestorm.co/comdata-group/metaverse-what-will-cx-look-like-in-…>

1 year, 5 months

To stop automatic creation of RabbitMQ queues by kazoo module

by Sharmila Sundar

Hello Team, I run into a problem with Kazoo module. We noticed that , amqp_max_channels parameter creates automatic queues in Rabbitmq-server based on the channel number provided. Expecting that , it should create only channels not queues. This is the modparam I added modparam("kazoo", "amqp_max_channels", 12) Can any one help on this issue as why the kazoo module creates an automatic queue based on amqp_max_channels param ? Please find the screenshot attached from rabbitmq server Regards SharmilaS -- * <https://www.ecosmob.com/> * *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

1 year, 5 months

RLS is not sending Notify on resource list updated

by Joey Golan

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=" http://www.w3.org/2001/XMLSchema-instance"> <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 year, 5 months

Create new listener on the fly

by H Yavari

Hi Kamailio community, I am running an IPsec server beside Kamailio, so I am interested to know if there is any method to create a SIP listener on a specific port on the fly. I mean, when I create the IPsec SAs through the IPsec server, I ask Kamailio to create a listener/handler for that port too.This case might be very rare, but it is always good to hear community ideas. Thank you. Regards,Hossein

1 year, 5 months

ims ipsec connectivity

by Oleg Belousov

Hi. Working on ims integration with the actual handset, have got a problem with ipsec establishment to complete registration. Initial steps are fine, including diameter exchange and 401 (with security server details) toward UE. On the next step UE and kamailio should establish ipsec connection, and UE to submit the next register with a response. As per trace UE is trying to establish the same (can see initial TCP SYN encapsulated onto ESP), using port-s, provided in Security-Server, but get an ICMP packet from server with destination/protocol unreachable. No more info either in P-SCSF log, no in kern.log. Proxy is listening to that port, it is tcp and available over telnet, so should not be a connectivity issue. Please let know if any ideas how to troubleshoot that further, -- obelousov.tel

1 year, 5 months

Problem with update/retrigger a htable

by Bernd Krueger-Knauber

Hi members, I run into a problemm with htable. For user push notifications I need a loop. So I did the following for a first test: modparam("htable", "htable", "user=>size=3;autoexpire=5") ... event_route[htable:mod-init] { xinfo("htable init"); $sht(user=>testkey) = "testvalue"; } event_route[htable:expired:user] { xinfo("Record expired $shtrecord(key) => $shtrecord(value)"); $sht(user=>$shtrecord(key)) = $shtrecord(value); } I see the htable init, and I reach Record expired, but only once. The 'new' entry $sht(user=>$shtrecord(key)) = $shtrecord(value); seams not to be re-added, because I never reach the expired event again. I expected to see cyclic expired events. Also strange: expire is set to 5 seconds I get: Nov 21 08:34:50 xxx /usr/sbin/kamailio[254662]: INFO: <script>: htable init ... Nov 21 08:35:10 xxx /usr/sbin/kamailio[254671]: INFO: <script>: Record expired testkey => testvalue If I'm right, this are 20 seconds and not 5. Any ideas what's wrong? Best regards

1 year, 5 months

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