Modifications to Registration Caching Behavior
With the SIP connect feature enabled, Oracle® Enterprise Session Border Controller registration caching works the same way that it does with the feature disabled, with the following exceptions:
The Oracle® Enterprise Session Border Controller determines whether the destination realm has the sip-connect-pbx-reg option configured, and then:
- If it is configured, the Oracle® Enterprise Session Border Controller replaces the user part of the Request-URI with the user part of the To header. When the INVITE contains a P-Called-Party-ID header, the Oracle® Enterprise Session Border Controlleruses the user part of the P-Called-Party-ID header (instead of the To header).
- If it is not configured, the Oracle® Enterprise Session Border Controller determines if the destination address is for a session agent and whether that session agent has sip-connect-pbx-reg option configured. When it is configured, the Oracle® Enterprise Session Border Controller performs the same replacements described in the bullet directly above. When it is not configured, the Oracle® Enterprise Session Border Controller does not make any replacements.
When it receives an INVITE request, the Oracle® Enterprise Session Border Controller checks the incoming realm for the sip-connect-pbx-reg option.
- If it is configured, the Oracle® Enterprise Session Border ControllerC uses the INVITE’s source address (instead of the AoR and Contact-URI) to search the registration cache for a matched registration entry.
- If it is not configured, the
Oracle® Enterprise Session Border Controller determines if the INVITE’s source address is for a session agent and whether that session agent has sip-connect-pbx-reg option configured.
When it is configured, the Oracle® Enterprise Session Border Controller replaces the user part of the Request-URI with the user part of the To header. When the INVITE contains a P-Called-Party-ID header, the Oracle® Enterprise Session Border Controlleruses the user part of the P-Called-Party-ID header (instead of the To header).
When it is not configured, the Oracle® Enterprise Session Border Controller does not make any replacements.


