Sunday, January 29, 2017

External DT

If this option is set to  0, the F-Route table selected is determined only by the digits dialed without any relation to the day or time of the call. If this option is set to  1, the system first refers to PRG 44-10. If there is a match, the pattern defined in that program is used. If not, the F-Route pattern in PRG 44-09 and time setting in 44-08 are used. 02 03 Dial Tone Simulation (V2.0 Added) Tone Kind  (V2.0 Added) Conditions None 1 digit (0 ~ 9) *, # cant be used 0 = Internal DT 1 = External DT When first dialed digit matches with the data set in this Program, system send simulated DT to calling party after receiving first digit. Numbering plan for the dial needs to configure as F-Route at PRG 11-01. Set simulated DT kind which can change the tone used at PRG 44-01-02 and PRG 44-02-04.

Wednesday, January 18, 2017

PRI local number

PRI  local  number  digit  length Tells  the  system  whether  there is  seven- or  10-digit  local  dialing in  the  system’s  area.  If  the local  calling area  uses  only  seven-digit  dialing,  set  this  value to  7  (this tells  the  system  not  to  wait  for  additional  digits when  a local  seven-digit  number  is  dialed). Range: 7 or  10.  Default:  10  (supports  both 10- and  seven-digit  dialing). Field 8:  Dialing off-hold Enables  or  disables  outside  callers’  ability  to  dial  off-hold  only  when  MOH  590  (external  source) is selected.  When this  is  enabled, CO  callers  will  be  able  to  dial  extension,  department,  and  mailbox numbers while on  hold.  When this  is  disabled, the  system  will ignore  digits  dialed  by  CO  callers.  To enable  or  disable outside callers’  ability  to  dial  off-hold,  press a  scroll  key to  make the desired selection and then  press  #  to  confirm. Default:  Enabled. Field  9:  Re-sending  of  Caller  ID  in  Intelligent  Call Forwarding This  parameter  “turns  off”  the repeat  Caller  ID  (re-sending)  component  of  Intelligent  Call  Forwarding. Some  service providers  —  local  exchange  carriers  or  inter-exchange  carriers  —  don’t  allow repeating the caller’s  CID  data when making  an  outgoing  call. If re-sending  of  Caller ID  is  disabled, the  PRI  pilot number  of  the  station’s  tenant will  be  sent  instead. If re-sending  of  Caller ID  is  enabled,  CO  calls that  are forwarded to  an  off-premises  number  over  a  PRI channel will  send  the  original  caller’s  CID  data  to  the  called  person.  To  enable or  disable this  parameter, press a scroll  key  to  make  the  desired selection and  then  press  #  to  confirm. Default:  Enabled.

Friday, January 13, 2017

Adding a KSU2 Second Cabinet

Adding a KSU2 Second Cabinet You can add one KSU2  to a KSU1. The KSU2 adds: •   eight  digital  DX-80 extension ports •   four CO line  ports •   one Power  Failure Transfer  port •   Extension Expansion connectors for two  additional DPM8s or  one  APM4 •   Ribbon cable for one APM4 •   Ribbon cable for one COM4 Connect  the  KSU2  to the KSU1  via a designated  connector  located  on the CPM inside  the KSU1. To  install the KSU2 perform  the following steps. 1. Be sure  that the  entire system is turned off. 2. Remove the  KSU  cover (four screws at each  corner)  on  both KSU1  and  KSU2. 3. Connect  a static discharge  wrist  strap to a  suitable  earth  ground.   Be sure  that the strap  is touching bare skin.

Monday, January 9, 2017

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.

Saturday, January 7, 2017

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.

Tuesday, January 3, 2017

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

Sunday, January 1, 2017

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.