Realm Bridging with Static and Dynamic Routing

The Oracle® Enterprise Session Border Controller uses static routing and policy-based, dynamic routing to handle H.323 traffic. These types of routing have to do with the way that the outgoing stack is selected.

• Static routing—The incoming H.323 stack always uses the associated H.323 stack that you configure for outgoing traffic; no other stacks are considered.
• Dynamic routing—When there is not an associated stack configured, the Oracle® Enterprise Session Border Controller performs policy-based, dynamic routing known as realm bridging. In this type of realm bridging, the Oracle® Enterprise Session Border Controller checks the configured local policies for address information corresponding to the incoming traffic and finds an address that matches. Next, it checks the next hop in the local policy to determine a realm and uses the first H.323 interface that matches it.

Before You Configure

In order to run H.323 on your Oracle® Enterprise Session Border Controller, you need to configure the basic parameters: physical and network interfaces; global system parameters; SNMP, trap receiver, and accounting support, and any holiday information you might want to set.

You should also decide how you want to set up realms and routing (including the use of session agents and session agent groups) to support H.323 operations.