When does a call not interflow?

Last Updated : Sep 08, 2012 |

A call does not interflow under the following circumstances:

  • If the interflow-qpos conditional is not met.

    As with other conditionals, the route-to number... if interflow-qpos step or the goto step/vector branch is executed only if the conditional is met, otherwise vector processing goes to the next step.

  • If the call is not in a split or skill queue, or not in the eligible portion of the queue when the conditional step is executed.

    If the call is not in queue when the route-to number... if interflow-qpos step is executed, a vector event is logged and vector processing continues at the next step.

    If the call is not in queue when a goto... if interflow-qpos step is executed, the queue position of the call is treated as infinite in determination of the conditional.

    Note:

    A vector event is not logged if the call is in queue, but is not in the eligible portion of the queue.

  • Interflow failure or LAI rejection

    Interflow failure or LAI rejection will also go to the next step. Route-to operation and feature interactions will be the same as other configurations of the route to number command, for example, route to number ___ with cov _ if digit CM x.

The following table outlines what action is taken for different cases of interflow eligibility.

Case

Action at route-to step

Action at goto step

The call not eligible for interflow.

The call is never routed.

Treat as if the interflow queue position is infinite.

The call is not in any split queue.

The call is treated as if the interflow queue position is infinite.

Treat as if interflow queue position is infinite.

The call is eligible for interflow.

Act according to the conditional.

Act according to the conditional.