- sr-users - kamailio.org

Fwd: kamailio with evapi crashing on high volume
by Jayesh Nambiar 02 Oct '18

02 Oct '18

Hello Daniel, Just a quick update on this. After running from the 5.1 branch twice it happened that Server became unresponsive. It never crashed and on forceful shutdown it only generated a core with shutdown routine. Here is what the syslog contained off while the calls were being sent to kamailio but kamailio was not processing any calls: Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd23ce5648), called from tm: h_table.c: free_cell_helper(235), first free tm: h_table.c: free_cell_helper(235) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd24a38ea8), called from tm: h_table.c: free_cell_helper(234), first free tm: h_table.c: free_cell_helper(234) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd23ce5648), called from tm: h_table.c: free_cell_helper(235), first free tm: h_table.c: free_cell_helper(235) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd24a38ea8), called from tm: h_table.c: free_cell_helper(234), first free tm: h_table.c: free_cell_helper(234) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd23ce5648), called from tm: h_table.c: free_cell_helper(235), first free tm: h_table.c: free_cell_helper(235) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd24a38ea8), called from tm: h_table.c: free_cell_helper(234), first free tm: h_table.c: free_cell_helper(234) - aborting Sep 22 16:09:04 triviamedia /usr/local/kamailio/sbin/kamailio[16006]: CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: freeing already freed pointer (0x7fcd23ce5648), called from tm: h_table.c: free_cell_helper(235), first fre And here's the "bt full" of the core file: [New LWP 16003] Cannot access memory at address 0x7fcd64e1a148 Cannot access memory at address 0x7fcd64e1a140 Failed to read a valid object file image from memory. Core was generated by `/usr/local/kamailio/sbin/kamailio -P /var/run/siptrunk.pid -f /usr/local/carrie'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fcd6443f428 in ?? () (gdb) bt full #0 0x00007fcd6443f428 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffed40e9e68 Thanks, - Jayesh On Sat, Sep 15, 2018 at 7:09 PM Jayesh Nambiar <jayesh1017(a)gmail.com> wrote: > Hello Daniel, > I have now git cloned from 5.1 branch and restarted kamailio today. Also > an observation; that when one particular customer with around 40-50cps > capacity starts his dialing is when the kamailio kept crashing. I will > observe in the coming week and report of any crashes accordingly. > > Thanks, > > - Jayesh > > On Wed, Sep 12, 2018 at 3:11 AM Jayesh Nambiar <jayesh1017(a)gmail.com> > wrote: > >> Thank you Daniel. I will deploy from 5.1 branch. I will be able to update >> it in next two days. Since this is a production system, I will have to have >> find a proper time slot to get this updated. Will let you know once that is >> done. >> Thanks again. >> >> - Jayesh >> >> On Tue, Sep 11, 2018 at 2:16 PM Daniel-Constantin Mierla < >> miconda(a)gmail.com> wrote: >> >>> Hi Jayesh, >>> >>> I looked over the weekend and seems like a race or a double free. I >>> backported some patches to tm module from master to 5.1 branch (a counter >>> to see if there is more than one free). Would you be able to deploy from >>> branch 5.1 or nightly builds for 5.1? With the next crash I can evaluate >>> (rule out or go for it) if it is double free or not. >>> >>> I haven't written you yet, because I planned to dig more into libev >>> (which is used by evapi), to see if it creates some threads that can mess >>> up with some kamailio globals, although I expect it is event loop in a >>> single thread. Other work related project took a lot of time these days, so >>> not there yet ... >>> Cheers, >>> Daniel >>> >>> On 11.09.18 09:56, Jayesh Nambiar wrote: >>> >>> Hi Daniel, >>> Just a gentle follow up on this. Could you find anything useful? >>> >>> Thanks, >>> >>> - Jayesh >>> >>> >>>>>> On 07.09.18 09:56, Jayesh Nambiar wrote: >>>>>> >>>>>> Hi Daniel, >>>>>> This happens randomly. It is not a testbed and never reproducible on >>>>>> the test server. I can still give you access if you wish to analyse the >>>>>> core files to check whats happening here exactly. >>>>>> It simply feels like on heavy load the evapi socket gives up. Earlier >>>>>> I was running 5.0.2 and in that kamailio would get stuck by not sending any >>>>>> async events on evapi socket. Not even the evapi:connection-closed event >>>>>> gets triggered. After I upgraded to latest stable version (5.1.5), it at >>>>>> least started crashing. Here are two core dumps put onto pastebin. >>>>>> https://pastebin.com/nn6gJapm >>>>>> https://pastebin.com/ph7b8vFH >>>>>> >>>>>> Thanks for all the support, >>>>>> >>>>>> - Jayesh >>>>>> >>>>>> On Fri, Sep 7, 2018 at 1:55 AM Daniel-Constantin Mierla < >>>>>> miconda(a)gmail.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> are you able to reproduce it somehow? Or just happens randomly? >>>>>>> >>>>>>> Is it on a testbed where I could get access to investigate the >>>>>>> corefiles? If not, then I will ask for more details from cores over email, >>>>>>> first would be 'bt full' for both cores and 'p *dead_cell' for the second >>>>>>> one. >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> On 05.09.18 17:47, Jayesh Nambiar wrote: >>>>>>> >>>>>>> Hi Daniel, >>>>>>> Have got these core dumps. Let me know if I should be doing a bt >>>>>>> full. I'll pastebin and send. Thanks, >>>>>>> >>>>>>> Core was generated by `/usr/local/kamailio/sbin/kamailio -P >>>>>>> /var/run/siptrunk.pid -f /usr/local/carrie'. >>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>> #0 0x0000000000505d30 in sip_msg_shm_clone (org_msg=0x7f6ab0d9f618, >>>>>>> sip_msg_len=0x7ffdddb2e8bc, clone_lumps=1) at core/sip_msg_clone.c:491 >>>>>>> 491 LUMP_LIST_LEN(len, org_msg->add_rm); >>>>>>> (gdb) bt >>>>>>> #0 0x0000000000505d30 in sip_msg_shm_clone (org_msg=0x7f6ab0d9f618, >>>>>>> sip_msg_len=0x7ffdddb2e8bc, clone_lumps=1) at core/sip_msg_clone.c:491 >>>>>>> #1 0x00007f6af0bdf68d in fake_req (shmem_msg=0x7f6ab0d9f618, >>>>>>> extra_flags=0, uac=0x7f6ab1738980, len=0x7ffdddb2e8bc) at t_reply.c:854 >>>>>>> #2 0x00007f6af0c3aa27 in t_continue_helper (hash_index=58039, >>>>>>> label=413633661, rtact=0x7f6af10500f0, cbname=0x0, cbparam=0x0) at >>>>>>> t_suspend.c:293 >>>>>>> #3 0x00007f6af0c3eed4 in t_continue (hash_index=58039, >>>>>>> label=413633661, route=0x7f6af10500f0) at t_suspend.c:583 >>>>>>> #4 0x00007f6aae4dd010 in w_t_continue (msg=0x7ffdddb2fa60, >>>>>>> idx=0x7f6af1098e90 "8\306\t\361j\177", lbl=0x7f6af1098ff0 >>>>>>> "\240\264\t\361j\177", rtn=0x7f6af1099150 "0\275\t\361j\177") at >>>>>>> tmx_mod.c:760 >>>>>>> #5 0x000000000045b477 in do_action (h=0x7ffdddb2f850, >>>>>>> a=0x7f6af109ab38, msg=0x7ffdddb2fa60) at core/action.c:1085 >>>>>>> #6 0x0000000000467fd5 in run_actions (h=0x7ffdddb2f850, >>>>>>> a=0x7f6af1096630, msg=0x7ffdddb2fa60) at core/action.c:1565 >>>>>>> #7 0x000000000045b234 in do_action (h=0x7ffdddb2f850, >>>>>>> a=0x7f6af10a0f80, msg=0x7ffdddb2fa60) at core/action.c:1058 >>>>>>> #8 0x0000000000467fd5 in run_actions (h=0x7ffdddb2f850, >>>>>>> a=0x7f6af10a0f80, msg=0x7ffdddb2fa60) at core/action.c:1565 >>>>>>> #9 0x0000000000468797 in run_top_route (a=0x7f6af10a0f80, >>>>>>> msg=0x7ffdddb2fa60, c=0x0) at core/action.c:1654 >>>>>>> #10 0x00007f6aabe79370 in evapi_run_cfg_route (evenv=0x7ffdddb30250, >>>>>>> rt=3, rtname=0x7f6aac08cb18 <_evapi_rts+56>) at evapi_dispatch.c:161 >>>>>>> #11 0x00007f6aabe7f271 in evapi_recv_client (loop=0x7f6aabe698e0, >>>>>>> watcher=0x27af5e0, revents=1) at evapi_dispatch.c:467 >>>>>>> #12 0x00007f6aabc5fd73 in ev_invoke_pending () from >>>>>>> /usr/lib/x86_64-linux-gnu/libev.so.4 >>>>>>> #13 0x00007f6aabc633de in ev_run () from >>>>>>> /usr/lib/x86_64-linux-gnu/libev.so.4 >>>>>>> #14 0x00007f6aabe7867c in ev_loop (loop=0x7f6aabe698e0, flags=0) at >>>>>>> /usr/include/ev.h:835 >>>>>>> #15 0x00007f6aabe83fc6 in evapi_run_dispatcher (laddr=0x7f6af0f72300 >>>>>>> "127.0.0.1", lport=8060) at evapi_dispatch.c:705 >>>>>>> #16 0x00007f6aabe6e262 in child_init (rank=0) at evapi_mod.c:213 >>>>>>> #17 0x0000000000542cad in init_mod_child (m=0x7f6af0f71b70, rank=0) >>>>>>> at core/sr_module.c:943 >>>>>>> #18 0x0000000000542971 in init_mod_child (m=0x7f6af0f72968, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #19 0x0000000000542971 in init_mod_child (m=0x7f6af0f73d38, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #20 0x0000000000542971 in init_mod_child (m=0x7f6af0f74670, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #21 0x0000000000542971 in init_mod_child (m=0x7f6af0f76708, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #22 0x0000000000542971 in init_mod_child (m=0x7f6af0f76c08, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #23 0x0000000000542971 in init_mod_child (m=0x7f6af0f770d0, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #24 0x0000000000542971 in init_mod_child (m=0x7f6af0f77cf0, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #25 0x0000000000542971 in init_mod_child (m=0x7f6af0f78808, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #26 0x0000000000542971 in init_mod_child (m=0x7f6af0f78bd8, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #27 0x0000000000542971 in init_mod_child (m=0x7f6af0f794c8, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #28 0x0000000000542971 in init_mod_child (m=0x7f6af0f79920, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #29 0x0000000000542971 in init_mod_child (m=0x7f6af0f7a330, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #30 0x0000000000542971 in init_mod_child (m=0x7f6af0f7afd0, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #31 0x0000000000542971 in init_mod_child (m=0x7f6af0f7bc80, rank=0) >>>>>>> at core/sr_module.c:939 >>>>>>> #32 0x000000000054303d in init_child (rank=0) at core/sr_module.c:970 >>>>>>> #33 0x0000000000425399 in main_loop () at main.c:1701 >>>>>>> #34 0x000000000042bd5c in main (argc=13, argv=0x7ffdddb31088) at >>>>>>> main.c:2638 >>>>>>> >>>>>>> And this: >>>>>>> [New LWP 15804] >>>>>>> [Thread debugging using libthread_db enabled] >>>>>>> Using host libthread_db library >>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>> Core was generated by `/usr/local/kamailio/sbin/kamailio -P >>>>>>> /var/run/siptrunk.pid -f /usr/local/carrie'. >>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>> #0 0x00007f6af0b90b70 in free_cell_helper >>>>>>> (dead_cell=0x7f6ab0a6baa8, silent=0, fname=0x7f6af0c8f630 "timer.c", >>>>>>> fline=654) at h_table.c:230 >>>>>>> 230 foo = tt->next; >>>>>>> (gdb) bt >>>>>>> #0 0x00007f6af0b90b70 in free_cell_helper >>>>>>> (dead_cell=0x7f6ab0a6baa8, silent=0, fname=0x7f6af0c8f630 "timer.c", >>>>>>> fline=654) at h_table.c:230 >>>>>>> #1 0x00007f6af0c24409 in wait_handler (ti=932640643, >>>>>>> wait_tl=0x7f6ab0a6bb28, data=0x7f6ab0a6baa8) at timer.c:654 >>>>>>> #2 0x00000000004bb445 in timer_list_expire (t=932640643, >>>>>>> h=0x7f6ab03ad158, slow_l=0x7f6ab03ae480, slow_mark=271) at core/timer.c:874 >>>>>>> #3 0x00000000004bb8ab in timer_handler () at core/timer.c:939 >>>>>>> #4 0x00000000004bbd30 in timer_main () at core/timer.c:978 >>>>>>> #5 0x00000000004250f9 in main_loop () at main.c:1691 >>>>>>> #6 0x000000000042bd5c in main (argc=13, argv=0x7ffdddb31088) at >>>>>>> main.c:2638 >>>>>>> >>>>>>> On Wed, Sep 5, 2018 at 3:13 PM Daniel-Constantin Mierla < >>>>>>> miconda(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> the backtrace doesn't show any hint about kamailio, only from >>>>>>>> closelog() up. >>>>>>>> >>>>>>>> It may be the core generated by shutdown procedure, have you >>>>>>>> enabled one core file per pid/process? If not, do it and reproduce the >>>>>>>> issue again, you may get two core files, one being the runtime issue and >>>>>>>> the other one from shutdown procedure, which likely is an effect of the >>>>>>>> other one. The one from the runtime is more relevant. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Daniel >>>>>>>> >>>>>>>> On 05.09.18 10:09, Jayesh Nambiar wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> I'm using kamailio 5.1.5 with evapi. I have a node.js connecting >>>>>>>> with kamailio evapi to which I send events and also consume events based on >>>>>>>> which I do the routing. I have 8 evapi workers defined in the config. >>>>>>>> The problem is that kamailio randomly crashes on high load. I'm >>>>>>>> assuming that it is related to the evapi module as rest of the config is >>>>>>>> pretty straight forward. I could get a core file and here's the core dump: >>>>>>>> [New LWP 14042] >>>>>>>> [Thread debugging using libthread_db enabled] >>>>>>>> Using host libthread_db library >>>>>>>> “/lib/x86_64-linux-gnu/libthread_db.so.1”. >>>>>>>> Core was generated by `/usr/local/kamailio/sbin/kamailio -P >>>>>>>> /var/run/siptrunk.pid -f /usr/local/carrie’. >>>>>>>> Program terminated with signal SIGABRT, Aborted. >>>>>>>> #0 0x00007f9995283428 in __GI_raise (sig=sig@entry=6) at >>>>>>>> ../sysdeps/unix/sysv/linux/raise.c:54 >>>>>>>> 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. >>>>>>>> (gdb) bt >>>>>>>> #0 0x00007f9995283428 in __GI_raise (sig=sig@entry=6) at >>>>>>>> ../sysdeps/unix/sysv/linux/raise.c:54 >>>>>>>> #1 0x00007f999528502a in __GI_abort () at abort.c:89 >>>>>>>> #2 0x000000000041a029 in sig_alarm_abort (signo=14) at main.c:646 >>>>>>>> #3 <signal handler called> >>>>>>>> #4 0x00007f999534f497 in __libc_cleanup_routine (f=<optimized >>>>>>>> out>) at ../sysdeps/nptl/libc-lockP.h:291 >>>>>>>> #5 closelog () at ../misc/syslog.c:415 >>>>>>>> #6 0x0000000000000000 in ?? () >>>>>>>> >>>>>>>> Any help in this regards is would allow me to identify the reason >>>>>>>> of the crash. Thanks for the support. >>>>>>>> >>>>>>>> - Jayesh >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda >>>>>>>> Kamailio World Conference -- www.kamailioworld.com >>>>>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda >>>>>>> Kamailio World Conference -- www.kamailioworld.com >>>>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com >>>>>>> >>>>>>> >>>>>> -- >>>>>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda >>>>>> Kamailio World Conference -- www.kamailioworld.com >>>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com >>>>>> >>>>>> >>>>> -- >>>>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda >>>>> Kamailio World Conference -- www.kamailioworld.com >>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com >>>>> >>>>> >>> -- >>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda >>> Kamailio World Conference -- www.kamailioworld.com >>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com >>> >>>

