sr-users November 2020

sr-users@lists.kamailio.org

52 participants
65 discussions

htable + event_routes + mod-init + htable:expired
by Brandon Armstead 02 Nov '20

02 Nov '20

Running 5.5.0-dev3 modparam("htable", "htable", "ipban=>size=8;autoexpire=300;dmqreplicate=1;") modparam("htable", "enable_dmq", 1) modparam("htable", "dmq_init_sync", 1) modparam("htable", "timer_procs", 4) modparam("htable", "timer_interval", 5) modparam("htable", "db_expires", 1) modparam("htable", "htable", "account=>size=4;dmqreplicate=1;") modparam("htable", "htable", "server=>size=4;autoexpire=15;") I'm attempting to retrieve an auth token in the init process and also refresh the token upon expiration in the htable:expired event. I'm seeing some behavior where every other execution of htable:expired the variable $sht(server=>auth::token) is set per kamcmd htable.dump server, however xinfo() reports that the token was retrieved in the variable $sht (server=>auth::token). Please see remaining event route config below: event_route[htable:mod-init] { # generate auth token into http_client_query("https://www.cryy.com/api/auth/token", '{"email": " brandon(a)cryy.com", "password":"XXXX"}', "$var(result)"); sht_lock("server=>auth::token"); $sht(server=>auth::token) = $var(result); sht_unlock("server=>auth::token"); xinfo("AUTH_TOKEN_RECEIVED, $sht(server=>auth::token)"); } event_route[htable:expired:server] { # process expired htable, renew auth token xinfo("AUTH_TOKEN_EXPIRED, lets retrieve a new one"); http_client_query("https://www.cryy.com/api/auth/token", '{"email": " brandon(a)cryy.com", "password":"XXXX"}', "$var(result)"); sht_lock("server=>auth::token"); $sht(server=>auth::time) = $TS; $sht(server=>auth::token) = $var(result); sht_unlock("server=>auth::token"); xinfo("AUTH_TOKEN_RECEIVED, $sht(server=>auth::token)"); xinfo("AUTH_TOKEN_TIME, $sht(server=>auth::time)"); } I've tried both with locking and unlocking. Also one last thing worth mentioning is that on the alternation where kamcmd htable.dump server shows no auth token, $sht(server=>auth::time) is available, when the auth token is visible in kamcmd htable.dump server there is no sht(server=>auth::time) returned. Also just to be explicitly clear -- xinfo() always returns AUTH_TOKEN_RECEIVED correctly in both event routes. Perhaps I'm over looking something -- thank you for the help in advance. - Brandon

2 3

outgoing TCP connection ID
by Sergiu Pojoga 02 Nov '20

02 Nov '20

Hi there, Is there a PV that exposes the outgoing TCP connection ID? $conid seems to be for received only. *$conid - The TCP connection ID of the connection the current message arrived on for TCP, TLS, WS, and WSS. Set to $null for SCTP and UDP.* The objective is to check the status of the egress TCP connection like for e.g.: if(!tcp_conid_state(conid)) { Thanks. --Sergiu

2 4

Kamailio v5.3.7 Released
by Daniel-Constantin Mierla 02 Nov '20

02 Nov '20

Hello, Kamailio SIP Server v5.3.7 stable release is out. This is a maintenance release of the latest stable branch, 5.3, that includes fixes since the release of v5.3.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.3.x. Deployments running previous v5.3.x versions are strongly recommended to be upgraded to v5.3.7. Note that 5.3 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.4, with v5.4.2 being release out of it. For more details about version 5.3.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/11/kamailio-v5-3-7-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

Releasing Kamailio v5.3.7
by Daniel-Constantin Mierla 02 Nov '20

02 Nov '20

Hello, I am planning to release Kamailio v5.3.7 sometime next week, likely on Monday or Tuesday, this being the usual prior notice for heads up to identify issues not reported yet on bug tracker as well as the commits you are aware of that were not backported yet. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

Missing refresher parameter in the Session-Expires header and Min-SE header
by Jose Figueroa 01 Nov '20

01 Nov '20

Hello everybody, I am trying an INVITE with a SBCs but fails, finding out it seems the Session-Expires doesn't include the param refresher= and according to this closed issue is already included https://github.com/kamailio/kamailio/issues/288 but I cannot achive this, I read the sst module documentation but I don't see anything related this parameter. So, in summary the SBC expects the following: Session-Expires: 1800; refresher=uac; Min-SE: 600 I set only: modparam("sst", "enable_stats", 1); modparam("dialog", "dlg_flag", 5) modparam("sst", "sst_flag", 6); modparam("sst", "min_se". 1800); Now on the invite I the setflag(); 5 and 6 so I see now the header Session-Expires: 1800 but not the refresher=uac; and also I don't see how to set the Min-SE:600 Could you please point me to the right direction? Any hint would be very helpful. -- Jose Figueroa Software Engineer

1 0

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 November 2020