
Step 1:
10.Using the COR administration form, set the Direct Agent Calling field to y for any COR to be assigned to a trunk or station user who may initiate a Direct Agent call to an EAS agent, or to be assigned to an EAS loginID that may receive Direct Agent calls.
11.If EAS agent loginID passwords are to be administered, using the Feature- Related System Parameters form, set the Minimum
12.Using the Agent LoginID form, add the desired EAS loginIDs to be associated with human agents, AUDIX ports, and/or AAS
■Name
■COR
■Coverage Path (optional)
■Security Code (optional for Demand Print feature)
■LWC Reception (optional)
■AUDIX Name for Messaging (for MIPS only, if the LWC Reception field is set to audix, or if administered coverage path for the agent has an AUDIX coverage point)
■Messaging Server Name for Messaging (for MIPS only, if the LWC Reception field is set to
■Password (optional)
■Skills - Primary/Secondary (for at least one skill)
13.For AUDIX and AAS VRU port extensions, when these ports are associated with
If AUDIX port extensions (such as for the Embedded AUDIX product) are not associated with an ACD hunt group, no administration is required for these ports as part of the cutover to EAS. For the AUDIX and/or AAS ports that are associated with ACD hunt groups, add EAS agent loginIDs for these ports, where only the following fields need to be administered:
■Name