- sr-users - kamailio.org

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

Kamailio IMS installation from pacakges
by Mohit Chawla 22 May '19

22 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 -- _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

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

22 May '19

Hello, I am considering to release Kamailo v5.2.3 out of latest git branch 5.2 next week, likely on Wednesday, May 22. As usual, if you are aware of issues not reported to the github bug tracker, fill a report there as soon as possible to give a chance to be analyzed and fixed. Also, if there was a fix for an issue that you were reporting, check to see if it was backported to be sure it is not forgotten. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

remove_hf inside of onreply_route
by Володимир Іванець 21 May '19

21 May '19

Hello! I was wondering if someone is using remove_hf in onreply_route and if yes on which Kamailio version? I'm using Kamailio v5.2.1 and as soon as I add remove_hf function to onreply_route Kamailio will fail to start with following error messages: ERROR: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7fc1dc044010, 27120); Free fragment not found! ERROR: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7fc1dc044010, 27120) called from core: core/io_wait.c: init_io_wait(524), module: core; Free fragment not found! Thank you for any suggestions!

2 2

Modern SIP Trunking, Route on To: or INVITE Headers?
by JR Richardson 21 May '19

21 May '19

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 -- JR Richardson Engineering for the Masses Chasing the Azeotrope

4 3

$snd(proto) mapping?
by Andrew Chen 21 May '19

21 May '19

Hey guys, Is there a numeric mapping for $snd(proto)? Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 1

How to get started (configuring an interconnection)
by Benoit Panizzon 21 May '19

21 May '19

Dear Kamailio Users I might need a bit help with starting. We are a TSP and at the moment we use a commercial carrier grade voice switch, which is very VERY inflexible and where bugs we find either don't get fixed, or only with a large delay. As everywhere else we embrace opensource and enjoy the possibility to quickly fix bugs ourselves (we have a software development department) we are evaluating Kamailio. Basically, if we have a centralized SIP routing engine, which can record CDRS for Billing and do some Number Translations (lookup on external service or database) for (location based emergency numbers, call forwarding services, ported numbers, call spam blacklisting) we could do way more than our actual $$$ carrier switch is capable of. Kamailio sounds like perfect for this task. First step: Get a machine up and running with Kamailio and Siremis, done, that was easy. Next: Connect his SIP wise via what I would call a 'SIP carrier interconnecton', ip based authenticated trunk between our carrier switch and Kamailio so we can route some number ranges from our carrier switch to Kamailio and then continue to test with subscribers, subscriber trunks and all else we need on Kamailio. I'm quite fluent in Asterisk (our Voicemail and Announcement Services are based on Asterisk) and SIP and have come across many different PBX, but after reading parts of the documentation, and trying myself to understand how Kamailio talks to other SIP endpoints I am a bit at a loss. I would have expected that I would configure our carrier switch as 'remote SIP gateway' or whatever it would be called. But I start fearing, Kamilio works completely differently. So I might need a bit of pointing the right direction to get started. I did try with the 'CarrierRoute Management' or 'Dispatcher' functions, but I only find very little documentation on this. So how do I get started? How do I, for starters, tell Kamailio what the Hostname or IP of my Carrier switch is and how do I set a 'default' call route to this? Kind regards -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 ______________________________________________________

2 1

Storing an integer value into AVP from REDIS string
by Stephen Bucklin 21 May '19

21 May '19

Hi, Any quick thoughts. I am using a REDIS "GET" to retrieve a JSON obj as a string from REDIS and then the JANSSON get value to extract a key value from the string and pop it into an AVP ($avp(val)) and wish to ensure the value is an integer in the AVP. New to this, be kind :-) Steve

4 6

How to define IP Trunk in kamailio
by Mary Honey 21 May '19

21 May '19

Hello everyone, I install and setup an IMS Network by kamailio-5.2.2 . I have p-cscf, i-cscf and s-cscf in three different systems . my Hss is Fokus. Registration and call between subscribers of network work successfully . now I want to define IP Trunk in my network which can pass external calls through my IMS network. I don't know how to define IP Trunk and changes in which element(pcscf, icscf or scscf) should be done.

2 3

Rewrite contact header
by R, Rajkumar (Raj) 21 May '19

21 May '19

Hello, We are using alias routing from NATHelper module and I've a case where the alias part 'alias=ip~port~transport' needs to be removed from the contact header in 2xx message. There's contact header reference "$ct" pseudo variable but it is read only. Is there any approach available to achieve this as I haven't found anything in the forum archive search so far. thanks, raj

2 2

