Updating Expiration Values

This feature also supports updating the expiration values for the registration cache when a Contact element has the expires attribute. For this support, the following apply:

• If the value of the expires attribute is greater than the expiration value for the access-side registration cache entry, the Oracle® Enterprise Session Border Controller replaces the XML expires attribute value with the cached one from the access side.
• If the value of the XML expires attribute is less than the core-side expiration value for the core-side registration cache entry, the Oracle® Enterprise Session Border Controller updates the core-side expiration value with the value from the expires attribute. Further, the Oracle® Enterprise Session Border Controller adjusts the access-side expiration value of the registration cache in these ways:
  • If the value of the XML expires attribute is less than the current access-side expiration value for the registration cache entry, the Oracle® Enterprise Session Border Controller sets the access-side expiration value to be equal to the value in the expires attribute.
  • Otherwise, the Oracle® Enterprise Session Border Controller leaves the expires value for the access-side expiration value for the registration cache entry unchanged. If this happens, the Oracle® Enterprise Session Border Controller replaces the value of the XML expires attribute with the adjusted access-side expiration value.
• If the expires attribute from a Contact element is 0 (meaning that the core is removing the registration), the Oracle® Enterprise Session Border Controller removes that Contact-URI from its registration cache. And if the registration cache entry has no remaining Contact-URIs, the Oracle® Enterprise Session Border Controller deletes the registration cache entry altogether.