ATT DEFINITY Communications System Generic 3 Instructions Manual

							Call Vectoring
Issue  3   March 1996
3-457
— When a Call Promp ting command (such as a successful route-to 
command) terminates vector processing, the call must b e 
dequeued and dropped from all queues that it is currently residing 
in as part of the termination process.
— If a call is waiting in an announcement queue, waiting to b e 
connected to an announcement or an announcement queue 
(announcement retry), or is currently connected to an 
announcement, and the call is dequeued from a split’s queue and 
terminates to an a gent’s voice terminal extension, the 
announcement is disconnected and ringback is connected to the 
call.
—If a
 collect digits command is being processed for a call and the 
call is dequeued from a split’s queue and terminates to an agent’s 
voice terminal extension, the 
c ollect digits command is terminated 
and ringback is connected to the call.
nCall Waiting Termination
A route-to number command in a vector can dial a single-line voice 
terminal. If the 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.
nCAS 
A 
route-to numb er command in a vector can dial CAS. If a release link 
trunk can be seized, the 
route-to number operation is considered 
successful and vector processing is terminate d.
nCOR 
Each VDN in the system has a COR associated with it.  This VDN COR is 
used to d etermine the calling permissions/restrictions, the AAR/ARS PGN, 
and the priority queuing associated with a given vector.
nCode Calling Access
A VDN cannot b e used as the argument to the code calling access feature 
access code.
If a 
route-to number command in a vector specifies the c o de calling 
feature access code, vector processing continues at the next step.
nConference
A call to a VDN can be included as a party in a conference call only after 
vector processing terminates for that call (for exam ple, after a successful 
route-to command).
nCoverage Callback
A vector call does not follow any coverage paths; therefore, coverage 
callback is not available. 
						

							Feature Descriptions
3-458Issue  3   March 1996 
nDCS Attendant Control of Trunk Group Ac cess
This allows an attendant at any node in the DCS to exercise control over 
an outgoing trunk group at a different node in the cluster. If a 
route-to 
number
 step in a vector dials a controlled trunk group, vector processing 
continues at the next step.
nDCS Attendant Display
Calls to/from a system in a DCS environment have calling/called party 
identification transparency. The name of the originator is displayed on the 
called terminal’s alphanumeric d isplay. The name of the party to whom the 
call is directed is displayed on the originator’s display.
The same display operations occur even if the originator, VDNs, and 
terminator are on different nodes in a DCS network.
nDCS Automatic Callback
Automatic Callback calls do not apply for VDNs.
nDCS Call Forward ing
Calls can be forwarded to a VDN anywhere in the DCS network. An 
attendant cannot activate/deactivate call forwarding for a VDN.
nDCS LWC
LWC messages cannot be generated for a VDN.
nDCS Voice Terminal Display
This feature allows calling and called name information (plus 
misc ellaneous identifiers) to be sent from a terminal on one node to a 
terminal on another node. The name of the originator is displayed on the 
called terminal’s alphanumeric d isplay. The name of the party to whom the 
call is directed is displayed on the originator’s display.
The same display operations occur even if the originator, VDNs, and 
terminator are on different nodes in a DCS network.
nDID 
DID trunks can dial a VDN and be subject to the treatment of its 
associated vector.
nDOD 
DOD can be p rovided via a 
route-to command within a vector.  The COR 
of the VDN is used to determine calling party permissions/restrictions.
nDo Not Disturb
Do Not Disturb cannot be activated for a VDN.
nEmergency Access to the Attendant
When night service is in effect, emergency calls to the attendant route to 
the night destination. The night destination can be a VDN. 
						

							Call Vectoring
