Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							Automatic Route Selection and Toll Control
Step 3
7.18List the leading digits which are to be considered valid by the
system; i.e., those which satisfy the customer’s required access
to the public network. The following order is recommended: (1) direc-
tory inquiry numbers and local office codes; (2) codes which provide
unrestricted access to toll routes (i.e,, 0 and 01); (3) specific toll route
codes; (4) tie lines; (5) FX lines; (6) WATS lines; (7) calls to be com-
pleted via specialized common carriers. As each leading digits string is
entered, specify the number of digits to follow in the 
“QTY TO FOL-
LOW” column.7.19Complete the nested digit strings table. Digit strings index a
route, route list, or route plan depending on the type of call
initiated by the digit string. Analyze each digit string individually and
complete the nested digit strings table accordingly, ensuring that each
digit string terminates appropriately (route, list, or plan).
7.20If necessary specify the maximum number of dialed digits, oth-
erwise the default value of UNLIMITED applies (for North Amer-
ica).ARS Digit Strings
7.21The contents of the ARS Digit Strings tables have been com-
posed in accordance with the requirements of the scenario.
Each entry is described below.
7.22The leading digit has been specified as 9, which, in this sce-
nario, represents the trunk access code of the PABX. Return dial
tone is not required, therefore NO is specified in the “RETURN DIAL
TONE” field.
7.23Entries 1 and 2 contain digit strings which define free service
calls to any area code, using the 
wildcard digits NOX and NlX.These calls are completed over local trunks, and so only one Route is
required (Route 9).
7.24Entries 3 through 5 contain the complete digit strings for emer- 
*
gency services, repair services, and directory assistance. As
such, there are no digits to follow, and a 0 is placed in the “QTY TO
FOLLOW” column. These calls can only be completed over one route
(i.e., local trunks), and are therefore assigned to the first available route
(ROUTE I), in the Route Definition table.
7.25Entries 6 through 12 contain a cross section of office codes in
the Ottawa area. In reality, it is likely that all office codes would
have to be listed. The number of digits to follow in each case is four;
i.e., the remaining number of digits required to complete a local call.
These calls can only be completed over one route; i.e., local trunks. A
route (Route 
l), having the same trunk group, COR and digit modifica-
tion requirements as those required for entries 4 through 10 has
previously been defined. Therefore, ROUTE 1 can be entered in the
“TERM TYPE AND NUM” column of these entries.
Page 41 
						

							SECTION MlTL9’!09-094-220~NA
7.26Entry 13 provides an example of how access to an individual
telephone number can be controlled. Access to this number (a
local stockbroker) is restricted to the executive level by indexing it to a
route (ROUTE 2) which is associated (through COR Group 3) with COR
1. The number of digits to follow is 0.
7.27Entries 14 and 15 contain digits which allow unlimited access to
the toll call network; 
i.e+ digit 0 for operator assistance, and 01
for access to the international network. The number of digits to follow
for entry 14 is 0. The number of digits to follow for entry 15 is
UNKNOWN, since it is dependent on the call destination. The “QTY TO
FOLLOW” entry for this string therefore contains the word UNKNOWN.
A route, ROUTE 2 exists, and satisfies the COR and digit modification
requirements for entries 14 and 15. ROUTE 2 is therefore entered in the
‘TERM TYPE AND NUM” column of these entries.
7.28Entry 16 contains the complete digit string for the service office
in Winnipeg. As such, the number of digits to follow is 0. This
call can be completed over either of two routes: the Tie Trunk, or DDD.
Since these routes are not time-dependent (Tie Trunks are always less
expensive than DDD), a LIST (“LIST 1”) is defined in the “TERM TYPE
AND 
NUM” column.
7.29Entry 47 is an example of a toll number within the home area,
and therefore a new digit modification sequence must be de-
fined which inserts the toll digit 1 prior to outpulsing. This digit modi-
fication sequence is defined in entry 2 of the Modified Digits table, and
it is referenced from a newly defined route within the Route Definition
table (Route 3).
7.30Entry 18 contains the digit string which defines the number of
the plant in 
Boca Raton. Calls to this destination can be com-
pleted over two routes: SCC or DDD. The tariff structure for SCC is
similar to WATS in that SCC is less expensive than DDD during busi-
ness hours. As such, the two routes for entry 16 are indexed via the
Route Plan table and Route List Definition table. The number of digits
to follow is 0 and the first available route plan is route plan 1.
7.31Entries 19 through 21 contain the digit strings which define toll
routes to specific 
COs within area code 416. The number of
digits required to complete a call to any of these offices is 4. These
calls can be completed over any one of three routes, namely, FX,
WATS, or DDD. These routes are time-dependent (Le., during some
times WATS is less expensive than DDD, and at others, DDD is less
expensive), and as such, they are indexed to PLAN 2 in the “TERM TYPE
AND NUM” column.
7.32Entry 22 contains a digit string which defines the area code
416. The digits to follow can be any combination of seven
digits. This provides a user, having the required COR, with unrestricted
access to any CO within the area defined by area code 416. Like
entries 19 through 21, these calls can be completed over any one of
three routes which are time-dependent. However, unlike entries 19
through 21, user access is not restricted to specific 
COs, and therefore
an additional set of routes having the relevant 
CORs is required. Con-Page 42 
						

							Automatic Route Selection and Toll Control
