sr-users June 2018

sr-users@lists.kamailio.org

88 participants
122 discussions

kamailio rabbitmq segfault
by Sylvain Boily 10 Jan '19

10 Jan '19

Hello, I tried to test the rabbitmq module in kamailio with the debian 9 repo from kamailio.org but there is a segfault when the service is launched. Is there is people also have this issue? /etc/init.d/kamailio restart [....] Restarting kamailio (via systemctl): kamailio.serviceJun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.y:1659]: yyparse(): loading module rabbitmq.so Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/sr_module.c:575]: load_module(): trying to load </usr/lib/x86_64-linux-gnu/kamailio/modules/rabbitmq.so> Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/kemi.c:1295]: sr_kemi_modules_add(): adding module: rabbitmq Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.lex:1737]: pp_define(): defining id: MOD_rabbitmq Jun 9 13:02:03 siprouter kernel: [159315.610811] kamailio[13226]: segfault at 7f03b2296287 ip 00007f03b2080ca3 sp 00007fff133285c0 error 7 in librabbitmq.so.4.2.0[7f03b2074000+13000] Jun 9 13:02:03 siprouter /usr/sbin/kamailio[13226]: DEBUG: <core> [core/sr_module.c:988]: init_mod(): rabbitmq Sylvain

4 6

RTPengine: shouldn't SDP <sess-version> be incremented when SDP is updated in-dialog?
by George Diamantopoulos 20 Nov '18

20 Nov '18

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

3 4

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

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

Kamctl Stats Update
by Noah Mehl 07 Aug '18

07 Aug '18

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

5 8

DMQ problems
by Aleksandar Sosic 05 Aug '18

05 Aug '18

Hi, I've set up a dmq server for other kamailio nodes with this parameters: ``` modparam("dmq", "server_address","sip:10.0.0.101:5060") modparam("dmq", "notification_address", "sip:127.0.0.1:5060") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) modparam("dmq", "ping_interval", 15) ``` On the kamailio nodes the config is the following: ``` modparam("dmq", "server_address", "sip:10.0.0.x:5060") modparam("dmq", "notification_address", "sip:10.0.0.101:5060") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) modparam("dmq", "ping_interval", 15) ``` On the kamailio dmq server I've got this in the logs: ``` 25(41) ERROR: dmq [notification_peer.c:596]: notification_resp_callback_f(): deleting server sip:127.0.0.1:5060 because of failed request 25(41) ERROR: dmq [notification_peer.c:599]: notification_resp_callback_f(): not deleting notification_peer ``` On the kamailio nodes the same thing with the ip of the dmq server: ``` 25(112) ERROR: dmq [notification_peer.c:596]: notification_resp_callback_f(): deleting server sip:10.0.0.101:5060 because of failed request 25(112) ERROR: dmq [notification_peer.c:599]: notification_resp_callback_f(): not deleting notification_peer ``` The request route on the dmq server is simple as this: ``` request_route { if(is_method("KDMQ")){ dmq_handle_message(); } }#end request_route ``` I've tried with some xlog-s inside the if(is_method("KDMQ")) but they don't show up so the dmq_handle_message() is not even executed. I've also tried to bind the dmq server to a different port but with no success on making it work. The dmq.list_nodes shows only the dmq server IP and the current node IP, the IPs of other nodes are not shown: ``` root@proxy-94b6ccf46-t8fx2:/# kamcmd dmq.list_nodes { host: 10.0.0.101 port: 5060 resolved_ip: 10.0.0.101 status: active last_notification: 0 local: 0 } { host: 10.0.0.45 port: 5060 resolved_ip: 10.0.0.45 status: active last_notification: 0 local: 1 } ``` And it's the same on all other kamailio nodes: dmq server ip and local ip. The kamailio version on all the nodes is: 5.2.0~dev6+0~20180616010152.1138+xenial Thanks, -- Aleksandar Sosic mail: alex.sosic(a)evosip.cloud

4 20

No cdr after Kamailio 5.0.4 and 5.2 dev restart
by Kordován Szabolcs 27 Jul '18

27 Jul '18

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

2 3

TLS CRL configuration
by Amarnath Kanchivanam 10 Jul '18

10 Jul '18

Hi All, I'm trying to configured kamailio as TLS server with below configuration (tls.cfg) and TLS server is started successfully. [server:default] method = TLSv1+ verify_certificate = yes require_certificate = yes private_key = ./sip/server.key certificate = ./sip/server.crt ca_list = ./bundle.crt crl = ./sip_crl.pem verify_depth = 9 [client:default] verify_certificate = no require_certificate = no TLS connection works fine. Later i have updated the sip_crl.pem with server certificate revoked details and performed tls.reload command to load the latest update. After this I expect any TLS client trying to establish TLS connection should fail, as the client and server certificates are signed by same authority and server certificate is revoked. But the clients are able to establish TLS connection without any errors. I'm not getting any traces to confirm CRL validation has been performed before accepting the TLS connection. Any advice would be help to proceed with evaluating CRL functionality. -Amar

3 5

ul.add | path & socket not correctly set
by Laurent Schweizer 09 Jul '18

09 Jul '18

Dear all, I have kamailio 5.0.6 and I have an issue to add permanent location When I add a location with : kamcmd ul.add location_ch demo(a)peoplefone.ch sip: demo@95.128.80.122:5060 0 0.0 . 0 128 6111 . udp:95.128.80.3:5060 then I get the following insertion: kamcmd ul.lookup location_ch demo@ { AoR: demo Contacts: { Contact: { Address: sip:demo@95.128.80.122:5060 Expires: permanent Q: 0.000000 Call-ID: dfjrewr12386fd6-343(a)kamailio.mi CSeq: 1 User-Agent: SIP Router MI Server Received: [not set] Path: . State: CS_SYNC Flags: 0 CFlags: 128 Socket: [not set] Methods: 6111 Ruid: ulcx-5b243cb5-67c6-31 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: 0 Keepalive: 0 Last-Keepalive: 0 Last-Modified: 0 } } As you can see the Path value is set to "." But it must be set to [not set] The Socket is also not set. Any idea ? BR Laurent

2 3

rtpengine installation dependencies
by Aqs Younas 05 Jul '18

05 Jul '18

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.

9 17

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 2018