sr-users

sr-users@lists.kamailio.org

38 participants
37512 discussions

SUBSCRIBE not work with public ip kamailio
by Nguyen Tran Nhan 07 Jul '17

07 Jul '17

Hello, I am using Kamailio with SEMS and rtpproxy for public ip address. I got issue that SUBSCRIBE message does not work. SUBSCRIBE works well with private ip address. Anyone face with this issue? Thanks, Nhan

2 5

Dialog List cannot be listed using kamcmd
by Muhammad Zaka 07 Jul '17

07 Jul '17

Hi We have over 400 active dialogs and I wanted to list all of them but it doesn't list any : - root@kamailio:~# kamcmd dlg.list ERROR: reply too big The command works fine when we have few dialogs. Is there any way to list all the active dialogs? Many Thanks Regards Muhammad Zaka

3 4

Kamilio doesn't start up with pymongo in the Kemi Python script..
by Muhammad Zaka 06 Jul '17

06 Jul '17

Hi all, In kamailio 5.0.1 with kemi interface for python I am trying to use pymongo to import Mongo Client interface for python but the kamailio service fails to start up properly. kamailio-kemi-python.py import sys import struct import Router.Logger as Logger import KSR as KSR from pymongo import MongoClient Case - I : No forking and no children in kamailio.cfg kamailio.cfg fork=no children=0 Kamailio service fails with the following error: - Jun 20 15:12:32 sbc99-kam-dev kamailio: ERROR: app_python [python_support.c:142]: python_handle_exception(): mod_init: Unhandled exception in the Python code:#012Traceback (most recent call last):#012 File "/etc/kamailio/kamailio-kemi-python.py", line 19, in <module>#012 from pymongo import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/__init__.py", line 87, in <module>#012 from pymongo.mongo_client import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/mongo_client.py", line 52, in <module>#012 from pymongo.client_options import ClientOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/client_options.py", line 23, in <module>#012 from pymongo.pool import PoolOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/pool.py", line 121, in <module>#012 ('type', platform.system()),#012 File "/usr/lib/python2.7/platform.py", line 1333, in system#012 return uname()[0]#012 File "/usr/lib/python2.7/platform.py", line 1300, in uname#012 processor = _syscmd_uname('-p','')#012 File "/usr/lib/python2.7/platform.py", line 1035, in _syscmd_uname#012 rc = f.close()#012IOError: [Errno 10] No child processes Case - II : Forking in kamailio.cfg fork=yes children=32 With forking Kamailio service fails with the following error: - Jun 20 15:19:07 sbc99-kam-dev kamailio: INFO: <core> [core/tcp_main.c:4665]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== from Python mod init Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.__init__ Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-127) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(3) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(5) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(6) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(7) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(8) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(9) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(10) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: jsonrpcs [jsonrpcs_sock.c:429]: jsonrpc_dgram_process(): a new child 0/19722 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(0) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19721]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 8 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 9 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 14 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 16 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 17 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 18 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 20 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 21 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 25 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 19 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 11 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 12 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Is there any pointers of what am I missing or is it kamailio bug? Many Thanks Regards Muhammad Zaka

2 5

SQL replication stops
by Brian Jenkins 05 Jul '17

05 Jul '17

Hello, When we reload Kamailio Kam stops impacting our sql replication. We are running 3.3.0. Has anyone seen this issue before. -- Brian Jenkins Network Operation

2 1

Reload an individual entry into a hash table from database
by Jonathan Hunter 05 Jul '17

05 Jul '17

Hi Guys, We are currently building a wholesale platform to route numbers to particular carriers, and we are looking to do this with hash tables. We will potentially have 100s of thousands of numbers we will need to lookup and query as to where to route them, and one idea is to populate them in a database, we would then load these values into a hash table which will be defined in the kamailio configuration file for us to query in realtime when an Invite arrives. The backend database will be modified constantly, so we would have the need to reload the hash table on demand. I can see there is the ability to reload a whole hash table, sht_reload, but is there an option to reload for an individual entry which has been added to the database, and we therefore want it in the hash table? I dont see anything in documentation (forgive me if I have missed it), is there an option to reload just an individual key entry from the database into cache? Thanks Jon

