sr-users April 2018

sr-users@lists.kamailio.org

81 participants
103 discussions

Via header force change protocol to TLS?

by Anthony Alba

I have kamailio behind a TLS termination proxy so the sockets are correctly deduced to be TCP. However the clients only talk TLS to the proxy and are confused when the top Via header added by Kamailio is TCP. Is there a way for Kamailio to forcibly pretend its protocol is TLS? Like advertised_address but "advertised_protocol" instead. (With pjsip testing: it has a flag use_tls which ignores TCP from Kamailio and continues to use the persistent TLS transport to proxy. Linphone fails because it tries to honor TCP in Via and is unable to establish TCP transport). BTW I am using t_relay_to_tcp so Kamailio will return traffic to the proxy as TCP even though the contact addresses specify transport=TLS.

5 months, 3 weeks

Re: [SR-Users] t_drop_replies not working with t_suspend in failure route

by Huber Andreas

Hi, We’re still using kamailio 4.4 but we’ll be migrating to 5.0 soon. Cool so it will be fixed when we migrate ! Thanks, Andreas From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Federico Cabiddu Sent: vendredi 12 mai 2017 11:56 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] t_drop_replies not working with t_suspend in failure route Hi, which version are you using? A similar case had been reported some months ago and it should be fixed in 5.0. Regards, Federico On Fri, May 12, 2017 at 11:44 AM, Huber Andreas <andreas.huber(a)nagra.com<mailto:andreas.huber@nagra.com>> wrote: Hello, We have a use case where we suspend a transaction in a failure_route to give UEs that might be woken by a push notification more time to REGISTER and join the INVITE. We’d like to drop the previous branches in this case. I tried using t_drop_replies() but it has no effect. The doc states that t_drop_replies() is only working if a new branch is added. And from my understanding t_suspend() adds a new branch. But is it possible that t_drop_replies() cannot be used with t_suspend()? Or am I missing something? Kind Regards, Andreas _______________________________________________ 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

3 years, 2 months

nat_uac_test(8)

by Sergiu Pojoga

When receiving an INVITE over a specific LTE carrier, I'm seeing 'c=IN IP4 192.0.0.4' in SDP, which isn't technically a RFC1918 or RFC6598 IP address and thus nat_uac_test(8) fails. What elegant workaround can be done to catch such specific cases? Thanks.

4 years, 7 months

need help with RTPProxy in bridged mode

by Grant Bagdasarian

Hello, I'm using RTPproxy for the first time in bridged mode and I can't get kamailio/rtpproxy to rewrite the c parameter to the correct public ip address of kamailio. The setup is as following: Carrier ------[fiber]------ Kamailio ---------[lan]--------- Freeswitch Kamailio is listening on two interfaces: 1) Private: 172.0.0.1 2) Public: 192.168.0.1 (since we have a dedicated fiber with our carrier, this is its public address) Freeswitch is listening on: 1) 172.0.0.2 Carrier is on: 1) 10.0.0.1 I've started an rtpproxy instance on the Kamailio box using: rtpproxy -s udp:127.0.0.1:7721 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.0.1 172.0.0.1 I've played around with rtpproxy_manage() and the various flags (ie, ei), but I can't get kamailio to set the correct public IP when the 200 OK has to be sent back to the carrier. It always sets it to its private address, instead of its public address. I'm using Kamailio 4.2 with sippy/rtpproxy 2.0. Could someone please point me into the right direction? Thanks! Grant

4 years, 7 months

rtpproxy does not response, disable it

by Zodiac

