Installation overview

Installation Overview The  following  steps provide  an  overview  of the  installation process.   Details  on each of these  steps  are contained in  the  following  sections of  this chapter.   Be sure to read  the detailed instructions  before installing the  DX-80. 1. Plan the  installation, including  the KSU1 or  KSU1  and KSU2 and  Main Distribution Frame (MDF) location, station  locations,  cable runs,  and optional equipment. 2. Assemble  the correct tools  and supplies: UTP  telephony grade cable/wiring, miscellaneous telephony  hardware,  66  blocks, modular wall jacks, etc.) 3. Run the  wiring  for speakerphones, DSS consoles and analog devices (FAX  machines, modems, etc.)  from the MDF  to  each location.   Wiring  topology  is referred  to  as  “star-wiring”  configuration; no  cable should loop  from  one telephone location to another. 4. Run cable/wiring to any  optional  equipment, such as external  paging  equipment,  loud  bell signaling devices, music sources, etc. 5. Mount the  MDF backboard and attach the  terminal  blocks  on the backboard.  Use a  dedicated MDF with  66 block wiring field to  promote full serviceability of  the system  and connections using  proven  techniques.   If you  route  extension  cables into the  KSU, you  have to terminate one cable  pair into standard crimping  modular connectors for  each cable.

RAD devices individually

Setting Up UCD Voice Announce (VA) Groups The  DX-80 system provides UCD groups  to  allow you  to  handle  high  traffic using third-party ancillary RADs.  Whenever the overflow destinations  of a  UCD group  require you to use more than  one RAD to handle the volume of call traffic, you can pool the  RADs  in a  group (available UCD  group) for  access.  If you do this, any of the available devices can handle  waiting calls with the same announcement. The following  conditions apply. •   You must  assign all voice announce  UCD group members to port type V.A. •   You  must  record all ancillary  RAD  devices  individually  for the same announcement. These conditions do not  apply when  using the DX-80 VP system  for  UCD Overflow announcements. 8.4.1  PROGRAMMING USING THE DET Note:  chg,  bksp,  save,  one,  always,  del,  and  ack  are interactive LCD button  operations.  Use  the three buttons below the LCD display  to  actuate  the associated  operation. 1. Enter Database Administration  using  the feature code  Feature # *  and then enter  the DB  Admin password. 2. Press  show.   The system displays the DB Item Select  screen. 3. First, program  the analog extension ports as type  V.A. 4. Enter  01-nnn-21, then press  save  (where “nnn” is the extension  number  of the  analog  port connected to  an ancillary RAD Device).  This advances you  to the selected  extension Port Type field. 5. Press  chg  to  select VA.

DSS

DSS (Direct Station Selection) Console The DSS console is a digitally interfaced component  of the DX-80.   It  connects to the  system via any available digital  port  (408M/E  or DPM8  digital  port).  The  DSS is equipped  with 60 programmable buttons.   Twelve  of these buttons  are  intended  for features  code  storage  only  and do  not have LED indications  associated  with them.   Forty  eight buttons  are equipped with dual  color (red /  green) LEDs and may be assigned any  system  feature code  or directory number; these buttons may be  assigned  for either  system  features  operations or CO  line access operations. You can  mount  the  DSS  console in one  of  two positions:  lower profile  desk  position and  wall mounted position.   DSS consoles  are programmed to  operate with  an associated  speakerphone.  You  can assign up  to four  DSS  consoles  per  speakerphone.  The maximum  number of DSS consoles supported by  the DX-80  is  12.   Each  equipped  DSS  console  requires  one digital  port, therefore  the total  number (system capacity) of speakerphones  possible is reduced by one for  each DSS console

50-pin amphenol cable

