Avaya Octel 200 Installation And Maintenance Manual page 651

11.9 INSTALLATION CHECKLIST
This section contains checklists of issues relating to the Octel 200/300 and to the M1. The list is
presented in the order in which the installation process should be followed. For details regarding any
topic, refer to the sections of this chapter pertaining to the issue.
PBX Checklist
Item Description
1. Before changing the database, print the following M1 database. Verify
and highlight areas where changes are required.
Print Issue (ISS) to verify the system release is 14 or later.
-
Print Package (PRT PKG ) to verify software options are equipped
-
with the following:
-
-
-
-
-
-
Print Terminal Number Block (TNB) of the Octel 200/300 port ex-
-
tensions to verify each port has the ability to
-
-
-
-
2. The routes and trunks that will be answered by the Octel 200/300 must
auto-terminate to the main pilot number of the hunt group.
3. If different company greetings will be used, Access Codes (ACOD) of
each trunk group route must be provided.
4. A complete hardcopy of Directory Number Block (DNB) and Terminal
Number Block (TNB) of all stations requiring a change.
PB60019-01
Table 11-4 M1 Requirements
EES (Enhanced End-to-end signaling)
SS25 (Special 2500 set features)
DDSP (Digit display)
MWC (Message Center)
DSET (Digital Set)
ARIE (Meridian Modular Telephone Set)
HUNT Terminal Hunting ports on busy conditions
CLS Class of Service on ports must provide and allow:
DTN Digitone Allowed (send DTMF)
HTA Hunting Allowed (followed the hunt
on a busy condition
XFA Call Transfer Allowed (perform a
hook-switch flash)
HPR High Priority Allowed
FNA Forward (RNA) Calls (ring-no-answer
condition)
FTR Feature for 2500 sets
CFW Call Forward All Calls
Meridian 1 Adaptive Integration
Complete
Octel 200/300
11-39
S.4.1