Unable to CDRs on "Busy Here 486" from remote side and save start and end time on successful call in table
by Shahid Mehmood 21 May '19

21 May '19

Hello, i want to save the status each call into the database. but failed to 1. record CDRs for "Busy Here 486/ service unavailable 503 " from remote side in database. 2. on successful call unable to record total time of call in database. Version of Kamailio Is *version: kamailio 4.4.7 (x86_64/linux) 35d8abflags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RESADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MBpoll method support: poll, epoll_lt, epoll_et, sigio_rt, select.id: 35d8ab* *Also Attached Config File* *Thanks*

1 0

kamailio Early IMS security
by eyas barhouk 20 May '19

20 May '19

hello community Does kamailio support Early IMS security authentication schema to be able to integrate with Huawei HSS ?? and if it's does how to configure it? B.R Eyas

1 0

Plans for next major release - v5.3.0
by Daniel-Constantin Mierla 20 May '19

20 May '19

Hello, a while ago, during the last IRC devel meeting, it was proposed to either do the next major release (5.3.0) before the usual summer holidays or leave it for autumn. Given that time is approaching, we have to decide. If it is going to happen before the summer holidays, probably we should freeze the development in 2-3 weeks, then do 3-4 weeks of testing and release during the first part of July. It would be a shorter development cycle, so I do not expect much needs for testing. Only a few new modules and plenty of work to consolidate and enhance the existing code. Any preference for one of the two options? Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 2

Kamailio usrloc mode 3 using mongodb
by José Seabra 20 May '19

20 May '19

Hello there, I'm testing usrloc module with mongodb and i have a couple of questions to do. What i would like to know/have confirmation is if the fields that are specified in the following link https://kamailio.org/docs/db-tables/kamailio-db-5.2.x.html#gen-db-location-… can be used to create indexes in mongodb? I'm noticing that when a register is updated/deleted or expires kamailio prints the following INFO logs: *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (methods) type id (10), use DB1_STRING as default* *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (instance) type id (10), use DB1_STRING as default* These fields (*methods and **instance*) are stored in mongodb document with a null string, e.g: *{* * "_id" : ObjectId("5cdc775a6472740055289a11"),* * "username" : "x1000",* * "contact" : "sip:x1000@192.168.1.1:5674;transport=UDP",* * "expires" : ISODate("2019-05-15T20:33:26Z"),* * "q" : -1,* * "callid" : "sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61 <sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61>",* * "cseq" : 2,* * "flags" : 0,* * "cflags" : 0,* * "user_agent" : "sipp",* * "received" : "sip:191.30.10.23:8888 <http://191.30.10.23:8888>",* * "path" : "<sip:172.31.2.61:5060;received=sip:191.30.10.23:8888;lr>",* * "socket" : "udp:172.31.2.11:5060 <http://172.31.2.11:5060>",* * "methods" : null,* * "last_modified" : ISODate("2019-05-15T20:32:26Z"),* * "ruid" : "uloc-15-5cdc7756-55-1",* * "instance" : null,* * "reg_id" : 0,* * "server_id" : 21,* * "connection_id" : -1,* * "keepalive" : 0,* * "partition" : 0* *}* Should i be concerned about that log msg? how can i avoid it? Thanks Regards -- Cumprimentos José Seabra

2 5

BYE relays Digest and others in Proxy-Authorization header
by Sergiu Pojoga 19 May '19

19 May '19

Hi ppl, Noticed BYE requests relayed from caller to callee have the *Proxy-Authorization* header including *Digest*, *nonce* and *response*. Is that by SIP definition or am I doing something wrong? My concern is the callee gets to see caller's authentication credentials. Thanks.

4 6

Centos7 Packages
by Matt Lamer 18 May '19

18 May '19

I am trying to install the kam server on centos7. When running the install I get the following: Install 5 Packages (+2 Dependent packages) Total size: 14 M Total download size: 14 M Installed size: 63 M Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. kamailio-debuginfo-5.2.2-7.el7 FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.2.x-rpms/C…: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Anyone else having this issue?

2 1

"If you're struggling with your Tele callers to improve sales? you're not alone.
by Prakash 17 May '19

17 May '19

