AAR/ARS Partitioning

The Class of Restriction (COR) assigned to the VDN determines the Partition Group Number (PGN). The PGN in turn determines the AAR/ARS routing tables used by route-to commands.

ASAI

For direct calls to a VDN, the adjunct routing command operates like the route to digits command with coverage set to y. For calls that cover to a VDN, the adjunct routing command operates like the route to digits command with coverage set to n.

Attendant

Vectors connect calls, covering to a VDN, to an attendant queue or a hunt group. Internal calls that route to an attendant display the COR of the originating station if the attendant presses the display COR button.

An attendant cannot establish a conference with a call covering to a VDN if the call is in vector processing. If a call placed to a local destination has covered to a VDN and the attendant attempts to add this call to a conference, conferencing is denied until the call has completed vector processing.

If the attendant extends a call to a local destination that covers the call to a VDN, the attendant’s return call timer cancels when vector processing begins and the Return Call button does not affect the call.

If a call covers to a VDN and is then routed to an attendant, the attendant can transfer the call to another VDN.

AUDIX

Calls that cover to a VDN can be routed to an AUDIX by the route-to or messaging vector commands. Calls that cover to a VDN can be subsequently transferred to the AUDIX. Calls can also be transferred out of an AUDIX to a VDN.

Automatic Call Distribution (ACD)

A VDN can be the last point in an agent’s coverage path for direct agent calls.

Call Coverage

A VDN cannot be a member of a coverage answer group. A vector cannot route a covered call to a coverage answer group. Coverage Callback and Leave Word Calling work normally when a vector delivers a call to a covering user.

Call Forwarding

Calls that have covered to a VDN cannot be redirected by Call Forwarding unless the Cvg Enabled for VDN Route-To Party field applies.

Call Park

A parked call does not cover to a VDN. When a call is parked at an extension with a VDN in its coverage path, the call continues to ring the extension. If the call parks to a hunt group extension and the call is in queue, the call remains in the queue until it is retrieved, answered by an agent, or abandoned by the caller. A vector event is generated for the calls when the administered coverage criteria are met.

Once a call covers to a VDN, Call Park cannot be established until the call is delivered to an extension and vector processing ends.

Call Vectoring

The COR assigned to a VDN determines the PGN. The PGN in turn determines the AAR/ARS routing tables used by route-to commands.

When a call covers to a VDN, VDN Override has no effect on the display shown on an answering display. This station shows the normal display for a covered call.

Adjunct Routing: For direct calls to a VDN, the adjunct routing command operates like the route to digits command with coverage set to y. For calls that cover to a VDN, the adjunct routing command operates the same as a route to digits command with coverage set to n.

Converse: Covered calls to a VDN work with the converse command. If a call in vector processing is connected to an agent in a converse split, the agent cannot activate Consult, Coverage Callback, or Coverage Leave Word Calling.

Messaging: The messaging command handles covered calls differently depending on whether an extension is specified in the command. If the command messaging split xxxx extension none is used, the mailbox of the principal extension is used for the call. The number of the principal extension and the reason for redirection are passed to the messaging adjunct in the CONNECT message.

When an extension is specified in the messaging command, no information on the principal extension is passed to the adjunct. Instead, the number of the extension specified in the command is passed to the adjunct in the CONNECT message along with the reason for redirection. The mailbox for the specified extension is used.

Route-to: A call covering to a VDN can be routed to any valid destination by the route-to command. When the route-to command terminates a covered call locally, information identifying the principal and the reason for redirection are retained with the call. This information can be displayed on display phones or passed to an AUDIX or a Message Center system.

Class of Restriction

The COR assigned to the covering VDN governs the vector routing of the call.

Conference

Calls in an established conference do not cover to a VDN. Once a call covers to a VDN, a conference cannot be established until the call is delivered to an extension and vector processing ends.

Consult

The feature normally uses a Temporary Bridged Appearance on the principal’s set. Call coverage to a VDN removes the Temporary Bridged Appearance from the principal’s set, but the Consult feature still works.

Hunt Groups

A VDN can be the last point in a hunt group’s coverage path. If the coverage vector for a split or hunt group routes calls to another using a route-to or messaging command, calls queue at the second resource with the queue priority assigned for the first split or hunt group. If a queue-to, check, or converse command is used, calls queue at the second split or hunt group with the priority specified in the command.

If an inflow threshold has been assigned to a hunt group, the group does not allow new calls to queue when the oldest call in queue has exceeded the threshold. Therefore, covered calls are not connected to a hunt group when the group’s inflow threshold has been exceeded. The interaction can also occur when a messaging split, or route-to command routes a covered call to a split that is not vector-controlled.

Look-Ahead Interflow

For calls that have covered to a VDN, LAI works like a route-to digits/number vector command with coverage = n. Any Dialed Number Identification Service (DNIS) digits sent with the interflowed call indicates the VDN to which the call covered, not any VDN the call encountered before it went to coverage.

Night Service

Calls that have covered to a VDN cannot be redirected by Night Service.

Personal CO lines (PCOL)

A VDN can be assigned as the last point in a PCOL coverage path.

Phone Display

Calls covering to a VDN and then directed to an agent in a split/hunt group by a queue-to, check, converse, or route-to command display the following information to the agent.

a=EXT 3174   to   EXT 3077     b

In this example, station A calls station B. Station B is busy, and the call covers to a VDN.

Redirection on No Answer (RONA)

RONA applies to calls that cover to a VDN. If the vector associated with the VDN queues the call to a resource (for example, a split or agent) that uses RONA, the call can be requeued for the same resource. The call cannot be redirected, however, since it has already covered to the VDN unless RONA occurs as a result of a route-to command with cov=y vector step and the Cvg Enabled for VDN Route-To Party field applies.

Terminating Extension Groups

A VDN can be assigned as the last point in the coverage path for a Terminating Extension Group (TEG), since it has already covered to the VDN.

Transfer

Calls can be transferred to extensions that cover to a VDN. Users who receive a covered call can transfer the call to a VDN. If a transfer attempt goes to coverage and covers to a VDN, the user at the answering station can complete the transfer by pushing the Transfer button or by flashing the switchhook on an analog station.

Calls that cover to a VDN can be subsequently transferred to AUDIX. Calls can also be transferred out of AUDIX to a VDN.