sr-users September 2019

sr-users@lists.kamailio.org

57 participants
82 discussions

Planning the release of v5.1.9
by Daniel-Constantin Mierla 26 Sep '19

26 Sep '19

Hello, I am considering to release v5.1.9 out of the branch 5.1 during the next week, on Tuesday (Sep 24) or Thursday (Sep 26). As usual, if you are aware of issues not reported on tracker or commits that should be backported to branch 5.1, do report them asap in order to get them a chance to be sorted out. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

1 2

Kamailio ARM support improved, tests
by Henning Westerholt 25 Sep '19

25 Sep '19

Hello, as part of the testing for 5.3.0 I looked into the ARM support in Kamailio. Previously the core used some deprecated assembler functions for atomic operations (locking etc..). There was also no native support for the ARM v7 architecture available. After several fixes and extensions both topics should be now much improved. I did today a lot of tests on Rasberry Pi and also some benchmarking (will send another e-mail when the report is ready). If you use Kamailio on another embedded ARM (>= v6) system it would be great if you also give it a try. Use git master revision ccc0eb6d12a1d (or newer) for your tests. Please report eventual issues to the sr-dev list. Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

1 0

Development for v5.3.x is frozen
by Daniel-Constantin Mierla 25 Sep '19

25 Sep '19

Hello, the formal notification that the development for the next major version 5.3.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 5.3 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, pull requests can still be done, but they will be merged after branching 5.3. Can still be done commits with documentation improvements, enhancements to related tool (e.g., kamctl, kamcmd) and exporting missing KEMI functions to the modules already exporting most of the other functions (done for previous releases, because likely that was a fail to notice, all functions should be exported for a module at the same time). Once the branch 5.3 is created, new features can be pushed again to master branch as usual. From that moment, the v5.3.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 5.3 is collected at: * https://www.kamailio.org/wiki/features/new-in-5.3.x Upgrade guidelines will be collected at: * https://www.kamailio.org/wiki/install/upgrade/5.1.x-to-5.3.0 Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.2.x to 5.3.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 8

Extract user from AOR
by Grant Bagdasarian 25 Sep '19

25 Sep '19

Hello, I've been trying to extract the user part from an AoR using transformations in Python (KEMI), but without success. The reg_fetch_contacts function has been called successfully before trying to access the AoR. None of the below statements work for me. They all return None. user = _.pv.get("$(ulc(profile=>aor){uri.user})") user = _.pv.get("$(ulc(profile=>aor){tobody.user})") or _.pv.sets("$var(aor)", _.pv.get("$(ulc(profile=>aor))")) user = _.pv.get("$(var(aor){tobody.user})") user = _.pv.get("$(var(aor){uri.user})") I'm not sure what's causing the None result. Could it be the curly braces being used for string interpolation in Python? Or are these transformations not able to extract the value since the AoR has the following format: user@domain? If the same can be accomplished in another way, please let me know. Regards, Grant

2 1

Question
by Shahdee Nelson 25 Sep '19

25 Sep '19

With your software would I be able to create, and modify VOIP lines? As in saying would I be able to provide VOIP numbers that can make outbound calls to USA from USA?

2 1

Problem restoring To and From (uac_replace)
by Duarte Rocha 24 Sep '19

24 Sep '19

Greetings, I'm getting some errors with the auto restore of From and To from UAC Module. After the restore, the URI has lots garbage and it's not like the original. I think the problem lies on the way the client sends the Route Header to me, but i'm not sure. When Kamailio sends the INVITE Record-Route are like this : Record-Route: <sip:xxx.xxx.xxx.xxx;................> Record-Route: <sip:aaa.bbb.aaa.bbb;................> However, when my client sends a BYE to finish the call, the Route are on this mode : Route: <sip:aaa.bbb.aaa.bbb;................>,<sip:xxx.xxx.xxx.xxx;................> The module's documentation says this : "One uses the rr module and appends to the Record-Route header a parameter containing some strings from which the original and new URI can be computed. The problem with this mode is that it relies on the fact the parties will send the Route exactly as it was received. In case there is a change, the resulting URIs will not be correct." Can this change by the client be the cause of this issue? Is there anything i can do to avoid this? Best Regards, Duarte Rocha

1 0

Can I load balance Kamailio with Kamailio?
by Ne Mo 24 Sep '19

24 Sep '19

3 2

Parsing json file on kamailio.cfg file
by Melek Oktay 24 Sep '19

24 Sep '19

