sr-users

sr-users@lists.kamailio.org

37519 discussions

Addition of a code of conduct to the Kamailio repository
by Henning Westerholt 11 Oct '18

11 Oct '18

Hello, with commit a213d9d1 I introduced a Code of Conduct to the Kamailio repository [1]. This topic was initially discussed during the Kamailio development workshop, started from Daniel. During the development workshop we came to the conclusion that this is a policy decision and needs broader discussion in the Kamailio Management board and also the Kamailio Admin-Team. This discussion started last Friday, and after several days of discussion we decided to choose an existing Code of Conduct. We adapted the CoC of the Debian Project [2] and did a few changes for readability and also to adapt it to the (smaller) scope of our project. This CoC is in my opinion a good, generic and pragmatic document. Many people in our community are already in one way or the other involved in the Debian project. I am aware that this is (especially right now) a hot topic for some people. My personal opinion is that we managed to get a great fit to the existing Kamailio community culture. The history of this project shows that we are an open project and welcome contributions from anybody. So I don't expect any impact because of this change. We also ensured that the CoC only applies inside the Kamailio project, and that the Kamailio Management board is the authoritative instance in any conflicts about this topic. I don't want to start a classical "bike-shedding" discussion on this list about this topic.. But if you have any questions about this, lets us know. You can also contact the Kamailio Management Board, if you want to keep it private. Best regards, Henning Westerholt [1] https://github.com/kamailio/kamailio/blob/master/CODE_OF_CONDUCT.md [2] https://www.debian.org/code_of_conduct

1 0

Websocket configuration for kamailio 5.1.6
by Priyaranjan Nayak 09 Oct '18

09 Oct '18

Hi All, I have compiled the kamailio v5.1.6 source code with tls and websocket module enabled in ubuntu 18.04 LTS. Now I am able to start the kamailio in UDP and TCP port 5060. I wanted to run the kamailio in WS, WSS and TLS port as well. I have generated the private_key, certificate and ca_list and provided the absolute file path in tls.cfg file. I observed tls.so and websocket.so is present in the module path after compile and installation of code. I have used below command to compile and install. 1. make proper 2. make PREFIX="/usr/local/kamailio-5.1" include_modules="db_mysql tls websocket" cfg 3. make all 4. make install I have attached the kamailio.cfg and tls.cfg. Could you please suggest the modification in configuration file to run in WS, WSS and TLS port ? Thanks Priyaranjan

2 1

Kamailio 5.1.6 Debian Package -> SEGFAULT
by Floimair Florian 09 Oct '18

09 Oct '18

Hi! I just upgrade from 5.1.5 to 5.1.6 on my machine and I see Kamailio segfaulting (SIGSEGV). Unfortunately the systemd service is also not restarted in this case. I will generate coredumps and look into the backtrace and provide you with any insights I can gather.

1 0

force_send_socket
by David Villasmil 08 Oct '18

08 Oct '18

Hello all, I'm very rusty when it comes to variables :( There's a part of my config where i load a parameter from usr_preferences to know whether i should append a branch and call him to a fixed IP as well as to their current location. I tried doing this on the REQUEST_ROUTE and append a branch like: # This will check if the TO user is an office user if (avp_db_load("$to", "$avp(office)")) { if ( $avp(gsm)==1 ) { xlog("L_ERR","[REQUEST_ROUTE]: [$rm] callid: $ci from=$fU to=$tU should be ($avp(gsm)) branched - Appending branch\n"); append_branch("sip:$tU@1.2.3.4:5060"); } } And later when the script hits the RELAY, the branch is actually sent, BUT from the *PRIVATE IP.* I tried adding: force_send_socket(67.215.186.219:5060); Right after the "append_branch" to set the socket from where to send, but kamailio is still sending from the private ip. Any ideas? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 11

Kamailio with Asterisk as Media Relay
by Benjamin Marty 08 Oct '18

08 Oct '18

Hello I would like to ask if there is any available informations on how to use Kamailio as a SIP Proxy but letting (multiple) Asterisk Instances do the Media Relaying. Is this scenario supported and if yes are there any tutorials or documentation available for it? I know the Kamailio Dispatcher Module, but this does as far as I know a dispatching of also the SIP Traffic. Not just the Media Traffic.

4 4

set_advertised_address with variable
by Patrick Wakano 08 Oct '18

08 Oct '18

Hello list, Hope you all doing fine! I am using version 5.0.7 and I was trying to use the set_advertised_address with an avp variable but it does not replace with the avp value.... I then find out this thread https://lists.kamailio.org/pipermail/sr-users/2016-March/092327.html, in which is mentioned: *"I expect those functions not to support pvs, but I think this issomething to address in 5.0 and get all core functions working with pvs."* Looks like this was actually not done.... is that correct? Is there any plan to do it? In my case I want to use the set_advertised_address after reading the value from DB, so I can't use the advertised_address or listen options.... Any idea on how I could achieve that? Thank you, Kind regards, Patrick Wakano

3 6

