sr-users October 2018

sr-users@lists.kamailio.org

81 participants
121 discussions

Kamailio as TCP UDP proxy
by M K 05 Oct '18

05 Oct '18

Hi, I'm struggling with the configuration to use Kamailio as TCP UDP proxy: [SIP Client] <-(TCP)-> [Proxy] <-(UDP)-> [SIP Server] should be the setup. I only have one client and one SIP server. How do I get Kamailio configured as a proxy so that translation between TCP and UDP works (and vice versa)? I have not yet found any documentation and examples that have caused messages to arrive at my SIP server. I think I've been on the wrong track so far and I'm looking forward to any help. Thank you in advance, Laqoore

3 2

Development for Kamailio v5.2 series is frozen
by Daniel-Constantin Mierla 05 Oct '18

05 Oct '18

Hello, short note to mark the freezing of development for Kamailio v5.2 series. For few weeks, please do not push new features in the master branch. Once the branch 5.2 is created (expected to happen in 3-4 weeks from now), the master branch becomes again open for new feature. Meanwhile the focus has to be on testing current code. Work on related tools (e.g., kamctl) or documentation can still be done as well as getting the new modules in 5.2 in good shape, plus adding exports to kemi interface (which should not interfere with old code). The entire testing phase is expected to be 4 to 6 weeks, then the release of v5.2.0 will be out. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

PATH when used with multiple listening ports
by Sergiu Pojoga 04 Oct '18

04 Oct '18

Hi again, When acting as an intermediary proxy for a non-colocated Registrar, the REGISTER request coming in on one port and going out on another, shouldn't the *add_path[received]()* generate *two* nodes in the Path header? Otherwise, how are the subsequent requests supposed to be routed back to the UAC? Scenario with Kamailio proxy on IP 1.1.1.1 with dual port listeners UAC => proxy:5070 <=> proxy:5060 => Registrar:5060 Path: <sip:1.1.1.1;lr;received=sip:123.123.123.123:59593> I would expect it to be something like: Path: <sip:1.1.1.1;lr>,<sip:1.1.1.1:5070;lr;received=sip: 123.123.123.123:59593> modparam("rr", "enable_double_rr", 1) modparam("path", "use_received", 1) Merci!

2 2

Kamailio in a mobile world - ts_append issue
by Dan Quinney 04 Oct '18

04 Oct '18

Using "Kamailio in a mobile world" as a base, I have the following routes to store information about the current transaction, however, if the transaction is already cancelled registrations for the user will still trigger `ts_append`, raising an error as the htable hasn't expired yet. Is there anyway to remove the htable entry when the original transaction cancels? Or something else that I'm missing?

2 1

Kamailio v5.1.6 Released
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, Kamailio SIP Server v5.1.6 stable release is out. This is a maintenance release of the latest stable branch, 5.1, that includes fixes since the release of v5.1.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.6. For more details about version 5.1.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2018/10/kamailio-v5-1-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

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

is_first_hop() fails to detect 'myself' when using advertise
by Sergiu Pojoga 04 Oct '18

04 Oct '18

Hi ppl, If I add a FQDN advertise address to the listen statement, *is_first_hop() <https://kamailio.org/docs/modules/4.3.x/modules/siputils.html#siputils.f.is…>* seems to return FALSE no matter how I play with the listen and alias settings. listen=udp:1.1.1.1:5060 advertise sip.mydomain.net:5060 alias="sip.mydomain.net:5060" This statement doesn't get executed in the *onreply_route* *onreply_route[MANAGE_REPLY] {* *if(is_first_hop())* *set_contact_alias(); # contact alias doesn't get set?* *}* *is_first_hop()* *"The function returns true if the proxy is first hop after the original sender. For incoming SIP replies, it means that top Record-Route URI is 'myself' and source address is not matching it"* *This is the reply.* 2018/10/03 17:03:38.276846 2.2.2.2:62033 -> 1.1.1.1:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP sip.mydomain.net:5060 ;branch=z9hG4bK49b3.bfbe15.0;received=1.1.1.1 Via: SIP/2.0/UDP 10.10.10.10:5060;rport=5060;branch=z9hG4bK1af96136 *Record-Route*: <sip:sip.mydomain.net;lr=on;did=4cc.734> Contact: <sip:888@10.17.0.35:62033> Suggestions? Thanks.

3 2

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