AP Demand Print: A VDN cannot be used as an argument to the feature access code for AP Demand Print.
Attendant Control of Trunk Group Access: If a route-to step in a vector dials a controlled trunk group, vector processing continues at the next step.
Attendant Recall: Attendant Recall to a VDN is blocked.
Screen Field
Abbreviated Dialing Lists
Call Coverage Paths Allow it as the last coverage point only
Hunt Group Night Destination
Listed Directory Numbers Night Destination
Trunk Groups ● Night Destination
● Incoming Destination
Call Vectoring
Authorization Codes: If authorization codes are enabled, and if a route-to command in a prompting vector accesses AAR or ARS and the VDN’s FRL does not have the permission to utilize the chosen routing preference, then no authorization code is prompted for and the route-to command fails.
Automatic Alternate Routing (AAR)/Automatic Route Selection (ARS): Any route-to command in a vector can dial an AAR/ARS FAC followed by other digits. It cannot dial only the FAC.
Automatic Callback: Automatic Callback cannot be used for calls placed to a VDN.
Bridged Call Appearance: VDN extensions cannot be assigned to bridged appearance buttons. A route-to command to an extension with bridged appearances updates bridged appearance button lamps.
Busy Verification - Terminals, Trunks: Busy verification of VDNs is denied and intercept tone is returned.
Call Coverage: A VDN may be administered as the last point in a coverage path.
Call Forwarding: Calls can be forwarded to a VDN. Calls placed by a route-to command to an extension that has call forwarding activated are forwarded.
An attendant or phone with console permission cannot activation/deactivation call forwarding for a VDN.
An attendant or phone with console permission cannot activation/deactivation call forwarding for a vector-controlled hunt group.
Call Detail Recording: You can administer the Feature Related System Parameters screen so that the VDN extension is used in place of the Hunt Group or Agent extension. This overrides the Call to Hunt Group - Record option of CDR for Call Vectoring calls.
If a vector interacts with an extension or group that has Call Forwarding All Calls active, normal Call Forwarding/CDR interactions apply.
For incoming calls to a VDN, the duration of the call is recorded from the time answer supervision is returned.
If answer supervision is returned by the vector, and the call never goes to another extension, then the VDN extension is recorded as the called number in the CDR record.
If the call terminates to a hunt group, then the VDN, hunt group, or agent extension is recorded as the called number as per the administration described above.
If the call terminates to a trunk, then the following two CDR records are generated:
● An incoming record with the VDN as the called number and the duration from the time answer supervision was provided to the incoming trunk.
● An outgoing record containing the incoming trunk information as the calling number and the dialed digits and the outgoing trunk information as the called number.
ACD call center features
Outgoing vector calls generate ordinary outgoing CDR records with the originating extension as the calling number.
No Ineffective Call Attempt records are generated for Call Vectoring route-to commands that are unsuccessful.
Call Detail Recording - Account Code Dialing: If a route-to number command in a vector specifies an CDR account code, vector processing continues at the next step.
Call Park: Calls cannot be parked on a VDN.
Call Waiting Termination: If an extension is busy and has call waiting termination
administered, the route-to with cov n operation is considered unsuccessful and vector processing continues at the next step. Route-to with cov y is successful (call will wait) and vector processing terminates.
Class of Restriction: Each VDN in the system has a COR associated with it. This VDN COR is used to determine the calling permissions/restrictions, the AAR/ARS PGN, and the priority queuing associated with a vector.
Code Calling Access: A VDN cannot be used as the argument to the code calling access feature access code.
If a route-to number command in a vector specifies the code calling feature access code, vector processing continues at the next step.
Conference: A call to a VDN can be included as a party in a conference call only after vector processing terminates for that call.
Data Restriction: Music will play on calls from data restricted extensions when the call receives music as the result of a wait-time vector step.
Facilities Restriction Level: If a route-to command dials an external number using AAR/
ARS, the FRL associated with the VDN COR is used to determine the accessibility of a routing preference in an AAR/ARS pattern.
Facility Busy Indication: The facility busy lamp indication for a VDN is always off. A facility busy button may be used to call a VDN.
Facility Test Calls: If a route-to number command in a vector specifies a Facility Test Call, vector processing continues at the next step.
Call Vectoring
Intercept Treatment : A VDN cannot be used for Intercept Treatment.
Inter-PBX Attendant Calls: A route-to number command in a vector can dial the Inter-PBX Attendant. If the call attempts to access a controlled trunk group, vector processing continues at the next step.
Intraflow and Interflow: The functionality of intraflow and interflow may be obtained using the check and goto Call Vectoring commands.
Calls may intraflow from an ACD split or skill that is not vector-controlled into one that is vector-controlled.
Leave Word Calling: LWC messages cannot be stored, canceled, or retrieved for a VDN.
Night Service: A VDN can be administered as a night service destination. Route-to commands that route to destinations with night service activated redirect to the night service destinations.
Priority Calling: A VDN cannot be used with the priority calling access code. Intercept tone is supplied to the user. If a route-to number in a vector specifies the priority calling access code, vector processing continues at the next step.
Property Management System Interface: VDNs cannot be used with the following features and functions: Message Waiting Notification, Check-In, Check-Out, Room Status, and
Automatic Wakeup.
Recorded Announcement: The first announcement extension, second announcement extension, first announcement delay, second announcement delay, and recurring second announcement do not exist for a vector-controlled hunt group.
Redirection on No Answer: If an ACD split or skill or direct agent call is not answered after an administered number of rings, RONA can redirect that call to a VDN for alternate treatment.
Ringback Queuing: External call attempts made using route-to commands with coverage no are not queued using Ringback Queuing when all trunks are busy. External call attempts made using route-to commands with coverage yes are.
Send All Calls: If the destination of a route-to with coverage no command has the Send All Calls feature active, calls are not redirected. If there is an idle appearance, the call terminates and vector processing stops. If not, vector processing continues at the next step.
If the Send All Calls button is pressed after a vector call is terminated, button activation is denied.
Time of Day Routing: Since a route-to number command in a vector can specify the AAR or ARS access codes, the TOD routing algorithm can be used to route the call.
Timed After Call Work (ACW): A Timed ACW interval can be assigned to a VDN.
Timed Reminder: The attendant Timed Reminder is not available for calls placed, transferred, or extended to a VDN. Vectoring causes all other timers to be ignored.
ACD call center features
Transfer: Calls can be transferred to a VDN.
Traveling Class Mark: A TCM is sent when a route-to command dials a seven-digit Electronic Tandem Network (ETN) or 10-digit DDD number using AAR/ARS. This TCM is the FRL associated with the VDN COR.
VDN in a Coverage Path: A call covering to a VDN can be routed to any valid destination by the call vectoring command route-to. The coverage option for the route-to digits command is disabled for covered calls. In other words, the route-to digits with coverage=y functions like the route-to digits with coverage=n command when processing covered calls. 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 Message Center system.
The class of restriction assigned to a VDN determines the partition group number (PGN). The PGN in turn determines the AAR or 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 telephone. This station will show the normal display for a covered call.