sr-users May 2018

sr-users@lists.kamailio.org

92 participants
140 discussions

Releasing Kamailio v5.1.4
by Daniel-Constantin Mierla 05 Jun '18

05 Jun '18

Hello, I am considering to release a new minor version out of branch 5.1, respectively the v5.1.4, sometime next week, likely on Tuesday, June 5, 2018. As usual, if there is any issue not yet reported on github tracker, do it as soon as possible to give it a chance to be fixed. Soon I am going to do the backports of commits with fixes in master that apply in branch 5.1, so keep a close eye and if someone is missing, let me know to push it in the stable branch. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com

3 3

Kamailio Behind TCP Load Balancer
by Colin Morelli 04 Jun '18

04 Jun '18

Hey all, I'm looking to put Kamailio behind a TCP load balancer that is SIP-unaware. My application is deployed in AWS and I'm tying to place Kamailio behind an ELB. For the most part, everything is fine. For my specific implementation I'm disabling UDP as a signaling transport and using only TLS. This enables me to not have to worry about a SIP-aware LB at the edge because replies to an incoming request will be sent over the existing established TCP socket (avoiding any crazy routing requirements). However - this poses an issue with source addresses. Does Kamailio support anything like the proxy protocol ( http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) for getting TCP stream information from a load balancer? Do I need to go back to exposing it directly to the world so that I can get source addresses? Thanks, Colin

3 4

Anybody using 2 instances with topos communicating with each other?
by Daniel Tryba 01 Jun '18

01 Jun '18

Scenario: endpoint (bob) <-> kamailio proxy (5.1.3) <-> kamailio backend (5.1.2) Both kamailio instances are running the topos module (mysql backend). Call setup is fine, but forwarding BYEs fail. With a call from endpoint to kamailio, topos on the proxy scrambles Contact to kamailio backend. But in responses from backend contact remains untouched. In the ACK to the 200, topos on the proxy does nothing. If the caller hangsup, the BYE will loop internally till max hops is exceeded (483 which will be send to caller eventually). When the backend initiates the call to the endpoint, topos appears to work, but the BYE from the endpoint on hangup get a 404 Not here from the proxy (route[WITHINDLG]). Disabling topos on the proxy will result in a functioning proxy (config attached). Is there something wrong with my config? Or is this an unforseen scenario that just doesn't work with topos? * Endpoint to backend scenario endpoint:5060 -> proxy:5060 INVITE sip:callee@sip.pocos.nl;transport=tcp SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Max-Forwards: 70 Route: <sip:proxy:5060;lr> Contact: <sip:bob@endpoint:5060;ob> proxy:5060 -> backend:5060 INVITE sip:callee@sip.itco.nl;transport=tcp SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... CSeq: 29848 INVITE Route: <sip:proxy:5060;lr> Contact: <sip:btpsh-5af5972d-bf5e-2@proxy> backend:5060 -> proxy:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy;branch=... Contact: <sip:atpsh-5af19bf0-9f94-7@backend> proxy:5060 -> endpoint:5060 SIP/2.0 200 OK Contact: <sip:atpsh-5af19bf0-9f94-7@backend> Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Record-Route: <sip:proxy;lr> endpoint:5060 -> proxy:5060 ACK sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Route: <sip:proxy;lr> proxy:5060 -> backend:5060 ACK sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... endpoint:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... Max-Forwards: 70 Route: <sip:proxy;lr> proxy:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Max-Forwards: 69 Route: <sip:proxy;lr> proxy:5060 -> proxy:5060 BYE sip:atpsh-5af19bf0-9f94-7@backend SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Via: SIP/2.0/UDP proxy;rport=5060;branch=... Via: SIP/2.0/UDP endpoint:5060;received=endpoint;rport=5060;branch=... Max-Forwards: 68 Route: <sip:proxy;lr> [not going to mention the 50+ BYEs adding Vias and decrementing Max-Forwards. * Backend to endpoint scenario backend:5060 -> proxy:5060 INVITE sip:bob@endpoint:5060;ob SIP/2.0 Via: SIP/2.0/UDP backend;branch=... Route: <sip:loadbalancer@proxy;lr;received=sip:endpoint:5060> Contact: <sip:btpsh-5af07a27-72b-502c1@backend> proxy:5060 -> endpoint:5060 INVITE sip:bob@endpoint:5060;ob SIP/2.0 Via: SIP/2.0/UDP proxy;branch=... Contact: <sip:btpsh-5af5972d-bf5d-5@proxy> endpoint:5060 -> proxy:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy;received=proxy;branch=... Contact: <sip:bob@endpoint:5060;ob> proxy:5060 -> backend:5060 SIP/2.0 200 OK Contact: <sip:bob@endpoint:5060;ob;alias=endpoint~5060~1> Via: SIP/2.0/UDP backend;rport=5060;branch=... Record-Route: <sip:proxy;lr> endpoint:5060 -> proxy:5060 BYE sip:btpsh-5af5972d-bf5d-5@proxy SIP/2.0 Via: SIP/2.0/UDP endpoint:5060;rport;branch=... proxy:5060 -> endpoint:5060 SIP/2.0 404 Not here Via: SIP/2.0/UDP endpoint:5060;rport=5060;branch=...

