AT&T DEFINITY Generic 3 Manuale Utente
Step 4: Pre-EAS Cutover Administration for Messaging
Server
Server
Issue 4 September 1995
K-7
NOTE:
On the MIPS, the AUDIX Name for Messaging field on the Agent LoginID
form must be set to the correct AUDIX name to provide proper AUDIX
coverage of calls made to EAS agents, or to leave LWC messages for EAS
agents if LWC reception to AUDIX is set up for the agents’ loginIDs.
form must be set to the correct AUDIX name to provide proper AUDIX
coverage of calls made to EAS agents, or to leave LWC messages for EAS
agents if LWC reception to AUDIX is set up for the agents’ loginIDs.
Refer to "Step 1: Pre-EAS Cutover Administration for the G3V2 (or later) Switch"
for information on how to administer EAS loginIDs for AUDIX port extensions on
the switch.
for information on how to administer EAS loginIDs for AUDIX port extensions on
the switch.
Step 4: Pre-EAS Cutover
Administration for Messaging Server
Administration for Messaging Server
If EAS agents are administered with coverage paths that route to a Messaging
Server coverage point, the Messaging Server adjunct must be administered with
extension information that correlates to these EAS loginIDs.
Server coverage point, the Messaging Server adjunct must be administered with
extension information that correlates to these EAS loginIDs.
NOTE:
The Messaging Server Name for Messaging field on the Agent LoginID
form must be administered to provide proper Messaging Server coverage
of calls made to EAS agents, or to leave LWC messages for EAS agents if
LWC reception to AUDIX is set up for the agents’ loginIDs.
form must be administered to provide proper Messaging Server coverage
of calls made to EAS agents, or to leave LWC messages for EAS agents if
LWC reception to AUDIX is set up for the agents’ loginIDs.
Step 5: Pre-EAS Cutover
Administration for ASAI
Administration for ASAI
For customers who utilize ASAI-based applications for call center operations, the
cutover to EAS may necessitate an upgrade of the ASAI-related application
software on the adjunct. If the customer uses OCM (Outgoing Call Management),
the upgrade to EAS requires that specialized vectors be administered to handle
the launching of calls from VDNs (as opposed to the non-EAS environment where
OCM calls are launched from splits). For more information on the procedures to
convert an ASAI application for EAS, refer to
cutover to EAS may necessitate an upgrade of the ASAI-related application
software on the adjunct. If the customer uses OCM (Outgoing Call Management),
the upgrade to EAS requires that specialized vectors be administered to handle
the launching of calls from VDNs (as opposed to the non-EAS environment where
OCM calls are launched from splits). For more information on the procedures to
convert an ASAI application for EAS, refer to
DEFINITY Communications System
CallVisor ASAI Planning
, 555-230-222.
Step 6: EAS Cutover
After all pre-EAS activities have been completed, the EAS feature may be
activated. Just prior to the EAS cutover, a tape backup of the current switch
translations should be made for possible recovery purposes in case some
difficulty is encountered during cutover. In particular, since the transition to EAS
results in the removal of all ACD hunt group members, the pre-EAS tape backup
could save a considerable amount of time in restoring non-EAS hunt group
translations if the cutover to EAS is not completed.
activated. Just prior to the EAS cutover, a tape backup of the current switch
translations should be made for possible recovery purposes in case some
difficulty is encountered during cutover. In particular, since the transition to EAS
results in the removal of all ACD hunt group members, the pre-EAS tape backup
could save a considerable amount of time in restoring non-EAS hunt group
translations if the cutover to EAS is not completed.