Configuring the Gatekeeper Interface for Registration Caching

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

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

To configure the gatekeeper 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—Set this parameter to disabled to run the H.323 stack as a Gatekeeper proxy.
6. gatekeeper—Leave this parameter empty.
7. auto-discovery—Disable the Automatic Gatekeeper discovery feature upon start-up. Set this parameter to disabled.
8. gk-identifier—Set this parameter to the identification of the gatekeeper to which RRQs received on this interface must be proxied.
9. registration-ttl—Enter the number of seconds to set the timeToLive field in the RCF destined for an endpoint. If you do not configure another value, this timer is set to 120 seconds (default).

   This value should not be set too high or too low:

   • Setting a value that is too high causes the registration to be alive too long. If an endpoint reboots during this interval and re-registers with the same terminal aliases (but changes its call signaling address), the registration will be rejected with the reason duplicateAlias.

   • Setting a value that is too low puts an unnecessary load on the Oracle® Enterprise Session Border Controller because it has to handle keep-alive registrations from the endpoint constantly, especially when there are many registered endpoints. If an endpoint does not set the timeToLive field in its RRQ, the registration of that endpoint will not expire.

     If an endpoint registers again without first unregistering itself (e.g., when it crashes and reboots), the Oracle® Enterprise Session Border Controller rejects the registration using the reason duplicateAlias. The Oracle® Enterprise Session Border Controller uses this reason when the endpoint’s call signaling address (IP address and port) is changed but its terminal aliases remain the same.