Does Microsoft
Messenger 5.1 have a problem with presence updates? I get updates for 4.6
clients but not for 5.1.
ser.cfg
is:
cat
ser.cfg
#
# $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 andrei Exp
$
#
# simple quick-start config script
#
# ----------- global
configuration parameters ------------------------
#debug=3
# debug level (cmd line:
-dddddddddd)
#fork=yes
#log_stderror=no
# (cmd line: -E)
/* Uncomment these
lines to enter debugging mode
debug=4
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"
alias="xxx.com"
alias="xxx.local"
alias="sip.xxx.local"
# ------------------
module loading ----------------------------------
# Uncomment this if
you want to use SQL database
loadmodule
"/usr/lib/ser/modules/mysql.so"
loadmodule
"/usr/lib/ser/modules/sl.so"
loadmodule
"/usr/lib/ser/modules/tm.so"
loadmodule
"/usr/lib/ser/modules/rr.so"
loadmodule
"/usr/lib/ser/modules/maxfwd.so"
loadmodule
"/usr/lib/ser/modules/usrloc.so"
loadmodule
"/usr/lib/ser/modules/registrar.so"
# Uncomment this if
you want digest authentication
# mysql.so must be loaded !
loadmodule
"/usr/lib/ser/modules/auth.so"
loadmodule
"/usr/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", 1)
# -- 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)
# -- registrar
parameters
modparam("registrar","default_expires",1800)
modparam("registrar","use_domain",0)
#
------------------------- 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 ( msg:len > 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("iptel.org", "subscriber"))
{
#
www_challenge("iptel.org",
"0");
#
break;
#
};
log(1,"request for register
received");
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();
};
}