Nortel Meridian Meridian 1 Implementation Manual page 54

Page 54 of 208
6
Figure 16
DNROUTE example
Figure 17
OFRT example
7
553-3001-358 Standard 1.00
The ACD login ID must match the MICB physical port connection to the
Meridian SL-100. The ACD agents login must be in descending order,
otherwise the MICB card cannot login the agents. After adding the ACD login
IDs, enter the first agent's ID in the MICB BUI (see
Settings" on page
Note: If using Enhanced ACD Login to login specific ACD agent IDs,
datafill tables CUSTACD and ACDENLOG to make sure MICB ACD agents
can log in.
AREACODE OFCCODE STNCODE DNRESULT
------------------------------------------------------------------
214 997 1601 FEAT ACD MICB PRIM 0 0
214 997 1602 FEAT ACD MICB SUPP 0
214 997 1603 FEAT ACD MICB SUPP 0 (Also used for TUI and Assistant DN)
.......cont until # of ports needed are configured
214 997 1701 FEAT ACD MICB SUPP 0 0
214 997 1702 FEAT ACD MICB SUPP 0
214 997 1703 FEAT ACD MICB SUPP 0
.......cont until # of ports needed are configured
Note: The DNs in bold are only required when using single access DNs.
RTE RTELIST
---------------------
600 (RT 214 NP LCL 9971400 Y N $) $
Note: Use this table to forward, through night service, the ACD main
conference and chairperson conference to the MICB ACD prime DN. This
example uses 997 1400 as the ACD Prime DN.
Define each MICB port as an M2616 digital telephone set. Define MICB ports
as ACD agents in SERVORD. Define the digital set keys as follows:
• Key 1: ACD
• Key 1: M0200
• Key 1: COMMUNICTR
• Key 2: Secondary DN
• Key 3: Not Ready (NRD)
• Key 4: ACD Not Ready (ACDNR)
• Key 5: Fast Transfer (FXR)
The following example shows how to datafill the ACD agents using
SERVORD. The configuration requires up to 32 LENs and 64 DNs. ACD
Incalls and Key 2 use a secondary DN.
October 2003
69).
"Step 1 – Basic Card