http://www.doocti.com +919790776655 Doocti Next Generation CTI for Smarter Sales Teams http://www.doocti.com Dear Customer, Greeting from Tevatel. Hope this mail finds you well. We are happy to announce the launch of our new product Doocti - Call center connector for crm What is Doocti? Doocti is a Computer telephony integration platform that can integrate your communication devices with your Helpdesk, CRM, and Other Key Tools. Increase agent productivity, improve customer experience and enable personalized service through deep customer insights at the point of interaction. Features of Doocti Single click Dial On-Screen Customer Profile Build on the Customer Profile Efficient Call Disposition Auto Dial Sticky Agent Feedback from the clients Reduce call time by 10-20 seconds per call Instantly retrieves and screen-pops customer related information Provides a better and more immediate response to the customers Offers a more personalized experience to the caller Dials out automatically and faster with a single mouse click Handles higher call volumes Increases first call resolution Intergrated with Currently we have associated with more than 20 brands. Curious to see what's under the hood? Enjoy a detailed look at the Doocti experience in a demo guided by a member of our team. Get a meeting on the calendar today. mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti Request for a Demo [ mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti ] Communications Simplified Contact Us: +919790776655 | prakash.n(a)tevatel.com No:76, Swamibakthan Street, Nammalwarpet, Chennai - 600012. www.tevatel.com | www.doocti.com http://viewstripo.email/?utm_source=templates&utm_medium=email&utm_campaign… ---------------------------------------------------------------------- This email was sent by prakash.n(a)tevatel.com to sr-users(a)lists.sip-router.org Not interested?Unsubscribe - https://tihk.maillist-manage.com/ua/optout?od=27218d28c96aa859ed0ac1287be0e… Update profile - https://tihk.maillist-manage.com/ua/upc?upd=164d3589027540e5&r=164d35890275… Asterfone technologies pvt ltd | Swamibakthan St, Thiruvalluvar Nagar, Nammalwarpet, Ayanavaram, Chennai, Tamil Nadu 600010 Our Privacy Policy [ ] and Terms of Use. [ ]

2 1

rtpengine sessions on timeout not freeing up RTP ports
by Istvan Mogyorosi 17 May '19

17 May '19

Hello Another rtpengine related question after having successfully implemented a dispatcher configuration. Call flow is ok, everything works well until I tried to increase call volume. Kamailio log showing "proxy replied with error: Ran out of ports" In the beginning both channels are up, then I can see a teardown on the incoming channel loosing the ability to collect DTMF. Using the CLI tool I have statistics showing that none (!) of the calls are "regular terminated", they are on timeout. After experimenting with handling BYE, I ended up could getting a "regular terminated" call by using route[RELAY] .... if (is_method("BYE")) { rtpengine_delete(); } and then I can see some good things! Received command 'delete' from 127.0.0.1:58538 Scheduling deletion of call branch 'as65b95845' (via-branch '') in 5 seconds Replying to 'delete' from 127.0.0.1:58538 (elapsed time 0.000216 sec) Please correct me if I'm doing wrong this way! cheers Istvan

1 0

RFC: Kamailio command line parameters
by Daniel-Constantin Mierla 17 May '19

17 May '19

Hello, a while ago I added support for long format parameter names for Kamailio command line. That's opening the door for more options to be set via command line arguments and I discovered that especially in a containerized environment, it is a trend to start applications using more command line parameters, than relying on config files. The current command line parameters are listed by: kamailio -h Use the master branch for it, because has many more than 5.2.x. Anyhow, the purpose of this message is to see if anyone else considers useful to add other command line parameters, and if yes, which ones. A typical candidate will be a global parameter that you have to change when relocating to/spinning up another Kamailio environment and you need to change the kamailio.cfg. Those that generate the interest of many people, can be easily added now. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Testing the KEMI interpreters for functions with 4 and 5 parameters
by Daniel-Constantin Mierla 17 May '19

17 May '19

Hello, because there were many variants not handled for KEMI functions with 4 and 5 parameters, I made a script to generate the code in order to be sure none is missing. The script was pushed in Kamailio repo at: * https://github.com/kamailio/kamailio/tree/master/misc/tools/kemi You don't have to use it, I listed it for reference, just in case the code needs adjustments in the future. If anyone is using a KEMI interpreter and has functions exported by Kamailio with 4 or 5 parameters, it would be appreciated if you can run some tests with master branch and report the results. All kemi interpreter modules were updated, so it doesn't matter which one you test. If the results are good, then the patches will be backported to branch 5.2, so there will be no case of unhanded functions with these numbers of parameters. The cases with up to 3 parameters were not affected. For 6 params, still only string values are handled. The other variants can be added, but I think they are not needed for the moment, so I tried to keep it small for the moment. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Kamailio World thanks
by Daniel Pocock 16 May '19

16 May '19

Hi Daniel and Kamailio team, Well done on another successful Kamailio World in 2019. As usual, it was a great opportunity to meet people and learn new things. Regards, Daniel

2 1

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