OUTFLOWCALLS

최근 업데이트 : Aug 22, 2022 |

The OUTFLOWCALLS item is included in the following database tables:

Split/skill tables

The number of CALLSOFFERED that are redirected to another destination while queued to this split/skill. This can happen under different circumstances, depending on the communication server release and on whether the Vectoring feature is active or not.

On communication servers without the Vectoring feature, a call can be counted as OUTFLOWCALLS in any of the following instances:

  • The call intraflowed or interflowed.

  • The split/skill call forwarding was active.

  • A ringing ACD call was answered using call pickup.

  • A ringing ACD call redirected on no answer.

On communciation servers with vectoring, a call can be counted as OUTFLOWCALLS in any of the following instances:

  • A ringing ACD call redirected on no answer.

  • The call rang at an agent in this split/skill and was answered using call pickup.

  • The call was routed to another VDN.

  • The call routed to a number or digits.

  • The call queued to a messaging split/skill.

  • The call queued to this split/skill as the primary split/skill and was answered by an agent in another split/skill, rang at an agent in another split/skill and then abandoned or was redirected by the Redirection on No Answer feature.

OUTFLOWCALLS includes INTERFLOWCALLS, NOANSREDIR, and SLVLOUTFLOWS.

This is a cumulative item.

Vector tables

The number of INCALLS that are redirected to another destination by way of a “go to” vector command or by a “route to” or “adj rout link” command to a destination other than a split/skill or direct agent. Calls that route to a split/skill or direct agent by way of a “route to”, “adj rout link”, or “messaging split/skill” vector command are still tracked in the vector. OUTFLOWCALLS includes GOTOCALLS and INTERFLOWCALLS.

This is a cumulative item.

VDN tables

The number of INCALLS that are redirected to another VDN or to a destination outside the communication server by way of a “route to” or “adj rout link” vector command, or calls that are redirected to another VDN by the Redirect on No Answer feature. Calls are only counted as outflows from the VDN when they are redirected to another VDN or to an off-communication server destination. Calls in the VDN that route to other destinations, such as split/skills or extensions, are not counted as outflows from the VDN. OUTFLOWCALLS includes INTERFLOWCALLS and SLVLOUTFLOWS.

This is a cumulative item.