Routing Calls from the IP-PBX

The Oracle® Enterprise Session Border Controller (E-SBC) looks for a match in the registration cache based on the From header or the P-Preferred-Identity header. The header should contain the user portion of one of the Associated-URIs that it received from the registrar in the 200 (OK) responses to REGISTER requests. It should also have the same hostname that is configured in the customer-host parameter. If that parameter is not configured, then the hostname should be same as the one configured for the register-host parameter.

After the corresponding registration Service-Router entry is found, the E-SBC uses the Service-Route for this endpoint to route the call, if it exists. If no Service-Route exists but the SIP interface’s route-to-registrar parameter is enabled, the E-SBC tries to route this to the registrar. You can configure the surrogate agent to override the SIP interface’s route-to-register setting. If the surrogate agent’s route-to-register parameter is set to disable, it takes precedence over the SIP interface’s setting. The E-SBC will not try to route the call to the registrar.