2 1

Re: [SR-Users] host to get name of local server
by Daniel-Constantin Mierla 05 Jul '17

05 Jul '17

I haven't looked at its implementation, so be careful if it does DNS (or system call) query every time it is used, it may slow down the processing, in that case you can just store in another variable and use it instead. Cheers, Daniel On 05.07.17 17:01, Henry Fernandes wrote: > I ended up using $HN(). > > https://www.kamailio.org/wiki/cookbooks/4.2.x/pseudovariables#hn_key_-_host… > > > > > > > From: Daniel-Constantin Mierla <miconda(a)gmail.com > <mailto:miconda@gmail.com>> > Reply-To: "miconda(a)gmail.com <mailto:miconda@gmail.com>" > <miconda(a)gmail.com <mailto:miconda@gmail.com>> > Date: Monday, July 3, 2017 at 1:03 AM > To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org>>, Henry Fernandes > <henry(a)usinternet.com <mailto:henry@usinternet.com>> > Subject: Re: [SR-Users] host to get name of local server > > Hello, > > > On 29.06.17 18:11, Henry Fernandes wrote: >> We have multiple Kamailio 4.4.x servers and I am setting up stats >> tracking. I would like to track the stats for each individual >> Kamailio server separately like so: >> >> kamailio_1.sip.register.count >> kamailio_2.sip.register.count >> kamailio_3.sip.register.count >> >> The problem is that we use one common file (in version control) for >> our Kamailio configuration. Thus, I can’t just hardcode the hostname >> into the file because it will be the same for each server. >> >> Does anyone have a solution for me? Is there a variable that >> provides the hostname or is there something else I can do? >> >> Ideally, I’d love to be able to do something like this. >> >> statsd_incr($host_name + “.sip.register.count"); >> >> > > one option would be to define it via command line parameter with -A > option. Your start script can set it using the usual shell scripts. > > 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 -- 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

host to get name of local server
by Henry Fernandes 05 Jul '17

05 Jul '17