2 2

Dispatcher module ERROR
by Aleksandar Sosic 01 Jun '18

01 Jun '18

Hi everyone, We have an error using the dispatcher module. In the logs: ```0(107) ERROR: dispatcher [dispatcher.c:815]: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled``` We are running 5.2.0~dev5+0~20180523010152.1118+xenial The configuration file parts regarding dispatcher are as follows: ``` loadmodule "dispatcher.so" ... # ----- dispatcher params ----- modparam("dispatcher", "list_file", "/tmp/dispatcher.list") # Dispatcher: Enable Failover-Support modparam("dispatcher", "flags", 2) # Dispatcher: Overwrite Destination address, if required. modparam("dispatcher", "force_dst", 1) # AVP's required for Fail-Over-Support: modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") # Try to recover disabled destinations every 15 seconds. modparam("dispatcher", "ds_ping_interval", 15) # Actively query the gateways: modparam("dispatcher", "ds_probing_mode",0)# ----- dispatcher params ----- modparam("dispatcher", "list_file", "/tmp/dispatcher.list") # Dispatcher: Enable Failover-Support modparam("dispatcher", "flags", 2) # Dispatcher: Overwrite Destination address, if required. modparam("dispatcher", "force_dst", 1) # AVP's required for Fail-Over-Support: modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") # Try to recover disabled destinations every 15 seconds. modparam("dispatcher", "ds_ping_interval", 15) # Actively query the gateways: modparam("dispatcher", "ds_probing_mode",0)``` What are we doing wrong? What are we missing? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Acc module and PostgreSQL
by Javohir Maxmarajabov 01 Jun '18

01 Jun '18

Is it possible to enable accounting module with PostgreSQL? All I found is documentation and examples that showing accounting module is used with MySQL module. -- Javokhir M.M. ________________________________________________ Disclaimer: The information in this e-mail is confidential. If you are not addressed recipient then please return and delete this e-mail from your system. Unauthorised use of or disclose the contents of this e-mail may be unlawful.

2 1

Strange behavior with $shtinc
by Brooks Bridges 01 Jun '18

01 Jun '18

Let me preface this with the statement that as best I can tell from docs and code, this function is supposed to be 100% atomic and this shouldn't be able to happen. I also have not found anything in the module's github commit logs that would indicate this behavior has changed from previous versions. That being said, I appear to have run into an oddity where intermittently I'm getting 2 slots being put in the same entry, which results in trying to parse the output for graphing and reporting not working quite right. The mechanism I'm using is a very simple counter mechanism to record statistics about calls. As an example, I am using the following mechanism: $var(z) = $shtinc(callstats=>$avp(realm),cps_exceeded); or $var(z) = $shtinc(callstats=>$avp(realm),sessions_exceeded); This typically results in something like this: { entry: 4335 size: 1 slot: { { name: realm1,total_requests value: 2365034 type: int } } } { entry: 4532 size: 1 slot: { { name: realm2,cps_exceeded value: 30 type: int } } } And so on... However, one or more of them sometimes end up like this: { entry: 4646 size: 2 slot: { { name: realm1,total_requests value: 15958026 type: int } { name: realm2,cps_exceeded value: 6432103 type: int } } } Thanks in advance for your help and/or suggestions! Brooks Bridges | Engineering Manager O1 Communications 4359 Town Center Boulevard, Suite 217 El Dorado Hills, California 95762 office: 916.235.2097 | main: 888.444.1111, Option 2 email: bbridges(a)o1.com<mailto:bbridges@o1.com> | web: www.o1.com<http://www.o1.com/>

