1. User's Guide
  2. Using Policy to Refine Routing
  3. The Redirect Action

The Redirect Action

The redirect action causes the Oracle Enterprise Communications Broker (OECB) to redirect the incoming call through a particular agent by way of policy. You can use redirect to send a call to an external resource or service, such as a transcoding Session Border Controller or a call-recorder.

When applied, the policy engine performs an additional routing lookup for the call to the specified redirect agent. The system pre-pends additional hops from the redirect to the hops that were already calculated for the current route. The redirect action adjusts the routes to send the call to the specified redirect agent first, and then to the call destination.

Redirect action configuration includes theHairpin signaling field. When you enable Hairpin signaling, the OECB routes the call to the redirect agent first, then routes it back to the OECB before sending it to the original destination. Hairpin signaling ensures that the OECB can route the call even when the redirect agent cannot reach the final destination. Note that keeping Hairpin signaling disabled eliminates the extra hops and extra session required when the destination is reachable by the redirect agent.

The OECB uses the same source agent, calling number, and called number parameters as the original call to reach the redirect agent. Only the dest-agent parameter gets replaced with the redirect agent specified in the redirect policy action. Take special care with default routes or routes that use a wildcard in the dest-agent field because such routes can become part of the path to the redirect agent.

Note the following details when evaluating and configuring redirect action:

  • Hops incurred by the redirect action do not affect the route cost. The system determines the route-set and order-set before the redirection takes place.
  • The system does not evaluate policies applied to the redirect routes, which prevents redirection loops and other undesirable behavior.
  • The system uses only the first (lowest cost) redirection path, which prevents the exponential increase of backup paths.
  • You can configure redirection to agent groups, which operate normally.
  • The system applies the same routing parameters of the call (source agent/number and dest number) to the redirection route lookup as the original route.
  • The system does not use default routes ('*' for all match patterns) for redirection. When the OECB finds no valid routes for the redirect, the OECB rejects the call.