sequently, ‘additional Route Lists are required to list the new routes,
and hence an additional Route Plan is required to associate the new
route lists with day and time zones. PLAN 3 is therefore entered in the
“TERM TYPE AND NUM” column.
7.33Entries 23 through 25 cbntain digit strings whi.ch define the
three area codes which, in conjunction with entry 22, define the
area codes accessible through Zone 2 WATS. Unlike entry 22, calls
made via entry 23 through 25 can only be completed over either of
two routes: WATS, or DDD. These two routes are time-dependent and
are therefore indexed to PLAN 3 in the ‘TERM TYPE AND 
NUM” column.
Route Definition Table
7.34Calling devices which are routed to Route 1 from the ARS Digit
Strings tables are allowed to complete calls over the CO Trunk
Group 1 if they are part of COR Group 2. The digit modification
sequence for such calls is defined in Modified Digits table entry 1.
Similarly, devices are routed via routes 2 through 9 from the Route List
table.Route List Table
7.35List number 1 is referenced from the AR’S Digit Strings table. It
provides alternate routing by listing two routes: Route 4 and
Route 5. The routes are listed in order of cost (i.e., route 4 is identified
in the Route Definition 
Table as the Tie Line between Ottawa and
Winnipeg), and as such it is always less expensive than the alternative
DDD route defined by route 5.
7.36List numbers 2 and 3 are referenced from the Route Plan 1.
Within that plan they are assigned to time zones such that for
any given time zone they define the least cost routing. Each entry lists ,
two routes: routes 3 and 6 (route 3 being DDD and route 6 being 
’identified within the Route Definition Table as SCC).
7.37List numbers 4 and 5 are referenced from Route 
Plan 2. They
list three routes (2, 7 and 8) in order of cost for the Day and
Time zones defined within Route Plan 2.
7.38List numbers 6 and 7 are referenced from Route Plan 3. They
are similar to entries 4 and 5 with the exception that the FX line
is not included.
Route Plan Table
7.39Route Plans 1 through 3 are referenced from the ARS Digit
Strings tables. They assign Route Lists to the day and time
zones which are defined in the associated Day Zone table. In Route
Plan 1, least cost 
iouting is provided by Route List 2 during Day Zone
1, Time Zones 1 and 2, and Day Zone 2, Time Zone 1, and by Route List
3 in the remaining day/time zones.
Page 43 
						

							SECTION Ml’h191 CI9-094~ZZO-NA
MtilMUM NUMBER OF DIALED DIGiTS
12
3
P
5
6
7
6
9
101112131.13
16
1718
19
Z-0
31
22
22
1425
BUNK GROUPS: 1 - LOCAL TRUNKS
2 - ZONE 2 WATS
3 - FX LINE4 - TlE LINE
:OR ASSIGNMENT:
:OR 1- ALL TRUNKS:OR 2 - WATS, FX TIE. SCC. LOCAL:OR 3 - FX. TlE. SCC. LOCAL:OR 4 - FX, TIE. LOCAL:OR 5 - TIE, LOCAL:OR 6 - INTERNAL CALLS ONLY
M06
06
.Figure 7-2(a) Table Network (Part 1)
Page 44 
						

							Automatic Route Selection and Toll Control
ROUTE TABLERout0Trunk Group
COR GrowDlglt ModificationNumbs,NumbsrNumborNumborw .I...:. .:.:.:. :.:.:.:.:.:.,r:.:.:.:.:.::.yL,h2191‘.’,gT.$:. :‘I .:.: :.:.:.:I$.:: .:. :.:.;.:-. .-: ::3 :.: .::.: :.: .$ :. I.:. ::I-::,. ::: ,: j,
L_ :..:.:s:. y_::,:_ 1.1 ‘,:d:,::
I-ROUTE LIST TABLELhl1st Choke I  2nd Choka3rd Choics4th Choice 5th Choice6th Choicm6 1221Numbw RoutsRoutewtRouteWIRoutsvetRoutswtRoutewt911I12
:::::~:.:.:.‘.:.:.:.:~.,.:.:.:, . . . .4N”+” ‘m.
473v2V5‘I,2’v 6 vCOR GROUP TABLE662N?26vICOR GROUPNUlllbarCOR MEMBERS
IDAY ZONE TABLEI
Day ZoneMON :  WEWED THUR5 FRI ’  SATSUN
+1S’S * ..2l3.*
4I  5-255A-25II
IMODIFIED DIGIT TABLE
I
EnWQtv. toNumber :DDmo/ CommentI  Dinits To 0sFigure 7-2(b) Table Network (Part 2)
Page 45 
						

							SECTION MlTb9199-094-22O-NADay Zone 
