- sr-users - kamailio.org

New Diameter IMS Module : can we use it as SWx interface
by Igor Potjevlesch 11 Jul '17

11 Jul '17

Dear Kamailio users, Recently has been added to Kamailio two new modules : CDP and CDP_AVP There is not the TS 29.273 in it but I wanted to know if we can use it to emulate SWx interface? or add it with a non-hardcoded solution? I have seen the kamailio conference online and one session told about emulate IMS HSS with those two modules. Is someone tried to do it and want to share is experience with me ? Some DIAMETER functions in these modules are closed from the SWx. Best regards Igor Potjevlesch --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

2 1

Setup IMS core Network When Network behind nat
by Mojtaba 11 Jul '17

11 Jul '17

Hello, I am working on IMS core network. In this network we have these node with private IP: P-CSCF: 192.168.100.101(pcscf.kamailio-ims.test) I-CSCF: 192.168.100.102(icscf.kamailio-ims.test) S-CSCF: 192.168.100.103(scscf.kamailio-ims.test) HSS: 192.168.100.200(hss.kamailio-ims.test) I have two default users (bob and alice) and all things right great. Now i want use this network with one public IP behind nat. Let me know What should i do? In one way i could use SEMS-SBC and set public IP on it, How should i config sems-sbc to work correctly? Thanks.With Regads. M.ES.S

2 1

Siremis updates
by Daniel-Constantin Mierla 11 Jul '17

11 Jul '17

Hello, there is some ongoing work on Siremis (web management interface for kamailio) to make it fully compatible with Kamailio 5.0.x as well as update some of its legacy components: - https://github.com/asipto/siremis So I thought to start a discussion here and see if some of those changes are going to impact too much existing installations or what are the best options to use for the future. Done so far: 1) implemented the JSONRPC client using UDP and unix domain sockets, to work in pair with jsonrpcs module as a replacement for removed MI interface. The old JSONRPC over HTTP is still an option. 2) charts system has been migrated from open flash chart (ofc) to echarts (pure html5/javascript) -- therefore no more requiring to enable flash in browser. Configuration is the same and the charts should look pretty similar. If you upgrade, apart of different html view for the charts, the config files should not be changed. If you notice something broken, open an issue on github project linked above. Planned to be done: 3) Relocate siremis/modules/ser to siremis/modules/sipadmin -- this purely for more suggestive name for the admin module related to the SIP services offered by Kamailio, and be in pair with the module sipuser. This is mainly search and replace over php and xml files, however, it is going to impact if you developed your own internal extensions for siremis and placed them in the 'ser' module. It will require that you do the same search+replace 4) Review existing database tables views and add fields for missing columns. 5) Add views for other database tables. First in my mind being the table for rtpengine module. If you use some modules with tables not yet managed by siremis, reply and list them to set a list of priorities. Should have other things to report about siremis and are not yet listed on project's issue tracker, let's discuss here. Testing and feedback for 1) and 2) are very appreciated! 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 1

deb nightly-builds not being built
by Victor Seva 10 Jul '17

10 Jul '17

We are having some issues with our building infrastructure so packages are not being built. We are working on it, please be patient. Cheers, Victor

2 3

m_dump sends multiple messages
by Rahul Mehta 10 Jul '17

10 Jul '17

hello, when m_dump() function is called as user gets online, the function i.e=m_dump() sends multiple copies of same message,can anyone please provide way to stop m_dump() sending multiple copies of same message. I am providing the code of m_dump function if (m_dump("$fu")) { xlog("L_INFO","MSILO: offline messages dumped - if they were\n"); }else{ xlog("L_INFO","MSILO: no offline messages dumped\n"); };

2 1

kamctl v5 issues sending rpc from jsonrpc_exec_ex
by Abdoul Osséni 10 Jul '17

10 Jul '17

Hello, Got this error : ERROR: jsonrpcs [jsonrpcs_mod.c:1323]: jsonrpc_exec_ex(): method callback not found [dlg.end_dlg 3660 9594] Regards

2 3

domain vs uid_domain module
by Huber Andreas 10 Jul '17

10 Jul '17

Hi, I was comparing the documentation of the "uid_domain" and "domain" modules and I was wondering what is the main difference between the two modules. While the "uid_domain" module has more documentation, it seems to me that both modules are offering very similar functionality, or am I missing something ? Also I found it curious that the documentation of the "uid_domain" module uses "domain" as the module name in all its examples for the module configuration. E.g. modparam("domain", "domain_table", "new_name") But when I try to use the "uid_domain" module, I actually have to specify the parameters as : modparam("uid_domain", "domain_table", "new_name") The same question also applies to the "uid_auth_db" module that resembles closely the "auth_db" module in the documentation, but not in the implementation. Kind Regards, Andreas

2 1

app_lua reload - what exactly gets reloaded?
by Sebastian Damm 10 Jul '17

10 Jul '17

