sr-users February 2024

sr-users@lists.kamailio.org

49 participants
39 discussions

Development is open for future release of v5.9.x series

by Daniel-Constantin Mierla

Hello, the branch 5.8 was created, therefore the master branch is open for adding new features, to be part of future release series v5.9.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.8.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.8 or 5.7. Expect that v5.8.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.9.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime during the last part of 2024 or the beginning of 2025. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

2 months, 2 weeks

Branch 5.8 has been created

by Daniel-Constantin Mierla

Hello, the branch 5.8 has been created, to be used for releasing v5.8.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.8 cd kamailio-5.8 git checkout -b 5.8 origin/5.8 Pushing commits in this branch: git push origin 5.8:5.8 Note that 5.8 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.8 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.8 will be out, respectively Kamailio v5.8.0. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

2 months, 2 weeks

Building Debian packages for further modules

by Christian Berger

Hi, for our workflow we build our own Debian packages for kamailio. We are currently trying and failing to create a package for the kafka modules. What we have tried so far: Adding the "Build-Depends:" entries for librdkafka-dev in debian/control Adding a "Package" in debian/control Adding kafka to the PACKAGE_GROUPS in debian/rules So far it seems to build the module and a package for it, but the package only contains metadata, but no .so file. We are currently running out of ideas. What else can we do? Best wishes Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

2 months, 2 weeks

Kemi questions

by Stefan-Cristian Mititelu

Hello, When writing kemi cfg (python in my case), is there any way to get rid of standard cfg shared variables and use kemi cfg variables instead? E.g. Instead of $shv(blabla) (in standard config) can I use some global python var called 'blabla'? Is it seen and shared by all kamailio processes? Or I still need to use KSR.pv.get/set("$shv(blabla)") ? Thank you, Stefan

2 months, 2 weeks

Freeswitch and Kamailio Integration.

by jayapal＠ring4.com

Greetings, I am new to Kamailio and seeking assistance. I have installed FreeSWITCH version 1.10.11 and Kamailio version 5.6.5. I have two inquiries: I aim to configure FreeSWITCH with Kamailio. Could someone kindly guide me on achieving this integration? I am curious about the storage location of Kamailio's log files. Could someone please provide information regarding this? Thank you in advance for your help and guidance.

2 months, 2 weeks

htable write access state

by Patrick Karton

Hello are htable protected for multiple write access? can i safely update htable from one process and be sure another process will access it for write operation ? if yes is the lock on all the htable or only on the bucket where the key belongs ? Thanks.

2 months, 2 weeks

rpm kamailio git master version

by Henning Westerholt

Hello, just a question about the https://rpm.kamailio.org/ repository, especially regarding git master builds. It seems that the git master build there was updated last autumn. It would be great if it could be updated, now as we want to test for the coming release. Thank you, Henning Westerholt -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

2 months, 2 weeks

dialog:event unknown and kemi callback error

by Duarte Rocha

Hello all, I'm currently developing some kamailio scripts with app_jsdt by migrating a proxy of mine from Kamailio routing script to Js. I've migrated some parts of my request_route and everything seems to be working fine. I am now trying to migrate my event routes to JS and I started with dialog. dialog parameters : modparam("dialog", "event_callback", "dialogEvent") Code : function dialogEvent(event) { KSR.info("Dialog event " + event + " in JS") } After this i try to make a call and in my logs i have : "Dialog event unknown in JS" "Dialog event dialog:start in JS" Is this normal behaviour that I should ignore and only try to process "start,end,failure" or is this a signal of something wrong in my code? I also have this error in my code : "sr_kemi_cbname_lookup_idx(): index 1 is out of range". Does that mean that i have a JS function that calls a missing function in kamailio script or the opposite? How can I identify the root cause? Thanks in advance, Cheers

2 months, 2 weeks

Variable specific to branch reply?

by Benoit Panizzon

