Hi, I read in http://kamailio.org/docs/modules/1.4.x/nathelper.html that
Kamailio might rewrite ip address in o= in SDP to facilitate NAT traversal.
It may decide to use to original IP or use IP of RTP server. What factors
affect its decision ?
--
Khoa Pham
HCMC University of Science
Faculty of Information Technology
Hi All,
We have finished the Kamailio & Asterisk real time integration and load
balancing also done using dispatcher module.
Queue and voice mails are load balancing as well.When we are calling
extension to extension it is showing in all the servers.It seems extension
are not load balancing as per our knowledge.
I have attached the kamailio.cfg for your reference,Find my coding below as
mentioned.
*# -- dispatcher params for DB support --*
*modparam("dispatcher","db_url", "mysql://
openser:openserrw@192.168.1.170/openser")*
*modparam("dispatcher", "table_name", "dispatcher")*
*modparam("dispatcher", "setid_col", "setid")*
*modparam("dispatcher", "destination_col", "destination")*
*modparam("dispatcher", "flags_col", "flags")*
*modparam("dispatcher", "priority_col", "priority")*
*
*
*
-----------------------------------------------------------------------------------------
*
*# Dispatch requests*
*route[DISPATCH] {*
*if ( method=="INVITE" ) {*
*# dst_select( "GROUP", "HASH METHOD")*
* ds_select_dst("1","4");*
* sl_send_reply("100","Trying");*
* forward();#uri:host, uri:port);*
* exit();*
*}}*
Kindly suggest the solution for the same.
Thanks in advance.
Regards,
N.Prakash
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Dmitry (dmdm21)
Attached to Project - sip-router
Summary - FIFO deadlock after dispatcher reload
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - High
Priority - Normal
Reported Version - 3.3
Due in Version - Undecided
Due Date - Undecided
Details - kamailio-3.3.4
/usr/local/kamailio/sbin/kamctl fifo ds_reload
After couple of reloads FIFO interface stops responding.
After that command like bellow hangs.
/usr/local/kamailio/sbin/kamctl fifo ds_list
Normaly when FIFO is alive the process is running:
# strace -p 15519
Process 15519 attached - interrupt to quit
read(6, ^C <unfinished ...>
Process 15519 detached
After it's locked, it in this stage:
# strace -p 15519
Process 15519 attached - interrupt to quit
futex(0xaf0c8f10, FUTEX_WAIT, 2, NULL^C <unfinished ...>
Process 15519 detached
# gdb -p 15519
...
(gdb) bt
#0 0xb7732430 in __kernel_vsyscall ()
#1 0xb76826e7 in syscall () from /lib/tls/i686/cmov/libc.so.6
#2 0xaee41036 in futex_get (dsht=0xaf0c8b30) at
#../../mem/../futexlock.h:110
#3 ds_ht_clear_slots (dsht=0xaf0c8b30) at ds_ht.c:162
#4 0xaee38556 in ds_load_list (lfile=0xb71c2840
#"/usr/local/kamailio/etc/kamailio/dispatcher.list") at dispatch.c:601
#5 0xaee3c050 in ds_mi_reload (cmd_tree=0xa1dee18, param=0x0) at
#dispatcher.c:776
#6 0xb71a76f2 in run_mi_cmd (fifo_stream=0xa1ddad0) at
#../../lib/kmi/mi.h:77
#7 mi_fifo_server (fifo_stream=0xa1ddad0) at fifo_fnc.c:509
#8 0xb71a96b0 in fifo_process (rank=1) at mi_fifo.c:247
#9 0xb71a9a18 in mi_child_init (rank=0) at mi_fifo.c:211
#10 0x08123c5f in init_mod_child (m=0xb71ba5d8, rank=0) at sr_module.c:893
#11 0x08123bd0 in init_mod_child (m=0xb71ba6f0, rank=0) at sr_module.c:890
#12 0x08123bd0 in init_mod_child (m=0xb71baac8, rank=0) at sr_module.c:890
#13 0x08123bd0 in init_mod_child (m=0xb71bb798, rank=0) at sr_module.c:890
#14 0x08123bd0 in init_mod_child (m=0xb71bbb48, rank=0) at sr_module.c:890
#15 0x08123bd0 in init_mod_child (m=0xb71bbd88, rank=0) at sr_module.c:890
#16 0x08123bd0 in init_mod_child (m=0xb71bc0e0, rank=0) at sr_module.c:890
#17 0x08123bd0 in init_mod_child (m=0xb71bdbc8, rank=0) at sr_module.c:890
#18 0x08123bd0 in init_mod_child (m=0xb71bdd68, rank=0) at sr_module.c:890
#19 0x08123bd0 in init_mod_child (m=0xb71bded0, rank=0) at sr_module.c:890
#20 0x08123bd0 in init_mod_child (m=0xb71be1e8, rank=0) at sr_module.c:890
#21 0x08123bd0 in init_mod_child (m=0xb71be828, rank=0) at sr_module.c:890
#22 0x08123bd0 in init_mod_child (m=0xb71bec88, rank=0) at sr_module.c:890
#23 0x08123bd0 in init_mod_child (m=0xb71bef48, rank=0) at sr_module.c:890
#24 0x08123bd0 in init_mod_child (m=0xb71bf0c8, rank=0) at sr_module.c:890
#25 0x08123bd0 in init_mod_child (m=0xb71bf378, rank=0) at sr_module.c:890
#26 0x08123bd0 in init_mod_child (m=0xb71bffb0, rank=0) at sr_module.c:890
#27 0x08123bd0 in init_mod_child (m=0xb71c0220, rank=0) at sr_module.c:890
#28 0x08123bd0 in init_mod_child (m=0xb71c1ac0, rank=0) at sr_module.c:890
#29 0x08123bd0 in init_mod_child (m=0xb71c1c28, rank=0) at sr_module.c:890
#30 0x08123bd0 in init_mod_child (m=0xb71c2218, rank=0) at sr_module.c:890
#31 0x08123bd0 in init_mod_child (m=0xb71c24d0, rank=0) at sr_module.c:890
#32 0x08123bd0 in init_mod_child (m=0xb71c38c8, rank=0) at sr_module.c:890
#33 0x080a8ccd in main_loop () at main.c:1710
#34 0x080ab337 in main (argc=13, argv=0xbfc04964) at main.c:2546
(gdb) quit
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=275
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.