2 2

[DMQ] dmq_send_message function usage.
by Denys Pozniak 02 Oct '18

02 Oct '18

Hello! I have set of Kamailios which distributed location via dmq_usrloc. Could I construct synthetic DMQ message from separate Kamailio node to this cluster to get location info for the specific user? If yes, please explain how to do it. -- BR, Denys Pozniak

3 3

Forcing outbound transport to TCP
by Ivan Ribakov 02 Oct '18

02 Oct '18

I’m new to Kamailio and currently evaluating it’s capabilities. One of the things I would like to be able to do is to change outbound message transport based on some dynamic logic. Kamailio setup: I’m running on a setup from this guide - http://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/ <http://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/> and using default configuration file. In a basic scenario of one2one call, I was able to make Kamailio to forward INVITE to callee over TCP by issuing a REGISTER request with “transport=tcp” parameter. Although it worked, as far as I understand that means all communication with the callee will be happening over TCP. I would like to be able to change transport dynamically so looking for a way to do that from config file. I tried modifying $ru/$du in the following manner, but it didn’t seem to work. # default config content if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting # added to try to force TCP transport $du = $du + ";transport=tcp"; } Any pointers as to how can I modify the outbound message transport? Do I need to use some extra modules or can it be achieved with a basic setup? Thanks in advance, Ivan

