<p dir="ltr">Hi, </p>
<p dir="ltr">Are these features enabled by default in the latest version of OpenSIPS (2.2.x) + NAT script? Or do they need to be enabled manually? </p>
<div class="gmail_quote">On 1 Oct 2015 09:33, "Ionut Ionita" <<a href="mailto:ionutionita@opensips.org">ionutionita@opensips.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">*Hello all,<br>
<br>
I’m glad to announce a new feature that allows OpenSIPS to monitor<br>
(via SIP OPTIONS probing) and disable/delete in realtime the registrations<br>
which are not responding.<br>
The previous approach had two issues when came to so called “zombie”<br>
registrations (registrations which are not valid anymore):<br>
* resources - such zombie registrations may waste resources in your<br>
OpenSIPS server (memory, processing time, DB space, useless NAT pinging,<br>
TCP connect attempts);<br>
* user experience - using the zombie registration to reach un-existing<br>
users translates into useless calls (calls that will simply timeout),<br>
giving delays in the call setup (instead of going straight to VM, you may<br>
burn 5-10 seconds in trying to reach the user);<br>
The main idea behind these features is to delete contacts that do not<br>
respond to a certain number of SIP pings. The SIP pinging is provided by the<br>
nathelper module which was enhanced to keep the state of each pinging requests<br>
(basically, the module is waiting and checking the reply of each SIP request<br>
sent to the registered users). For registrations detected as “dead” (not responding),<br>
the nathelper module interacts directly with the usrloc module in order to<br>
remove the zombie contact.<br>
For usage perspective, the nathelper module now has two new parameters:<br>
* ping_threshold - timeout to consider a ping as unanswered;<br>
* max_pings_lost - the number of unresponded pings after which the contact is<br>
removed from usrloc;<br>
In order to activate this feature, every contact must have the sipping_bflag<br>
(to be pinged) and remove_on_timeout_bflag (to be deleted on no-answer) activated.<br>
This means these flags must also be configured in the nathelper module. [0]<br>
For full documentation of the nathelper module including the newly added<br>
feature see [1]. Any feedback is highly appreciated.<br>
<br>
Regards,<br>
Ionut Ionita<br>
<br>
[0]<a href="http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html#id248011" rel="noreferrer" target="_blank">http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html#id248011</a><br>
[1]<a href="http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html" rel="noreferrer" target="_blank">http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html</a><br>
*<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>