Avaya Communication Manager Administrator's Manual page 1511

If an announcement is invalid during vector processing, the treatment is the same as if the announcement
did not exist. Specifically, call processing continues and does not wait for an announcement that does not
exist. Any previous feedback preceding the announcement continues:
•
An announcement step continues at the next step
•
A wait step that references an announcement continues after any specified wait treatment expires
•
A disconnect step disconnects immediately
•
A collect step continues at the next step
•
If the VDN of Origin Announcement (VOA) does not exist, vector processing delivers the call to
the agent, bypassing the VOA.
The Outgoing Intercept Treatment
announcement administration. The Multi-Location feature changes that entire screen into an indexed
screen with indices 1-8. Since customers will be able to assign up to 8 different MFC announcements,
there is no need to allow short extensions to be entered into this field.
Interactions
Attendant
This feature provides a way to administer multiple attendant codes. This does not provide a way to
administer multiple attendant groups. Only one attendant group is allowed per switch, unless you have
attendant partitioning. This feature does provide a way to support multiple local centralized answering
points. The LCAPs do not utilize attendant groups to support this.
Attendant Vectoring
If attendant vectoring is enabled, it will take precedence over any local attendant codes administered.
This is how attendant vectoring currently works. Attendant seeking or "dial 0" calls (
Codes , Attendant Code
Code (FAC) screen) are processed using call vectors and not using the normal attendant console call
routing.
Automatic Circuit Assurance
The field
ACA Referral Destination
the
Attd Administration
Access Code on the Feature Access Code (FAC) screen. This field requires that an attendant group
exists.
Automatic Wakeup
If a station has automatic wakeup requests pending when the
the wakeup requests are canceled.
Call Forwarding
Any call forwarding information stored with an extension is lost when using the change extension-station
command. If the station that is changed with the
station, the extension using that forwarded-to extension must be manually updated. If not, calls are not
forward correctly.
Administrator's Guide for Avaya Communication Manager
November 2003
field on the Multi-frequency System Parameters screen allows for
on the Dial Plan screen or
on page 1 of the System Features Parameters screen requires either
on the Dial Plan Analysis Table screen, or administration of the
change extension-station
Attendant Access Code on the Feature Access
change extension-station
command is a forwarded-to
Feature Reference
Dial plan
Local Attendant
Attendant
command is run,
1511