Meridian America Link/Customer Controlled Routing User Manual
Page 363

Chapter 12: Meridian 1 configuration for Meridian Link/CCR 345
Meridian Link Release 5C/CCR Release 3C Installation and Upgrade Guide
Note: Systems with two modules (two Application Modules, two IPE
Modules, or one of each), with Meridian Link activated in one and
CCR activated in the other, will require two AMLs and hence two VAS
IDs. In that case, you must define two VSID numbers in Table 109 and
assign two status message groups in one of Tables 124Ð127.
Table 129
LD 23ÑDefine an ACD DN with IVR handling (if applicable)
Prompt
Response
Comment
REQ
NEW
Create or change data in the database
TYPE
ACD
Automatic Call Distribution data block
CUST
0Ð99
Customer number
ACDN
xxxx
ACD Directory Number
MWC
DSAC
MAXP
xx
Maximum number of agent positions for
this ACD DN
SDNB
BSCW
ISAP
CCR messages sent across the link
VSID
0Ð15
Value Added Server Identification as
defined in LD 17; only required if the
IVR/VRU unit is connected to Meridian 1
by an AML/CSL
IVR
YES
This ACD DN handles IVR routing
TRDN
xxxx
Treatment DN for IVR calls (used by CCR
if IVR treatment is not specified in the
script)
This DN refers to treatment within an
IVR/VRU unit connected by an AML/CSL
REQ
NEW, END
Either define another ACD DN or exit the
overlay, saving changes