sr-users

sr-users@lists.kamailio.org

42 participants
37517 discussions

remove_hf() leaves junk in the headers?
by Oded Arbel 27 May '19

27 May '19

I'm trying to rewrite the `From` header in an invite going out to an external system (*), by calling remove_hf("From"); followed by append_hf("From: <some value>\r\n"); but the result is an invalid SIP message, because apparently after `remove_hf()` finishes, it leaves the content of $fU in place of the `From` header - just the raw text, without a header name or even a "\r\n" - and that eats the next header line and breaks the INVITE. Here is how the INVITE originally looks (without either `remove_hf()` or `append_hf()`): ---8<--- INVITE sip:972522353283@10.20.30.40:5060 SIP/2.0 Record-Route: <sip:10.90.80.70;lr;did=649.f0b> Via: SIP/2.0/UDP 10.90.80.70:5060;branch=z9hG4bK6188.ff5c4fd855bd2970fdf32d4807b114c2.0 Via: SIP/2.0/UDP 10.90.80.71:5066;received=10.90.80.71;branch=z9hG4bK581897a4;rport=5066 Max-Forwards: 69 From: <sip:972515340014@example.com:5066>;tag=as0bcee217 To: <sip:972522353283@10.20.30.40:5060> Contact: <sip:972515340014@10.90.80.71:5066> Call-ID: 722299dc15aad53d28172d433e8665f4@10.90.80.71:5066 CSeq: 102 INVITE User-Agent: Asterisk PBX 14.7.2 Date: Sun, 26 May 2019 14:42:52 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: ad199638-4df3-4aef-81f1-1b50581032a7 Content-Type: application/sdp Content-Length: 280 v=0 o=root 817636675 817636675 IN IP4 10.50.60.70 s=Asterisk PBX 14.7.2 c=IN IP4 10.50.60.70 t=0 0 m=audio 39064 RTP/AVP 8 0 18 9 a=maxptime:60 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:39065 a=ptime:20 ---8<--- and here is another call with the same setup, with just `remove_hf("From");` being invoked (without calling `append_hf()` - this is just for reproduction): ---8<--- INVITE sip:972522353283@10.20.30.40:5060 SIP/2.0 Record-Route: <sip:10.90.80.70;lr;did=f45.91b1> Via: SIP/2.0/UDP 10.90.80.70:5060;branch=z9hG4bK024d.2690ebf7a809edca2208e6b2561ccf9e.0 Via: SIP/2.0/UDP 10.90.80.71:5066;received=10.90.80.71;branch=z9hG4bK79ae3073;rport=5066 Max-Forwards: 69 972515340014To: <sip:972522353283@10.20.30.40:5060> Contact: <sip:972515340014@10.90.80.71:5066> Call-ID: 7b20ba5a549f6f886c22985146765736@10.90.80.71:5066 CSeq: 102 INVITE User-Agent: Asterisk PBX 14.7.2 Date: Sun, 26 May 2019 14:44:20 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: ffbb4ac1-3a0f-4dd6-9ce9-7ad24361081a Content-Type: application/sdp Content-Length: 280 v=0 o=root 509740923 509740923 IN IP4 10.50.60.70 s=Asterisk PBX 14.7.2 c=IN IP4 10.50.60.70 t=0 0 m=audio 39102 RTP/AVP 8 0 18 9 a=maxptime:60 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:39103 a=ptime:20 ---8<--- As you can see, the `From` header is indeed gone, but it left the $fU just before the `To` header. WTF? I'm running Kamailio 5.2.2 built locally. Notes: *) the problem I'm trying to solve is that I can't get my Asterisk installation to generate the `From` header I want, the reason is out of scope of this question, so I'm sending custom SIP headers over to Kamaiio and I want to rewrite the header in Kamailio to the "correct" value. -- Oded Arbel

6 8

PRE-PAY update timer
by Steve Bucklin 25 May '19

25 May '19

