sr-users June 2019

sr-users@lists.kamailio.org

63 participants
96 discussions

dialog:end event route
by Igor Olhovskiy 13 Jun '19

13 Jun '19

Hi! Just to confirm, is event route [dialog:end] not called on fr_inv_timer expiry? Cause it's called on call busy (486) and reject (whatever 6xx). So, what's the idea of not calling it on timeout? Or I'm missing something? Kamailio 5.2 Thanks! Regards, Igor.

2 8

Best practises for websocket authentication
by Grant Bagdasarian 12 Jun '19

12 Jun '19

Hello, I was wondering if there are any best practices for authenticating websocket connection establishment inside the xhttp event route? Thanks and regards, Grant

3 3

TCP reset behavior
by R, Rajkumar (Raj) 12 Jun '19

12 Jun '19

Hi All, In our setup running kamailio (alpine image) in stateless mode and have following TCP config set. After client registers to the backend see two TCP connections created - one towards the client and the other towards the backendserver. If there's a abrupt network disconnect either at the client side or at the backend side, do not see TCP reset happening from kamailio as per the config. Per below config expected after 120seconds( = [tcp_keepidle] + ( [tcp_keepintvl * tcp_keepcnt] ) instead it keeps resending TCP keepalive packets at varying intervals for varying duration length(like 6mins, 14mins..) before resetting the TCP connections. Also want to mention that we are not using TCPOPS module here. I am trying to achieve consistent duration for TCP reset in kamailio. Could you please point me if I have missed anything here? Setup: Client ---- Kamailio (stateless mode) ---- Backend server TCP Config: tcp_connection_lifetime = 3600 tcp_accept_aliases = no tcp_async = yes tcp_connect_timeout = 10 tcp_crlf_ping = yes tcp_keepalive = yes tcp_keepcnt = 3 tcp_keepidle = 30 tcp_keepintvl = 30 # Total 2 mins - 30+(30*3)=120 sec tcp_linger2 = 30 tcp_rd_buf_size = 65536 tcp_send_timeout = 10 thanks, raj

2 9

Setting the probing state failed
by Daniel Greenwald 12 Jun '19

12 Jun '19

ERROR: dispatcher [dispatch.c:2635]: ds_options_callback() Setting the probing state failed (sip:10.0.9.133:5064, group 0) I get this message periodically from 3 kamailio dispatchers simultaneously for the same destination host. Any idea what this error means? Dispatcher settings below: modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(dsdst)") modparam("dispatcher", "grp_avp", "$avp(dsgrp)") modparam("dispatcher", "cnt_avp", "$avp(dscnt)") modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "sock_avp", "$avp(dssocket)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") modparam("dispatcher", "ds_hash_size", 3) modparam("dispatcher", "force_dst", 1) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_from", "sip:pinger@MYPRIVATEIP :INTERNALPORT") #modparam("dispatcher", "ds_ping_method", "INFO") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 1) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=480;code=404")

2 1

How reply INVITE request with 200 OK that contains SDP?
by Ali Shirvani 11 Jun '19

11 Jun '19

Hi all, I tried to implement simple announcer by using play_media function in latest rtpengine module. I implemented simple Lua script and I tried to test the implementation with simple SIPp scenario. Here is the Lua function to reply the received INVITE request. ```Lua function ksr_route_announcer() KSR.info("======= Announcer =====\n"); local u = KSR.pv.gete("$rU"); KSR.info("username is: " .. u .. "\n"); if u == "ann" then KSR.info("announcer has been called.\n"); if KSR.textops.has_body_type("application/sdp") then KSR.info("request contains SDP.\n"); KSR.tm.t_newtran(); KSR.rtpengine.rtpengine_manage0(); KSR.tm.t_reply(200, "OK"); KSR.x.exit(); end end end ``` According to kamailio logs rtpengine modified the INVITE SDP, but I want to add SDP to 200 OK response. How should I manage rtpengine to append SDP answer to the 200 OK response? The attached is the SIPp log, as you can see that last 200 OK doesn't contain SDP. Regards, Ali

2 1

Re: [SR-Users] [EXT] Re: Kamailio 5.2.2 ICSCF changing sip to tel
by Woscek, Martin W. 11 Jun '19

11 Jun '19