Table7.40The Day Zone Table defines three day zones and three time
zones. These are combined in the route plan table to form nine
day and time zones.
7.41In this scenario, three trunk groups are time-dependent: the
WATS lines and the CO and SCC trunks. The tariff structure for
these two groups is such that WATS is less expensive than DDD on
Monday through Friday from 
08:OO -18:00 and on Saturday from 08:OO
- 12:oo.
COR Group Definition Table
7.42 All entries in the COR Group Definition table are referenced
from the Route Definition table. Group 1 contains 
CORs 6,
through 25. Thus, peripheral devices which have been assigned any of
these 
CORs are restricted from completing calls via routes which
reference COR Group 1. Similarly, COR Groups 2 through 5 define
different levels of service.
Modified Digits Table
7.43All entries in the Modified Digits table are referenced from the
Route Definition table. Entry Number 1 is associated with digit
strings in the ARS Digit Strings table where the digits to be outpulsed
are identical to those dialed by the user. As such, only the leading digit
of the string is absorbed and no digits need be inserted.
7.44Entry Number 2 is associated with digit strings in the ARS Digit
Strings table which represent toll calls and therefore require the
leading digit to be absorbed and the toll digit 1 to be inserted.
7.45Entry Number 3 is associated with digit strings in the ARS Digit
Strings table which are outpulsed over the Tie Line to Winnipeg,
and as such, all digits dialed by the user are deleted and a 0 for the
distant attendant is inserted.
7.46Entry Number 4 is associated with calls which are completed
via the SCC link. The SCC account code is inserted in the digits
to be outpulsed.
7.47Entry Number 5 is associated with the digit strings in the ARS
Digit Strings table which are outpulsed over the FX Line to
Toronto. The first four digits are deleted and a dial tone marker is
inserted in the “Digits to be Inserted” column.
Page 46 
						

							Automatic Route Selection and Toll Control
8. SYSTEM PROGRAMMING
General8.01When the paper fdrms are complete, the data must be entered
into the system memory through the CDE terminal or Attendant
Console. This is part of the Customer Data Entry process, described in
Section 
MITL9109-094-Zl O-NA, Customer Data Entry (CDE).
Page 47 
						

							SECT%ON MITL91 Q9-094-220-NAPage 48 
						

							Automatic Route Selection and Toll Control
9. AUTOMATIC DATA ROUTE SELECTION (ADRS)
General9.01Similar to voice calls, outgoing data calls are dependent upon
the digits dialed, time of day and restrictions set up during CDE.
An additional requirement of ADRS is the grouping of trunks as to their
ability to carry data at a maximum baud rate. Since trunks can 
pres-
ently be grouped and named, no modifications are required to the
existing program. ADRS is not available with Generic 1002.
Application
9.02This section is intended as an example of an ADRS/ARS pro-
gram which could be used by a programmer in Kanata. In this
section a bottom-up path through the steps taken by the programmer
will be followed. This is not intended to represent the full CDE require-
ments.
In the following example 
Mite1 has three locations: Kanata, Florida and
England. The programmer needs the following information:
1.Knowledge of available trunks (number, type and line speed).
2.The assigned class of restriction.
3.Toll Control requirements.
4.Internal numbering plan specifics. ,
The following outgoing trunks are available:
1.Eight CO trunks, five of which are 600 baud lines, two are 1200
baud and the remaining line has a 4800 baud data rate.
2.There is a 1200 baud TIE line to Florida.
Trunk Groups
9.03The CO trunks are defined in the Non Dial-In Trunk Form (Form
#14) and the TIE trunk is defined in the Dial-In Trunk Form
(Form 
#15). The following lists trunks that are grouped according to
their common characteristics (Trunk Groups Form 
#16). In this example
all trunks of the same type and speed are considered to form a group.
Page 49 
						

							SECTION MITL91 Q9-094-220-NATABLE 9-l
TRUNK GROUPS
Trk Grp 
#Trunk TypeGroup Members
1600baudCO1,2,3,4,5
2
1200baudCO6,9
34800baudCO8
41200baudTIE9COR Groups
9.04 The Cor Group Definition Form (Form 
#20) is set-up to create1 -all necessary COR groupings. These are as follows:
TABLE 9-2
COR GROUPS
Toll Control 
Reqyirements
COR GroupCOR Group MembersComments
1President
l-3Pres 
& Upper Mgr
1-6Pres 
& Managers
l-9All but Admin
l-15All
Voice Station Requirements
9.05The following restrictions are imposed for outgoing voice calls:
1.Everyone is allowed to call Florida using the TIE trunk.
2.Technical staff, management and the president are allowed to
call anywhere in north America usng any trunks.
3.Middle management is allowed to call the England office only
during evening hours (discount rate applies).
4.Upper management is allowed to call the England office any
time.
5. The president is allowed to call any number (including the
operator 9-O) any time.
6.Administration staff are NOT allowed any long distance calls.
Data Station Requirements
9.06The following restrictions apply for outgoing data calls:
1.The. president is unrestricted and can use lines of any speed
during the day or night.
Page 50