Administrator's Guide

Features and technical reference
555-233-5061484 Issue 5 October 2002
See ‘‘QSIG to DCS TSC Gateway screen’’ on page 1085 to permit authorized
callers from remote locations to access your system.
See ‘‘Trunk Group’’ on page 1233 to require an authorization code be dialed to
complete incoming calls on a trunk group.
See ‘‘Setting up authorization codes’’ on page 404 for instructions.
Automated attendant
Automated Attendant uses vector commands to allow a caller to enter the
extension of the party that he or she would like to reach. The call is routed by the
vector to that extension.
See Avaya MultiVantage™ Call Center Software Call Vectoring and Expert Agent
Selection (EAS) Guide for a detailed description of Automated Attendant and for a
sample vector that can be used for Automated Attendant. The guide contains
information that is critical to the effective and efficient use of Automated
Attendant.
You can administer any display-equipped phone or attendant console with a Caller
Information CALLR-INFO button. The button displays digits collected for the
last
collect digits command.
Automated Attendant competes with several features for ports on the call
classifier — detector circuit pack or equivalent.
Interactions
■ AUDIX
Automated Attendant gives the caller the option of leaving a message or
waiting in queue for an attendant. See “Message Collection” in Chapter 5
of the Avaya MultiVantage™ Call Center Software Call Vectoring and
Expert Agent Selection (EAS) Guide.
■ Authorization Codes
If authorization codes are enabled, and a
route-to command in a prompting
vector accesses AAR or ARS, if the Vector Directory Number’s (VDN’s)
FRL does not have the permission to use the chosen routing preference,
then the system does not prompt for an authorization code and the route-to
command fails.