- sr-users - kamailio.org

Mid-Registrar
by Mark Thomas 20 Jan '19

20 Jan '19

I’m currently and OpenSIPS user and I really want to be able to use their software on OpenWRT, but I have found it really hard to cross-compile. Is there a possibility to run Kamailio as a mid-registrar? For my application this is required, and I haven’t been able to find any information on this.

3 3

handling BYEs generated by dialog-timeout
by * Paolo Visintin - evosip.cloud 19 Jan '19

19 Jan '19

Hello! I'm wondering if someone have experience in changing $du on local kamailio generated packets (like BYE generated at the dialog-timeout) I'm trying to manipulate in `event_route[tm:local-request]` with no success. In the end I have it working using the `forward()` function and then using `exit;` but in this case instead of having 2 BYEs , kamailio sends 4 BYEs (2 with original $du, 2 with new $du) this an example : event_route[tm:local-request] { if ($rm == "BYE") { route(SELECT_OUTBOUND_PROXY); forward(); exit; } } I'm using a kamailio proxy on top with no record-route (we want to have multiple instances of proxy that can change ip address). Thanks in advance! Paolo

2 6

Dev documentation on implementing event_route events in custom module
by Ivan Ribakov 19 Jan '19

19 Jan '19

Is there any documentation for module developers that lays out API for registering and triggering events from a custom Kamailio module (similar to https://kamailio.org/docs/modules/5.0.x/modules/tm.html#tm.event_routes)? I have been referring to https://www.kamailio.org/docs/kamailio-devel-guide/ <https://www.kamailio.org/docs/kamailio-devel-guide/> up until now but it doesn’t seem to cover event_routes. Thanks in advance, Ivan

3 5

Diameter (CDP) crashes on startup. ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
by Denys Pozniak 18 Jan '19

18 Jan '19

Hello! Please help me to find the issue with CDP module as it blocks Kamailio to start. [root@10-10-10-10 kamailio]# cat diameter.xml <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="10-10-10-10.ams.proxy.dev" Realm="proxy.dev" Product_Name="Diameter Credit Control" Vendor_Id="10415" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="32"> <Peer FQDN="dev-diameter-1.ams.proxy.dev" Realm="proxy.dev" port="3868"/> <Acceptor port="3868" bind="10.10.10.10"/> <Auth id="16777216" vendor="10415"/> <Acct id="16777216" vendor="0" /> <Auth id="16777216" vendor="10415"/> <Auth id="16777216" vendor="0" /> <SupportedVendor vendor="10415"/> <Realm name="proxy.dev"> <Route FQDN="dev-diameter-1.ams.proxy.dev" metric="1"/> </Realm> <DefaultRoute FQDN="dev-diameter-1.ams.proxy.dev" metric="10"/> </DiameterPeer> 38(7825) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 37(7824) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 39(7826) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 40(7827) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 41(7828) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 41(7828) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process starting up... 42(7829) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process doing init on new process... 42(7829) INFO: cdp [receiver.c:184]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [dev-diameter-1.ams.proxy.dev] 42(7829) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process starting up... 43(7830) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 0(7787) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 43(7830) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 3868 43(7830) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 3868 43(7830) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 44(7831) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... [root@10-10-10-10 kamailio]# 44(7831) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer dev-diameter-1.ams.proxy.dev 44(7831) INFO: cdp [receiver.c:869]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 44(7831) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer dev-diameter-1.ams.proxy.dev:3868 connected 42(7829) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 42(7829) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0, abcdefed)[0x7f3ecb7ef018:0x7f3ecb7ef050]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 45(7832) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 52 0(7787) ALERT: <core> [main.c:739]: handle_sigs(): child process 7829 exited by a signal 6 0(7787) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(7787) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD DNS record dev-diameter-1.ams.proxy.dev is pointed to 10.10.10.20 NU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 7829] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -DDDD -E'. Program terminated with signal 6, Aborted. #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-34.el7.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 #21 0x0000000000424f85 in main_loop () at main.c:1701 #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 (gdb) bt full #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 qm = 0x7f3ecb4d0000 f = 0x7f3ecb7ef018 size = 140726864040496 next = 0x7df14b prev = 0x7f3ed067f329 __FUNCTION__ = "qm_free" #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 avp_t = 0x7f3ecb7ef050 avp = 0x7f3ecb7eef40 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 avp = 0x7f3ecb7ef440 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -798486160 next_event = 32574 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 avp1 = 0xd0684fc0 avp2 = 0x7f3ecb7eed10 __FUNCTION__ = "receive_message" #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 cnt = 184 n = 184 version = 1 dst = 0x7f3ecb7ef4f4 "" dmsg = 0x7f3ecb7ee9f0 __FUNCTION__ = "do_receive" #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 49 cnt = 1 msg = 0x0 sp = 0x7f3ed76feec8 sp2 = 0x7f3ed76feec8 p = 0x7f3ecb7a00d8 fd = 8 fd_exchange_pipe_local = 49 __FUNCTION__ = "receive_loop" #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7f3ecb7a00d8 __FUNCTION__ = "diameter_peer_start" #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424f85 in main_loop () at main.c:1701 i = 32 pid = 7821 si = 0x0 si_desc = "udp receiver child=31 sock=10.10.10.10:5060\000\177\000\000`\336\275\206\375\177\000\000A\307g\000\000\000\000\000`\202A\000\000\000\000\000ȖP\313>\177", '\000' <repeats 14 times>, "\001\000\000\000\260\336\275\206\375\177\000\000\234\240h\000\000\000\000\000 \243w\000\000\000\000\000H\361m\327>\177\000" nrprocs = 32 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 cfg_stream = 0x2b13020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758490 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 4201223303 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 4 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 82198, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1547739314, tv_nsec = 582000000}, st_mtim = {tv_sec = 1547743303, tv_nsec = 194148453}, st_ctim = {tv_sec = 1547743303, tv_nsec = 194148453}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) -- BR, Denys Pozniak

1 1

event_route[usrloc:contact-expired]
by Javier Valencia 18 Jan '19

18 Jan '19

Hi there! I'm using Kamailio 4.4.3, and I add this code to my Kamailio: event_route[usrloc:contact-expired] { xlog("L_INFO", "EXPIRED CONTACT START\n"); xlog("L_INFO", "EXPIRED CONTACT for $ulc(exp=>aor)\n"); xlog("L_INFO", "EXPIRED CONTACT END\n"); } I can't see this entries in the log. I read many times the docs and code, but I don't understand why it's not working. I have two phone with 60 and 300 expiry seconds, if then expire, when it's event_route[usrloc:contact-expired] triggered? Why this event route it's named as usrloc but it's documented in registrar module? I need to provide more info about? Thank you very much.

3 11

segfault at 0 - process stopped
by AL RSM 18 Jan '19

18 Jan '19

3 2

rtpengine_manage() in async tasks
by Alex Balashov 18 Jan '19

18 Jan '19

Hi, I've run into an issue with handling reinvites in async task workers--which I need to do in order to introduce a small delay to avoid a UA race condition--in which some state that is necessary for rtpengine_manage() to do the right thing seems to be lost. Specifically, if I do this: -- loadmodule "mqueue" loadmodule "rtimer" ... modparam("rtimer", "timer", "name=reinvite_q1;interval=10000u;mode=1;") modparam("rtimer", "exec", "timer=reinvite_q1;route=REINVITE_DEQUEUE") modparam("mqueue", "mqueue", "name=reinvite_q"); ... route { ... if(has_totag()) { if(loose_route()) { ... if(is_method("INVITE")) { if(!t_suspend()) { sl_send_reply("500", "Server Internal Error"); exit; } mq_add("reinvite_q", "$T(id_index):$T(id_label)", ""); } else route(IN_DLG_REQ); exit; } ... } route[REINVITE_DEQUEUE] { while(mq_fetch("reinvite_q")) { $var(id) = $(mqk(reinvite_q){s.select,0,:}{s.int}); $var(label) = $(mqk(reinvite_q){s.select,1,:}{s.int}); t_continue("$var(id)", "$var(label)", "IN_DLG_REQ"); } } route[IN_DLG_REQ] { handle_ruri_alias(); if(is_method("BYE")) rtpengine_manage(); else if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove") t_on_reply("MAIN_REPLY"); if(!t_relay()) sl_reply_error(); } onreply_route[MAIN_REPLY] { if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove"); } -- What I find is that if I generate a reinvite from either side, rtpengine_manage() passes through the SDP offer in the reinvite unadulterated, although the answer returns properly adulterated by RTPEngine. The same thing occurs if I use 'async', which as I gather is just a wrapper of convenience around t_suspend/t_continue() anyway. That module won't do for my purposes because I need a millisecond-level delay resolution rather than second-level, anyhow. Anyway, surely enough, this is because the execution context is one that insinuates a stream deletion. When the reinvite offer comes across and I call rtpengine_manage(), the command sent is 'delete': -- Jan 14 20:24:23 staccato.evaristesys.com rtpengine[33830]: INFO: [c94347dcf92e7ccc10dee84c4e0d1c8a]: Received command 'delete' from 209.51.167.66:39788 -- The RTPEngine module documentation actually warns about this: https://kamailio.org/docs/modules/5.2.x/modules/rtpengine.html#rtpengine.f.… But this insight is buried in the fourth bullet point: "If BYE or CANCEL, or called within a FAILURE_ROUTE[], then call rtpengine_delete(). Be careful with calling this function after resuming a suspended transaction (e.g., after t_continue()), because the context of executed route is FAILURE ROUTE (in other words, rtpengine_manage() in the route block of t_continue() does the same as in failure_route)." This would lead one to believe that it applies only in the context of handling a BYE or CANCEL in a resumed transaction, when in fact it seems to hold true of non-BYE/CANCEL and non-failure contexts as well, as can be clearly seen with the reinvite. The behaviour is exactly as expected if I don't use rtpengine_manage() and instead manually call rtpengine_offer()/rtpengine_answer(). And expected behaviour comes from rtpengine_manage() if I don't handle the request in a resumed transaction context. This yields the fundamental question: Is there any way to have my cake and eat it too? I really want to use rtpengine_manage() because I need to handle a potential SDP offer-in-ACK scenario and don't want to do a bunch of state-keeping in order to use the correct choice of rtpengine_{offer|answer}() in the right context, which is a problem rtpengine_manage() solves beautifully. At the same time, I absolutely need the slight reinvite delay that can be accomplished via async processing; a UA on this side has a nasty habit of sending a reinvite almost simultaneously to the 2xx answer for the INVITE transaction, leading to indeterminate egress velocity for those respective messages out of Kamailio worker threads. Many thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

authentification issue when nb user increase
by Laurent Schweizer 18 Jan '19

18 Jan '19

Hello, I have a proxy with Kamailio 5.0.6 working since few month without any issue. Around 4500 locations and 5300 contacts This weekend we move a very old proxy (Kamailio 3.3.2 with an old server )to this new one, adding around 14’000 users and 15’000 contacts. Yesterday when calls was starting we get an big issue with this new proxy, lot of phones was disconnected and some calls was rejected. I see that the issue was the authentication (done via a mysql DB with the cluster db module) many phone get a failure and was disconnected, mostly phone connected via TCP or TLS we see less issue with UDP even we have much more . The issue was not the number of TCP/TLS connection as we see the REGISTER and the 401 going back, so connection was correctly done Currently it’s working but I don’t know exactly why ☹, I mean I have done a change but it has really no relation … , during the same time I get another issue, some calls have no voice… We are using rtpengine (on the old proxy we was using rtpproxy) and with the rtproxy we already face a long time ago such case and to solve it we setup multiple rtpproxy (on the same host) So I try to do the same, I setup a second rtpengine on the same host and when I reload the config with : kamcmd rtpengine.reload all registration was working perfectly ... As they is no relation with the registration end the rtpengine I don't know why now it's working. Any idea ? BR Laurent

2 1

Limitation in Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

AWS binat external -> internal routing and record_route
by Dmitry Sytchev 17 Jan '19

17 Jan '19

Hi all! I have a question that arises in mailing list sometimes, but it is still not clear for me how to work with this. We have AWS instance with standard Amazon bi-nat, so basically communication with external hosts works with listen udp:ip:port advertise ip:port But in case when we need to send external call to internal network by internal ip addresses, we want to have internal host in record-route. As far as I understand, basic recommendation is to use separate port or internal address and select it with appropriate function. Maybe it is more theoretical question, but can we do something to generate correct record-routes and VIA for calls coming from external network to make their softswitches happy, and still maintain internal address in messages going to internal hosts, using single host and port on Kamailio behind nat? Thanks! -- Best regards, Dmitry Sytchev, IT Engineer

3 6

Invalid sqlops parameter
by Yağız AYDIN 17 Jan '19

17 Jan '19

Hello, I'm trying to install Kamailio IMS for my Ubuntu 18.04 device. I have followed the configuration files which are provided by installation, but I have a problem about sqlops module. While I'm trying to execute pcscf module, following errors appear: root@yagiz-HP-ZBook-15:/usr/local/src/kamailio# kamailio -f /etc/kamailio/pcscf/kamailio.cfg -c loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(12536) ERROR: sqlops [sql_api.c:669]: sql_parse_param(): invalid sqlops parameter [mysql://Mysql@localhost/pcscf] at [29] 0(12536) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 278, column 60: Can't set module parameter 0(12536) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16 0(12536) CRITICAL: <core> [core/cfg.lex:1599]: sr_push_yy_state(): cannot open included file: route/register.cfg (/etc/kamailio/pcscf/route/register.cfg) 0(12536) : <core> [core/cfg.lex:1308]: yylex(): error at /etc/kamailio/pcscf/kamailio.cfg line 907 I have set my sqlops parameter as : #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" PS: I have created necessary databases and tables which are mentioned on usrloc files ( which are ims_usrloc_pcscf-create.sql and ims_usrloc_scscf-create.sql) Here is my pcscf.cfg file # IP-Adress for incoming SIP-Traffic, in the following format: # SIP / UDP listen=udp:10.3.0.188:5060 # SIP / TCP #listen=tcp:11.22.33.44:5060 # SIP / TCP/TLS #listen=tls:11.22.33.44:5061 alias=pcscf.mnc001.mcc001.3gppnetwork.org #!define MY_WS_PORT 80 #!define MY_WSS_PORT 443 #!define PCSCF_URL "sip:pcscf.mnc001.mcc001.3gppnetwork.org" #!define TCP_PROCESSES 8 #!subst "/NETWORKNAME/mnc001.mcc001.3gppnetwork.org/" #!subst "/HOSTNAME/pcscf.mnc001.mcc001.3gppnetwork.org/" # SIP-Address of capturing node, if not set, capturing is disabled. ##!define CAPTURE_NODE "sip:127.0.0.1:9060" # Allowed IPs for XML-RPC-Queries ##!define XMLRPC_WHITELIST_1 "127.0.0.1" ##!define XMLRPC_WHITELIST_2 "127.0.0.1" ##!define XMLRPC_WHITELIST_3 "127.0.0.1" #!define RTPPROXY_ADDRESS "udp:10.1.2.186:22222" # Databases: #!define DB_URL "mysql://Mysql@localhost/pcscf" ##!define DB_URL "mysql://kamailio:kamailiorw@localhost/kamailio/pcscf" ##!define DB_URL2 "con2=>mysql://pcscf:heslo@127.0.0.1/pcscf" #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" ##!define SQLOPS_DBURL "mysql://root@localhost/pcscf" #! Optional: Server-URL for Websocket-Requests ##!define WEBSOCKET_WEBSERVER "phone.ng-voice.com" ##!define TRF_FUNCTION "trf.mnc001.mcc001.3gppnetwork.org" # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable nat traversal execute: # - define WITH_NAT # - define the connection to the RTP-Proxy: RTPPROXY_ADDRESS # # *** To force alls calls through the RTP-Proxy # - this will automagically enable NAT-Traversal # - define FORCE_RTPRELAY # # *** To enable IPv4/IPv6 Translation (RTPProxy) # - this will automagically enable NAT-Traversal # - define WITH_RTPIPV4 # # *** To enable TCP support execute: # - define WITH_TCP # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # - this will automagically enable TCP # # *** To enable XMLRPC support execute: # - define WITH_XMLRPC # - this will automagically enable TCP # # *** To enable anti-flood detection execute: # - adjust pike and htable=>ipban settings as needed (default is # block if more than 16 requests in 2 seconds and ban for 300 seconds) # - define WITH_ANTIFLOOD # # *** To enable the Rx-Interface: # - Configure Rx-Diameter-Interface in pcscf.xml # - define WITH_RX # # *** To enable a Homer SIP-Capter-Node: # - define CAPTURE_NODE with a proper address # # *** To enable support for the SEMS-SBC # - define WITH_SBC # - configure dispatcher-list with a set of SBC's # # Enabled Features for this host: ##!define WITH_DEBUG #!define WITH_NAT #!define WITH_NATPING #!define FORCE_RTPRELAY ##!define WITH_TLS ##!define WITH_XMLRPC ##!define WITH_IPBLOCK ##!define WITH_ANTIFLOOD ##!define WITH_RX ##!define WITH_RX_REG ##!define WITH_RX_CALL ##!define WITH_TCP ##!define WITH_RTPIPV4 ##!define WITH_SBC ##!define WITH_SBC_CALL ##!define WITH_REGINFO ##!define WITH_RTPPING ##!define WITH_WEBSOCKET Any helps would be appreciated, Regards, Yağız --

2 1

Setting up Kamailio IMS in a Box difficulties.
by Jason Tsay 17 Jan '19

17 Jan '19

Hi miconda, I am new to the Kamailio and RCS world. I'm trying to set up an IMS core so I can get two devices communication through RCS. I am trying to set up the Kamailio IMS in a box vmware image, and when I boot it up, it asks for the server login information. ??All parameters and passwords used are documented in the log-file.? I couldn't find documentation for the username and password. I was wondering if there is a new link available or login information where I could see the set up. These are the things that I have found (to be working) getting started - https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ configs - https://www.dropbox.com/s/nm51v4orxrox4ac/Kamailio-IMS%20config-files.zip?d… pdf - https://www.kamailio.org/docs/tutorials/ims/Kamailio-IMS-in-a-Box.pdf I did find the config files in a dropbox but I wanted to get the vmware sandbox working so I have a working environment (as I have failed many times to get my own instance set up.) In addition, I was looking for some Android clients or if you could recommend some. I've tried rcsjta but I keep getting an API not compatible error (Doesn't work on Android Pie (Pixel 3 device) or Android M (6.0.1) Nexus device.) I also tried IMSdroid, and it looks like it works with Android M (6.0.1) Nexus device but not compatible with Android Pie. Thanks, Jason

2 1

Updating default kamailio.cfg to use rtpengine
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, being discussed at events offline or during irc meetings couple of times, I want to open the discussion about updating the default configuration file to use rtpengine. So far I let rtpproxy because was packaged in many Linux distros, however, given the benefits of rtpengine in terms of performance as well as webrtc support, doubled by the fact that nowadays in the community it seems to be the primary choice of rtp relay, we should decide what to do. I see two options: 1) add a define to allow selection between rtpproxy and rtpengine 2) replace rtpproxy completely with rtpengine I would prefer 2) for simplicity of the configuration file, but the main question for the users community is how easy they find the deploying of rtpengine. Using Debian/Ubuntu should be trivial, there are packages for it, but I do not know about CentOS, Fedora, openSUSE or other Linux/BSD OSes people here are using it. Reply to sr-users if you have an opinion on this matter (I cc-ed sr-dev mainly to make aware the devs, but it is a matter of using kamailio). Of course, other suggestions are welcome as well. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 2

