Routing Fields

The Routing Table configuration displays the route list.

To add routes, click Add. The Oracle Enterprise Communications Broker displays the Routing Table configuration.

Note:

The routing engine finds the optimum route based on the Source and Destination Agents. Oracle recommends avoiding wild cards in both Source and Destination Agents. When these values are configured as wild cards, the ECB must check the entire routing table for a match and this negatively impacts performance.

The following list describes the fields available in the Add dialog and the corresponding configuration instructions.

Source Agent

Select the agent from which the traffic must come to match the route.

The default is the wildcard *, meaning to match traffic from any agent.

Calling Number

Type in the number from which the traffic must come to match the route. A valid entry includes numeric characters or an FQDN resolvable through ENUM.

Regular expressions and special character such as "~", “!”, “*”, “x”, "(x)", “[x]”.

The default is the wildcard *, meaning to match traffic with any calling number.

Dest Agent

Select the agent to which the traffic must be targeted to match the route.

The default is the wildcard *, meaning to match traffic to any agent.

Called Number

Type in the number to which the traffic is targeted to match the route. A valid entry includes numeric characters or an FQDN resolvable through ENUM.

Regular expressions and special character such as "~", “!”, “*”, “x”, "(x)", “[x]”.

The default is the wildcard *, meaning to match traffic with any called number.

Route

Select the agent that is the next hop in the route path.

Cost

Enter a cost associated with this route to specify route use preference when there are multiple routes to the same destination.

A valid entry is numeric ranging from 0 to 100, with the lowest number (cost) being the preferred route.

Description

Enter any descriptive text you find helpful in identifying this route.