CO line connection Note:  For  greatest  simplicity,  this  section mentions  each  port  card  without  the use of  an “ESI,”  “E2-,“  or  “CS-“ prefix,  as  cards  otherwise  are  functionally  identical  —  e.g.,  we  refer  to  an  E2-684  or  CS-684  as  just  a  “684.” Local  loop An ESI  Communication  Server’s  advanced  CO  line  circuitry provides  for open loop  detection  and the system’s  built-in  Caller  ID  interface.  Loop  start  lines  are  connected via  the  last  6  pairs  on each  66  block  on  the 612 and 684  cards.  Note:  Observe  correct  order  of  connection to  preserve  proper  rotary  hunting  of  the CO  lines. T1/PRI For  T1 or  PRI  applications  (only  PRI on  the  ESI-50; it doesn’t support  T1),  an  ESI  Communications  Server can use a  compatible  digital  line  card  (DLC)1: •  ESI-1000,  ESI-600,  ESI-200,  ESI-100 —  DLC  and  DLC12,  each  for  either  T1  or  PRI. •  ESI-50  —  DLC82  for  only  PRI. Depending  on  how  you configure it,  each  supports  either  (a.)  a  single  T1 circuit  at  24  DS0 channels or  (b.)  a PRI  circuit  supporting  23  “B”  (bearer)  channels  and  one “D”  (data link)  channel.  The DLC12 and  DLC82 each also  support  12  digital  stations.  The  T1 or  PRI  line is  connected  via the  last  two pairs  of  the industry-standard 50-pin  amphenol  cable  connector  on  the front  of  the  DLC. Each  ESI  Communications  Server  has  a  different  maximum  number  of  system-wide  DLCs  (see  “Port  card options,”  page  A.4).  Partial  T1  or  PRI  applications  are supported  through  line  programming. Each DLC has built-in  CSU  functionality.  The  integrated  CSU  can be enabled  or  disabled  via system programming2.  The following functionality is  provided:  line,  payload,  DTE  and none  (normal  operation) loopback  modes  with  the  ability  to  respond  back  controlled  via  system  programming;  alarm  conditions,  and both  ANSI  T1.403  and  TR  54016  performance messages  for  ESF only.  Important:  On  the ESI-50,  the DLC82 may be installed in  only  slot  2. If  you’re  installing more  than one  T1  or  PRI,  the  DLC  in the lowest  number  slot  will synchronize (“slave”) the system  with  the public  network.  The system will  synchronize  to  only one clock  source.  Therefore,  ESI strongly  recommends  that  the first  DLC  in the  system be connected to  the  T1  or  PRI  that’s connected either  to  the local  CO  or  the nationwide long-distance provider,  either  of  which typically will provide  veryhigh-accuracy  clocking (Strata 3).  The DLC  doesn’t  provide master  or  sub-master  clocking for  privatenetwork  T1  spans.

VRS

VRS Fixed Message 02 General Message Number Input Data 0 = Disable (VRS fixed message will not be played.) 1 = Enable (VRS fixed message will be played.) 0 ~ 100 (0 = No General Message Service) Description Enable (1) or disable (0) the system ability to play the fixed VRS messages (such as You have a message). This item assigns the VRS message number to use for the General Message. Default 0 Related Program 0 03 04 05 06 07 08 VRS No Answer Destination VRS No Answer Time Park and Page Repeat Timer (VRS Msg Resend) Set VRS Message for Private Call Refuse (VRS Msg Private Call) Set VRS Message for Caller ID Refuse (VRS Msg CID) Call Attendant Busy Message 0 ~ 25 (Incoming Ring Group Number) 0 ~ 64800 seconds 0 ~ 64800 seconds 0 = No Message Played 1 ~ 100 = VRS Message 1 ~ 100 101 = VRS Fixed message (Message will only play if PRG 40-10-01 is enabled.) 0 = No Message Played 1 ~ 100 = VRS Message 1 ~ 100 101 = VRS Fixed message (Message will only play if PRG 40-10-01 is enabled.) 0 ~ 100 (0 = No message) This item assigns the transferred Ring Group when the VRS is unanswered after Call Forwarding with Personal Greeting Message. If an extension has Personal Greeting enabled and all VRS ports are busy, a DIL or DISA call to the extension waits this time for a VRS port to become free. If a Park and Page is not picked up during this time, the Paging announcement repeats. This item assigns the VRS Message number to be used as Private Call Refuse. When Fixed message is set, VRS message guidance is: “Your call cannot go through.” This item assigns the VRS Message number to be used as Caller ID Refuse. When Fixed Message is set, VRS message guidance is: “Your call cannot go through.” 0 (No Setting) 0 0 0 0 0