Daniel, Actually, the HSS is not returning the uri with the +. There are no users int the HSS database with a public ID with a + so the HSS returns the USER_UNKNOWN. Looking at the PCAP, the I-CSCF sends a diameter msg to the HSS asking for the verification the public ID of: Public-Identity: sip:+alice@ims522.irisims.org The diameter msg from HSS is returning : AVP: Experimental-Result-Code(298) l=12 f=-M- val=DIAMETER_ERROR_USER_UNKNOWN (5001) Why do we want the I-CSCF to add a + to all URI's don't start with a +? The I-CSCF is the module that is adding the +, assuming that we should be able to included Kamailio.cfg for respective modules, is there a directive or variable that I need to set? Or do I simply comment out that code? Thanks, Martin Woscek The MITRE Corp. mwoscek(a)mitre.org<mailto:mwoscek@mitre.org> Phone: 703-983-2650 FAX: 703-983-7142 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Sent: Tuesday, June 11, 2019 6:22 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>; Woscek, Martin W. <mwoscek(a)mitre.org> Subject: [EXT] Re: [SR-Users] Kamailio 5.2.2 ICSCF changing sip to tel Hello, that prefix operation is done only if the r-uri username does not have +. So if you HSS is returning the r-uri with +, then all is ok, no other + is added. On the other hand, I am not sure what is the error or the issue you try to sort out. The error message is because of the xlog(...) in the config. Cheers, Daniel On 10.06.19 16:17, Woscek, Martin W. wrote: Hello all, The HSS is responding with 604 errors when the I-CSCF checks the public identity of the caller. PCAP attached. It looks like our I-CSCF is modifying the sip uri's to tel uri's (e.164-like), referenced attached PCAP: in_uri=sip:alice@ims522.irisims.org out_uri=sip:+alice@ims522.irisims.org<mailto:alice@ims522.irisims.org> syslog output: Jun 6 16:50:06 imskamailio /usr/local/sbin/kamailio[14066]: ERROR: <script>: $ru => sip:+alice@irisims.org Looking at the default (out of the box) Kamailio.cfg for I-CSCF the following script snipet is where the modification to our sip URI is happening: # ------------------------- request routing logic ------------------- # main routing logic route{ #!ifdef WITH_DEBUG xlog("I-CSCF >>>>>>>>>>>>>>>>>>>> $rm $ru ($fu => $tu ($si:$sp) to $tu, $ci)\n"); #!endif if !($rU =~ "\+.*") { prefix("+"); } Is there a I-CSCF setting directive we missed? Or should we simply comment the above? Any advice is appreciated. Thanks, Martin Woscek _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

2 1

Relay NAP Probing
by Duarte Rocha 11 Jun '19

11 Jun '19

Greetings, I have a Kamailio as Sip Proxy between my clients and my Media gateway. I have NAPs (One per client) for clients and NAPs for the MediaGateway (One for each client). The MediaGateway probes Kamailio in order to see if it's alive and Kamailio probes clients. However, i would like for the MediaGateway to be aware of the client status. I thought of a few solutions : - When Kamailio probes a client and it fails, both NAPs (Client Side and MG side) could be set as inactive. - Automatically relay the MG probe to the client - Some scripting that reads the result of dispatcher.list and if it finds an inactive NAP, set the MG NAP as inactive too. Is there a better/simpler way to do this? I'd rather have everything on Kamailio configuration files instead of doing exatra scripting. Any opinions ? How can i achieve this? Best Regards, Duarte Rocha

2 1

Kamailio 5.2.2 ICSCF changing sip to tel
by Woscek, Martin W. 11 Jun '19

11 Jun '19

Hello all, The HSS is responding with 604 errors when the I-CSCF checks the public identity of the caller. PCAP attached. It looks like our I-CSCF is modifying the sip uri's to tel uri's (e.164-like), referenced attached PCAP: in_uri=sip:alice@ims522.irisims.org out_uri=sip:+alice@ims522.irisims.org syslog output: Jun 6 16:50:06 imskamailio /usr/local/sbin/kamailio[14066]: ERROR: <script>: $ru => sip:+alice@irisims.org Looking at the default (out of the box) Kamailio.cfg for I-CSCF the following script snipet is where the modification to our sip URI is happening: # ------------------------- request routing logic ------------------- # main routing logic route{ #!ifdef WITH_DEBUG xlog("I-CSCF >>>>>>>>>>>>>>>>>>>> $rm $ru ($fu => $tu ($si:$sp) to $tu, $ci)\n"); #!endif if !($rU =~ "\+.*") { prefix("+"); } Is there a I-CSCF setting directive we missed? Or should we simply comment the above? Any advice is appreciated. Thanks, Martin Woscek

2 1

Operations after relay
by Nicolas Breuer 11 Jun '19

11 Jun '19

Hello, I want to do some sql operations after a 200 reply, after relaying the sip packet Is it possible or sending the sip packet is the last operation permitted ?

3 3

Connect SIP Trunk to PBX
by Chad Kenealy 10 Jun '19

10 Jun '19

Hello, I hope you can help, We are trying to connect our SIP trunk to our new PBX system, however our SIP trunk provider requires a static IP to add to the endpoint. Our new PBX provider uses a range of IPs that are connected to a domain and the IPs change all the time. Is there a way of using Kamailio that we could get our Sip Trunk provider and PBX system to work together? Regards

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

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 June 2019