sr-users September 2018

sr-users@lists.kamailio.org

72 participants
123 discussions

USRLOC db_mode=4 and server_id
by Darren Williams 31 Oct '18

31 Oct '18

I am currently using multiple instances of Kamailio with a common database and using the usrloc module with db_mode=4 and server_id to filter the contacts that get loaded at startup on each server. The problem I seem to have is that using the RPC call ul.add, I cannot see any parameter to send to specify the server_id. The server_id that the contact is given is 0. If I manually go into the db and modify the server_id everything works as expected. I think I must be missing something somewhere as I'm sure you shouldn't need to do this. Can anyone help please. Thanks Daz

3 2

Http_async_client stops script execution
by Denys Pozniak 18 Oct '18

18 Oct '18

Hello! Please help me to understand how http_async_client module behaves. I am going to use it for call routing according to the http response. if (is_method("INVITE")) { t_newtran(); xlog("L_ERR", "ASYNC0-$fU-$rU-$rm---- \n"); http_set_timeout(1000); http_set_method("POST"); http_append_header("Content-Type: application/json"); http_async_query("http://10.10.10.10:8080/RPC", "{\"jsonrpc\": \"2.0\", \"method\": \"ul.lookup\", \"params\": [\"location\",\"user\"], \"id\": 1}", "HTTP_REPLY"); xlog("L_ERR", "ASYNC1-$fU-$rU-$rm---- \n"); } route[HTTP_REPLY] { xlog("L_ERR", "HTTP_REPLY: ok $http_ok \n"); xlog("L_ERR", "HTTP_REPLY: status $http_rs\n"); xlog("L_ERR", "HTTP_REPLY: body $http_rb\n"); xlog("L_ERR", "HTTP_REPLY: error $http_err)\n"); } In syslog I see HTTP_REPLY log strings with correct response, but do not see ASYNC1 string and script execution stops. What's wrong with this? # kamailio -v version: kamailio 4.4.2 (x86_64/linux) 892ad6 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 892ad6 compiled on 12:58:38 Aug 28 2017 with gcc 4.8.5 -- BR, Denys Pozniak

2 8

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

kamailio + rtpproxy behind NAT
by Bonjour Madame 05 Oct '18

05 Oct '18

Hello, I have kamailio and rtpproxy running on the same server located behind a router with NAT just like below. UA(internet)---public ip---router(NAT)--Kamailio+RTPproxy(private ip)--UA(private network) There are several issues like one way audio. I need users on the internet to communicate with each other, users on the private network to communicate with each other, and users on the internet and the private network to communicate with each other. What is the best approach? Best regards, Clarence

3 5

Roadmap to next major release - v5.2.0
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, as it was discussed during our last IRC devel meeting before the summer, the time to release a new major version should be this autumn. With the Kamailio Developers Meeting planned for September 27-28, 2018, I think it is better to freeze the code couple of days after that event. So I propose the following milestones: * on Thursday, October 4, 2018 - last development day, code for 5.2.0 will be frozen at the end of the day * 4 to 6 weeks of testing * release sometime in November, to be decided more precisely after the first weeks of testing, some rough candidates being within the weeks of Nov 5 or Nov 19 If anyone has something to add or adjust, let's discuss on sr-users mailing list. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

2 3

Planing the release of Kamailio v5.1.6
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, a matter of the schedule to be agreed in the morning and the availability during the Kamailio Developers Meeting, we may do a new stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the afternoon. Given that several of us will be in the same room, the special goal would be to try to automate the process as much as possible. If the time doesn't allow it, then the release will be done next week, a specific day to be decided by the end of this week. Anyhow, this is the informal notification to report as soon as possible any issues you are aware of and not yet in bug tracker, so they get a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

2 4

tcp Free fragment not found
by Diego Nadares 04 Oct '18

04 Oct '18

