Administratively Disabling a SIP Registrar

The Oracle® Enterprise Session Border Controller's registration cache feature is commonly used to support authorization. It also allows the Oracle® Enterprise Session Border Controller to respond directly to SIP REGISTER requests from endpoints rather than forwarding every REGISTER message to the Registrar(s). In the Oracle® Enterprise Session Border Controller, Registrars are frequently configured as session agents, and an association between each endpoint and its Registrar is stored with the registration cache information.

In Release 4.0.1 and later, the invalidate-registrations parameter in the session agent configuration enables the Oracle® Enterprise Session Border Controller to detect failed Registrar session agents and automatically forward subsequent REGISTER requests from endpoints to a new Registrar. You can now perform the same behavior manually through a new ACLI command. When you use this command, the Oracle® Enterprise Session Border Controller acts as though the registrations have expired.

For each SIP session agent, you can enable the manual trigger command, and then use the command from the main Superuser ACLI prompt. The reset session-agent command provides a way for you to send a session agent offline. Session agents can come back online once they send 200 OK messages the Oracle® Enterprise Session Border Controller receives successfully.

Without using the manual trigger, session agents can go offline because of they do not respond to pings or because of excessive transaction timeouts. However, you might not want to use these more dynamic methods of taking session agents out of service (and subsequently invalidating any associated registrations). You can disable both of these mechanisms by setting the following parameters to 0:

• ping-interval—Frequency (amount of time in seconds) with which the Oracle® Enterprise Session Border Controller pings the entity the session agent represents)
• ttr-no-response—Dictates when the SA (Session Agent) should be put back in service after the SA is taken OOS (Out Of Service) because it did not respond to the Oracle® Enterprise Session Border Controller

However, you can still use the new SIP manual trigger even with these dynamic methods enabled; the trigger simply overrides the configuration to send the session agent offline.