4 5

Registrar Module
by Dan Quinney 01 Oct '18

01 Oct '18

Hi, So, route[REGISTRAR_1] will, when the max_contacts is reached, reply to the endpoint with a 503 error containing a "P-Registrar-Error: Too many registered contacts" header - this seems wrong to me so I've tried to work around it with route[REGISTRAR_2] which returns the right response, but, also writes "INFO: registrar [save.c:615]: test_max_contacts(): too many contacts for AOR" to the log file, which is messy. Does anyone have any pointers for doing this better? Thanks, Dan route[REGISTRAR_1] { if ( is_method("REGISTER") ) { if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); setbflag(FLB_NATSIPPING); } if ($avp(maximum_contacts) != $null) { $xavp(reg=>max_contacts) = $avp(maximum_contacts); } save("location"); } return; } route[REGISTRAR_2] { if ( is_method("REGISTER") ) { if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); setbflag(FLB_NATSIPPING); } if ($avp(maximum_contacts) != $null) { $xavp(reg=>max_contacts) = $avp(maximum_contacts); } save("location", "0x02"); switch ($retcode) { case -1: sl_send_reply("500", "Server Internal Error"); exit; case -2: sl_send_reply("403", "Forbidden"); exit; }; sl_send_reply("200", "OK"); } return; }