Hello all (again), I am looking at a 'good' method to start a call with "chunks" of time allocated. I wish the initial call to check a credit, and if credit is good, allow a small amount of time (say 30 seconds). I have enabled DIALOG and have looked at CNXCC, but am confused! When the initial 30 seconds runs out, I want to authorise another 30 seconds, etc, etc, etc. I have started to play and set a dialog timer that expires to a route, and then can 'return' allowing the call to continue - BUT was not able to reset the dialog timer to trip again after another 30 seconds. I tried to 'set_max_time' on cnxcc, but this did not seem to trip the event route upon timeout? Does anyone have a pointer to any examples? I also am unsure of how to update the timer and keep a call in play! Steve

5 4

No Private memory left using usrloc with db_redis in mode 3
by José Seabra 24 May '19

24 May '19

Hello there, i have stored ~200 000 registrations contacts in redis database and when kamailio starts looking for expired contacts in redis then it starts giving these errors: WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1099]: db_redis_perform_query(): performing full table scan on table 'location' while performing query WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 0 is 'expires' *WARNING: PR_LOG: 123: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 1 is 'expires'* *ERROR: PR_LOG: 123: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7ff80922b010, 3055920); Free fragment not found!* *ERROR: PR_LOG: 123: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7ff80922b010, 3055920) called from core: db_res.c: db_allocate_rows(183), module: core; Free fragment not found!* *ERROR: PR_LOG: 123: <core> [db_res.c:185]: db_allocate_rows(): no private memory left* *ERROR: PR_LOG: 123: db_redis [redis_dbase.c:1115]: db_redis_perform_query(): Failed to allocate memory for rows * I have configured the private memory to 128 MB but seems that isn't enough to handle with all these contacts. Is the only option here increase the private memory or there is any other kind of configuration(in redis or kamailio) that i can make to avoid this? Best Regards José Seabra -- Cumprimentos José Seabra

2 1

Re: [SR-Users] Kamailio IMS installation from pacakges
by Mohit Chawla 24 May '19

24 May '19

Hi, My name is Mohit Chawla working on LTE Network integration with Kamailio IMS server. We are facing issues in installation & Configuring of kamailio IMS on CentOS 7 due to no documentation is available on web (or at least I am not able to find one). Primarily I am interested in installing packages (not building from source code as of now) and use it for further testing. I can go with building the package from source if its more easier and quick. Can you guys help me share any document/wiki which is helpful for my cause ? I will be really grateful if someone can reply me by today. Thanks and Regards, Mohit From: Mohit Chawla [mailto:mohit.chawla@azcom.in] Sent: Wednesday, May 22, 2019 5:57 PM To: 'sr-users(a)lists.kamailio.org' Subject: Kamailio IMS installation from pacakges Hi, My name is Mohit Chawla working on LTE Network integration with Kamailio IMS server. We are facing issues in installation & Configuring of kamailio IMS on CentOS 7 due to no documentation is available on web (or at least I am not able to find one). Primarily I am interested in installing packages (not building from source code as of now) and use it for further testing. I can go with building the package from source if its more easier and quick. Can you guys help me share any document/wiki which is helpful for my cause ? I will be really grateful if someone can reply me by today. Thanks and Regards, Mohit -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

2 3

Use of kamailio as IMS server to integrate with LTE Core Network
by Mohit Chawla 24 May '19

24 May '19