DMQ tries to resolve dns AAA even when it is disabled in kamailio core config
by José Seabra 16 Jan '19

16 Jan '19

Hi all, I'm using DMQ with multi_notify set to 1, the dns_try_ipv6 is disabled and dns_cache_flags is set to 1, but even this way DMQ is making dns AAA queries. Once that AAA queries are disabled in core dns config it seems that DMQ is not respecting those configurations, is that supposed? Thank you for your support Best Regards -- Cumprimentos José Seabra

2 3

Kamailio on Kubernetes
by Amar Tinawi 16 Jan '19

16 Jan '19

Hello all i'm wondering if Kamailio docker file is ready to be built over kubernetes i haven't try it yet, but don't know if it is available with all kamailio modules? does the database included or should be on different containers? Thanks in advance Regads

2 1

Kamailio v5.2.1 Released
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, Kamailio SIP Server v5.2.1 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.1. For more details about version 5.2.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/01/kamailio-v5-2-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Overhead of health check with dispatcher
by Jesse Strahn 16 Jan '19

16 Jan '19

Hi all, I'm new to Kamailio. I am using Kamailio/dispatcher to distribute calls to several SIP IVRs. I'm trying to determine the best solution to autoscale in AWS when call capacity of the IVRs is reached. The most straight forward solution is to spin up a new IVR on a dedicated subnet when required. I would configure dispatcher such that the whole IP range of this subnet is in the dispatcher.list so that once a new instance becomes available, Kamailio starts sending calls there. My question is, how much overhead would this add as Kamailio/dispatcher would be polling the IPs in the subnet that were not yet active. The plan would be to have a /28 subnet with 16 IPs. To start, there would be 2 active IVRs up and responding and 14 IPs in dispatcher.list that would not be responding. Appreciate any insight. Thanks, Jesse