3 5

Authentication against outbound carrier trunk
by Krzysztof Grobelak 31 May '18

31 May '18

Hello List, I have a working setup with a kamailio + freeswitch where i can register extension and make succesfull calls between them. I added now a "external" path for outbound call to which i can successfully route using the dialplan + dispatcher combo. My problem is that my outbound path requires authentication and i'm struggling to find a way to successfully authenticate with the remote end. I configured the UAC module to register against the remote end with a set of credentials but in the SIP trace i can see that the kamailio simply uses the local user credentials instead of the external ones. I believe that this is because the 401 Unauthorized from the carrier gets proxied to the extension which responds with its own credentials. Can anybody suggest how can i stop forwarding them in this case to extension and instead use the UAC to reply with different set of credentials? Regards, Krzysztof The config: request_route { ... if($rU=~"[0-9]{5,}"){ xlog("L_INFO","Looking up route for $rU\n"); dp_match("1", "$rU"); $var(dsid) = $(var(attrs){s.int}); if(!ds_select_dst("$var(dsid)", "4")) { send_reply("404", "No destination"); exit; } if(!ds_select_domain("$var(dsid)", "4")) { send_reply("404", "No destination"); exit; } xlog("L_INFO", "Looking up $fn in database\n"); $avp(s:auth_realm_avp) = "realm.com"; $avp(s:auth_username_avp) = "username"; $avp(s:auth_password_avp) = "password"; if(uac_reg_request_to("$fn", 1)) { xlog("L_INFO", "Found remote user [$rU] on [$rd] via [$du]"); t_on_failure("REMOTE_AUTH"); xlog("L_INFO", "going to <$ru> via <$du>\n"); route(RELAY); } exit; } failure_route[REMOTE_AUTH] { if ($T_reply_code == 401 or $T_reply_code == 407) { xlog("L_INFO", "Remote asked for authentication"); uac_auth(); } } -- PGP: 9E5D E635 5A03 485C 2E00 4530 EB83 920A 9E21 FBA8

1 0

error in tls configuration in kamailio 5.1.3
by Narasimhaiah, Vinod Maralenahalli 31 May '18

31 May '18

Hi, I upgraded kamailio 4.4.2 to kamailio5.1.3 and i am getting this error *"Unable to load certificate file '/etc/kamailio/kamailio-selfsigned.pem",* kamilio 4.4.2 does not need the ssl file, but kamailio 5.1.3 need ssl file, what changes required in kamailio 5.1.3 to run with tls. Please help me in resolving this issue. Thank you vinod.M.N -- To download the app, click: iOS <http://goo.gl/ZJx3y1> | Android <http://goo.gl/G1ehjZ> -- ***This transmission contains information that is confidential and proprietary of Kirusa Inc.,its affiliates and/or its partners and customers. This information is intended to be shared only with the recipient of this e-mail who is bound by confidentiality. If you received this e-mail in error, please delete the e-mail and notify the sender by return e-mail.***

4 4

Upgrade issue with old Kamailio 3.0.3 in table rls_presentity
by Kristijan Vrban 31 May '18

31 May '18

Hi, i try a upgrade from old 3.0.3 Kamailio mysql db. Got stuck with update the structure : ALTER TABLE rls_presentity MODIFY callid VARCHAR(255) NOT NULL;ALTER TABLE rls_presentity MODIFY contact VARCHAR(128) NOT NULL; found on: https://www.kamailio.org/wiki/install/upgrade/3.1.x-to-3.2.0 But this two table does not exist? See also table definition at: https://kamailio.org/docs/db-tables/kamailio-db-3.1.x.html#GEN-DB-RLS-PRESE… I reckon it is safe to skip this to tables? Kristijan

2 4

31 May '18

Hi, https://www.kamailio.org/wiki/start?do=register Is not working. You get a empty page here. Kristijan

2 2

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 May 2018