sr-users February 2018

sr-users@lists.kamailio.org

90 participants
109 discussions

How to avoid automatic string to int conversion?

by Yuriy Gorlichenko

Hi im using kamailio 5.1 with native cfg file and using json_get_value( method) form jsonso module When i get json string that contains strings and i need to have these strings kamailio tries to convert string i find into int and affcource it can't then i see warning and can't get vaules of the string i have rval_expr_eval_int(): rval expression conversion to int failed (24,6-24,14) How to say kamailio to not convers strng to int?

6 years, 2 months

dmq_usrloc - which server?

by Alex Balashov

Hi, The Socket parameter of location entries is not replicated under dmq_usrloc. To make matters worse, the technical characteristics of the registrar module are such that I cannot straightforwardly modify the incoming Contact to add a rider indicating the server on which the register was received. The AoR domain is the same for all registrations received on any server in the DMQ mesh. To reach the registrants, I need to forward the registration to the correct server that corresponds to the true provenance of the registration. What is a reasonable way of finding out what that is? I don't see any method of injecting such values into the replicated contacts, as dmq_usrloc does not provide hooks for this. Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

6 years, 2 months

any interest in segmentation fault at startup ?

by Jean Cérien

Hi I guess I'm a bit too creative when it comes to kamailio syntax.... just edited the cfg file and got the following error upon startup: kamctl start INFO: Starting Kamailio : /usr/sbin/kamctl: line 1915: 5294 Segmentation fault $OSERBIN -P $PID_FILE -f $ETCDIR/kamailio.cfg $STARTOPTIONS > /dev/null 2> /dev/null ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed I assume it is my syntax in cfg that creates this, I just need to correct it, but if there is interest, I can provide the faulty cfg file J.

6 years, 3 months

Re: [SR-Users] Blind Transfer WS Error

by Matteo Campana

Dear Kamailians, does anyone have any idea on the issue below? Alessio told me that is always reproducible, and he can also provide captures and more logs. Thanks in advance! Matteo *From: *sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of Alessio Miranda <smirolandia(a)gmail.com> *Reply-To: *"Kamailio (SER) - Users Mailing List" < sr-users(a)lists.kamailio.org> *Date: *Tuesday, 16 January 2018 at 14:18 *To: *"sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> *Subject: *[SR-Users] Blind Transfer WS Error Hi, I have a problem with the blind transfer via WebSocket, debugging from the browser we see that in some cases when the REFER is done and the sip message "202 Accepted" arrives, the message "180 Ringing" arrives first and then the "100 Trying" and the transfer goes in error with "500 JsSIP Internal Error" I have an architecture with Kamailio in frontend and asterisk in backend on the same network, the sip dialogue between FE and BE is in SIP / UDP. The WebRTC client connects to WebSocket at Kamailio's public address. We have verified that the sip messages exchanged between kamailio and asterisk are always correct. Kamailio Ver. 4.4.4 Asterisk Ver. 13.18.3 PJSIP Ver. 2.6 JSSIP Ver. 3.2.2 Thanks Alessio

6 years, 3 months

Via header force change protocol to TLS?

by Anthony Alba

I have kamailio behind a TLS termination proxy so the sockets are correctly deduced to be TCP. However the clients only talk TLS to the proxy and are confused when the top Via header added by Kamailio is TCP. Is there a way for Kamailio to forcibly pretend its protocol is TLS? Like advertised_address but "advertised_protocol" instead. (With pjsip testing: it has a flag use_tls which ignores TCP from Kamailio and continues to use the persistent TLS transport to proxy. Linphone fails because it tries to honor TCP in Via and is unable to establish TCP transport). BTW I am using t_relay_to_tcp so Kamailio will return traffic to the proxy as TCP even though the contact addresses specify transport=TLS.

6 years, 3 months

Contact and Record-Route are using Private IP Address- is this correct?

by Wilkins, Steve

Hello All, Contact and Record-Route are using Private IP Address - is this correct? I though the Public IP should be used. I do not know what setting is causing this to happen. Does anyone have any ideas? Thank you, -Steve

6 years, 3 months

Info: Markus Monka replacing Marcus Hunger in management group

by Daniel-Constantin Mierla

Hello, Markus Monka has just replaced Marcus Hunger in Kamailio project management group. Marcus (still at sipgate) has moved to work more on frontend applications than backend, no longer interacting with Kamailio project. Markus Monka has managed the VoIP operations at sipgate for more than 15 years, helping the project over the years with various resources, mainly in respect of organizing events and testing infrastructure, sipgate being one of the oldest VoIP services using Kamailio (since first releases of SER). The change is reflected now on the website: * https://www.kamailio.org/w/management/ Warm welcome to Markus and many thanks to both of them for what they did so far for Kamailio project! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 3 months

Info: Kamailio project administration updates

by Daniel-Constantin Mierla

Hello, after several discussions at some of the past IRC devel meetings, finally we started to build a team to be involved more actively in the administration of Kamailio. The project has grown steadily, not only in terms of code, but also packaging, continuous integration, social networking interactions as well as participation to events world wide. For a better coordination and ability to handle related tasks, I invited the most active developers and community members to join so called Kamailio Administration Team, the initial details about it are published as part of management page on kamailio.org: * https://www.kamailio.org/w/management/ Some more details about its rules and purpose: * https://www.kamailio.org/w/kadmin/ It will still take some time to get it properly rolling, more or less now looking to see if the community has suggestions/improvements on what can be done in these aspects. I wrote to all mailing lists for the initial announcement, but you can just reply to sr-users, if you are subscribed there, otherwise it's fine to write back to any of the lists. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 3 months

Re: [SR-Users] Contact and Record-Route are using Private IP Address- is this correct?

by Ammar Tinawi

Is it mandatory to have an interface with public ip in order to overcome NAT problems ?

6 years, 3 months

Issue with Socket selection on Forwarding ACK message

by Thomas Carvello

Hello, i have an issue with my Kamailio 4.1.9 configuration. This configuration is multi-homed, we have*two network* interfaces, one on a private network and on the public Internet. Kamailio is configured to listen on port 5060 and 5066 on both interfaces. We register two users Alice and Bob on the public Internet using port 5066. Both users are behind a NAT and we capture the SIP exchange on the proxy server. We have set the parameter mhomed=1 When Alice calls Bob, we have Alice Proxy Bob src=5063 dst=5066 INVITE ------------------> src=5066 ------ INVITE ---------------> dst=5060 dst=5066 <------- 200 OK -------------- src=5060 dst=5063 <------- 200 OK --------- src=5066 src=5063 dst=5066 -------- ACK -----------> *src=5060 (blocked by NAT)* ------ ACK-----x dst=5060 The ACK packet gets relayed with the wrong source port. Then the NAT rejects the packet and the call cannot be established. For some reason, when Bob calls Alice, the call is correctly established. Could it be because Bob happend to use 5060 as local port? Also, if we set nhomed=0 it works BUT we are not sure that multi homed is handled correctly. I was wondering if you have encounter this issue before? I have investigated the code for selection socket and what is the logic of this selection ? /*How does kamailo knows that it should choose 5066 as src port if the user is registered using port 5066 instead of 5066?* / Thank you for your time. Thomas

6 years, 3 months

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 2018