11.3 M1 Configuration - Avaya Octel 200 Installation And Maintenance Manual

11-6 Integration Volume

11.3 M1 CONFIGURATION

The configuration of the M1 is divided into six sections:
Incoming Trunks
-
Customer Datablock
-
Calling Party Name Display
-
Octel 200/300 Port Extensions
-
SIC8 Link Modular Telephone Extensions
-
Customer Telephones
-
Incoming Trunks
The Octel 200/300 can distinguish between different trunk groups that auto-terminate into the Octel
200/300 and play different greetings accordingly. The information the Octel 200/300 uses to make this
distinction is the trunk group number. This number is configured into the M1 and assigned to a group of
incoming CO, WATS, DID, or TIE trunks. There is no need to split the Octel 200/300 ports to achieve
different greetings as long as the trunks themselves belong to different trunk groups. Therefore, to
configure Octel 200/300 to play different greetings to external callers, the specific trunk group numbers
must be known.
Print the Route Datablock to determine the access code numbers and list individual trunk members to
auto-terminate each group. Change each trunk member and put the Octel 200/300 pilot number in the
ATDN (Auto-Terminate Directory Number).
All the incoming CO trunks to be answered by the Octel 200/300 must be auto-terminated to the pilot
number of the Octel 200/300 hunt group. The pilot number is the same as the first extension number of
the hunt group (usually port 1).
Customer Datablock
Some of the specific customer options (i.e., Digit Display Allowed, Message Center included) of the M1
software must be activated in the Customer Datablock configuration of the M1.
To determine which options are activated, print the Customer Datablock. Check OPT (command):
IDP (digit display)
MCI (message center)
All M1 installations with X11, Release 14 or later, have the ability to selectively forward DID versus
non-DID calls on a busy condition or a ring-no-answer condition. If the customer requests this feature and
their M1 supports it, the specific forwarding features must be enabled in the Customer Datablock
configuration of the M1. Look at FNAD and FNAN. There are four ways in which calls can be answered
system-wide for non-DID and for DID calls:
FDN =
HNT =
Octel 200/300 S.4.1
= Allowed
= Allowed
Follow forwarding DN
Hunt
PB60019-01