We have multiple Kamailio 4.4.x servers and I am setting up stats tracking. I would like to track the stats for each individual Kamailio server separately like so: kamailio_1.sip.register.count kamailio_2.sip.register.count kamailio_3.sip.register.count The problem is that we use one common file (in version control) for our Kamailio configuration. Thus, I can’t just hardcode the hostname into the file because it will be the same for each server. Does anyone have a solution for me? Is there a variable that provides the hostname or is there something else I can do? Ideally, I’d love to be able to do something like this. statsd_incr($host_name + “.sip.register.count");

2 2

kamcmd dialogs count
by Arek Łazarczyk 05 Jul '17

05 Jul '17

Hi, I have a problem with kamcmd, for now i use kamctl fifo profile_get_size to get dialogs count to pass to nrpe and futher to nagios. Since fifo is deprecated, and i want to migrate to kamailio v5.0, i must change my method of counting dialogs to kamcmd dlg.profile_get_size. Problem is that i have dialog profiles values starting with 0, so kamctl fifo profile_get_size caller 004 returns correct vaule, but kamcmd dlg.profile_get_size caller 004 returns 0, i think that kamcmd converts 004 to just 4 on fly. Is there any way to prevent such behavior ? Thx4help in advance. Best regards, AŁ.

2 3

Kamailio Crashing inconsistently
by hemanth＠advaitamtech.com 05 Jul '17

05 Jul '17

Hello, I am using Kamailio 4.4, Kamailio is crashing inconsistently, I am not able find the root cause of the issue, Error which i get for the process which crashed at multiple occations kamailio[9137]: : <core> [mem/q_malloc.c:145]: qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten(6363e160b12, abcdefed)[0x7f205db59070:0x7f205db590a8]! Memory allocator was called from tm: h_table.c:152. Fragment marked by tm: t_reply.c:1903. kamailio[21724]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f1fe804a1e8 (address 0x7f1fe804a220) end overwritten (4ae8cfaec87c0a27, 192f1270797ac90b)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. kamailio[21950]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7fe541a2cd68 (address 0x7fe541a2cda0) end overwritten (c0082c06, abcdefed)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. kamailio[23200]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f1fae7fa260 (address 0x7f1fae7fa298) end overwritten (3a46e86e1b362938, 7260f1875617e)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. There are 2 cores generated whenever it crashes, I have given the backtrace of the core generated, (gdb) bt #0 0x00007fe16aca4c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fe16aca8028 in __GI_abort () at abort.c:89 #2 0x000000000066b4ac in qm_debug_frag (qm=0x7fe160bc2000, f=0x7fe160ec9108, file=0x7fe1684dc84e "tm: h_table.c", line=179) at mem/q_malloc.c:147 #3 0x000000000066e255 in qm_free (qmp=0x7fe160bc2000, p=0x7fe160ec9140, file=0x7fe1684dc84e "tm: h_table.c", func=0x7fe1684dcb00 <__FUNCTION__.10973> "free_cell_helper", line=179, mname=0x7fe1684dc250 "tm") at mem/q_malloc.c:480 #4 0x00007fe16840cab9 in free_cell_helper (dead_cell=0x7fe160f09e50, silent=0, fname=0x7fe1684eeb8c "timer.c", fline=648) at h_table.c:179 #5 0x00007fe1684584a7 in wait_handler (ti=1156027084, wait_tl=0x7fe160f09ed0, data=0x7fe160f09e50) at timer.c:648 #6 0x000000000063a329 in timer_list_expire (t=1156027084, h=0x7fe160c3faf0, slow_l=0x7fe160c42da8, slow_mark=776) at timer.c:874 #7 0x000000000063a79d in timer_handler () at timer.c:939 #8 0x000000000063ac3d in timer_main () at timer.c:978 #9 0x00000000004c2550 in main_loop () at main.c:1683 #10 0x00000000004c9211 in main (argc=13, argv=0x7ffe6bf7da98) at main.c:2627 (gdb) bt #0 0x00007fe16aca4c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fe16aca8028 in __GI_abort () at abort.c:89 #2 0x000000000066b02c in qm_debug_frag (qm=0x7fe160bc2000, f=0x7fe160ec8de0, file=0x7fe1684dc84e "tm: h_table.c", line=179) at mem/q_malloc.c:136 #3 0x000000000066e255 in qm_free (qmp=0x7fe160bc2000, p=0x7fe160ec8e18, file=0x7fe1684dc84e "tm: h_table.c", func=0x7fe1684dcb00 <__FUNCTION__.10973> "free_cell_helper", line=179, mname=0x7fe1684dc250 "tm") at mem/q_malloc.c:480 #4 0x00007fe16840cab9 in free_cell_helper (dead_cell=0x7fe160ed6a28, silent=1, fname=0x7fe1684dc9c1 "h_table.c", fline=449) at h_table.c:179 #5 0x00007fe16840e491 in free_hash_table () at h_table.c:449 #6 0x00007fe168436141 in tm_shutdown () at t_funcs.c:90 #7 0x00000000005c0a50 in destroy_modules () at sr_module.c:811 #8 0x00000000004b6449 in cleanup (show_status=1) at main.c:525 #9 0x00000000004b7ad6 in shutdown_children (sig=15, show_status=1) at main.c:667 #10 0x00000000004ba428 in handle_sigs () at main.c:759 #11 0x00000000004c343e in main_loop () at main.c:1744 #12 0x00000000004c9211 in main (argc=13, argv=0x7ffe6bf7da98) at main.c:2627 Thanks & Regards Hemanth

2 3

kamailio LTE HSS
by Ibrahim Almahi 04 Jul '17

04 Jul '17

Dear Expert Fellows,Good Day, I'm wonder whether kamailio developed an open source based LTE HSS handles both IMS and LTE procedures "LTE Attach, Location Update, Authentication, ....". If it's not yet developed, is there any plan for it in the near future. Thanks and have a nice day. Ibrahim Almahi966594996362

3 3

Jump to page:

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