H.323 Registration Caching

The Oracle® Enterprise Session Border Controller can cache and proxy an H.225 RRQ between an H.323 endpoint and a gatekeeper. Registration caching has two benefits:

• It allows the aggregation of RRQs sent to a gatekeeper stack and proxies those requests through the gateway stack. If the external gatekeeper associated with the outbound (gateway) interface does not support additive registration, then the Oracle® Enterprise Session Border Controller consolidates the requests by placing them all in the same packet. Otherwise, additive registration is used on the outbound (gateway) interface.
• It allows the gatekeeper stack to use the registration information to route calls from other realms to the endpoints in its realm.

For registration caching, you need to configure at least two H.323 interfaces:

• One gatekeeper interface to receive registrations
• One gateway interface to proxy registrations

The Oracle® Enterprise Session Border Controller caches all successful registrations, using the cache to route calls back to the associated endpoint.

The following diagram shows how RRQs flow during registration caching.