Issue  3   March 1996
3-459
The extension num ber where emergency queue overflow redirects can be 
a VDN.
nFacility Busy Indication
The facility busy lamp indication for a VDN is always off. A facility busy 
button may be used to call a VDN.
nFR L  
If a 
route-to command dials an external number via AAR/ARS, the FRL 
associated with the VDN COR is used to determine the accessibility of a 
routing preference in an AAR/ARS pattern.
nFacility Test Calls
Provides a voice terminal user with the capability of making test calls to 
access sp ecific trunks, touch-tone receivers, time slots, and system tones. 
The test call is used to make sure the facility is operating properly. A local 
voice terminal user can make a test call by dialing an access code. An 
Initialization and Administration System (INADS) terminal user can also 
make test calls.
If a 
route-to number command in a vector specifies a Facility Test Call, 
vector processing continues at the next step.
nForced Entry of Account Codes
Requires users to dial an account code when making certain types of 
outgoing calls. To maximize system security, it is recommended that the 
Forced Entry of Account Codes feature be enabled and administered on 
the System.  The Forced Entry  of Account Codes option must be enabled 
on the System-Parameters Customer-Options form before associated 
forms and fields on forms can be administered. 
If a COR requiring entry of account codes is assigned to a VDN, the 
route-to number commands executed by the associated vector are 
unsuccessful and vector processing continues at the next step.
nIndividual Attendant Access
Each attendant console can b e assigned an individual extension number.  
That extension numb er can b e used as the argument to a 
route-to number 
command in a vector.
Each attendant has a queue that allows two incoming calls to wait. This 
individual attendant q ueue has priority over all other attendant-seeking 
calls. A call established by a 
route-to number command in a vector can 
wait in this queue and is removed from vector processing.
nIS D N - PR I
A VDN may be accessed by an ISDN-PRI trunk. ISDN-PRI calls may be 
disconnected without providing answer supervision.
A vector may initiate calls over ISDN-PRI facilities via a 
route-to number 
command. 
						

							Feature Descriptions
3-460Issue  3   March 1996 
nIntegrated Directory
VDN names and extensions are not available in the Integrated Directory 
feature.
nIntercept Treatment
A VDN cannot  be used for Intercept Treatment.
nIntercom — Automatic
A VDN cannot  be included in an intercom group.
nIntercom — Dial
A VDN cannot  be included in an intercom group. 
nInter-PBX Attendant Calls
A 
route-to numb er 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.
nIntraflow and Interflow
The functionality of intraflow and interflow may be obtained using the 
check-backup split and goto Call Vectoring commands.
Calls may intraflow from an ACD split which is not vector-controlled into 
one that is vector-controlled.
nLast Numb er Diale d
After a voice terminal user with a Last Numb er Dialed button dials a VDN 
extension, the VDN extension is stored as the Last Numb er Dialed and 
may be redialed by pressing the button.
nLW C  
LWC messages cannot be stored, canceled, or retrieved for a VDN.
nManual Message Waiting
Message Waiting buttons may point to a VDN.
nManual Signaling
A manual signaling button can point to a VDN. However, activation of a 
Manual Signaling button which points to a VDN is ignored.
nMultiple Listed Directory Numbers
The incoming destination for each CO trunk group and each FX trunk 
group used for LDNs can be a VDN. The DID LDN night extension can be 
a VDN.
nMusic-on-Hold Access
The system-wide Music-on-Hold Access feature must be administered in 
order for music to be heard when a 
wait-time c ommand with system music 
is executed. If it is not administered, the calling party receives silence. 
						

							Call Vectoring
Issue  3   March 1996
3-461
nNetwork Access — Priva te
A 
route-to numb er command in a vector can access private networks.
nNetwork Access — Public
A 
route-to numb er command in a vector can access public networks.
nNight 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.
nPriority Calling
A VDN cannot  be use d with the priority calling access code. Intercept 
tone is supplied to the user. If a
 route-to numb er in a vector specifies the 