Hi , We have successfully installed the kamailio IMS server on centOS 7 using the following link (http://www.kamailio.org/wiki/tutorials/ims/installation-howto) with appropriate changes for command in CentOS 7. We are currently trying to integrate the PCSCF module with LTE Core network , but I don't have any idea how to do this. Neither I am able to find any tutorials which I can use to understand how kamailio works. Can anyone share any reference document to help me understand the kamailio working in my use case. Thanks and Regards, Mohit -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

1 0

listen (bind) to variable ip and port
by Roiss-Weiss, Roman 23 May '19

23 May '19

Hi guys, is it somehow possible to bind to a variable ip-address and port? e.g. getting the ip and port from a database? Kind regards, Roman

3 2

Kamailio CDRs for calls interrupted without BYE
by Ildar Mukhametzhanov 23 May '19

23 May '19

Hello! I am using dialog+acc modules to write CDRs in kamailio. Everything works great except one test. During active call I switched off both UACs preventing them to send BYE. Rtpengine reported about call interruption, but kamailio thinks that this call is in-progress for a long time. What is the right way to make kamailio know about calls interrupted without BYE. Thanks. -- Sincerely, *Ildar Mukhametzhanov* Head of software development VoiceON Telecom Services GmbH im(a)voice-on.net <mailto:im@voice-on.net> t. +49 30 398 20 500-77

3 8

warning logs - DB_Redis and usrloc in mode 3
by José Seabra 22 May '19

22 May '19

Hello there, I'm testing the db_redis with usrloc module in mode 3 and i have been noticing that every time that kamailio checks if there is contacts expired then it logs the following warning messages: *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1099]: db_redis_perform_query(): performing full table scan on table 'location' while performing query* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 0 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 1 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1274]: db_redis_perform_delete(): performing full table scan on table 'location' while performing delete* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 0 is 'expires'* *WARNING: PR_LOG: 5a14aea50d9d9b17-75(a)172.31.1.11 <5a14aea50d9d9b17-75(a)172.31.1.11>: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 1 is 'expires'* I'm not sure what is the rational behind of this, but having these logs being written when we have log level equal 2 in production is something unnecessary, so i'm asking if it shouldn't be better we have it as debug instead of warning? or do you forecast any performance issues using usrloc module in mode 3 with db_redis? Thank you for your support Cheers José -- Cumprimentos José Seabra

2 1

Re: [SR-Users] Modern SIP Trunking, Route on To: or INVITE Headers?
by JR Richardson 22 May '19

22 May '19

Benoit, Alex, I appreciate the feedback, confirming my assumptions. Good news is the Vendor finally responded positively and agreed to add in configuration option to route on INVITE R-URI in next SDK release, expected later this year. In the meantime I added 'uac_replace_to' function to my proxy to re-write To: header with R-URI, so far so good. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope > > The To header is a cosmetic, purely logical commentary on the intended ultimate destination of the call, and no routing should ever be done on it. The RURI of the INVITE is the appropriate vehicle for that. > > When dealing with proxies, however, one will encounter from time to time the grim reality that there are user agents which expect the To URI and the INVITE RURI to be in alignment. For that scenario, you can use ‘uac’ module’s stateful rewriting functionally (uac_replace_to()) to modify To with Kamailio in a way that displays fidelity and esteem for protocol formalities. > > — > Sent from mobile, with due apologies for brevity and errors. > > > On May 21, 2019, at 9:32 AM, JR Richardson <jmr.richardson(a)gmail.com> wrote: > > > > Hey Folks, > > > > I could use some feedback to see if my mind is right on this topic.I'm > > in a discussion with a software Vendor (respectfully unnamed) with > > terminal software routing on To: header info. It's my contention any > > modern SIP software should use INVITE header to retrieve DID info and > > route from there. > > > > My reasoning is due to the To: header should contain the original > > intended DID, Extension, Name, AoR or whatever else the original SIP > > transaction wanted to contact, but being in a multi-carrier, > > multi-hop, call forwarding environment, the INVITE header contains the > > hop-to-hop true intention of where the call should route at any given > > transaction. So in the case of terminal software the To: header could > > likely be irrelevant where as the INVITE header is accurate. > > > > My most recent response from the Vendor suggest I put a SIP Proxy in > > front of the terminal software and transform the To: header to > > whatever I need for this application. Although I can do this, I'm > > concerned with breaking RFC for CANCEL and BYE transaction sent back > > from the terminal software that may not be recognized by upstream > > origination carriers. > > > > Plus modifying To: header is widely frowned upon by most folks. > > > > Thanks. > > > > JR

1 0

Kamailio v5.2.3 Released
by Daniel-Constantin Mierla 22 May '19

22 May '19

Hello, Kamailio SIP Server v5.2.3 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.3. For more details about version 5.2.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/05/kamailio-v5-2-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

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