Cor - Avaya Octel 200 Installation And Maintenance Manual

The name may contain any other information that is desired, but the strings specified above must precede
any other numeric characters. The character immediately following the string must be a non-numeric
character.
The following are examples of valid names.
Valid Names for Extension 1234
Valid Names for Trunk Group 615
Valid Names for Port 333
Valid Names for Link Extension 382 or
for Link Hunt Group 382
The following are examples of invalid names.
Invalid Names for
Extension 1234
Invalid Names for
Trunk Group 615
Invalid Names for Port
333

COR

Two new CORs (Classes of Restriction) must be defined in the DEFINITY G3i for use with Adaptive
Integration:
One COR is assigned to the digital stations configured as Octel 200/300 links. (link COR)
-
The other COR is assigned to Octel 200/300 ports that are to be integrated. (port COR)
-
All CORs should have access to the digital link's COR. This is because all calls handled by the Octel
200/300 are received by the Octel 200/300 and then transferred to an available Octel 200/300 port for call
processing. COR must be the only COR that has access to the COR of the 200/300 ports (except for the
operator and trunks, see below). This is to prevent other extensions from directly accessing the Octel
200/300 ports.
PB60019-01
Joe 1234 Jones
Joe Jones 1234
1234 Joe Dept. 4
T-615
T-615 InWATS
D-333
Octel 200/300 D-333
D-333 Octel 200/300
A-382
Octel 200/300 A-382
A-382 Link 2
Joe Jones No extension number
Dept. 4 Joe 1234 A number precedes the extension
number and will be decoded as
extension 4.
T-1234 Joe Jones Contains trunk ID "T-"
Joe 12345 Jones Invalid extension number
Incoming Trunk No trunk number
Trunk 615 Missing "T-"
999 First T-615 Number precedes trunk group
333 Missing "D-"
Port1 D-333 A number precedes D-XXXX string
and will be decoded as extension
DEFINITY G3 Adaptive Integration
Octel 200/300
7.1-9
S.4.1