Hi,
We were looking to a way to integrate this in a more natural way - there
is a feature request (https://github.com/OpenSIPS/opensips/issues/337)
for being able to track the replies to pinging OPTIONS . By doing that,
you can see when the end point dies (it will simply stop answering to
ping) and you can forcedly unregister it . But this is just a plan yet.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.02.2015 16:46, microx wrote:
Hi Tin,
As long as the registration of the user has timed out, the user's
registration info will be invalid.
With OpenSIPS, you can set an upper bound on the maximum expiry value of
user registration (modparam("registrar", "max_expires",
your_preferred_value)) and set the interval in which the expired user
registration data are removed (modparam("usrloc", "timer_interval",
your_preferred_value)).
If you would like to delete such users on your own, you may use the MI
function ul_rm provided in the usrloc moduel.
Kind wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/The-user-s-address-stay-in-memory-tp7595234p7595242.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
