9 Routing Configuration

The Oracle Enterprise Communications Broker performs session routing via its route configuration. Route configuration establishes hop-by-hop paths to signaling endpoints.

End stations may or may not be known by the Oracle Enterprise Communications Broker; endpoints configured within the user database are known, all others are not. Whether or not they are known by the system, the last hop (agent) leading towards that end station is often known. For this reason, the Oracle Enterprise Communications Broker builds its hop list by starting with the last agent it knows in the path and recursively adding hops (agents) needed to get to that hop. In the case where the last hop is not known, the system provides its last known hop with endpoint information and allows unknown hops to try to find the endpoint.

Oracle Enterprise Communications Broker routing configuration allows the user to specify a route's cost to specify route preference. Cost may or may not be based on monetary considerations. But the reach of an enterprise’s network often does allow the user to configure routes that keep session traffic within the enterprise infrastructure rather than incurring cost associated with a service provider.

The Oracle Enterprise Communications Broker allows for a range of route preference criteria to differentiate between routing paths. Criteria includes source routing based on the agent or calling number. Target-oriented criteria is also available, allowing the enterprise to designate preferred paths for specific called numbers.