SIPconnect

The Oracle® Enterprise Session Border Controller supports the SIPconnect model, wherein PBXs register themselves so that service providers do not need to know IP addresses or locations in advance for static configurations. This is particularly helpful when the PBX is behind a NAT.

In the PBX registration process, the PBX creates a binding between one of its phone numbers as the address of record (AoR) and Contact-URI in the REGISTER message. The registrar knows that the single AoR actually represents many addresses, and so it registers them implicitly. However, the registrar does not return the implicit AoR number in P-Associated-URIs.

The SIPconnect feature resolves the following issues that arise from using this model:

• SIP INVITEs sent to the PBX from the Registrar through the Oracle® Enterprise Session Border Controller have the Request-URI of registered contact. Because it typically ignores the To-URI, the PBX needs the Request-URI username portion to be the specific extension number being called.

  With the SIP connect feature enabled, the Oracle® Enterprise Session Border Controller overwrites the Request-URI username with the To-URI username.

• SIP INVITEs from the PBX have the From AoR and Contact-URI usernames of specific phones rather than of the registered AoR and Contact-URI. For the Oracle® Enterprise Session Border Controller, this means that it cannot use the allow-anonymous parameter value of register; there would be no registered user matches, and the Oracle® Enterprise Session Border Controller would reject them (with a 403 Forbidden).

  With the SIP connect feature enabled, the Oracle® Enterprise Session Border Controller performs allow-anonymous checking based on the registered Via address, which is the same for all requests for the same PBX.