sr-users September 2020

sr-users@lists.kamailio.org

84 participants
108 discussions

Dispatcher stops working
by Sergio Charrua 12 Oct '20

12 Oct '20

Hello, Using Kamailio 5.1.6 for load balancing & failover, I noticed that from time to time, and very rarely, the dispatcher module stops dispatching to the Asterisk servers. I have to execute a "kamcmd dispatcher reload" for it to (re)start working. This is my dispatcher.list : 1 sip:10.19.XXX.YYY:5060 0 1 duid=sipgw01;maxload=100 1 sip:10.19.XXX.YYY:5060 0 2 duid=sipgw02;maxload=100 1 sip:10.19.XXX.YYY:5060 0 3 duid=sipgw03;maxload=100 1 sip:10.19.XXX.YYY:5060 0 4 duid=sipgw04;maxload=100 This is my dispatch routes: # Dispatch requests route[DISPATCH] { if(!ds_select_dst("1", "10","4")) { xlog("L_INFO","no destination selected from dispatcher list!"); send_reply("404", "No destination"); exit; } xlog("L_INFO","going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Sample failure route failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } xlog("L_INFO", "Media server $du failed to answer, selecting other one!"); # next DST - only for 500 or local timeout if ( t_check_status("500") || (t_branch_timeout() && !t_branch_replied()) ) { #mark the destination Inactive and Probing ds_mark_dst("ip"); if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } I suspect that the ds_mark_dst("ip") command in RTF_DISPACTH is the cause. Is there any think I can improve on this? Or any know bug with the dispatcher in Kamailio 5.1.6 version? Thanks in advance, *Sérgio Charrua*

4 4

Logging problem
by Jan Rozhon 12 Oct '20

12 Oct '20

Hi, sorry for quite stupid and newbie questions, but I am out of ideas. 1. On one of my Debian 10 servers I am unable to stop logging kamailio messages to /var/log/syslog. It is funny, because I have 3 more servers where it works but on this one, it doesnt and no matter what I try it still keeps sending logs to syslog (and to the file configured). My related configs: /etc/kamailio/kamailio.cfg log_stderror=no log_facility=LOG_LOCAL7 /etc/rsyslog.conf local6.* /var/log/kamailio/cdr.log local7.* /var/log/kamailio/kamailio.log /etc/rsyslog.d/kamailio.conf if $programname contains 'kamailio' then /var/log/kamailio/kamailio.log & stop /etc/systemd/system/multi-user.target.wants/kamailio.service SyslogIdentifier=kamailio 2. It is probably related to 1. I am unable to get the CDRs logged to anything else but /var/log/syslog. I tried database (nothing) and setting cdr_facility and again nothing. It just keeps sending everything to /var/log/syslog. Related configs: modparam("acc", "cdr_enable", 1) modparam("acc", "cdrs_table", "acc_cdrs") modparam("acc", "cdr_facility", "LOG_LOCAL6") Example output in syslog file: Sep 30 09:21:41 sip2 /usr/sbin/kamailio[1151]: NOTICE: {2 21 INVITE ZPZI7Hqytw} acc [acc.c:279]: acc_log_request(): ACC: call missed: timestamp=1601450501;method=INVITE;from_tag=1GH5hGQxN;to_tag=QwcYFet;call_id=ZPZI7Hqytw;code=486;reason=Busy here;src_user=XXXXXXXXX; Is there something trivial I am missing? Thank you. Regards, Jan

4 7

SIP client - Linphone
by Pavithra Mohanraja 06 Oct '20

06 Oct '20

Hi, I am a newbie to sipclient Linphone. I know this issue is not related with kamailio.Yet If anybody have tried it before , kindly provide me with some links or procedures to be followed for call registration and connectivity with kamailio since in my case, request is going but response is not coming back resulting in timeout issue. This happens only in linphone.If i do the samething in PJSIP/zoiper, call registration and call establishment happens perfectly fine. Kindly help. Thanks, Pavithra

4 10

kamailio SBC - session timers
by marek 06 Oct '20

06 Oct '20

hi, i have kamailio+rtpengine acting as a SBC (private/public net interfaces) kamailio 5.4.x/rtpengine 9.x/centos 7 using TOPOH module modparam("topoh", "mask_ip", "public_IP") i'm rewriting IPs in INVITE like this $var(ruri) = "sip:" + $(ru{re.subst,/private_IP/public_IP/g}); $ru = $(ru{re.subst,/private_IP/public_IP/g}); $tu = $(tu{re.subst,/private_IP/public_IP/g}); $fu = $(fu{re.subst,/remote_private_IP/public_IP/g}); the same for route[WITHINDIALOG] and INVITE i have problem with session timers using re-INVITE method in the first INVITE SDP is correct c=IN IP4 public_IP but in the reinvite is c=IN IP4 private_IP and remote SBC drop with 422 because SDP is changed and SDP version is not. any tips / best practice? thanks Marek

2 2

Releasing Kamailio 5.2.8
by Henning Westerholt 02 Oct '20

02 Oct '20

Hello, I am planning to release next week (likely on Friday 2nd October) the next minor version out of branch 5.2, version 5.2.8. Backports of fixed issues from git master will be integrated as usual. If you are aware of new issues which were not yet reported, let us know (by creating an issue on the tracker). Unless major regressions are discovered after the release, this will be the last release of the 5.2 stable branch. The current stable branches 5.3 and 5.4 will continue to be maintained. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