2 1

RTPEngine Question
by Wilkins, Steve 01 Oct '18

01 Oct '18

Hello All, I have an issue where Kamailio-RTPEngine-Asterisk calls work good when a softphone UAC on an IOS phone makes an Inbound call to a WebRTC client. However, if the softphone UAC is on Windows, it does not work (No Audio/Video). I noticed in the Wireshark trace that when using IOS I see STUN packets, but when using Windows I see no STUN packets. I believe this may be my issue, but I am not sure why the IOS would create STUN packets but when using Windows I get no STUN packets. Does anyone have any thoughts on what could be causing this? Thank you,

1 0

Re: [SR-Users] Problem with replicating dialogs using DMQ
by Charles Chance 01 Oct '18

01 Oct '18

Hi Jan, Setting multi_notify parameter should fix. Cheers, Charles On Mon, 1 Oct 2018 at 08:26, <jenus(a)cyberchaos.nl> wrote: > Charles, > > I have the follwing parameters configured: > > # ----- dmq params ----- > modparam("dmq", "server_address", "sip:10.10.10.1:5060") > modparam("dmq", "num_workers", 4) > modparam("dmq", "ping_interval", 90) > modparam("dmq", "notification_address", > "sip:sip04.voip.domain.test:5060") > > And the output of dmq.list_nodes is: > > { > host: 10.10.10.2 > port: 5060 > resolved_ip: 10.10.10.2 > status: active > last_notification: 0 > local: 0 > } > { > host: sip03.voip.domain.test > port: 5060 > resolved_ip: 10.10.10.1 > status: active > last_notification: 0 > local: 0 > } > { > host: sip04.voip.domain.test > port: 5060 > resolved_ip: 10.10.10.2 > status: active > last_notification: 0 > local: 0 > } > { > host: 10.10.10.1 > port: 5060 > resolved_ip: 10.10.10.1 > status: active > last_notification: 0 > local: 1 > } > > > As you can see the nodes are listed twice, one time with the ip and one > time with the hostname. If i change the notification_address to a ip > address the duplicate entry's are gone. > > Thanks, > > Jan > > Charles Chance schreef op 2018-09-28 20:54: > > Hello, > > > > Can you share your dmq config (modparams) and the output of > > dmq.list_nodes? > > > > Cheers, > > > > Charles > > > > On Thu, 27 Sep 2018 at 12:51, Jan Hazenberg <jenus321(a)gmail.com> > > wrote: > > > >> In the output of "kamcmd dmq.list_nodes" i see nodes twice. One with > >> ip address of the host and one with the hostname of the host. > >> > >> Jan > >> > >> On Thu, Sep 27, 2018 at 12:47 PM Jan Hazenberg <jenus321(a)gmail.com> > >> wrote: > >> > >> Daniel, > >> > >> It indeed sends duplicate DMQ messages, one to the ip of the other > >> node and one to the hostname of the other node. > >> > >> Unknown request: KDMQ sip:dialog@sip04.voip.domain.acc:5060 | > >> (application/json) > >> Unknown request: KDMQ sip:dialog@10.10.10.12:5060 [5] | > >> (application/json) > >> > >> Is there any way to disable this? > >> > >> Thanks, > >> > >> Jan > >> > >> On Thu, Sep 27, 2018 at 11:50 AM Daniel-Constantin Mierla > >> <miconda(a)gmail.com> wrote: > >> > >> Hello, > >> > >> the log message says that the dialog was already added to the timer. > >> Do you see retransmissions of the DMQ requests on the network with > >> ngrep/wireshark/...? > >> Cheers, > >> Daniel > >> > >> On 27.09.18 10:40, Jan Hazenberg wrote: > >> > >> Hello, > >> > >> I'm trying to replicate active dialogs using the DMQ module. I see > >> the dialogs on the other nodes but it generates a error message in > >> the logs on all the nodes: > >> > >> Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog > >> [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus dlg > >> tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80 tl->prev=0x7efdca14cb80 > >> Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog > >> [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer > >> 0x7efdca1beb98 [2643:3725] > >> > >> Even with the timeout_avp option disabled i still see the error > >> messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same > >> results. > >> > >> With debug enabled i see the correct data is replicated to the other > >> nodes: > >> > >> dlg_dmq_replicate_action(): sending serialized data > >> > > > {"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":" > sip:sipuser@10.10.10.10:1057;alias=10.10.10.10~1055~1","contact2":" > sip:+31101234567@10.10.10.10:5060 > >> [6]"} > >> > >> "lifetime":7200 is in the serialized data, and when i check on the > >> other node with "kamcmd dlg.list" i see that the lifetime data is > >> not updated. > >> > >> Thanks, > >> > >> Jan > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> -- > >> Daniel-Constantin Mierla -- www.asipto.com [1] > >> www.twitter.com/miconda [2] -- www.linkedin.com/in/miconda [3] > >> Kamailio World Conference -- www.kamailioworld.com [4] > >> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- > >> www.asipto.com [1] > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > > > > CHARLES CHANCE > > Managing Director > > > > t. 0330 120 1200 m. 07932 063 891 > > Sipcentric Ltd. Company registered in England & Wales no. 7365592. > > Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt > > Street, Birmingham Science Park, Birmingham B7 4BB. > > > > Links: > > ------ > > [1] http://www.asipto.com > > [2] http://www.twitter.com/miconda > > [3] http://www.linkedin.com/in/miconda > > [4] http://www.kamailioworld.com > > [5] http://sip:dialog@10.10.10.12:5060 > > [6] http://sip:+31101234567@10.10.10.10:5060 > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- *Charles Chance* Managing Director t. 0330 120 1200 m. 07932 063 891 -- Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.