Hi, we have written some logic for a project in lua. There is a small function that gets called from Kamailio, but the main logic is done in a self-written module. That module does initialize some values from database on the first request that comes in. Now when reloading app_lua from kamcmd or via jsonrpc, I don't see the log output generated when initializing. In the debug log, I can see that the reload is taking place, but the variables and state seem to not get reset. What does the reload command actually reload? Best Regards, Sebastian

2 7

How to delay messages when msilo messages are dumped
by Rahul Mehta 10 Jul '17

10 Jul '17

Hello, We are facing scenario when msilo dump function is called the user's device gets hanged/crash as messages are sent together to the user who gets online,please provide solution how to delay the messages which are send to the user when 'm_dump' function is called. I am providing the code of m_dump function if (m_dump("$fu")) { xlog("L_INFO","MSILO: offline messages dumped - if they were\n"); }else{ xlog("L_INFO","MSILO: no offline messages dumped\n"); };

2 1

Random Proxy Crash, Restarted OK Anything Here For Concern?
by JR Richardson 10 Jul '17

10 Jul '17

Hi All, I have a basic proxy up and running for over 6 months without issue, had a random crash, not sure why. Restarted kamailio process and it's working as expected. Any clue is the log to indicate what might have happened? ----snip---- Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13416]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7fa1e1ebd658), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ALERT: <core> [main.c:775]: handle_sigs(): child process 13416 exited by a signal 6 Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13423]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13420]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13424]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13419]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13421]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13422]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13418]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13417]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) ----snip---- RTPProxy also running on the server was not affected. root@sip-router3-ve206:/var/log# kamailio -V version: kamailio 4.1.0 (x86_64/linux) 350d2e flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 350d2e compiled on 16:41:38 Dec 17 2013 with gcc 4.4.5 Yes, I know it's an older version but I prefer not to upgrade unless absolutely necessary. I'm sure this was a random event, not too concerned but since it is a production server, I'm obligated to investigate. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

3 2

remove_hf_re error on startup
by Grant Bagdasarian 07 Jul '17

07 Jul '17

Hi, I'm trying to remove all custom headers starting with X-, except a certain header, but Kamailio won't start due to an error. ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:455 remove_hf_re("^(?!X-ThisHeaderShouldNotBeRemoved)X-.*") or remove_hf_re("^(?!X- ThisHeaderShouldNotBeRemoved)X-") This is valid regex according to https://regex101.com/ Any idea's why this won't compile? Regards, Grant

3 3

How to convert ipv6 to ipv4 address inside message body
by Narayan P 07 Jul '17

07 Jul '17

Hi, I am using kamailio as outbound proxy integrated with rtpproxy.I have done the configuration of ipv6 to ipv4 network. But when 183 session progress came ,kamailio is sending its ipv6 address to pjsip client inside sdp body.So that it is not accepting and 488 error message is giving. How to convert ipv6 to ipv4 inside kamailio so that pjsip can accept. Below is the sip trace from client. 20:49:20.152 pjsua_app.c .....Call 0 state changed to EARLY (183 Session progress) 20:49:20.152 pjsua_media.c .....Call 0: updating media.. 20:49:20.152 pjsua_media.c ......pjmedia_stream_info_from_sdp() failed for call_id 0 media 0: Unsupported address family (PJ_EAFNOTSUP) 20:49:20.152 pjsua_media.c ......Error updating media call00:0: Unsupported address family (PJ_EAFNOTSUP) 20:49:20.152 pjsua_call.c .....Unable to create media session: No active media stream after negotiation (PJMEDIA_SDPNEG_ENOMEDIA) [status=220048] 20:49:20.152 pjsua_core.c ........TX 418 bytes Request msg CANCEL/cseq=12308 (tdta0x7f0b28008400) to UDP 2001:db8:bad:a55::2:5070: CANCEL sip:919035438928@185.122.206.62 SIP/2.0 Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz Max-Forwards: 70 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 CANCEL Route: <sip:[2001:db8:bad:a55::2]:5070;lr> Content-Length: 0 --end msg-- 20:49:20.154 pjsua_core.c .RX 457 bytes Response msg 200/CANCEL/cseq=12308 (rdata0x7f0b28001d08) from UDP 2001:db8:bad:a55::2:5070: SIP/2.0 200 canceling Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport=5077;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz;received=2001:DB8:BAD:A55:0:0:0:2 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62>;tag=6374de6d95f421336d5241fc0a072275-2b9b Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 CANCEL Server: kamailio (5.0.0-dev5 (x86_64/linux)) Content-Length: 0 --end msg-- 20:49:20.310 pjsua_core.c .RX 380 bytes Response msg 487/INVITE/cseq=12308 (rdata0x7f0b28001d08) from UDP 2001:db8:bad:a55::2:5070: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport=5077;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz;received=2001:DB8:BAD:A55:0:0:0:2 From: <sip:OTT919620649614@185.122.206.62>;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> CSeq: 12308 INVITE Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 Content-Length: 0 --end msg-- 20:49:20.310 pjsua_core.c ..TX 412 bytes Request msg ACK/cseq=12308 (tdta0x7f0b2800cf40) to UDP 2001:db8:bad:a55::2:5070: ACK sip:919035438928@185.122.206.62 SIP/2.0 Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz Max-Forwards: 70 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 ACK Route: <sip:[2001:db8:bad:a55::2]:5070;lr> Content-Length: 0 --end msg-- 20:49:20.311 pjsua_app.c .....Call 0 is DISCONNECTED [reason=488 (Not Acceptable Here)] 20:49:20.311 pjsua_app_comm ..... [DISCONNCTD] To: <sip:919035438928@185.122.206.62>;tag=GB-1498835320600 Call time: 00h:00m:00s, 1st res in 361 ms, conn in 0ms #0 audio deactivated 20:49:20.311 pjsua_media.c .....Call 0: deinitializing media.. 20:49:20.311 pjsua_media.c .......Media stream call00:0 is destroyed 20:49:21.311 pjsua_aud.c !Closing sound device after idle for 1 second(s) 20:49:21.311 pjsua_app.c .Turning sound device OFF 20:49:21.311 pjsua_aud.c .Closing default sound playback device and default sound capture device Any suggestion will be highly appreciated. Thanks, Narayan

