Table of Contents
Advertisement
7.1-10
Integration Volume
The COR for the operator and the trunks must allow access to the Octel 200/300 ports. All other CORs
should be denied access to the Octel 200/300 ports.
If other extensions have the same COR as the operator or the trunks, they must be issued a new COR.
The operator and/or trunk COR may be the same as the COR used for Link 1.
Configuration
Proceed with the configuration of the CORs as follows:
1. Obtain a list of CORs currently in use on the DEFINITY G3i.
2. Designate two new CORs which may be used exclusively for the Octel 200/300.
3. Add the COR for the links and their hunt group. This COR is referred to as COR LK.
4. Set up COR LK according to Figure 7.1-1. Under CALLING PERMISSION, enter a Y for all other
CORs on the system.
5. Add the COR for the Octel 200/300 ports. This COR is referred to as COR DP.
6. Set up COR DP according to Figure 7.1-2. Under CALLING PERMISSION, enter a Y for all other
CORs on the system.
7. Change each COR on the system. Make sure the calling permission is Y for COR LK and N for COR
DP. All other CALLING PERMISSION entries should be left unchanged. Figure 7.1-3 shows the
data entry screen for COR XX of a DEFINITY G3i installation in which COR LK is 62 and COR DP
is 63.
The screen examples displayed in this chapter are for an DEFINITY G3i. Screens for other AT&T system
configurations may be different, depending on the type, release and version.
Octel 200/300
S.4.1
PB60019-01
Advertisement
Chapters
Table of Contents
