Hi,
Im using OpenSER v1.3.1 and sipping does not work with my configuration. Here is a sample:
loadmodule "usrloc.so"
loadmodule "nathelper.so"
modparam("nathelper", "natping_interval", 10)
#modparam("nathelper", "ping_nated_only", 1)
modparam("nathelper", "sipping_bflag", 7)
modparam("nathelper", "sipping_from", "sip:pinger@cmovil.net")
modparam("nathelper", "received_avp", "$avp(i:801)")
modparam("registrar", "received_avp", "$avp(i:801)")
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "nat_bflag", 6)
route {
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
}
# for clients behind nats
if ( nat_uac_test("1") ) {
if (method=="REGISTER") {
fix_nated_register();
setbflag(6);
setbflag(7);
} else if ( method=="SUBSCRIBE" || method=="PUBLISH ) {
fix_nated_contact();
setbflag(6);
setbflag(7);
};
};
...
}
...
TCP clients register without problems and NAT users are identified properly. Routing for them works fine and so on, but I cannot see any ping packet leaving OpenSER to keep the TCP connection alive. Is there something missing?
Thank in advance.
Pablo
El Tuesday 03 June 2008 09:07:07 Pablo Guijarro Enríquez escribió:
but I cannot see any ping packet leaving OpenSER to keep the TCP connection alive. Is there something missing?
Yes, nathelper doen't send pings (OPTIONS) for antted TCP clients, just for UDP clients. For now, AFAIK, the only way to ensure the keepalive for TCP clients is by setting a max REGSITER expire of 32 seconds (T1*64).