3 2

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

Kazoo module json library kamailio 4.4.1
by Grant Bagdasarian 04 Jul '17

04 Jul '17

Hi, Could someone please tell me which json library I have to install in order for the kazoo module to compile? I've tried many different json library, none of them work. It keeps complaining: make all CC (gcc) [M kazoo.so] kz_trans.o In file included from kz_trans.c:53:0: kz_json.h:12:18: fatal error: json.h: No such file or directory #include <json.h> ^ compilation terminated. ../../Makefile.rules:97: recipe for target 'kz_trans.o' failed make[1]: *** [kz_trans.o] Error 1 Makefile:511: recipe for target 'modules' failed make: *** [modules] Error 1 There is another thread regarding this same issue, but no solution was provided by the creator of the thread. Any ideas? Regards, Grant

3 5

Re: [SR-Users] sr-users Digest, Vol 146, Issue 2
by Narayan P 04 Jul '17

04 Jul '17

Hi Sebastian, Thanks for your reply. Today I am trying to install rtpengine as suggested by you.Could you please tell me from which part of the script I need to add rtpengine functions as my client is getting 183 from kamailio as of now. My architecture is like this, external ipv4 network(port 5060)----------rtpproxy(ipv4)--kamailio(ipv6)(port 5070)----------client(ipv4)(port 5077) Please look at the attached wireshark capture. Highly appreciate any suggestion as always. Thanks, Narayan ________________________________ From: sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of sr-users-request(a)lists.kamailio.org <sr-users-request(a)lists.kamailio.org> Sent: Monday, July 3, 2017 10:00:02 AM To: sr-users(a)lists.kamailio.org Subject: sr-users Digest, Vol 146, Issue 2 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: host to get name of local server (Daniel-Constantin Mierla) 2. Re: remote ip address of sender and receiver (Daniel-Constantin Mierla) 3. Re: remote ip address of sender and receiver (Daniel-Constantin Mierla) 4. Re: Question regarding calling a shell script from kamailio (Daniel-Constantin Mierla) 5. Re: Compiling errors (Daniel-Constantin Mierla) 6. Re: evapi module and async_relay (Daniel-Constantin Mierla) 7. Re: Using lock() correctly (Sebastian Damm) 8. Re: call forward on no answer (Daniel-Constantin Mierla) 9. Re: How to convert ipv6 to ipv4 address inside message body (Sebastian Damm) 10. Re: UAC auth for incoming call (Daniel-Constantin Mierla) 11. Re: drouting / do_routing / prefix unknown (Daniel-Constantin Mierla) 12. Re: Using lock() correctly (Daniel-Constantin Mierla) 13. Re: Using lock() correctly (Sebastian Damm) 14. Re: Using lock() correctly (Daniel-Constantin Mierla) ---------------------------------------------------------------------- Message: 1 Date: Mon, 3 Jul 2017 09:03:16 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, Henry Fernandes <henry(a)usinternet.com> Subject: Re: [SR-Users] host to get name of local server Message-ID: <9c3f6b62-d79f-1376-b0f5-1ccbb69e37c1(a)gmail.com> Content-Type: text/plain; charset="windows-1252" 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<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> Kamailio Advanced Training - www.asipto.com<http://www.asipto.com> Kamailio World Conference - www.kamailioworld.com<http://www.kamailioworld.com>

2 2

missing request username on register
by 赵国杰 04 Jul '17

04 Jul '17

Hello all, I have two kamailio servers(A and B) with exact same config using the same mysql db. I can register to A but not B. Server B complained: ERROR: <script>: fu is sip:851968556538527744@104.198.52.31, ru is sip:104.198.52.31, rU is <null> After capture the udp packet on both server using ngrep, the REGISTER they received are both good except A returns 200 OK and B returns 403 Not relaying. I don't have a clue what went wrong. How come the $rU is null when all the headers in REGISTER are valid? Can someone please point me the direction? Thanks Jesse

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