Sending INVITE from loopback subnet
by Joonas Kamailio 08 Oct '18

08 Oct '18

Dear List, I am trying to achieve a scenario where I can recognize the original peer and mask it as peer from subnet 10.0.7.0/24 with kamailio. Basic IP connectivity is established with the following network configuration (Debian9): auto lo:1 iface lo:1 inet static address 10.0.0.0/24 And of course I have routed 10.0.0.0/24 to servers public IP address (hereby known as x.x.x.1) in my router. Please consider the following scenario: - Peer1 192.168.0.1 is sending INVITE to kamailio at IP x.x.x.1 - Kamailio sends INVITE to peer2 at 172.10.0.1 from socket 10.0.0.1 - Peer2 receives the INVITE and knows that since it came from IP 10.0.0.1 it means that INVITE is originally from peer1 - IF peer2 sends INVITE to kamailio, it should be sent to peerX from socket 10.0.0.2 This works if I list both 10.0.0.1 and 10.0.0.2 with 'listen=' parameter but things get out of hand if I have multiple peers. In my tests I have noticed that 60 peers equals 60 listen parameters which equals roughly 500 kamailio processes. At some point there are just too many processes and everything melts. If I omit the listen parameter altogether, kamailio has only one socket from /24 subnet and it is 10.0.0.0. Error message when listen parameter is omitted: [pv_core.c:2612]: pv_set_force_sock(): no socket found to match [10.0.0.1] My kamailio has the following configuration in request_route: $avp(e_private) = $(sht(get_private=>$si)); $fs = $avp(e_private); I know that the case is a bit confusing and totally something normal people won't do. If you have any questions I am happy to answer. Best Regards, Joonas Keskitalo

2 1

Server_id expects number only
by Denys Pozniak 08 Oct '18

08 Oct '18

Hello! I need to separate Kamailio's dmq_usrloc by server_id and will be much easily if server_id can accept string values also, like: server_id="192.168.100.100" But currently it accepts only integer: https://www.kamailio.org/wiki/cookbooks/5.1.x/core#server_id Syslog: 0(11488) CRITICAL: <core> [core/cfg.y:3447]: yyerror_at(): parse error in config file /etc/kamailio/global.cfg, line 126, column 11-24: syntax error 0(11488) CRITICAL: <core> [core/cfg.y:3447]: yyerror_at(): parse error in config file /etc/kamailio/global.cfg, line 126, column 11-24: number expected -- BR, Denys Pozniak

2 4

High number of aborted mysql connections
by Sergiu Pojoga 08 Oct '18

08 Oct '18

Hi all, I'm trying to understand why some Kamailio processes become Connor MacLeod and go to live forever causing high # of aborted connections. While watching in time over *SHOW PROCESSLIST*, some 12 kamailio connections in *SLEEP* state, most of them are reused over time (time value gets reset). However, a select few go on to SLEEP forever for as much as the mysql's *wait_timeout* allows them to. Default was 28800 sec, that's how long they lived. If I lower this to say 600 sec, even higher abort rate is observed. I suppose my questions are: 1. Is this normal to have so many SLEEPing connections? 2. What is the recommended MySQL *wait_timeout* value under Kamailio? 3. Any other suggestions as to why such a high rate of aborted connections? Merci!

2 2

Intercepting local reply attributes
by Alex Balashov 06 Oct '18

06 Oct '18

Hi, I have Kamailio in a weird interop/adaptation layer role with the following call flow: SUBSCRIBE to Kamailio with Expires: 0 ---> <-- immediate 200 OK from Kamailio [some time passes] <-- NOTIFY with additional info from Kamailio 200 OK to Kamailio ---> The NOTIFY follows a series of lengthy async HTTP interrogations, so it's constructed at a later point in time with $uac_req(...). The problem is that the standard which regulates this is extremely eccentric in the following way: despite the immediate expiration of the subscription, the NOTIFY is expected to conform to the format of an in-dialog request as if a dialog existed. Don't ask. It's as idiotic as it sounds. But it's a Broadsoft "standard". I can match the To URI / To-tag by capturing it from the incoming From header on the SUBSCRIBE and reproducing it into the outgoing To header on the NOTIFY. The issue is that my From-tag on the NOTIFY does not match the To-tag on the 200 OK for the SUBSCRIBE. So, from the point of view of the subscriber, the NOTIFY is "From" a different party to the one that "initiated" a "dialog" in response to its subscription. I'm just sending the "200 OK" for the SUBSCRIBE like this: --- append_to_reply("Event: $hdr(Event)\r\n"); append_to_reply("Expires: $hdr(Expires)\r\n"); append_to_reply("Contact: <sip:$sel(cfg_get.domain.sip_domain):$Rp>\r\n"); send_reply("200", "OK"); --- I am not aware of anything like an onsend_route that I can use to gain access to the To header of this reply. Nor am I aware of any means of removing headers from a reply and injecting my own To header with a self-generated To-tag I can later mimic in the From tag of the NOTIFY. Any creative workarounds would be appreciated! -- 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

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