Gatekeeper Proxy Settings

If you are using the H.323 stack as a gatekeeper proxy, you might want to set:

• Whether registration processing is enabled or disabled
• Whether or not this H.323 interface is signaling-only
• At what H.225 call stage the H.245 procedures should be initiated

  To configure gatekeeper proxy settings:

1. process-registration—To have the Oracle® Enterprise Session Border Controller drop all RRQs, meaning that it does not acknowledge any requests, leave this parameter set to disabled, its default. To have the Oracle® Enterprise Session Border Controller process any RRQs that arrive on this H.323 interface, set this parameter to enabled. Valid values are:

   • enabled | disabled

     When registration processing is enabled and the Oracle® Enterprise Session Border Controllerreceives an RRQ on this H.323 interface, it will route the request to the appropriate gatekeeper. After the gatekeeper confirms that registration with an RCF, the Oracle® Enterprise Session Border Controller also confirms it with the endpoint that sent the RRQ. Then the registration becomes part of the Oracle® Enterprise Session Border Controller’s registration cache. If this endpoint does not confirm the registration, then the Oracle® Enterprise Session Border Controller will reject the registration with an RRJ and will not cache it.

2. proxy-mode—Set this field to the proxy mode that you want to use for the signaling only operation mode. Valid values are:

   • H.225 | H.245

     You can leave this field blank (default) if you are not using a proxy mode.

3. h245-stage—Set this field to the stage at which the Oracle® Enterprise Session Border Controller transfers the H.245 address to the remote side of the call, or acts on the H.245 address sent by the remote side. The default value is connect. Valid values are:

   • Setup | Alerting | Connect | Proceeding | Early | Facility | noh245 | Dynamic