ok. I got this working now..no core dumps.
But still having problems with dispatcher.
I have the following setup:
sip client 1 -> SER -> sip client2 & sip client3
when client1 makes a call, it seems like SER does not
receive the request. I don't see any logs written and
the call timesout. Seems like SER is not receiving the
requests but when I do a netstat, I see it listening
on 5060.
udp 0 0 castor:5060 *:*
Normal routing without dispatcher works fine {thru
client registrations}. Am I missing some configs here?
thank you
ac
ser.cfg file:
#
# $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei
Exp $
#
# simple quick-start config script
#
debug=9 # debug level (cmd line: -dddddddddd)
fork=no
log_stderror=yes # (cmd line: -E)
children=2
check_via=no # (cmd. line: -v)
dns=off # (cmd. line: -r)
rev_dns=off # (cmd. line: -R)
port=5060
# for more info: sip_router -h
# ------------------ module loading
----------------------------------
loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
loadmodule "/usr/local/lib/ser/modules/sl.so"
#loadmodule "/usr/local/lib/ser/modules/tm.so"
loadmodule "/usr/local/lib/ser/modules/dispatcher.so"
# ----------------- setting module-specific parameters
---------------
# -- dispatcher params --
modparam("dispatcher", "list_file",
"/usr/local/etc/ser/dispatcher.list")
modparam("dispatcher", "force_dst", 1)
# main routing logic
route{
if ( !mf_process_maxfwd_header("10") )
{
sl_send_reply("483","To Many Hops");
drop();
};
ds_select_dst("1", "0");
forward(uri:host, uri:port);
# t_relay();
}
~
---dispatcher.list
# $Id$
# dispathcher destination sets
# gateways
1 sip:103@192.168.0.3:5060
1 sip:103@192.168.0.2:5060
from log :
0(0) DEBUG: init_mod: dispatcher
0(0) DISPATCHER: initializing ...
0(0) DISPATCHER:ds_load_list: dest [0/1/1]
<sip:103@192.168.0.3:5060>
0(0) DISPATCHER:ds_load_list: dest [0/1/2]
<sip:103@192.168.0.2:5060>
0(0) DISPATCHER:ds_load_list: found [1] dest sets
0(0) fixing /usr/local/lib/ser/modules/maxfwd.so
mf_process_maxfwd_header
0(0) fixing /usr/local/lib/ser/modules/sl.so
sl_send_reply
0(0) fixing /usr/local/lib/ser/modules/dispatcher.so
ds_select_dst
0(0) INFO: udp_init: SO_RCVBUF is initially 65535
0(0) DEBUG: udp_init: trying SO_RCVBUF: 131070
0(0) DEBUG: setting SO_RCVBUF;
set=131070,verify=131070
0(0) DEBUG: udp_init: trying SO_RCVBUF: 262140
0(0) DEBUG: setting SO_RCVBUF;
set=262140,verify=131070
0(0) DEBUG: setting SO_RCVBUF has no effect
0(0) DEBUG: udp_init: trying SO_RCVBUF: 133118
0(0) DEBUG: setting SO_RCVBUF;
set=133118,verify=131070
0(0) DEBUG: setting SO_RCVBUF has no effect
0(0) INFO: udp_init: SO_RCVBUF is finally 131070
0(0) WARNING: using only the first listen address (no
fork)
0(0) DBG: open_fifo_server: no fifo will be opened
0(0) init_unixsock_socket: No unix domain socket will
be opened
0(4567) DEBUG: init_mod_child (1): dispatcher
0(4567) DISPATCHER:init_child #1 / pid <4567>
1(4568) DEBUG: init_mod_child (-1): dispatcher
1(4568) DISPATCHER:init_child #-1 / pid <4568>
--- Andrei Pelinescu-Onciul <andrei(a)iptel.org> wrote:
On May 11, 2005 at 20:18, a c
<lra101(a)yahoo.com>
wrote:
hello,
I am getting a core dump when using the
dispatcher
module..Could someone help? I am using
http://lists.iptel.org/pipermail/serdev/2004-August/002592.html
to setup the
config.
Thanks, it's fixed on the latest cvs.
(some minor on ser exit missing null pointer check)
Andrei
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com