sr-users

sr-users@lists.kamailio.org

42 participants
37518 discussions

Upstream ignores reply, because To-tag doesn't match?
by Sergiu Pojoga 09 Apr '19

09 Apr '19

Hi ppl, Scenario: invite from upstream is t_relayed to a client gateway. After `fr_inv_timeout` occurs, in a failure route I simply t_reply with "503 - Service unavailable", then exit(). However, the upstream provider simply ignores this reply, call doesn't hang up. This doesn't happen when the client's gateway generates identical 503 or other negative replies. I suspect this is happening because the To-tag in the Kam generated 503 reply doesn't match with the To-tag that previously was forwarded from the client's gateway to the upstream provider in the `180 Ringing`. Any suggestions what can be done about it? 2019/04/06 10:42:46.127177 65.39.xxx.xxx:5060 -> 208.72.xxx.xxx:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP 208.72.xxx.xxx:5060;received=208.72.xxx.xxx;rport=5060;branch=z9hG4bK1982422573 Record-Route: <sip:65.39.xxx.xxx;lr=on;did=915.8af1> From: "SERGIU" <sip:514XXXXXXX@208.72.xxx.xxx>;isup-oli=00;tag=1975755942 To: <sip:514XXXXXXX@65.39.xxx.xxx>;tag=as2ab54180 Call-ID: DID-28270826(a)208.72.xxx.xx CSeq: 477023 INVITE Supported: replaces, timer, path Contact: <sip:1514XXXXXXX@65.39.xxx.xxx:5060> Content-Length: 0 2019/04/06 10:42:51.072516 65.39.xxx.xxx:5060 -> 208.72.xxx.xxx:5060 SIP/2.0 503 Service Unavailable Call-ID: DID-28270826(a)208.72.xxx.xx Via: SIP/2.0/UDP 208.72.xxx.xxx:5060;rport=5060;branch=z9hG4bK1982422573;received=208.72.xxx.xxx From: "SERGIU" <sip:514XXXXXXX@208.72.xxx.xxx>;isup-oli=00;tag=1975755942 To: <sip:514XXXXXXX@65.39.xxx.xxx>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-8e82 CSeq: 477023 INVITE Server: KAM Content-Length: 0 Thanks, --Sergiu

3 8

modifying via header from public IP to private IP
by Narasimhaiah, Vinod Maralenahalli 09 Apr '19

09 Apr '19

Hi , I have a cloud server, when I make call from a sip phone (registered with kamailio), in the INVITE header I am seeing the via header with public IP, is there any way that I can modify via header to send only the private IP. The calls are landing on another sip gateway, they will allow only the private IP. Please let me know, is it possible to replace. I tried all the replace functions but it is not working. Thank you vinod.M.N -- ***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.***

1 0

modifying via header from public IP to private IP
by vinod mn 08 Apr '19

08 Apr '19

3 2

How to Register sip trunk in kamailio without username and password?
by Mostafa Moradi 08 Apr '19

08 Apr '19

Hi, I'm mostafa moradi from iran, I Have installed kamailio, and I have a sip trunk without username and password, I want to register the sip trunk in kamailio with UAC Module, but this module only accepts sip trunk with user and password, How Can I Register sip trunk in kamailio without username and password? Thank you in advance Best regards,

4 3

Re: [SR-Users] Timeout between 100 & 183
by Alex Balashov 05 Apr '19

05 Apr '19

