hello list,
this is what i m getting logs when i start the ser sip server, please let me
know a work around to fix this and if possible what all fields/values has to
be in freeradius db wrt ser sip server query to radius.
===================================
Aug 2 18:09:12 sip ./ser[28920]: /usr/local/etc/raddb/clients.conf: line
34: unrecognized keyword: clients
Aug 2 18:09:12 sip ./ser[28920]: auth_radius: Error opening configuration
file
Aug 2 18:09:12 sip ./ser[28920]: init_mod(): Error while initializing
module auth_radius
==================================
and in /usr/local/etc/raddb/clients.conf
i have this on line no 34
clients sip.net4india.com {
secret = 123
shortname = sip
}
================================
here is my ser.cfg file
#debug=3 # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode
debug=7
fork=no
log_stderror=yes
*/
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
children=4
fifo="/tmp/ser_fifo"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
loadmodule "/usr/local/lib/ser/modules/mysql.so"
loadmodule "/usr/local/lib/ser/modules/sl.so"
loadmodule "/usr/local/lib/ser/modules/tm.so"
loadmodule "/usr/local/lib/ser/modules/rr.so"
loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
loadmodule "/usr/local/lib/ser/modules/usrloc.so"
loadmodule "/usr/local/lib/ser/modules/registrar.so"
loadmodule "/usr/local/lib/ser/modules/auth_radius.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "/usr/local/lib/ser/modules/auth.so"
loadmodule "/usr/local/lib/ser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
#modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_mode", 2)
#modparam("auth_radius", "radius_config")
#modparam("auth_radius", "service_type", 15)
# -- auth params --
# Uncomment if you are using auth module
#
#modparam("auth_db", "calculate_ha1", yes)
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
#modparam("auth_db", "password_column", "password")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if (len_gt( max_len )) {
sl_send_reply("513", "Message too big");
break;
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
record_route();
# loose-route processing
if (loose_route()) {
t_relay();
break;
};
# if the request is for other domain use UsrLoc
# (in case, it does not work, use the following command
# with proper names and addresses in it)
if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
# if (!www_authorize("sip.net4india.com",
"subscriber")) {
# if (radius_www_authorize("sip.net4india.com",
"subscriber")) {
# www_challenge("sip.net4india.com", "0");
# break;
# };
if (radius_www_authorize("202.71.131.54")) {
www_challenge("202.71.131.54", "1");
};
save("location");
break;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
# forward to current uri now; use stateful forwarding; that
# works reliably even if we forward from TCP to UDP
if (!t_relay()) {
sl_reply_error();
};
}
Ok, so I will try another setup:
2 proxies, each of them interacts with a separate mysql database.
Registrations will be replicated between the proxies using t_replicate.
I have also seen a replication parameter in serweb when adding new
contacts via the web interface and the FIFO. I found no documentation
about it, but I guess this will also replicate the new contact to
another sip proxy (don't know if its implemented yet).
So, both proxies can be used for registration and normal proxy tasks.
But how can a proxy catch up the lost REGISTER messages from the other
proxy during a "down" period?
I think, one possibility would be, that when the proxy/database is "up"
again, the database begins to mirror the complete state from the other
database, and only when this is finished, ser will be started again and
reads the current user location from the database.
Is there another, maybe simpler solution to this problem?
Klaus
> -----Original Message-----
> From: Jan Janak [mailto:jan@iptel.org]
> Sent: Wednesday, July 30, 2003 1:43 PM
> To: Klaus Darilion
> Cc: serusers(a)lists.iptel.org
> Subject: Re: [Serusers] Does lookup("location") queries the
> database or the memory?
>
>
> Hello,
>
> On 30-07 13:39, Klaus Darilion wrote:
> > Hello!
> >
> > I have found the db_mode option in the userloc module,
> which controls
> > updates in the location table. But how are the lookups
> handled in ser?
> >
> > If a user location will be requested by lookup("location"),
> will this query
> > the backend database or only the RAM. Is this lookup behaviour also
> > configurable (how?)?
>
> No, it will not query the database, only memory will be used.
>
> > I'm thinking about a configuration with 2 ser proxies and
> one database
> > backend. If the lookup only queries the cached location
> table, I would have
> > to froward the registrations between the two proxies via
> t_replicate. But
> > wouldn't this cause both proxies to update the database
> resulting in two
> > entries in the location table for each registration?
>
> Yes, this is not possible at the moment. Another database mode which
> will query the backend database when doing lookups is on
> our todo list.
>
> Jan.
>
>
Hi
>We are using the cisco 7206vxr gear. They report connect/disconnect
>messages to syslog as well. As you note we use the TDM disconnect
>to re-enforce our SIP BYE messages. Often the SIP BYE is missed.
What command you use for re-enforce SIP bye meessages?
kaiser