Dear friends, I am working on a program on Kamailio and rtpengine proxy. I am wondering whether can I set Kamailio and rtpengine daemon on different physical machines. For example, I set Kamailio on a machine with IP address:10.109.247.80, and launch rtpengine daemon on another machine with interface parameter as 10.109.247.90 and ng port 7723. I set parameter in Kamailio.cfg with modparam(“rtpengine”, “rtpengine_sock”, “udp:10.109.247.90:7723”). Unfortunately I got debug message like this: ERROR: rtpengine [rtpengine.c:1710]: send_rtpp_command(): can't send command to a RTP proxy ERROR: rtpengine [rtpengine.c:1746]: send_rtpp_command(): proxy <udp:10.109.247.90:7723> does not respond, disable it ERROR: rtpengine [rtpengine.c:1616]: rtpp_test(): proxy did not respond to ping And, I also tried to set Kamailio and rtpengine daemon in a same machine,and use modparam(“rtpengine”, “rtpengine_sock”, “udp:localhost:7723”). And Kamailio can work functionally under this situation. rtpengine daemon can receive ping message from Kamailio and rtpengine daemon can work as suspected. So for the later case, is it supposed that Kamailio be in the same machine with same localhost address? Otherwise, what’s the reason for my ERROR? ------------------------------------ 北京邮电大学网络技术研究院网络与交换技术国家重点实验室田军 +86 18810315790 mozillafire(a)bupt.edu.cn ------------------------------------

4 years, 10 months

RTPengine: shouldn't SDP <sess-version> be incremented when SDP is updated in-dialog?

by George Diamantopoulos

Hello all, I have the following issue (I think) with RTP engine. An INVITE comes in, and rtpengine will rewrite the SDP accordingly, as configured in kamailio.cfg. After some time a reINVITE is sent out in the opposite direction, for session refresh purposes. As I use rtcp-mux-offer in kamailio.cfg for this direction, RTPengine will inject the rtcp-mux parameter, and this reINVITE is forwarded to the UAC that sent the original INVITE. However, the SDP in the reINVITE is exactly the same as the SDP in the 200 OK to the original INVITE, with the exception of the rtcp-mux parameter. Since the SDP offered from the same end has changed, shouldn't session version be incremented as well? Does this sound like something that should be reported as a bug to rtpengine? Or am I missing something here? Thanks! Best regards, George Diamantopoulos

6 years

tcp Free fragment not found

by Diego Nadares

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

6 years, 1 month

Kamctl Stats Update

by Noah Mehl

Hey all, I was wondering if the kamctl stats output could be updated to provide a bit more parseable JSON? For instance: # kamctl stats shmem | jq . { "jsonrpc": "2.0", "result": [ "shmem:fragments = 18", "shmem:free_size = 467187808", "shmem:max_used_size = 69694104", "shmem:real_used_size = 69683104", "shmem:total_size = 536870912", "shmem:used_size = 41048984" ], "id": 4300 } I would hope would be more like this: { "jsonrpc":"2.0", "result":[ { "shmem":[ { "fragments":18, "free_size":467187808, "max_used_size":69694104, "real_used_size":69683104, "total_size":536870912, "used_size":41048984 } ] } ], "id":4300 } I apologize in advanced because I don’t have the skillset to contribute such a feature. Thanks! ~Noah

6 years, 3 months

No cdr after Kamailio 5.0.4 and 5.2 dev restart

by Kordován Szabolcs

Hi All, In March there was a discus about this issue. We tested the new 5.2 dev and 5.0.4 version of Kamailio and we experience that If we restart Kamailio during the call the cdr won't be stored in table acc_cdrs but the data will be inserted to table acc and data will be deleted from table dialog and dialog_vars. Did I omit the fix for it? Thanks for your help. Best regards, Szabolcs

6 years, 3 months

rtpengine installation dependencies

by Aqs Younas

Greetings list. This might not be related to Kamailio but I thought someone would be able to give a hand in resolving dependency during the installation of rtpengine on Debian 8 Jessie. It is complaining about below dependencies. root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg-buildpackage dpkg-buildpackage: source package ngcp-rtpengine dpkg-buildpackage: source version 6.3.0.0+0~mr6.3.0.0 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Sipwise Jenkins Builder < jenkins(a)sipwise.com> dpkg-buildpackage: host architecture amd64 dpkg-source --before-build rtpengine dpkg-source: info: using options from rtpengine/debian/source/options: --extend-diff-ignore=.gitreview dpkg-checkbuilddeps: *Unmet build dependencies: debhelper (>= 10~) libbcg729-dev* dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) I tried to install debhelper from deb but complained from dh-autoreconf and that itself complained abount debhelpler. So, no one is being installed. Also, If someone can help me how to resolve dependency for libbcg729-dev too. Any pointer or hint or link to some installation guide would be more than welcome. Br, Aqs.

6 years, 4 months

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