Back-to-Back Gatekeeper Proxy and Gateway

This section explains how signaling takes place when the Oracle® Enterprise Session Border Controller functions as a back-to-back gatekeeper proxy and gateway for H.323. The following diagram illustrates theOracle® Enterprise Session Border Controller acting as a B2B gatekeeper proxy and gateway.

In this application, with the service mode (isgateway) parameter set to disabled, the Oracle® Enterprise Session Border Controller responds to LRQs and issues LCFs and LRJs. It sends LRQs and LCFs/LRJs to the local IPv4 address for the H.323 interface. The Oracle® Enterprise Session Border Controller responds to the LRQs by providing a signaling address that performs gateway functions.

When you use it as a back-to-back gatekeeper proxy and gateway, the Oracle® Enterprise Session Border Controller does not issue ARQs. In addition, all parameters related to registration, such as gateway prefix numbers, are ignored.

When you do not configure a gatekeeper, the Oracle® Enterprise Session Border Controller uses the local policy to find the appropriate destination for the call. If there is a matching local policy, the Oracle® Enterprise Session Border Controller returns an LCF to the originating gateway. If no local policy matches, the Oracle® Enterprise Session Border Controller rejects the call by sending an LRJ.