sr-users June 2018

sr-users@lists.kamailio.org

88 participants
119 discussions

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

RTPEngine Recording does not work
by Mojtaba 05 Jul '18

05 Jul '18

Hi all, I installed RTPEngine (Version: 6.4.0.0+0~mr6.4.0.0 git-master-4eb80da) in my VM machine (Debian GNU/Linux 8 (jessie), i also installed kamailio 5.1. In kamailio routes, i have: route { ... #rtpengine_manage("record-call") rtpengine_manage(); start_recording(); ... } Here is all other configuration files: In /etc/default/ngcp-rtpengine-daemon file: RUN_RTPENGINE=yes CONFIG_FILE=/etc/rtpengine/rtpengine.conf CONFIG_SECTION=rtpengine PIDFILE=/var/run/ngcp-rtpengine-daemon.pid MANAGE_IPTABLES=yes TABLE=0 In /etc/default/ngcp-rtpengine-recording-daemon file: RUN_RTPENGINE_RECORDING=yes CONFIG_FILE=/etc/rtpengine/rtpengine-recording.conf CONFIG_SECTION=rtpengine-recording PIDFILE=/var/run/ngcp-rtpengine-recording-daemon.pid MUST_NFS=no NFS_HOST=192.168.1.1 NFS_REMOTE_PATH=/var/recordings NFS_LOCAL_MOUNT=/var/lib/rtpengine-recording # must match output-dir if used NFS_OPTIONS=hard,intr,tcp In /etc/rtpengine/rtpengine.conf file: [rtpengine] table = 0 interface = 192.168.122.200 listen-ng = 127.0.0.1:2223 recording-dir = /var/spool/rtpengine/ recording-method = proc In [rtpengine-recording] table = 0 # output-storage = db (use default) # output-format = mp3 (use default) # output-mixed = 1 spool-dir = /var/spool/rtpengine/metadata output-dir = /var/spool/rtpengine/recording But the recording is not work, I have these issues in syslog: [1530178531.860171] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command 'start recording' from 127.0.0.1:38654 [1530178531.860191] NOTICE: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Turning on call recording. [1530178531.860239] WARNING: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Call recording through /proc interface requested, but kernel table not open [1530178531.860262] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860269] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860275] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860281] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860287] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860292] ERR: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open recording metadata file '(null)' for writing: Bad address [1530178531.860303] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start recording' from 127.0.0.1:38654 (elapsed time 0.000112 sec) [1530178531.969040] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command 'start recording' from 127.0.0.1:39374 [1530178531.969069] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start recording' from 127.0.0.1:39374 (elapsed time 0.000004 sec) [1530178537.176906] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command 'delete' from 127.0.0.1:40258 [1530178537.177003] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Scheduling deletion of call branch '9052b05a' (via-branch '') in 30 seconds [1530178537.177026] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'delete' from 127.0.0.1:40258 (elapsed time 0.000084 sec) [1530178537.178368] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command 'start recording' from 127.0.0.1:40258 [1530178537.178392] INFO: [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start recording' from 127.0.0.1:40258 (elapsed time 0.000004 sec) ^C[1530178543.752740] INFO: Version 6.4.0.0+0~mr6.4.0.0 git-master-4eb80da shutting down Also when i start RTPEngine, I have FATAL error about module xt_RTPENGINEer in syslog: Jun 28 05:44:58 debian8 systemd[1]: Starting NGCP RTP/media Proxy Daemon... Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]: modprobe: FATAL: Module xt_RTPENGINE not found. Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]: iptables: No chain/target/match by that name. Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]: ip6tables: No chain/target/match by that name. Jun 28 05:44:58 debian8 systemd[1]: Started NGCP RTP/media Proxy Daemon. Jun 28 05:44:58 debian8 rtpengine[10219]: [1530179098.989322] INFO: Generating new DTLS certificate Jun 28 05:44:59 debian8 rtpengine[10219]: [1530179099.033499] ERR: FAILED TO CREATE KERNEL TABLE 0 (No such file or directory), KERNEL FORWARDING DISABLED J Let me know what is the problem and how can i solve it? -- --Mojtaba Esfandiari.S

4 7

Having trouble getting presence working with Polycom VVX phones
by Justin Foley 03 Jul '18

03 Jul '18

Hey everyone. I've set up a kamailio server on a local dev box and running the phones on the same subnet as it to avoid any NAT issues. Seems to work fine, phones register & can call eachother and hear voice but the issue I'm running into is I can't seem to get presence to work. I've enabled it in the kamailio.cfg file with #!WITH_PRESENCE but if I go into "do not disturb" or try to call on phone1, it's not indicated on phone2. Also running ngrep on port 5060, I'm not seeing the anything regarding presence being sent over the SIP protocol.

2 2

$rs printed null
by Andrew Chen 03 Jul '18

03 Jul '18

Hi community, So I'm running 4.1.5 Kam version and I wanted to print out $rs variable. It printed out <null> right after the 183 session. Should it print something? What our server side sent is this: INVITE 100 183 488 or 487 And this is the output in kam logs: Jun 28 15:05:49 sjomainfnsg51 /usr/local/sbin/*kamailio*[15215]: INFO: <script>: [4975Fz-ses1-414b02f5R68422169(a)192.168.0.22][2][CSeq 1] fuze_for_mac/99.99.99999 Reply status <null> detected... any thoughts? Thanks -- Andy Chen -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 4

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