queued call

While  a caller waits for a UCD group  member  to answer (in queue),  several  queued call operations are possible.   These  include the  following. •   No Answer – Member  advancement.  Each UCD  group has a No  Answer  Timer.   You can set this timer to  advance the call from one UCD group member to the next when the ringing  member does not answer  the call  within the  time allotted. •   Overflow  1 Destination programming.  Each  UCD  group has  an overflow 1 timer and destination.   You can set this timer  to determine how long calls  will  remain in queue,  before being routed  to the  overflow 1 destination.  The destination can  be an extension  responsible for handling  calls that  remain in  queue too long, or a voice  announcement device.  You  can use recorded announcement devices  to  play recorded messages  to callers  waiting in queue, for example, “All agents are still  busy  - please continue to hold.”   The system  plays the overflow  1  destination only once.   For high  traffic  scenarios,  you can  use  a  recorded voice announcement UCD group to play the  same  message to multiple callers. •   Overflow  2 Destination programming.  Each  UCD  group has  an overflow 2 timer and destination.   You can set this timer  to determine how long calls  will  remain  in queue, following  the overflow 1 timer, before being routed  to the overflow  2  destination (overflow 1  timer + overflow  1 destination recorded message time + overflow 2  timer.)   The destination can be  an  extension responsible for handling calls that remain in queue too long or a voice announcement device.   You can use  recorded announcement devices to  play  recorded  messages to  callers waiting in queue, for example, “Please continue  to hold to  reserve  your place in  queue.”   For high  traffic scenarios, you can use a recorded voice  announcement UCD  group to play  the same message to multiple callers. •   Overflow Count  programming.  Each UCD group has an overflow  count that is  associated with the  overflow 2 timer.   You can set  this timer to  allow a specific number  of times  that the  system may repeat the  overflow  2 timer.  For each cycle  of  the overflow 2 timer, the  system plays the overflow 2 destination  recording.   If a call  remains in queue so  long that the overflow count counter expires,  the system routes  this  call to the programmed  reroute  destination. •   Reroute Destination programming.   Each  UCD  Group has a reroute  destination.   You can program this  with an  extension number the system uses  to remove  the call from UCD  group queue.   The system  then routes the  call for immediate handling. Other features whose  programming may affect  UCD programming  includes the following. •   CO Line Ring  Assignment •   UCD Reroute  Destination •   UCD Voice Announce Group •   UCD Agent Log On/Log  Off •   Voice Mail -  Digital Integration •   Recorded  Announcement Devices (RADs)

received format

Receive Format Delimiter Dial Code Route Setup of Receive Dial 0 = Address 1 = *  ANI 2 = * *  DNIS 3 = *  ANI * *  Address 4 = 5 = ( *  ANI *  DNIS *  DNIS *  ANI *  = Delimiter Code) 1 ~ 9, 0, #, * 0 = Fixed Route (Item 08) (No Routing) 1 = Routes on Received DNIS or Address Data 2 = Routes on Received ANI Data COS 01 = 0 COS 02 ~ 15 = 0 * * * Use this option to specify the format of the ANI/DNIS data received from the Telco. Make sure your entry is compatible with the service the Telco provides. The character *  indicates a delimiter.If Program 34-01-02 is selected to 2 (MF), this Program works only as 4 = *ANI *DNIS *. This option defines the character Telco uses as a delimiter (see entries 1 ~ 5 in Item 1 above). Valid entries are 0 ~ 9, #, and *. This option specifies the source of the data the system uses to route incoming ANI/DNIS calls. If option  2  is selected, refer to Program 34-09-04