2 1

Problem with replicating dialogs using DMQ
by Jan Hazenberg 01 Oct '18

01 Oct '18

Hello, I'm trying to replicate active dialogs using the DMQ module. I see the dialogs on the other nodes but it generates a error message in the logs on all the nodes: Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus dlg tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80 tl->prev=0x7efdca14cb80 Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer 0x7efdca1beb98 [2643:3725] Even with the timeout_avp option disabled i still see the error messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same results. With debug enabled i see the correct data is replicated to the other nodes: dlg_dmq_replicate_action(): sending serialized data {"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:sipuser@10.10.10.10:1057 ;alias=10.10.10.10~1055~1","contact2":"sip:+31101234567@10.10.10.10:5060"} "lifetime":7200 is in the serialized data, and when i check on the other node with "kamcmd dlg.list" i see that the lifetime data is not updated. Thanks, Jan

4 5

registrar lookup with different URI
by Maarten Ureel 30 Sep '18

30 Sep '18

Hello I want the registar module to lookup a user with a different 'name' as the RURI. We have the extension & domain in variables, but the RURI is ext@ip-of-server, e.g. 200(a)1.1.1.1<mailto:200@1.1.1.1>, while we want to perform the lookup for 200(a)somedomain.tld<mailto:200@somedomain.tld>. We have somedomain.tld in a header, so we have it in a variable. However, if we perform the lookup like this (using Python module): lookup_result = KSR.registrar.lookup('location') We get a negative result, and the debug logs show that it tries to locate 200(a)1.1.1.1<mailto:200@1.1.1.1> - which makes sense. So according to docs you can specify an URI, however when I do this: lookup_result = KSR.registrar.lookup('location' '200(a)somedomain.tld') lookup_result is "False" and the function is not executed, according to docs because it cannot obtain the parameters for this function. How can we force the registrar module to lookup a different user?

