Caution for Using Forced Unregistration

You should use caution when applying SIP HNT forced unregistration for the following reasons:

• It can have an impact on the performance of your Oracle® Enterprise Session Border Controller and the registrar, especially when you have a large number of HNT endpoints in your configuration that become unavailable simultaneously.
• It is possible that the registrar might become vulnerable to overload in the case where the registrar must authenticate a large number of register messages generated when HNT endpoints are de-registered. It is possible that the cached registration credentials might become “stale” over time (e.g., the nonce value usually has a limited lifetime). Without proper credentials, the registrar will reject the de-registrations.

Given these concerns, we recommend that you consult with your Oracle systems engineer before adopting the use of forced unregistration.