Criteria for success/failure of Call Vectoring commands

Last Updated : Oct 19, 2012 |

The following table summarizes the success and failure criteria for various vector commands.

Note:

Skill replaces split if you enable Expert Agent Selection.

Call Vectoring command success/failure criteria

adjunct routing link

Fails if any of the following is true:

  • VDN’s COR does not permit routing to the adjunct-supplied destination

  • TAC/ARS/AAR code is invalid

  • Specified agent is not logged into the specified split for a direct agent call

  • Local extension is not in the dialplan

  • Invalid number was dialed

Stop any wait-time or announcement step (if present). Continue vector processing with the next sequential step.

Otherwise, succeeds

Route the call and provide feedback

announcement

Fails if specified announcement is not administered, not recorded, or busied out.

Continue vector processing with the next sequential step

Otherwise, succeeds

Play the announcement, and continue at the next sequential step

busy

Always succeeds. Central Office (CO) without answer supervision trunk callers will not hear the busy tone.

Exit vector processing, then play the busy tone for 45 seconds before dropping the call. (Unanswered CO trunk calls receive 45 seconds of ringback.)

check split

Fails if any of the following are true:

  • Vector conditional is false

  • Split’s queue is full

  • Split is not vector-controlled

  • Call is already queued at the specified priority to the specified split

  • Call is already queued to three different splits

Continue vector processing with the next sequential step

Otherwise:

Succeeds, and the call is terminated to an agent.

Exit vector processing, and pass control to call processing

Succeeds, and the call is queued or requeued in the specified split at the specified priority.

Continue vector processing with the next sequential step

collect digits

Fails if any of the following are true:

Call originates from an outside caller who is not using a touch-tone telephone

Call Prompting timer takes effect, command times out, and vector processing continues at the next vector step.

No TTR is in the system, or the TTR queue is full

Continue vector processing at the next step

Caller enters fewer digits than the maximum specified

Call Prompting timer takes effect, command is terminated, and any digits collected prior to the time-out are available for subsequent processing.

Otherwise, succeeds

Continue vector processing at the next step

consider locations

Fails if any of the following are true:

  • No BSR application administered in active VDN

  • Location not administered in BSR application

  • Status Poll VDN number not administered in BSR application

  • Status Poll VDN number is invalid

  • Status Poll fails because all trunks are busy

Continue vector processing with the next sequential step

Otherwise:

Succeeds, but takes no action if polling of specified location is suppressed.

Continue vector processing with the next sequential step

Succeeds, and place status poll call to the status poll VDN.

Suspend vector processing until status poll response received

consider split

Fails if any of the following are true:

  • VDN skill (1st, 2nd, 3rd) is used in consider step but not administered for active VDN.

Continue vector processing with the next sequential step

Otherwise: Succeeds, and the status of the local split is evaluated.

converse-on split

Fails if any of the following are true:

  • Converse split queue is full

  • Converse split is not vector-controlled

  • Auto-available split is in effect, and all agents are logged out by Redirection on No Answer (RONA)

Continue vector processing with the next sequential step

Otherwise: Succeeds, call is delivered to the converse split, and (if administered) digits are outpulsed to the VRU. The caller is connected to the VRU, the voice response script is executed, and (if necessary) digits are outpulsed to Communication Manager.

Continue vector processing with the next sequential step

disconnect

Always succeeds

Play the announcement (if specified). Then drop the call

goto step and goto vector

Fails if the step condition is not met.

Continue vector processing with the next sequential step

Succeeds if the step condition is met.

goto step - continue vector processing with the destination step

goto vector - continue vector processing with the first non-blank step of the destination vector

messaging split

Fails if any of the following are true:

  • Specified split is not a messaging-system split

  • Specified extension is invalid

  • Messaging split queue is full

  • Messaging split is not vector controlled and has no working agents (none logged in or all in AUX work mode)

  • Communications link with the messaging-system adjunct is inaccessible

Continue vector processing with the next sequential step

Otherwise, succeeds.

Terminate vector processing

queue-to split

Fails if any of the following are true:

  • Split’s queue is full

  • Split is not vector-controlled

  • Call is already queued at the specified priority to the specified split

  • Call is already queued to three different splits

Continue vector processing with the next sequential step

Otherwise:

Succeeds, and the call is terminated to an agent.

Exit vector processing, and pass control to call processing

Succeeds, and the call is queued or requeued in the specified split at the specified priority.

Continue vector processing with the next sequential step

reply best

Fails if any of the following are true:

  • Incoming call is not ISDN or SIP

  • Incoming trunk group is not administered for shared UUI or for QSIG Supplementary Service

Drop the call

Otherwise: Succeeds and returns status data of best resource found in consider series.

Drop the call

return

Fails if there is no return destination data stored for the call

Continues vector processing on the subsequent vector step. If this is the last step, the step is treated as a stop step.

Succeeds when there is return destination data

Returns to the calling vector

set

Always succeeds

If there is an invalid assignment, a vector event is generated

Continues to the next step with an invalid assignment or not

stop

Always succeeds

Exit vector processing. Control is passed to normal call processing. Any queuing or treatment in effect remains in effect. Call is dropped if not queued.

wait time

Always succeeds

Connect the specified treatment and pass control to the delay timer. Any feedback is continued until other feedback is provided.