1 0

Dialog timout reset when receiving a re-INVITE
by jenus＠cyberchaos.nl 30 Sep '18

30 Sep '18

Hello, I have a issue with setting the dialog timeout for a call. It works fine until i receive a re-INVITE. The re-INVITE seems to reset the dialog timeout back to the default value configured in the module parameters (7200 in my case). I use "dlg_set_timeout("900");" to set the timeout to 900 seconds. When i receive a re-INVITE i see the following in the debug logs: DEBUG: dialog [dlg_handlers.c:647]: get_dlg_timeout(): invalid AVP value, using default timeout This happens even with the "timeout_avp" module parameter disabled. I'm running kamailio 5.1.3. Thanks, Jan

3 2

Restoring htable shared variables via dmq after Kamailio restart
by Denys Pozniak 28 Sep '18

28 Sep '18

Hello! I have 2 nodes that replicates htable variables via DMQ. How can I recover them after one node restarting? -- BR, Denys Pozniak

3 2

kamailio rtp connection
by Pieter Muller 28 Sep '18

28 Sep '18

Good day all I hope Im on the right place to ask the question. Im a newbie to kamailio and have a little problem understanding how to set kamailio correctly. Scenario: VoIP Supplier (IP:161.161.252.20{Private Net}) à Connect via routing to Kamailio Server(155.155.16.2 eno2{private Net}),Kamailio Server(187.221.197.252 eno1{public facing})àconnect to PBX(public IP set in dispatcher) à connect to RTP server(Public IP) Now the problem is that if you call in Number(a)161.161.252.20 <mailto:Number@161.161.252.20> is send to kamailio, kamailio then sends it down to dispatcher IP and that PBX responds directly back via rtp server to 161.161.252.20. The 161.161.252.20 IP is private and cannot be reached from the cloud and vice versa . How do I get kamailio to be the middle man between 161.161.252.20 and RTP server(all traffic must go via the kamailio server) Is there specific modules I must load. Im running Kamailio 4.4 Any help would be muchly appreciated. Regards Pieter

2 3

Important: new module exports interface
by Daniel-Constantin Mierla 28 Sep '18

28 Sep '18

Hello, as a result of collaborative work at Kamailio Developers Meeting, we succeeded to merge the two existing module exports interface (one for kamailio modules and the other one from ser modules) in a single one. All public modules were updated, but if you have any private module then you have to update as well in order to get it compiled with the latest master. Just look at one of the modules (e.g., sl is a good option) and all the fields in mod exports structure have comments with their meaning. In short: we removed unused fields for statistics, mi commands and extra-processes (from kamailio old interface) and oncancel (from ser old interface), kept the rpc exports from ser interface and pv exports and dlopen flags from kamailio interface. The other fields were common in both interfaces, but be aware that order was also changed. If you have a module implementing the old ser interface, you also need to add the free_fixup_field in functions exports tructure -- you can just set it to 0. With this we have now a single mod exports interface in all modules, the core is also cleaner as we got rid of the various compatibility layers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 0

INFO: maintenance work on deb.kamailio.org
by Daniel-Constantin Mierla 28 Sep '18

28 Sep '18

Hello, we will do some maintenance work on deb.kamailio.org server these days in order to move to a better infrastructure, so it may not be available for a while -- the DNS needs to be updated as well, this also can affect you if your router/provider does caching. Once we finish with the migration, we will send updates. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 1

Re: [SR-Users] No dispatcher failover
by Gertjan Wolzak 28 Sep '18

28 Sep '18

Alex, Thank you for the feedback, just the info I needed. Failover is working now just as it should. Now I just have to tweak the failover timing. Rgds, Gertjan Wolzak

1 0

Cannot handle Cancel Request properly
by Aqs Younas 28 Sep '18

28 Sep '18

Greetings list, I am getting hard time to make kamailio perfectly handle cancels request. I am using http_async_client and MSILO to handle push notifications. Case 1. When B party record exists in location but it is off-line and I send cancel *instantly* from Party A while kamailio is sending push to wake B Party up. modparam("tm", "failure_reply_mode", 3) modparam("tm", "cancel_b_method", 1) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 120000) You can see in below picture 407 being generated after some time. [image: default.PNG] What could be the reason of this problem? any pointer is much appreciated. Br, Aqs.

2 1

replay of tls delayed by 30 secs.
by Andrew Chen 28 Sep '18

28 Sep '18