Hi List avp stacking is starting to drive me crazy... Somehow I don't understand what is going on in this situation: I have a main branch, and add two more branches with append_branch() I use a on_branch_route trigger: branch_route[BR_TO_CPE] { [Here, some code setting $var(needbh)] if ("yes" == $var(needbh)) { xlog("L_INFO", "$cfg(route): BR_idx: $T_branch_idx BACKHAUL: YES to $nh(u) \n"); add_rr_param(";rtp=yes"); record_route(); $avp(backhaul) = "yes"; $avp(nexthop) = $nh(u); rtpengine_manage($avp(rtp_to_cpe)); } else { xlog("L_INFO", "$cfg(route): BR_idx: $T_branch_idx BACKHAUL: NO to $nh(u) \n"); record_route(); $avp(backhaul) = "yes"; $avp(nexthop) = $nh(u); } } In the Logs, I see Branches Index 0,1,2 with the desired information. So I have 3 values stacked in the avp backhaul and nexthop, right? When I get a reply, I would like to determine if backhauling is required or not. onreply_route[MANAGE_REPLY] { xlog("L_INFO", "MANAGE_REPLY: for BR_idx: $T_branch_idx\n"); while ($(avp(nexthop)[$var(i)]) != $null) { xlog("L_INFO", "MANAGE_REPLY: DEBUG Branch: $T_branch_idx VAR IDX: $var(i) NH: $(avp(nexthop)[$var(i)]) \n"); $var(i) = $var(i) + 1; } } So on EVERY reply, I would expect to get three "DEBUG" lines as I stacked 3 AVP.. Bug I get only 2! Why I am missing one of the stacked AVP? (the last one as it looks like) Or is there any other way to access a arbitrary variable specific to a branch on the reply to that branch? PS: I don't need $avp(nexthop). It's just an easy way to make sure I get the correct avp index for the branch I am interested in. 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 ______________________________________________________

2 months, 2 weeks

mem_join_free flag in kamailio 5.6 deb

by Arsen Semenov

Hello! I have an issue with kamailio 5.6.5 after some time of flying there are errors in logs: <core> [core/mem/q_malloc.c:297]: qm_find_free(): > qm_find_free(0x7fc79c286010, 536); Free fragment not found! mem_join=1 by default, but it seems that MEM_JOIN_FREE flag is not defined in this build kamailio -I > Print out of kamailio internals > Version: kamailio 5.6.5 (x86_64/linux) > Default config: /etc/kamailio/kamailio.cfg > Default paths to modules: /usr/lib/x86_64-linux-gnu/kamailio/modules > Compile flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_BLOCKLIST, > HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED > MAX_RECV_BUFFER_SIZE=262144 > MAX_URI_SIZE=1024 > BUF_SIZE=65535 > DEFAULT PKG_SIZE=8MB > DEFAULT SHM_SIZE=64MB > ADAPTIVE_WAIT_LOOPS=1024 > TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select > Source code revision ID: unknown > Compiled with: gcc 10.2.1 > Compiled architecture: x86_64 > Compiled on: > OS Debian 11 bullseye However I noticed the flag exists in 5.7 installed from deb Print out of kamailio internals > Version: kamailio 5.7.4 (x86_64/linux) > Default config: /etc/kamailio/kamailio.cfg > Default paths to modules: /usr/lib/x86_64-linux-gnu/kamailio/modules > Compile flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, > *MEM_JOIN_FREE*, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED > MAX_RECV_BUFFER_SIZE=262144 > MAX_URI_SIZE=1024 > BUF_SIZE=65535 > DEFAULT PKG_SIZE=8MB > DEFAULT SHM_SIZE=64MB > ADAPTIVE_WAIT_LOOPS=1024 > TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select > Source code revision ID: unknown > Compiled with: gcc 10.2.1 > Compiled architecture: x86_64 > Compiled on: OS Debian 11 bullseye and now, what got me bit confused is that when I build 5.6.5 from source "make printcdefs" gives me this flag, alongside with other flags which I do not see later in "kamailio -v" output. So I am not sure whether this flag was defined during 5.6.5 deb build time or it has been somehow lost? So I need your advice. Regards, Arsen

2 months, 2 weeks

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 February 2024