Table of Contents
Advertisement
7.1-20
Integration Volume
The examples in the Name column of the screen below refer to the Slot, Unit and Link position, i.e.,
S1U1L1 = Slot 1, Unit 1, Link 1. The example shows a suggested naming convention. The Octel 200/300
does not access the information in the Name column to process calls.
Group Number: HX
Group Member Assignments
Ext
Name
EXS5U1L1
1:
EXS5U1L2
2:
EXS5U2L1
3:
EXS5U2L2
4:
EXS6U1L1
5:
EXS6U1L2
6:
EXS6U2L1
7:
8:
9:
10:
11:
12:
13:
Coverage Paths
All extensions that are to use the Octel 200/300 for call coverage must be assigned a coverage path that
includes as a coverage point. This may require addition of new coverage paths as well as modification of
existing coverage paths.
Caution!
DEFINITY G3i call coverage path provides flexibility in designating how the Octel 200/300 is to be used
for call coverage. Some questions to ask when specifying a coverage path that includes the Octel 200/300
are
Under what calling conditions (e.g., busy, RNA, send all calls) should calls be forwarded to the Octel
-
200/300
Which of the three coverage points should be used to forward calls to the Octel 200/300
-
Octel 200/300
S.4.1
Group Extension: EXTNH
Ext
Name
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
Figure 7.1-10 Hunt Group Data Entry Screen, Page 2
Every call coverage path that includes the Octel
200/300 as a coverage point must specify a greater
number of rings for RNA than the Octel 200/300
specifies in INFORMATION Table Indexes 7 and 8.
Hunt Group
Group Type: UCD
Ext
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
Page 2 of 6
Name
PB60019-01
Advertisement
Chapters
Table of Contents
