No, no, this is not the way to go.
This is due to firewall in between. First, try to limit re-register time
on device, in possible. THey will be flushed from database afer being
expired.
Then take countermeasures as below:
Solution that works:
* use nathelper module to ping UA regularly with short messages to keep
firewall open. Add those parameters to ser.cfg:
modparam("nathelper", "natping_interval", 10)
modparam("nathelper","ping_nated_only",1)
* use normal NAT-ed strategy in the rest of ser.cfg (as you probably do
now) - use fix_nated_sdp() and/or fix_nated_contact() where applicable.
--
Arek Bekiersz
tcchan wrote:
Hi All,
I encountered a situation that somehow a UA keep on Registering with the
server with the same IP but on different port. So SER, thought that
there are multiple instances of the same username and save the various
location into the database.
The problem is it registers so often that the memory is full not very
long.
I suspect it has something to do firewall but I am not sure.
Has anyone encounter this problem before? Any hint??
For the time being, is there a way to limit the number of REGISTER
message that the SER will take?