SIP REGISTER Forwarding After Call-ID Change

This feature addresses the case when an endpoint reboots and performs a third party registration before its old registration expires. During this reregistration, the contact header is the same as it was pre-reregistration. As a consequence of the reboot, the SIP Call-ID changes. In this situation, the Oracle® Enterprise Session Border Controller does not forward the REGISTER to the registrar, because it believes the endpoint is already registered, based on a previous registration from the same Contact: header URI.

To remedy this problem, the Oracle® Enterprise Session Border Controller now keeps track of the Call-ID in its registration cache. The forward-reg-callid-change option in the global SIP configuration element forces the Oracle® Enterprise Session Border Controller to forward a REGISTER message to the registrar when the Call-ID header changes in a REGISTER message received from a reregistering UAC.