priority calling access code, vector processing continues at the next step.
nProperty 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.
nRecorded Announcement
The first announcement extension, second announcement extension, first 
announcement delay, second announcement delay, and recurring second 
announcement do not exist for a hunt group translated as 
vector-controlled. Recorded announcements may be accessed via the 
announcement, collect digits, disc onnect, and route-to number vector 
commands.
nRemote Access
A remote access user can access a VDN.
nRingback Queuin g
External call attempts made via 
route-to commands with coverage no are 
not queue via Rin g back Queuing when all trunks are busy. External call 
attempts made via 
route-to commands with coverage yes are.
nSend All Calls
If the d estination of a 
route-to with c overage no command has the Send All 
Calls feature active, the feature activation is ignored. If there is an idle 
appearance, the call is terminated and vector processing terminates. 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.
nSubnet Trunkin g
Subnet trunking applies to AAR/ARS calls placed via a
 route-to numb er 
command. 
						

							Feature Descriptions
3-462Issue  3   March 1996 
nSystem Measurements
Hunt group measurements need different interpretation when Call 
Vectoring is used. For example, If a call  queues to splits/skills one, two, 
and three, but the caller abandons the call, the measurements show only 
split 1 as having an abandoned call (on BCMS and R3 CMS).
nTEG  
A VDN cannot  be administered as a TEG member.
A 
route-to numb er command in a vector can specify a TEG extension.
nTimed Reminder
The attendant Timed  Reminder is not available for calls placed, 
transferred, or extended to a VDN. Ve ctoring causes all other timers to be 
ignored.
nTime of Day Routing
Sin c e  a 
route-to number command in a vector can sp ecify the AAR or ARS 
access codes, the TOD routing algorithm can be used to route the call.
nTransfer
Stable trunk or internal calls (such as those that are currently in a talking 
state) can be transferred to a VDN. Calls in which vector processing is 
active are treated the same as ringing calls for transfer purposes.
nTCM 
A TCM is sent when a 
route-to command dials a seven-digit ETN or 
10-digit DDD number via AAR/ARS.  This TCM is the FRL associated with 
the VDN COR.
nTrunk Id entification by Attendant
This feature is available for incoming or outgoing calls routed through a 
VDN.
nUDP 
A 
route-to command can call a UDP extension.
nVoice Message Retrieval
If a 
route-to number command in a vector specifies the Voice Message 
Retrieval access code, vector processing continues at the next ste p.
Administration
Call Vectoring is administered on a per-system basis by the System Manager. 
For a  detailed description of the required administration see 
D EFI NIT Y 
Communications System Generic 3 Version 4 Implementation,
 555-230-655, or 
DEFI NI TY Com munications System Generic 3 V2/V3 Implementation, 
555-230-653. The following items require administration: 
						

							Call Vectoring
Issue  3   March 1996
3-463
n‘Call Vector form (one form per vector)
n‘Vector Directory Number form (one form per VDN)
n‘Hunt Group form
— Whether or not each hunt group is vector-controlled.
n‘System-Parameters Customer-Options form
The following list describes the features that are available with each 
selection on the System-Parameters Customer-Options form. The system 
administer can view this form. However, it can only be changed by AT&T 
personnel.
— Basic Call Vectoring, Call Prompting, or both must b e enabled.
Basic  Call Vectoring allows the vector to p lace calls in a queue for a 
split and to check the size of a q ueue for a p articular split. The latter 
facility is useful for d irecting a call to the sp lit where it receives the 
quickest response.
Vectoring with prompting allows the vector to collect digits from a 
caller and use these d i gits for routing the call. This facility can be 
used to p rogram an automatic answering service to direct the caller 
to the required department.
— Vectoring (G3V4 Enhanced)
Allows for the use of enhanced comparators, wildcards, Vector 
Routing Tables, and alternative audio/music sources for the 
wait-time step.
— Vectoring (G3V4 Advanced Routing)
Allows for the use of the Average Speed of Answer, VDN Calls, and 
Expected Wait Time conditionals.
— Vectoring (ANI/II-Digits)
Allows for the use of ANI and II-Digits for conditional routing.
For a comp lete description of the commands and features available 
with each customer option, see the 
DEFI NI TY Com munications 
System Generic 3 Call Vector/Expert Agent Selection (EAS) Guid e, 
555-230-520.
Administration software 
does not allow a VDN extension to be entered as data in 
the listed fields of the following screen forms:
nRecorded Announcements
nCall Coverage Answer Group
— Group Member Assignments 
						

							Feature Descriptions
