sr-users September 2019

sr-users@lists.kamailio.org

57 participants
78 discussions

by Juha Heinanen

Kamailio wiki does not tell what result $sht(htable=>key) gives if the key is not found in htable. It would be nice if it did. -- Juha

5 years

KEMI dialplan dp_replace returns not implemented yet

by Grant Bagdasarian

Hello, The dp_replace KEMI function is returning the message "not implemented yet". Function call: _.dialplan.dp_replace(1, _.pv.get("$rU"), "$var(dpr)") app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $rU <core> ¡core/pvapi.c:398¿: pv_cache_lookup(): pvar ¡$rU¿ found in cache app_python3 ¡apy_kemi.c:193¿: sr_apy_kemi_exec_func_ex(): execution of method: dp_replace app_python3 ¡apy_kemi.c:338¿: sr_apy_kemi_exec_func_ex(): not implemented yet app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $var(dpr) <core> ¡core/pvapi.c:371¿: pv_cache_add(): pvar ¡$var(dpr)¿ added in cache Using Kamailio 5.2.4 Docker image. version: kamailio 5.2.4 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 Regards, Grant

5 years

Kamailio Rasberry Pi benchmark results

by Henning Westerholt

Hello, as promised here the report on my Rasberry Pi benchmarks. The numbers were quite impressive! - 3000 registration requests per second (in-memory usrloc) - 300 calls per second for a p2p call (default cfg, only SIP traffic) - about 18 MBit/s incoming and 16 MBit/s outgoing SIP peak traffic could be processed All the details about the test setup and more numbers in the blog post: https://skalatan.de/blog/kamailio-rpi-benchmark Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

5 years

Kamailio v5.1.9 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v5.1.9 stable release is out. This is a maintenance release of the previous stable branch, 5.1, that includes fixes since the release of v5.1.8. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.9 or to v5.2.x series. For more details about version 5.1.9 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/09/kamailio-v5-1-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is the previous stable branch. The latest stable branch is 5.2, at this time with v5.2.4 being released out of it. 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 Kamailio World Conference - April 27-29, 2020 -- www.kamailioworld.com

5 years

ims_ipsec_pcscf: maybe core dump due to maximum count of connections

by Valentin Christoph

Hi, Doing some tests with the module ims_ipsec_pcscf, we encountered a core dump during startup of Kamailio and would like to understand the correct behavior. We assume the ipsec_max_connections parameter was the root cause --> how many max connections have been actually tested? Can it be that ipsec_client-port and ipsec_server_port were too close together (some overlapping)? Thx Christoph

5 years

install with kazoo

by Benoit Chesneau

Hi all, Can anyone share a simple configuration to use with kazoo or a link to it? I'm struggle in having it setup without using the defaults packages. Ideally it should dispatch messages to freeswitch. Any help is welcome :) Benoît

5 years

Planning the release of v5.1.9

by Daniel-Constantin Mierla

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

5 years

Kamailio ARM support improved, tests

by Henning Westerholt

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/

5 years

Development for v5.3.x is frozen

by Daniel-Constantin Mierla

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

5 years

Extract user from AOR

by Grant Bagdasarian

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

5 years

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