Hi Kam community, Facing an urgent issue here and not sure how to troubleshoot it further. So our engineers been getting reports of unknown SIP timeouts and they suspect it's something on the Kamailio side. I've logged every transaction from receiving the message to done relaying it as shown below: Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425(a)xxx.xxx.xxx.xxx][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Relaying [UPDATE] from (xxx.xxx.xxx.xxx ) to ( xxx.xxx.xxx.xxx ) via (tls) Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425@ xxx.xxx.xxx.xxx ][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Done relay [UPDATE] from (xxx.xxx.xxx.xxx ) to ( xxx.xxx.xxx.xxx ) via (tls) When I pulled the 443 SIP trace from my tcpdump session, it shows the application data left the machine at 18:44 as shown here: [image: image.png] Note: This packet is encrypted and can't see the actual SIP message. This matches what was received on the client logs: 2018-09-24T18:38:44.032Z [40927] [INF] fuze.sip SipParser.cpp:549 LogSipMessage: xxx.xxx.xxx.xxx:443 - 4292B (local time 09/24 11:38:44) -------------------- RECEIVE: UPDATE sips:Luke_Surazski@ xxx.xxx.xxx.xxx:50795;id=37262838;inst=52241254 SIP/2.0 Via: SIP/2.0/TLS xxx.xxx.xxx.xxx:443;branch=z9hG4bK15f.5052c318e1766a0a9405f10708f43188.0;i=acbb7 Via: SIP/2.0/TCP xxx.xxx.xxx.xxx :38342;rport=38342;branch=z9hG4bK-55f913-t9-I214262897 What would cause such delays? I'm running Kamailio 4.1.5 Thanks. -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 9

subst_hf to rewrite a contact header
by Ben Hood 27 Sep '18

27 Sep '18

Hi, I’m wondering how to use subst_hf() properly. I’m trying to debug a broken flow by manually rewriting the contact header from Contact: <sip:b73c6f29-0101-4802-afcd-efb63f1e6d8f@10.10.10.12:5090;transport=udp> to Contact: <sip:2018092417381900003@81.x.x.x> by using $var(ctct) = "<sip:2018092417381900003@81.x.x.x>"; subst_hf("Contact", “/\<.+\>/$var(ctct)\r\n/", "a”); but the result is Contact: <sip:2018092417381900003@81.x.x.x> sip:b73c6f29-0101-4802-afcd-efb63f1e6d8f@10.10.10.12:5090;transport=udp Testing the regex with an external tool appears to match all of the original header, so I’m wondering why subst_hf doesn’t appear to rewrite the entire header. Is there something I’m doing wrong? TIA, Ben

3 7

Documentation of Kamailio.cfg
by Prabhat Kumar 27 Sep '18

27 Sep '18

Hi everyone, I there any suitable documentation for understating kamailio configuration file. Regards, Prabhat Kumar Sr. Software Developer [image: phone] +91 92129 92129 Ext: 89 [image: moible] +91 80831 10443 [image: Facebook] <https://app.mailtag.io/link-event-v2?mt__id=379f500e-c250-11e8-a3de-0625822…>[image: Twitter] <https://app.mailtag.io/link-event-v2?mt__id=379f5248-c250-11e8-9d85-0625822…>[image: Twitter] <https://app.mailtag.io/link-event-v2?mt__id=379f5392-c250-11e8-b97b-0625822…>[image: Linkedin] <https://app.mailtag.io/link-event-v2?mt__id=379f54be-c250-11e8-8e23-0625822…>[image: Google+] <https://app.mailtag.io/link-event-v2?mt__id=379f55f4-c250-11e8-affd-0625822…> [image: Logo] <https://app.mailtag.io/link-event-v2?mt__id=379f570c-c250-11e8-a472-0625822…>

2 1

Kamailio - Asterisk integration
by denislav.tsonev＠musala.com 27 Sep '18

27 Sep '18

Hello guys, I'm following this guide: https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb And I have the following schema: Phone A -----> Kamailio -----> Asterisk -----> Phone B (10.0.8.249) (10.0.6.123) (10.0.3.144) (10.0.13.23) I think the flow it is like (because when UAC register to Asterisk, the contact points to Kamailio IP): 1. Phone A --> Kamailio --> Asterisk 2. Asterisk --> Kamailio --> Phone B In attachment is the pcap of the call, kamailio config. The problem is that I never receive ACK after 200 OK and call drops after 30 seconds? Kamailio version 5.1 and Asterisk version 15.1 Phones are grandstreams and also tested with microsip soft client and same results... Like "Phone A" never sends ACK back I tried different approaches to change contact header in 200 OK, because is Asterisk IP. Disable NAT handling. Different "nat_uac_test" flags, but still without success :( Also tried with this NAT detection and manage routes (again without any success) - source https://github.com/sipwise/kamailio/blob/master/etc/kamailio.cfg # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT force_rport(); if (nat_uac_test("19")) { if (is_method("REGISTER")) { fix_nated_register(); } else { if(is_first_hop()) { set_contact_alias(); } } setflag(FLT_NATS); } #!endif return; } # RTPProxy control and signaling updates for NAT traversal route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; if(nat_uac_test("8")) { rtpproxy_manage("co"); } else { rtpproxy_manage("cor"); } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); } } #!endif return; } Thanks in advance Denislav Raychev Tsonev | Integration and Infrastructure Engineer | Musala Soft JSC www.musala.com | t: +359 2 969 58 21 | m: +359 878 270 965 | f: +359 2 969 58 22 World Trade Center, 36 Dragan Tsankov blvd., Sofia 1057, Bulgaria

1 0

Problem with replicating dialogs using DMQ
by jenus＠cyberchaos.nl 27 Sep '18

27 Sep '18

Hello, I'm trying to replicate active dialogs using the DMQ module. I see the dialogs on the other nodes but it generates a error message in the logs on all the nodes: Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus dlg tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80 tl->prev=0x7efdca14cb80 Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer 0x7efdca1beb98 [2643:3725] Even with the timeout_avp option disabled i still see the error messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same results. With debug enabled i see the correct data is replicated to the other nodes: dlg_dmq_replicate_action(): sending serialized data {"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:sipuser@10.10.10.10:1057;alias=10.10.10.10~1055~1","contact2":"sip:+31101234567@10.10.10.10:5060"} "lifetime":7200 is in the serialized data, and when i check on the other node with "kamcmd dlg.list" i see that the lifetime data is not updated. Thanks, Jan

1 0

create domain "on the fly" in registrar modukle
by Maarten Ureel 27 Sep '18

27 Sep '18

I'm building a setup with FreeSWITCH and Kamailio 5.2 but I'm having troubles in handling the registrations for multiple domains. So far I have in my config these related settings: # Disable database completely modparam("usrloc", "db_mode", 0) # Take domain into account when saving modparam("usrloc", "use_domain", 1) # Preload location table modparam("usrloc", "preload", "location") I'm using the app_python module; when performing the registrar save like this: KSR.registrar.save(KSR.pv.get('$fd'), 1) It fails, the debug shows that it cannot find the domain that the SIP user has here. When I use: KSR.registrar.save('location', 1) The phone registers just fine; however I'm bothered by the fact that the documentation states that you should specify the domain as a parameter. Is it OK if everything is in one 'location' domain? How can I let Kamailio know what domains exist (where does Kamailio get this information from)? We have a unique domain for every customer, like g123.ctx.ourcompany.tld. Kind regards Maarten Ureel

2 1

Adding new rtpproxy instance without restarting Kamailio
by Pintu Lohar 27 Sep '18

27 Sep '18

Hi All, I have a very basic question. Is there any way to add new rtpproxy instance without restarting Kamailio? As per my understanding, we can reload the dispatcher table when Kamailio server is running with kamctl dispatcher reload but do we have any such for rtpproxy list also from db when rtpproxy table ? Below is my rtpproxy related config, load from DB , #Once RTPProxy was found unreachable and marked as disabled, #the rtpproxy module will not attempt to establish communication to RTPProxy for rtpproxy_disable_tout seconds. modparam("rtpproxy", "rtpproxy_disable_tout", 120) #only for local host. modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2") modparam("rtpproxy", "db_url", "mysql://kamailio:xxxxxxxx@10.xx.xx.xx /kamailio") modparam("rtpproxy", "table_name", "rtpproxy") #enable marker for sdp modification by rtpproxy modparam("rtpproxy", "nortpproxy_str", "a=sdpmangled:yes\r\n") my current instance : ./kamcmd rtpproxy.list { setid: 0 url: udp:xxx.xx.xxx.xxx:7722 index: 2 disabled: 0 weight: 1 recheck: 0 } Db +----+-------+--------------------------+-------+--------+-------------+ | id | setid | url | flags | weight | description | +----+-------+--------------------------+-------+--------+-------------+ | 1 | 0 | udp:XXX.XXX.XXX.XXX:7722 | 0 | 1 | | +----+-------+--------------------------+-------+--------+-------------+ I already explored ./kamcmd rtpproxy.enable command , but it seems that this command is useful for re-enabling or disabling existing rtpproxy instance . My purpose is to add new rtpproxy instance when Kamailio is running. Thanks in advance. Any suggestion would very helpful. Thanks & Regards Pintu

1 0

KAMAILIO 5.1 : How to enable and subscribe to all of the SIP events and kamailio server through tcp, json
by yboujraf＠by-systems.be 26 Sep '18

26 Sep '18

Dear All, I am currently working to control from third party system Kamailio I have there are several way to interact with Kamailio but not sure I could make what I am expecting My question is : * I would like to get from my third party system subscribe to all of the sip events and status of the kamailio server My best way is TCP, JSON, scrambled if possible It will be great if anybody could route me to the correct direction. Best Regards, Youssef --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

KAMAILIO 5.1 - how to make a full redundancy of two kamailio Proxy server ?
by yboujraf＠by-systems.be 26 Sep '18

26 Sep '18

Dear All, I am currently thinking to use TWO (2) Kamailio Proxy server in redundancy. The system is : * I have one (1) public address * Two (2) Kamailio Servers with two different IP address My questions are : * What I need to add in front of the two Kamailio servers to be sure sip phone will be connected through the public ip address to one of the kamailio server at time. I have seen we could enable "cluster module" to sync the dabase of the two (2) kamailio server at the same time but not for the request. * Script to add to be sure the kamailio servers are correctly configured. Best Regards, Youssef --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

kamailio not forwarding 407
by David Villasmil 26 Sep '18

26 Sep '18

Hello guys, I have an almost default config, the box behind kamailio sends out the register, it is forwarded to the provider, which replies with 401, this gets forwarded back to the box which sends out the REGISTER with credentials and all works well. BUT when calling out, INVITE is sent to kamailio which is properly forwarded to the provider. The provider replies with a 407 and this 407 is NOT forwarded back to the box. Any ideas why? I can't figure it out! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

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