Route Policy

The Oracle Enterprise Communications Broker (OECB) includes a route configuration control called Policy that allows you to alter the behavior of routes. As the OECB assembles hops together to create a complete route, it considers and acts on the policies configured on each route entry.

You configure a route Policy from the Policy Entries entry dialog. The parameter values include:

Policy [ Deny | StopRecurse ]

The default setting is empty, which imposes no policy on the route.

The Deny policy in any resultant SIP routes to a destination prevents the OECB from forwarding a SIP request to the destination point in question. You can use the Deny policy to prevent sessions between two endpoints for policy or cost reasons. Consider this route entry.

Source Agent Calling Number Destination Agent Called Number Route Cost Policy
Class_B * Protect_Agnt * Transit_Agnt 0 Deny

The preceding route entry is designed to prevent calls passing through the agent named Class_B from reaching any endpoint behind Protect_Agnt. This route entry may be installed as part of one or multiple routes that could potentially reach Protect_Agnt. The routing engine recognizes the presence of this entry and rejects the call.

To expand upon the example, consider this route.

Source Agent Calling Number Destination Agent Called Number Route Cost Policy
Class_A * Protect_Agnt * Transit_Agnt 0 StopRecurse

The preceding route configuration allows traffic to reach Protect_Agnt as long as it originates througha the agent named Class_A.

The StopRecurse policy stops further attempts to forward a SIP request to a given destination if that route stops responding. The StopRecurse policy can prevent the system from forwarding calls on routes that are cost-prohibitive or might cause loops in SIP call flows.

For example, consider the scenario where an endpoint can be reached using two routes.

  • Route 1: Agent_1 to Agent_2 (StopRecurse) to PBX
  • Route 2: Agent_3 to PSTN

Route 1 uses a StopRecurse policy defined on the hop between Agent_2 and PBX. The OECB stops processing the call if Route 1 does not receive a successful response. This configuration can prevent calls initially targeted for Route 1 from using the PSTN.