Call Coverage

When the Display VDN for Route-to DAC feature is activated for a call, and a vector-initiated direct agent call is made to an EAS agent having a coverage path that has other agents as coverage points, the active VDN name associated with the call is displayed on a covered-to agent’s station display instead of the originally-called EAS agent’s LoginID extension.

Call Forwarding

Display VDN for Route-to DAC has no impact on the Call Forwarding feature.

Station Conference/Transfer

When an EAS agent transfers or conferences a vector-initiated direct agent call that has the Display VDN for Route-to DAC feature activated to another agent or station user, the station display of the answering agent or station does not show the active VDN name that was previously displayed for the call. This is consistent with the existing station display treatment for transferred or conferenced calls that have a VDN name shown as the to party for a call.

VDN Override

Active VDN name station display rules for the VDN Override feature are applied to the Display VDN for Route-to DAC feature. For example, if an incoming trunk call is routed through a VDN where the VDN Override feature is enabled, and the call is routed to a second VDN by a route-to number vector step where the Display VDN for Route-To DAC? option is set to y, the station display for an EAS agent that receives a subsequent vector-initiated direct agent call shows the second VDN’s name for the call instead of the called EAS agent’s LoginID extension.

Redirect on No Answer (RONA)

The Display VDN for Route-to DAC feature is activated only for vector-initiated direct agent call to an EAS LoginID extension. When the RONA timer expires after the call is not answered, one of the following results occurs:

• If subsequent vector processing again routes the call to an EAS LoginID extension by means of the Direct Agent Calling (DAC) feature, and the Display VDN for Route-to DAC feature is enabled, the active VDN name is shown on the covered-to agent station display.

• If subsequent vector processing again routes the call to an EAS LoginID extension by means of the DAC feature, and the Display VDN for Route-to DAC feature is not enabled, then the EAS LoginID for the covered-to agent is shown on their station display.

Messaging systems for EAS Agents

The Display VDN for Route-To DAC feature has no interaction with messaging systems for a vector-initiated direct agent call that is routed to an EAS agent and subsequently covers to the agent’s messaging-system mailbox.

Adjunct Routing

If a call is routed through a VDN having the Display VDN for Route-to DAC feature set to y, and an adjunct route vector step is executed that results in a direct agent call to an EAS agent, the active VDN name is displayed on the routed-to agent’s station display instead of the called EAS agent’s LoginID.