Third Party Registration Server States
If the third party server does not respond to a REGISTER request, the Oracle Communications Core Session Manager adheres to standard SIP session agent retransmission/ timeout procedures. If the third party server is set to out of service, the Oracle Communications Core Session Manager attempts connectivity retry procedures. The retry procedures dictate that the Oracle Communications Core Session Manager periodically send a REGISTER message to the third party server to check if connectivity has come back. The time interval for checking connectivity to a third party server is set with the retry interval parameter. Retries continue forever or until the third party server responds. The retry mechanism may be disabled by setting the retry interval parameter to 0.
Note:
When using the ACLI generated third party registration method, the time interval for checking connectivity to a third party server is set with the retry interval parameter in the third party regs configuration element.When a third party server is out of service, the Oracle Communications Core Session Manager maintains a queue of outstanding third party registration requests. When the third party server returns to service, the Oracle Communications Core Session Manager gracefully flushes the queue of outstanding requests. This prevents a registration flood from being directed at the third party server .