On Fri, Apr 05, 2019 at 06:23:16PM -0400, Alex Balashov wrote: > route { > ... > > # Initial INVITE handling: > > if(is_method("INVITE")) { > # Set fr_inv_timer initially to 5 seconds, so that > # if we do not receive an answer or at least one non-100 1xx > # response, trigger a failure_route and try the next gateway > # or whatever. > > t_set_fr(50000); Sorry, this would have been a lot more pedagogically useful if it had read: t_set_fr(5000); -- 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/

1 0

UAC authentication challenge response using KEMI/app_ruby
by Andrew White 05 Apr '19

05 Apr '19

Hi all, I’m continuing on my quest to use app_ruby for my logic - it’s working very well so far! The last major hurdle I’ve come across is UAC response to WWW challenge. On my outbound path, the correct URIs for From and To are set based on provider requirements, and the INVITE is sent using t_relay(): def ksr_route_to_trunk() KSR.info("Route to trunk") if KSR::TM.t_is_set("failure_route") < 0 then KSR::TM.t_on_failure("ksr_failure_manage_trunk") end # Relay KSR::PV.sets("$fu", "sip:#{$uacs[trunk]['r_username']}@#{$uacs[trunk]['r_domain']}") KSR::PV.sets("$fn", '') new_uri = "sip:61400123123@#{uacs[trunk]['r_domain']}" KSR.info("New URI is #{new_uri}") KSR.seturi(uri) KSR::UAC.uac_replace_to('', uri) KSR::TM.t_relay() exit end I’ve stripped it back, but this function is great and works perfectly. An INVITE is sent to the correct place, and the trunk receives the INVITE. It then responds with a 401/WWW-Authenticate. My failure route is called fine. Below is the stripped down code: def ksr_failure_manage_trunk() exit if KSR::TM.t_is_canceled() > 0 KSR.info("Hit trunk failure manage route") KSR::PV.sets("$avp(auser)", 'user') KSR::PV.sets("$avp(apass)", 'pass') KSR::PV.sets("$avp(arealm)", 'test.local') KSR.info("AVPs: #{KSR::PV.gete("$avp(auser)")} #{KSR::PV.gete("$avp(apass)")} #{KSR::PV.gete("$avp(arealm)")}") if KSR::UAC.uac_auth() then KSR.info("UAC authed, relaying") KSR::TM.t_relay() else KSR.info("UAC NOT authed, no relay") end exit end Also the AVP values are set (I believe) correctly: modparam("uac", "auth_username_avp", "$avp(auser)") modparam("uac", "auth_password_avp", "$avp(apass)") modparam("uac", "auth_realm_avp", "$avp(arealm)") This throws the following complaint, and doesn’t send a new response back to the trunk: Apr 5 02:55:22 ip-10-0-0-2 /usr/local/sbin/kamailio[26870]: ERROR: {1 102 INVITE 3a84da15272da66e527a79144c48516c@10.0.0.20:5060} tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding Apr 5 02:55:22 ip-10-0-0-2 /usr/local/sbin/kamailio[26870]: ERROR: {1 102 INVITE 3a84da15272da66e527a79144c48516c@10.0.0.20:5060} tm [tm.c:1619]: _w_t_relay_to(): t_forward_noack failed I don’t understand branches very well, however after some digging around, I appended KSR::COREX.append_branch() in before the t_relay() in the failure. This stops the error and now we send an ACK and a new INVITE, but still without the expected authorisation header. I feel like my lack of understanding about branches is the issue here - I seem to be sending an INVITE, but not adding the auth header that I suspect is being generated somewhere! Thanks for your help. ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 2

Statistics of received replies
by Duarte Rocha 04 Apr '19

04 Apr '19

Greetings, Does Kamailio have statistics like the sl.stats but for received replies instead of locally generated ones? I want to be able to look at how many "491" replies i'm receiving, for example. Best Regards, Duarte Rocha

2 1

Kamailio v5.0.8 Released
by Daniel-Constantin Mierla 04 Apr '19

04 Apr '19

Hello, Kamailio SIP Server v5.0.8 stable release is out. This is a maintenance release of the old stable branch 5.0, that includes fixes since the release of v5.0.7. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.0.x. Deployments running previous v5.0.x versions are strongly recommended to be upgraded to v5.0.8 or even better directly to v5.1.x or v5.2.x because v5.0.x is getting out of the official maintenance time frame. Important note: this is the last planned release from branch5.0. For more details about version 5.0.8 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/04/kamailio-v5-0-8-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the latest stable branch is 5.2, at this moment with its latest release v5.2.2. See more details about it at: * https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/ 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 Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com

1 0

Kamailio-error reading: Connection reset by peer
by Mangesh Kharade 04 Apr '19

04 Apr '19

Hi Team, We are facing issue with kamailio application , we are not able to communicate to kamailio application getting below error. Can you please suggestion us how to resolved this issue issue, it production servers and we did not get any clue to resolve it. Error1:- Apr 2 06:53:54 urcmcs /usr/local/sbin/kamailio[2240]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:53:54 urcmcs /usr/local/sbin/kamailio[2240]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Apr 2 06:54:12 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:54:12 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Apr 2 06:54:17 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:54:17 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Error1:- Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3008 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3009 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3010 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3011 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3012 has closed Please let us know if you need more help from our end. Thanks and Regards, Mangesh Kharade Consultant - Microsoft Azure | Managed Services [cid:image003.png@01D15FFB.27B1AA80] Pune IT Park, 34 Aundh Road Bhau Patil Marg, Pune 411020 Tel: +91.20.30204000 | Extn. 9694 VOIP: +1.713.353.7464 Mobile: +91.9168181166 Mangesh.kharade(a)silicus.com<mailto:Mangesh.kharade@silicus.com>| www.silicus.com<http://www.silicus.com/> The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

2 2

Releasing Kamailio v5.0.8
by Daniel-Constantin Mierla 04 Apr '19

04 Apr '19

Hello, I am considering to release v5.0.8 to mark the end of official maintenance for branch 5.0 on Thursday, April 4. If no major regression will be introduced, this will be the last release from branch 5.0. Afterwards, the stable branches maintained will be 5.1 and 5.2. In case you have in mind some specific commits that should get into 5.0 branch, then reply and list them to be sure they are not missed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com

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