sr-users

sr-users@lists.kamailio.org

39 participants
37513 discussions

Using reserved keywords in cfg variables
by Paul Claudiu Boriga 07 Jun '17

07 Jun '17

Hello all, We found out that when using cfg variables certain keywords are not allowed, and Kamailio logs a generic error: <core> [cfg.y:3368]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 256, column 9-14: syntax error For example we cannot use words like enable/disable for var name or group name but we can use disabled or enabled: group_name.enable = 1 descr "test variable" Looking into the cfg.lex file, I noticed that these are keywords which will be interpreted as values (I don't have too much experience with flex/bison so I am not sure I got this right). We have been using Kamailio 4.4 to test this, but I think it is not specific to a version. Is this behavior documented somewhere? If not, where should it be documented? Also can we have a more specific log message in this case? Thank you, Claudiu Boriga.

2 6

Issue with Dispatcher Failover algorithm
by Cristi Constantin 07 Jun '17

07 Jun '17

Hello, I have an issue with the behavior of ds_select_dst() method in case of using algorithm 8 (dispatch based on priority). In case both destinations are available, they are used alternatively, instead of always using the one with the highest priority. By searching through the mailing list I found that the lower the priority number, the higher the priority (1 is first, 2 is second, etc.). Based on this, I set the following in dispatcher.list: 7 sip:10.126.54.51:5060;transport=sctp 9 1 7 sip:10.126.55.51:5060;transport=sctp 9 2 After running "kamcmd dispatcher.reload" and "kamcmd dispatcher.list", I have the confirmation that the priorities are correctly set: SET: { ID: 7 TARGETS: { DEST: { URI: sip:10.126.55.51:5060 ;transport=sctp FLAGS: AP PRIORITY: 2 } DEST: { URI: sip:10.126.54.51:5060 ;transport=sctp FLAGS: AP PRIORITY: 1 } } } The dispatcher settings from kamailio.cfg is the following: modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_interval", 10) modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", "sip:kamailio@sdp-t-lb2") modparam("dispatcher", "ds_probing_mode", 3) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)") And the code which should do the displatch is the following: if (ds_is_from_list(7, 3, "$ru")) { remove_hf("Route"); if(!ds_select_dst("7", "8")) { send_reply("404", "No destination"); exit; } } With the settings above, I was expecting to always have the messages delivered to 10.126.54.51. Instead, they are dispathed to 10.126.54.51 and 10.126.55.51 alternatively. Thanks a lot, Cristian

6 15

Kamailio / Docker
by sain hassam caicedo 07 Jun '17

07 Jun '17

Dear Kamailio, My name is Sain, I from Colombia. I wonder if is possible to use Kamailio with Docker in Ubuntu 16 ? Also, respectfully do you have an easy installation manual or any recommendation to start doing some testing? I am interesting to learn more about Kamailio . Thank you very much

2 1

Auth_radius - digest auth problem
by Donat Zenichev 06 Jun '17

06 Jun '17

Hi all. Have a problem with radius authorization. I'm using auth_radius.so modparams, only path to client file: modparam("auth_radius", "radius_config", "/etc/radiusclient/radiusclient.conf") Freeradius installed and is working properly, radtest authentication from kamailio host succeed . How authorization block looks like: if (!is_present_hf("Authorization")) { xlog("L_NOTICE", "----- Athorization HF is not found - passing the challenge -----\n"); if (nat_uac_test("2")) { force_rport(); } www_challenge("$fd", "1"); exit; if (!radius_www_authorize("$fd","$fU")) { if (nat_uac_test("2")) { force_rport(); } xlog("L_NOTICE", "----- Registeration $au@$ar ($fU) from $si:$sp Rejected. Code: $rc -----\n"); sl_send_reply("401","Unauthorized"); exit; Radius log is filled by rows like: Auth: [digest] Cleartext-Password or Digest-HA1 is required for authentication. Tried to use radius_www_authorize without $fU - didn't change anything. Tried to use www_challenge without qop - didn't change anything. So, this solution is quite simple, but I have a fail while digest authentication. Any ideas? -- -- BR, Donat Zenichev Wnet VoIP team Tel: +380(44) 5-900-808 http://wnet.ua

4 8

Any document to study and develop kamailio
by sgy 06 Jun '17

06 Jun '17

Hi All, I can't find any document(PDF) to study and develop kamailio, do someone show me where it is. thank you -- Best Regards, Shengy

3 3

Kamailio 4.4.4 crash in tcp_read_headers()
by Armen Babikyan 06 Jun '17

06 Jun '17

Hello, Over the past few months, I've seen a smattering of kamailio crashes on various systems with identical backtraces: SIGSEGV in tcp_read_headers(), at tcp_read.c line 628. Example here: https://pastebin.com/qJ3ypnVz Note that in frame 0, print *c shows that req->parsed is pointing to an address exactly 8GB lower than req->buf. That req->parsed is pointing to an invalid memory location, crashing kamailio when the location is dereferenced. In other coredumps, I see that req->parsed is pointing to an address exactly 4GB lower than req->buf. Other info: This is Kamailio 4.4.4 on x86_64. I've not had success trying to reproduce this yet. Also worth noting that the crashes seem to be consistently associated with processing traffic from a UA connected over SIP/TCP; I've seen no other transport associated with this crash. Thoughts are welcome. Thanks! Armen

2 3

Rtpproxy didn't work
by sgy 03 Jun '17

03 Jun '17

I install rtpproxy and config as follow, but it didn't work, is my config OK ? errorlog: Jun 3 15:00:56 iZ2ze3uk97m2bfv681kyx4Z /usr/local/sbin/kamailio[28971]: ERROR: rtpproxy [rtpproxy.c:2552]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy Jun 3 15:00:58 iZ2ze3uk97m2bfv681kyx4Z /usr/local/sbin/kamailio[28971]: ERROR: rtpproxy [rtpproxy.c:2552]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy My config: PUB_IP: public ip of kamailio PVT_IP: private ip of kamailio 1. start rtpproxy rtpproxy -l PUB -s udp:localhost:7722 -F 2. kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_ALIASDB #!define WITH_USRLOCDB #!define WITH_NAT listen=PVT_IP modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722") -- Best Regards, Shengy

3 3

Rtpproxy didn't work
by sgy 03 Jun '17

03 Jun '17

I install rtpproxy and config as follow, but it didn't work, is my config OK ? My config: PUB_IP: public ip of kamailio PVT_IP: private ip of kamailio 1. start rtpproxy rtpproxy -l PUB -s udp:localhost:7722 -F 2. kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_ALIASDB #!define WITH_USRLOCDB #!define WITH_NAT listen=PVT_IP modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722") -- Best Regards, Shengy

1 0

Adding debugger module to kazoo-kamailio
by Joe Baran 02 Jun '17

02 Jun '17

I’m hoping that someone might have some suggestions on how to approach this. I’ve been working with kamailio as part of kazoo (via RPM install) and have been attempting to add the debugger module so I can trace things as they pass through kamailio. However, I need some help in determining the most effective way of adding this. Has anyone already done this / have any suggestions? Thanks, Joe

2 1

topos module - possible bug
by Pete Kelly 02 Jun '17

02 Jun '17

Hi I am using the topos module when bridging 2 networks with Kamailio. The INVITE/200OK part of the transaction is working fine (i.e. the Contact on both sides matches correctly the corresponding network). However when the ACK is sent into Kamailio, instead of realising the next hop is myself and skipping it, Kamailio is sending the ACK directly to itself as a packet, causing the call setup to break. Does anyone have any advice for this situation?

3 34

Jump to page:

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