H.323 Registration Caching Configuration

In the ACLI, the parameters that apply to this feature are:

isgateway             Enable the stack to run as a gateway
registration-ttl      Number of seconds before the registration becomes invalid
terminal-alias        List of aliases for terminal
gatekeeper            Gatekeeper's address and port
gk-identifier         Gatekeeper's identifier

To configure the gateway interface parameters for registration caching:

1. In Superuser mode, type configure terminal and press Enter.

   ORACLE# configure terminal

2. Type system and press Enter to access the system-related configurations.

   ORACLE(configure)# session-router

3. Type h323 and press Enter.

   ORACLE(session-router)# h323

4. Type h323-stack and press Enter.

   ORACLE(h323)# h323-stacks
   ORACLE(h323-stack)#

5. isgateway—Enable H.323 stack functionality as a Gateway. Leave this parameter set to its default, enabled, so the H.323 stack runs as a Gateway. When this field is set to disabled, the H.323 stack runs as a Gatekeeper proxy.Leave this parameter for the service mode set to it’s default, enabled. Valid values are:

   • enabled | disabled

     Enabling this parameter ensures that registration with the gatekeeper upon startup. It also ensures that all calls will be preceded by an ARQ to the gatekeeper for admission control.

6. registration-ttl—Set the registration expiration parameter to the value of the timeToLive field in the RRQ sent to the gatekeeper. The default is 120. The valid range is:

   • Minimum—0

   • maximum—4294967295

     When the Oracle® Enterprise Session Border Controller receives an RCF from the gatekeeper, it extracts the timeToLive field and uses that value as the time interval for keeping the registration of the gateway interface alive. The Oracle® Enterprise Session Border Controller sends a keep-alive RRQ about ten seconds before the registration expires.

     The registration expiration you set value should not be too low because some gatekeepers simply accept the timeToLive in the RRQ, resulting in a potentially high volume of RRQs.

7. terminal-alias—Set this parameter if the gatekeeper requires at least one terminal alias in an RRQ. On startup, the gateway interface registers with the gatekeeper using this terminal alias.

   When the Oracle® Enterprise Session Border Controller forwards an RRQ from an endpoint and if the gatekeeper does not support additive registration, the RRQ has the interface’s terminal alias, the aliases of the registering endpoint, and other aliases of all registered endpoints. Otherwise, the RRQ only contains the aliases of the registering endpoint.

8. gatekeeper and gk-identifier—Configure these parameters if you do not want the Oracle® Enterprise Session Border Controller to perform automatic gatekeeper discovery. If the gatekeeper identifier is empty, then the Oracle® Enterprise Session Border Controller learns the gatekeeper identifier from the gatekeeperIdentifier field in the GCF.