sr-users June 2017

sr-users@lists.kamailio.org

79 participants
122 discussions

fix_nated_contact and IPv6
by Sebastian Damm 27 Oct '17

27 Oct '17

Hi, I'm trying to set up a Kamailio (4.1.3) server which converts between IPv6 and IPv4. Everything looks pretty good. Now I have a test client which sends packets via IPv6, but in contact header, SDP etc. there are still IPv4 addresses. (This comes from some converting from v4 to v6 earlier.) Thus, Kamailio tries to do a fix_nated_contact(). But after fixing, the Contact URI is wrong. Example: inbound Contact: <sip:bob@192.168.8.132> outbound Contact: <sip:bob@1234:1234:0:1234:0:0:0:2> The correct way of transforming the Contact URI would be: Contact: <sip:bob@[1234:1234:0:1234:0:0:0:2]> This incorrect Contact URI doesn't hurt first, but when the called party wants to hang up the call, it addresses the URI from Contact header, and Kamailio can't parse the Request URI: Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: rr [loose.c:934]: loose_route(): failed to parse Request URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: domain [domain.c:140]: is_uri_host_local(): error while parsing R-URI Is this a bug in the nathelper module? Was it never meant to handle IPv6 addresses? Or do I understand something wrong? Best Regards, Sebastian

4 4

NatHelper ignoring force_socket module parameter
by Asgaroth 24 Oct '17

24 Oct '17

Hi All, I have a strange issue, I have set the module parameter for nathelper's force_socket to a specfic ip/port, however, when I perform a sip trace I can see that all locally generated options messages are not sent from the socket defined in the modules parameters. I am not setting $fs anywhere in the script, so I am not over-writing it. Do any of the other module parameters have a bearing on if nathelper uses the force_socket parameter? My current nathelper settings are: modparam("nathelper", "received_avp", "$avp(RECEIVED)") modparam("nathelper", "natping_interval", 20) modparam("nathelper", "natping_processes", 4) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_from", "sip:keepalive@domain.com") modparam("nathelper", "sipping_method", "OPTIONS") modparam("nathelper", "sipping_bflag", NAT_BFLAG) modparam("nathelper", "force_socket", "1.2.3.4:5060") I am using kamailio v4.3.1: # kamailio -V version: kamailio 4.3.1 (x86_64/linux) f38e67 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: f38e67 compiled on 18:15:23 Jul 20 2015 with gcc 4.4.7 Thanks

2 5

Kamailio IMS deployment
by Ramya Y 22 Oct '17

22 Oct '17

Hi, I am newbie to kamailio world and we would like to deploy Kamailio based IMS platform. Can any body share the link or Step by step procedure(user Guide) to deploy Kamailio IMS. Regards, Ramya

5 22

Kamailio 4.3.4: receive_msg(): no via found in reply
by Grant Bagdasarian 15 Aug '17

15 Aug '17

Hello, We're testing kamailio 4.3.4 with two kamailio's communicating with each other. One of them is a gateway with rtpengine at the carrier side, the other is a basic sip router. When calling a destination and cancelling the INVITE a 487 is received from the carrier and directly ACK'd by the first kamailio and in turn is forwarded to the second. But the 487 response received by the 2nd kamailio doesn't have a Via header which results in kamailio printing the error: receive_msg(): no via found in reply. Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this? Note: IP's are changed. Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2 U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=109ac722. To: <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: <sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. . # U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. . # U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=109ac722. To: <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: <sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

4 16

Rate limiting
by NITESH BANSAL 31 Jul '17

31 Jul '17

Hello, I plan to add some rate limiting in the Kamailio. I'm already using Pike to rate limit based on the source IP. But in this case, i want to do the rate limiting per customer(regardless of the source IP), I can identify the customer based on a custom header in the INVITE, idea is to limit the customer to 'x' number of requests per second. Nitesh

5 12

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

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

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

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 2017