Kamailio fails to start when tls module parameter 'config' contains a folder name
by Leonid Fainshtein 02 Oct '20

02 Oct '20

Hi, I am using Kamailio 5.4.1 installed from the packages on Ubuntu 18.04. When I define 'modparam("tls", "config", "<folder>")', Kamailio fails to start: ERROR: tls [tls_config.c:418]: tls_load_config(): cannot make tmp file configrcCczj ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while initializing module tls (/usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so) I checked the tls_load_config() function and found that when a folder is defined in the 'config' parameter, the function tries to open a temporary file in the working directory. I believe that the working directory at that point is the folder where Kamailio was started: /usr/sbin. I succeeded to launch Kamailio in two ways: Method 1: copy 'kamailio' to /tmp and modify kamalio.service accordingly. This experiment result made me think that the working folder is the folder where kamailio is started. Method 2: add Kamailio command line parameter "-w /tmp" (I also tried to define the Systemd 'WorkingDirectory' parameter but it didn't have any effect.) I think that the ultimate solution for this problem is to modify the tls_load_config() function in such a way that it will open the temporary file in a folder that is intended for the temporary files. For example, the /tmp folder in Linux and *BSD systems. I guess that /tmp is a good place in MacOS as well. Best regards, Leonid Fainshtein

2 3

TOPOS issue
by David Villasmil 01 Oct '20

01 Oct '20

Hello guys, I have this scenario where I have an ongoing transaction. I receive a 180 (non 100rel) with some to_tag, which i forward back to the caller. Then I receive an 183 (100rel) which is forwarded back to the caller, who in turn PRACKs it. It is then that Kamailio (apparently) can't match that transaction internally and replies to the caller (the one PRACKing the 183 (100rel)), with 493 FORBIDDEN. I'm attaching a trace flow. (Kamailio is 10.255.0.1) you need to open the email really wide to see it properly. Anyone ever encountered this? Is this valid and should work? |Time | 10.15.169.4 (FS) 10.255.0.1 (KAM) | (KAM) 1.1.1.10 1.2.3.13 | | | | | | | | | | | | | |0.000000 | INVITE SDP (g722 g71 | | | | |(6000) ------------------> (5060) | | | |0.000941 | 100 Telnyx trying | | | | |(6000) <------------------ (5060) | | | |0.046558 | | | INVITE SDP (g722 g71 | | | | |(33033) ------------------> (5060) | |0.102078 | | | 100 Trying, boss | | | | |(33033) <------------------ (5060) | |0.386867 | | | 180 Ring a ling a li | | | | |(33033) <------------------ (5060) | |0.387578 | 180 Ring a ling a li | | | | |(6000) <------------------ (5060) | | | |3.413368 | | | 181 Prending to forw | | | | |(33033) <------------------ (5060) | |3.414373 | 181 Prending to forw | | | | |(6000) <------------------ (5060) | | | |6.441704 | | | 183 Seeing what I ca | | | | |(33033) <------------------ (5060) | |6.442896 | 183 Seeing what I ca | | | | |(6000) <------------------ (5060) | | | |6.890173 | PRACK | | | | | |(6000) ------------------> (5060) | | | |6.895497 | 403 Forbidden R1 | | | | |(6000) <------------------ (5060) | | | |9.473035 | | | 486 Actually, I'm qu | | | | |(33033) <------------------ (5060) | |9.473561 | | | ACK | | | | | |(33033) ------------------> (5060) | |9.473902 | 486 Actually, I'm qu | | | | |(6000) <------------------ (5060) | | | |9.921200 | ACK | | | | | |(6000) ------------------> (5060) | | | Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Record Route
by Andy Kama 01 Oct '20

01 Oct '20

Hi Guys I am trying to add a custom record route so i have added record_route_preset("mydomain:5061;transport=tls", "myip:5060"); yet kamailio is still not adding it in the sip message what am i doing wrong?

2 3

XHTTP_Prom syntax error with usrloc in Kamailio 5.3
by Tim Unkrig 30 Sep '20

30 Sep '20

Hello hello, I would like to monitor our production kamailio cluster (5.3) with prometheus and I was in the beginning so happy to spot the xhhtp_prom module. But when we enabled it, the output was in view of prometheus malformed in combination with the usrloc module, we got the following output: kamailio_usrloc_location-contacts 0 1597934423943 kamailio_usrloc_location-expires 0 1597934423943 kamailio_usrloc_location-users 0 1597934423943 Prometheus only accepts “_” instead of “-“. So unfortunately I get "strconv.ParseFloat: parsing "-contacts": invalid syntax” on the prometheus primary node, when I activated the scraper. This has been issued in the master branch of kamailio with a sanatize function for that problem. But I would like to avoid compiling modules by myself, because this can be messy from time to time. That´s why my question, is there maybe another way of fixing this? I really appreciate any comments here and thanks for your time, Tim Unkrig

2 1

xavu methods equivalent to that of xavp (e.g. xavp_get_child)
by Chaigneau, Nicolas 30 Sep '20

30 Sep '20

Using xavu (now that they have been fixed) in a custom C module, I've noticed that the following methods do not exist: xavu_get_child xavu_get_child_with_ival xavu_get_child_with_sval xavu_serialize_fields Though they are not strictly necessary, it could be useful to add them to Kamailio core. (Possibly with code refactoring, to avoid duplicating whole functions ?) What do you think? Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

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