Hi guys! We have four a scripts that sends dlg.list command to kamailio through xmlrpc. They are not executed simultaneously. Sometimes, we are getting the following errors: fm_search_defrag(): fm_search_defrag(0x7f212c25a000, 5273984); Free fragment not found!2017-05-26T13:54:20.438736-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [mem/f_malloc.c:498]: fm_malloc(): fm_malloc(0x7f212c25a000, 5273984) called from core: tcp_main.c: tcpconn_new(957), module: core; Free fragment not found!2017-05-26T13:54:20.439101-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:959]: tcpconn_new(): mem. allocation failure2017-05-26T13:54:20.439344-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:3985]: handle_new_connect(): tcpconn_new failed, closing socket I all ready increased this two variables: tcp_conn_wq_max=30000000 tcp_rd_buf_size=5273226 How can I see how much memory xmlrpc is using? Any advice will be appreciated. Thanks in advance! Diego

2 2

Freeing already Freed pointer
by Hamid Hashmi 04 Oct '18

04 Oct '18

I have been receiving CRITICAL core logs since I have updated my service to the following version. Print out of kamailio internals Version: kamailio 5.1.5 (x86_64/linux) d06080 Default config: /usr/local/SIPSer/etc/kamailio/kamailio.cfg Default paths to modules: /usr/local/SIPSer/lib64/kamailio/modules Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE=262144 MAX_URI_SIZE=1024 BUF_SIZE=65535 DEFAULT PKG_SIZE=8MB DEFAULT SHM_SIZE=64MB ADAPTIVE_WAIT_LOOPS=1024 TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select Source code revision ID: d06080 Compiled with: gcc 4.8.5 Compiled on: 14:17:56 Sep 13 2018 Thank you for flying kamailio! I have been starting kamailio with the following command $ /usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid -f /usr/local/etc/kamailio/kamailio.cfg -m 1024 -M 512 Sample Critical Logs are below Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 923000000001 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL: <core> [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer (0x7f30c8a4df30), called from tm: t_reply.c: relay_reply(1920), first free tm: h_table.c: free_cell_helper(155) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 923000000001 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL: <core> [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer (0x7f30c8a4cc40), called from tm: h_table.c: free_cell_helper(153), first free tm: h_table.c: free_cell_helper(153) - aborting Its also causing service crash. Complete logs are here<https://paste.ee/p/q65DE>. Regards Hamid R. Hashmi

2 2

What is the typical network setup for kamailio?
by Kevin Olbrich 03 Oct '18

03 Oct '18

Hi! I am working successfully with Kamailio in my lab setup where Kamailio is the SBC for Asterisk. The network layout is looking like this: SIP-Phone <== PUBLIC NET ==> Kamailio (SBC) <== PRIVATE NET ==> Asterisk <== PUBLIC NET ==> Carrier Each public network is reachable from the internet and has a local firewall with IP whitelists. The internal SIP transactions are UDP-only but for external phones I would like to also listen for TCP/TLS. For this layout to work with rtpproxy (before we move on to RTPengine), we have to enable mhomed in Kamailio. We also have some routing issues with packets leaving with the wrong IP via rtpproxy (when call between carrier and external phone needs to be bridged). Most examples show that Asterisk is deployed on the same network as the external interface of Kamailio (-> Asterisk exposed to the public network). In our tests, this works much better but I have great security concerns because this Asterisk instance itself does not need to be reachable from external. How do other users deploy Kamailio in front of Asterisk or similar as SBC to secure internals? There is lot of docs for Kamailio's config but IMHO less for the setup as DMZ (SBC) proxy. Thank you very much. Kind regards Kevin

7 15

rr module not detecting nat=ws route param
by Jon Bonilla (Manwe) 02 Oct '18

02 Oct '18

Hi all. I'm having problems with an indialog ACK request which is not being routed correctly. I call loose_route and print: $du=sip:MYIP:2443;transport=ws;r2=on;lr=on;did=1d1.7702;nat=ws $route_uri=sip:MYIP;r2=on;lr=on;did=1d1.7702;nat=ws But when I call check_route_param("nat=ws") I get false result. version: kamailio 5.1.4 any hints? cheers, Jon -- https://pekepbx.com https://www.issabel.com/multitenant

3 6

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