2 1

Releasing Kamailio v5.2.1
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, I am considering to release Kamailio v5.2.1 sometime next week, likely on Tuesday (Jan 15) or Wednesday (Jan 16). Should any of you be aware of issues not reported to the bug tracker, open a bug report as soon as possible to give it a chance for analysis and an eventual fix: - https://github.com/kamailio/kamailio/issues Days after it, I am planning to make new releases from branch 5.1 and 5.0 (it should be the last one from there to mark the end of official packaging). Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 2

Re: [SR-Users] Kamailio OPTIONS Round-Trip
by Soltanici Ilie 15 Jan '19

15 Jan '19

OK, that looks interesting - and I think I would able to generate such options from kamailio - but how do I measure the time for a response for this request? Is there any variables which can provide response time for some requests?

3 3

test
by AL RSM 14 Jan '19

14 Jan '19

1 0

N-Way call
by José Antonio Gutiérrez Delgado 14 Jan '19

14 Jan '19

Hi, I am trying unsuccessfully to create three calls from an already created call or, if possible, calls to n users. I do not know if I need an additional module or if I need to do it at the plot level. I have searched unsuccessfully for guides and manuals, so I would appreciate any kind of guidance. I use for MjSIP communication. Thank you -- José Antonio Gutiérrez Delgado Responsable técnico Oficina: (+34) 923040031 <http://www.arsoft-company.com/> *Este mensaje se dirige exclusivamente a su destinatario/s y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.* *Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es tarea de todos.*

2 1

siptarce module and SIP-Replying Messages
by Mojtaba 14 Jan '19

14 Jan '19

Hello, I am using siptrace module in Kamailio. As you know, it sends a copy of signalling message for specific destination. Like HOMER project. Because of i won't run main route block in destination, i just have changed this block like below: request_route { //do some works. drop(); exit; } I know it would make a question in your mind why i do this? No problem, Let's come back to question. All things works correct except Replying SIP message. The destination is trying to relay Replying SIP message that it get from siptrace module in other server. How can i disable replying SIP mesages? With Best Regards --Mojtaba Esfandiari.S

2 1

Response VIA Header
by Soltanici Ilie 14 Jan '19

14 Jan '19

Hi, version: kamailio 5.1.6 (x86_64/linux) 7d1964 Also, i'm using force_rport(); in routing configuration file, but 'received' parameter anyway is missing :( Thank You.

2 5

RADIUS auth func diff
by morfair＠gmail.com 14 Jan '19

14 Jan '19

Hello! In auth_radius manual present two functions: radius_www_authorize() and radius_proxy_authorize(). What is the difference?

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