Table of Contents
Advertisement
12.2-8
Integration Volume
12.2.3 CONFIGURING AT&T SYSTEM 75
The System 75 configuration used for the Octel 200/300 with Adaptive Integration is substantially
different from the configuration used for a non-integrated Octel 200/300.
This section provides details about the naming conventions to follow and changes to the System 75
configuration for the following:
COR (Class of Restriction)
-
APIC Port Hunt Group
-
APIC Port Digital Phone Extensions
-
Coverage Paths
-
Trunk Groups
-
Station Extensions
-
The System 75 Considerations section gives details about DEFINITY configuration modifications that
may be required.
.
The screen examples displayed in this chapter are for System 75. Screens may be different,
depending on the type, release, and version. In these screen examples,
-
-
-
-
Naming Conventions
The System 75 allows each extension, pilot number, and trunk group to have an alphanumeric name. The
information needed by the Octel 200/300 message server must be contained within the first 16 characters.
If an extension is given a name, Adaptive Integration requires that it meet certain restrictions. The port
extensions and trunk groups must have names.
Telephone Extensions
Trunk Groups
Octel 200/300
S.4.1
bold type represents an entry that must be made exactly as shown.
bold italic type represents a field that must have an assigned value.
* (an asterisk) represents an entry that must be made but the entry is specific to the particular
System 75 installation.
______ (a blank line), represents any entry that is configured for System 75. That entry does
not need to be changed.
The name must contain the string XXXX,
where XXXX is the extension number.
The number must not be preceded with T- or D-.
The name must contain the string T-XXX,
where XXX is the trunk group number assigned in the Octel 200/300
TRUNK GROUP Table.
The T should be in upper case in order for the call record to be
recognized.
PB60019-01
Advertisement
Chapters
Table of Contents