Hi, I am trying to monitor *uac *channels status periodically in kamailio config file. I call uac.reg_dump rpc command and result will be inside in $var(uac_channel) variable jsonrpc_exec('{"jsonrpc": "2.0", "method": "uac.reg_dump"}'); $var(uac_channel) = $jsonrpl(body); it returns me json formatted result like below, it has a several channels info and their status *flags* {"jsonrpc":"2.0", "result":[ {"l_uuid":"YY","l_username":"YY","l_domain":"YY","r_username":"YY","., " *flags*":16 }, {"l_uuid":"XX","l_username":"XX","l_domain":"XX","r_username":"XX",,... " *flags*":1 }}]} I could not parse this result on kamailio.cfg file ! I want to learn channel that has a 16 value in flag attribute for example !! Would you help me to figure out how I am gonna parse this json file please ?

2 2

qm_find_free() Free fragment not found, called from xcap_server, no more pkg
by Cody Herzog 23 Sep '19

23 Sep '19

Hello. Recently, for the first time, we experienced an apparent memory issue in our production environment. Here's an example of the relevant log messages: Sep 13 18:55:22 SIPCOMM /usr/local/sbin/kamailio[2302]: ERROR: <core> [core/mem/q_malloc.c:286]: qm_find_free(): qm_find_free(0x7fd8bbcfc010, 134648); Free fragment not found! Sep 13 18:55:22 SIPCOMM /usr/local/sbin/kamailio[2302]: ERROR: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7fd8bbcfc010, 134648) called from xcap_server: xcap_server.c: ki_xcaps_put(549), module: xcap_server; Free fragment not found! Sep 13 18:55:22 SIPCOMM /usr/local/sbin/kamailio[2302]: ERROR: xcap_server [xcap_server.c:552]: ki_xcaps_put(): no more pkg Sep 13 18:55:22 SIPCOMM /usr/local/sbin/kamailio[2252]: ERROR: app_perl [kamailioxs.xs:487]: XS_Kamailio_log(): 500 Server error The failed operation was the XCAP server module trying to generate a very large RLS contact list for a user. The issue only impacted users with very large lists, as though a large contiguous block of memory could not be found, whereas other smaller allocations continued to work fine. We believe the requested allocation was around 112 KB in size. The server had been up for 14 days. We were able to work around the issue temporarily by just restarting the Kamailio service. It's unusual, because our production server is often up for months, and we've never seen this issue before. The load on production is increasing slowly due to an increased concurrent user count, so that might be related. Before restarting the service on production, we captured the output of the following commands: kamctl stats shmem kamcmd mod.stats all shm kamcmd pkg.stats kamcmd mod.stats all pkg Here's the shared mem output: { "jsonrpc": "2.0", "result": [ "shmem:fragments = 27240", "shmem:free_size = 447203296", "shmem:max_used_size = 116175576", "shmem:real_used_size = 89667616", "shmem:total_size = 536870912", "shmem:used_size = 68824240" ], "id": 6934 } Here's the pkg output for the particular PID which was throwing the errors: { entry: 34 pid: 2302 rank: 14 used: 2415864 free: 4949688 real_used: 3438920 total_size: 8388608 total_frags: 1951 } We didn't see anything obvious in the stats output which explains the issue. We've been trying to reproduce the issue in a dev environment using simulated higher than production load running for many days, but so far we've had no luck. We've been monitoring memory stats over time, but we don't see any obvious leaks or issues. We've searched various past threads, but didn't find any obvious answers. Here are some of the documents and the threads we've been reading: https://www.kamailio.org/wiki/tutorials/troubleshooting/memory https://www.kamailio.org/wiki/cookbooks/3.3.x/core#mem_join https://sr-users.sip-router.narkive.com/3TEDs3ga/tcp-free-fragment-not-found https://lists.kamailio.org/pipermail/sr-users/2012-June/073552.html https://lists.kamailio.org/pipermail/sr-users/2017-February/096132.html https://lists.kamailio.org/pipermail/sr-users/2017-September/098607.html https://github.com/kamailio/kamailio/issues/1001 https://lists.kamailio.org/pipermail/sr-users/2016-April/092592.html https://lists.kamailio.org/pipermail/sr-users/2010-July/064832.html Regarding our Kamailio version and build options, here's the output of 'kamailio -v': ---- version: kamailio 5.1.0 (x86_64/linux) flags: 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_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 20:07:31 Jan 4 2018 with gcc 5.4.0 ---- We are running on a 64-bit Ubuntu Server virtual machine. Any help would be greatly appreciated. Thanks very much.

3 6

Using static entries with usrloc
by George Diamantopoulos 23 Sep '19

23 Sep '19

Hello, Normally I wouldn't be asking this but I was surprised to find no reference to anyone doing this online. I need to have a few AoRs with static entries in kami's location table, which will always be reachable at their contacts without ever having to register with Kamailio. Am I right in thinking that merely INSERTing respective rows in kamailio's location DB backend will do the trick? Is there anything I need to worry about, like contacts being periodically purged? If yes, how do I prevent that from happening? And will kamailio always query the DB when performing location lookup or do I need to restart upon inserting new records (to purge caches, for example)? Lastly, I'm not sure how to treat some fields present in usrloc tables like ruid, expires (can I set this to NULL?), callid and cseq (which is irrelevant since there's no REGISTER), flags, cflags and methods. Thanks, George

5 7

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 September 2019