Third Party Registration Expiration
The REGISTER message sent from the Oracle Communications Core Session Manager to the third party server uses the Expires: value returned from the User Subscriber Database or HSS. The third party server sends a 200 OK message containing Contact bindings and an expires value chosen by the third party server itself. The Oracle Communications Core Session Manager checks each contact address to determine if it created it. For those addresses it created (as SD-Contacts), the Expires value from the 200 OK is used as the final value.
Once the expires timer has reached half the expires period as returned from the third party server, the Oracle Communications Core Session Manager refreshes the registration.
If the third party server responds to a REGISTER Request with a 423 (Interval Too Brief) response, the Oracle Communications Core Session Manager updates the contact’s expiration interval to the Min-Expires value of the 423 response. It then submits a new REGISTER Request with the updated expires value.