3-464Issue  3   March 1996 
nCall Coverage Paths
— G3v1
—Coverage point assignments
— G3v2 and later
—Coverage Point Assignments, other than the last 
coverage point
nConsole Parameters
— CAS Bac k -up  Extension
nFeature-Related System Parameters
— ACA Long Holding Time Originating Extension
— ACA Short Holding Time Originating Extension
— Extensions With System wide Retrieval Permission
— Controlled Outward Restriction Intercept Treatment
— Controlled Termination Restriction (Do Not Disturb)
— Controlled Station-to-Station Restriction
nHospitality-Related System Parameters
— Extension of PMS Log Printer
— Extension of Journal/Schedule Printer
— Extension of PMS
— Extension to Receive Failed Wakeup LWC Messages
nHunt Groups
— Supervisor Extension
— Member Extensions
nIntercom Group
— Member Extensions
nListed Directory Numb ers
— LDN Extensions
nLoudspeaker Paging and Code Calling Access
— Extension Numbers Assigned to Codes
nPickup Groups
— Member Extensions
nRemote Access
— Remote Access Extension
nTerminating Extension Group
— Member Extensions 
						

							Call Vectoring
Issue  3   March 1996
3-465
Administration software d oes allow a VDN extension to b e entered as data in 
specific fields of the following screen forms:
nAbbreviated Dialing Lists
nCall Coverage Paths (G3v2 and later alow it as the last coverage point 
only)
nHunt Groups
— Night Destination
nListed Directory Numb ers
— Night Destination
nTrunk Groups
— Night Destination
— Incoming Destination
Administration software 
d oes not allow a VDN extension to be entered as 
auxiliary d ata for the following buttons:
nBrid ged Appearance (brdg-app)
nData Call Setup (data-ext)
Administration software 
d oes allow a VDN extension to b e entered as auxiliary 
data for the following buttons:
nRemote Message Waiting Indicator (aut-msg-wt)
nFacility Busy Indication (busy-ind)
nManual Message Waiting (man-msg -wt)
nManual Signaling (signal)
For more d etailed information on the administration of Call Vectoring, see 
DEFI NI TY Com munications System Generic 3 Version 4 Implementation, 
555-230-655, or 
DEFI NI TY Com munications System Generic 3 V2/V3 
Implementation
, 555-230-653.
Hardware and Software Requirements
Announcement hardware is required (see information on the Call Promp ting 
feature). Call Vectoring software is required. 
						

							Feature Descriptions
3-466Issue  3   March 1996 
Call Waiting Termination
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides for calls to b usy single-line voice terminals to wait and sends a 
distinctive call waiting tone to the called party.
Generally, the called party hears one quick b urst of tone when a c all from another 
voice terminal user is waiting, two quick bursts of tone when an 
attendant-handled or an outside call is waiting, or three quick bursts of tone 
when a Priority Call is waiting. The called party hangs up on the current call and 
immediately receives ringing from the waiting call. For G3i-Global, G3V2, and 
later releases, the defaults for the number of ring bursts may be changed by the 
system administrator.
The call in progress at the voice terminal can be placed on hold in order to 
answer the waiting call. After answering the waiting call, the voice terminal user 
can return to the held call or to ggle back and forth between the two calls. The 
single-line voice terminal user can only be connected to one call at a time.
The calling p arty hears special audible ringback tone if the call is allowed to wait. 
If C all Waiting is denied, the calling party hears b usy tone. Only one call can wait 
at a time.
NOTE:
Special ring types are not supported over DID facilities.
The burst(s) of tone heard by the called voice terminal user is not heard by other 
parties on the call.
An internal caller can activate LWC or Automatic Callback after Call Waiting has 
been activated.
A Priority Call and an attendant-handled call can wait for the voice terminal to 
become idle even if the Call Waiting Termination feature is not assigned.
Calls to a DDC or UCD group voice terminal cannot wait. However, such calls 
can enter the group queue (if provided) unless the queue is full.