Mitel SX-200 DIGITAL Pabx General Description Manual

							Automatic Route Selection and Toll Control
7.11The ARS tables in Figures 7-2(a) and 7-2(b) have been com-
pleted using the raw data produced in this scenario. The order
in which they were completed is the order in which they would nor-
mally be programmed. A detailed description of the contents of the
tables is given in the paragraphs immediately following Steps 
1through 3.
Step 17.12Complete the COR Group Definition table, listing in each COR
Group the COR members to be included. The COMMENTS field
may include reminders concerning which level within the company is
contained within each group, or comments concerning the destinations
being restricted by each COR Group.
7.13Complete the Day Zone table to provide day zones which sat-
isfy the effect of changing rates for the trunk groups involved.
Step 2
7.14 Complete the Modified Digits table. This table instructs 
,thesystem as to which digits should be outpuised, and which
should be absorbed by the system. Therefore, for example, if the
“outside line” access code 9 is not to be outpulsed, the 
system,shouldbe instructed to delete the leading digit 9 from any digit string being
analyzed. Similarly, if long-distance DDD calls are permitted, the sys-
tem could be instructed to insert the digit 
1 into the digit string, after 9
had been deleted. Since in this scenario it is known that (the SCC
network will be accessed, the system can be told to insert the SCC
number and account code. The user would then simply dial a 7-digit
telephone number (in this case, the office in 
Boca Raton). Digit modi-
fication need not consider specific user-dialed digit strings, but the
various dialing possibilities MUST be considered.
7.15Complete the Route Definition table. Determine how many
routes are available for the given trunks, and complete the table
accordingly. For example, if Trunk Group 1 has five routes available,
each route must appear on this table, with its own Route Number.
7.16 Complete the Route List Definition table. Assign each route
defined a level of “choice”. If Trunk Group 1 has five routes
available, order these according to First, Second, Third, Fourth and Fifth
choices. The priority of the routes is normally dependent on cost.
7.17Complete the Route 
PIan Definition table. This will permit the
system to select a route list on the basis of fluctuating costs
due to time of day and day of the week. The hours at which the rates
change must be entered in the START HOUR column.
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-Page 7-4 
						

							Automatic Route Selection and Toll Control
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-
pieted 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).
ARS Digit Strings
7.20The 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.21The 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 
DlALTONE” field.
7.22Entries 
‘I and 2 contain digit strings which define free service
calls to any area code, using the 
wildcard digits NOX and NIX.
These calls are completed over local trunks, and so only one Route is
required (Route 9).
7.23Entries 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 ttie “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.24Entries 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 
compieted 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.
7.25Entry 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.
Page 7-5 
						

							Automatic Route Selection and Toll Control
LEADING DIGITS: 
5IA1 TUNE(VES/NOJ:DIGITS TO BE AN
12
3
4
5
6
7
6
9
10
11
12
13
14
15
16
17
18
1920
71
22
23
24
25TRUNK GROUPS: 1 
- LOCAL TRUNKS2 - ZOME 2 WATS ,
3 - FX LINE
4 - TIE LINECOR ASSIGNMENT:
COR 
1 - ALL TRUNKS
COR 2 
- WATS,FX.TIE,SCC.
COR 3 - FX.TIE,SCC
CDR 4 - FX.TIECOR 5 
- TIE
COR 
6 - INTERNAL CALLS ONLY
Figure 
7-2(a) Table Network (Part 1)Page 7-6 
						

							Automatic Route Selection and Toll Control
ROUTE TABLERouteTrunk Group
COR GroupDigit Modification
NumberNumber
NumberN”ItlbW.c->y :_:.: :r:::::::.:,:::::::::::,‘:‘:‘:‘:’:’~. L..‘.‘.‘.’ ~.‘.‘:.-.‘. .-.,. : .(,.,._._. j., (.,_,._. Y,.,? ._.,.;,.,.... ,.,:_ ;,.13:,:::-.y::..:::$::: ,:I:. 1.1 ,:I:’ ::::.::1.1 _I., 1.: ,: ;:.:..:. ‘_I. .:.,_:_: ..- ..3 .! .Pt21ROUTE 
LIST TABLE,-r~--..--Number 
Rou:e
57 ;  2AY6Iv----_6-7 8 2 :  N72 ,8 /  ”I
16-25- ~1-T~-T-r~-----~-::;. ,..,.;3.;:;;::: .:.~~25:.:.:.:.:.:.:.;.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:::’:::.:.:.:.:.:::::--‘.’ yJ ‘., :.:/::+&I::,‘::, :::..:‘:.,:.:.‘:‘:‘,..: 1:: ,:;, f_ ,‘I. ._, ::.,:;I .:::.‘I:4
5-25
54-25~.--_I  
IMODIFIED DIGIT TABLEI4 j
1I  667a9aii:a4w7 !5 !4 :*1/
,
Figure 
7-2(b) Table Network (Part 2)
Page 7-7 
						

							Automatic Route Selection and Toil Control
7.26Entries 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 12 is 0. The number of digits to follow for entry 13 is
UNKNOWN, since it is dependent on the call destination. The “QTY TO
FOLLOW” entry for this striny therefore contains the word UNKNOWN.
A route, ROUTE 2 exists, and satisfies the COR and digit modification
requirements for entries 12 and 13. ROUTE 2 is therefore entered in the
“TERM TYPE AND NUM” column of these entries.
7.27Entry 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 fwo routes: the Tie Trunk, or DDD.
Since these routes are not time-dependent (Tie Trunks are always less
expensive than DDD), a LIST (“LIST 4”) is defined in the “TERM TYPE
AND NUM” column.
7.28Entry 17 is an example of a toil 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.29Entry 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 
SC6 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.30Entries 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 (i.e., 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.31Entry 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-
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.
Page 7-8 
						

							Automatic Route Selection and Toll Control
7.32Entries 23 through 25 contain digit strings which 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.33Calling devices which are routed to Route 1 from the AR.6 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.34List number 1 is referenced from the ARS 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.35List 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.36List 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.37List 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.38 Route 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 routing 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.
Day Zone Table
7.39The 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.
Page 7-9 
						

							Automatic Route Selection and Toll Control
7.40In 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.41All 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.42All 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 inset-ted.
7.43Entry 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.44Entry 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.45Entry 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.46Entry 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 7-l O/l 0 
						

							Automatic Route Selection and Toll Control
8. SYSTEM PROGRAMMING8.01When the paper forms are complete, the data must be entered
into the system memory 
througrh the CDE terminal or Attendant
Console. This is part 
pf the Customer Data Entry process, described in
Section 
MITL9108-093-2 1 0-NA, Customer Data Entry.
Page 
8-l/1 
						

							MITEL STANDARD PRACTICESIXTION MITL9108-093-221 -NAIssue 1, September 1986
SX-ZQQ” DIGITAL
PRIVATE AUTOMATIC BRANCH EXCHANGE (PABX)
STATION MESSAGE DETAIL RECORDING
Copyright of MITEL Corporation 1986
TM 
- Trademark of MITEL Corporation
@Registered Trademark of MITEL Corporationi 
						

							Station Message Detail Recording
CONTENTSPAGE1. INTRODUCTION...................................l-l
General.........................................l-l
Reason for Issue..................................l-l
BriefDescription..................................l-l
2. DETAILED DESCRIPTION. . . . . 
0.. s . . . . n . . 0 0 . . . s . . . . . 0 2-l
General 
,.O D n.Q.m n e,0 D m m a m s 0 O.s m.s m 0 O..O m.s 0
 m ..O. 2-l
Recorded Information e . . m . 0 . 
m D
 0 . . . m . . . . . e . . . . . . . . . . 2-l
Call Record Examples . . . . . . . . 
e, -. . . *.. . . . . . . . . s . , . . 2-6
Call Timing 
O.......m..s n D -.- e.s s s 0u..e..m s s -..-.. 2-8
5. SMDR PROGRAMMING AND CONTROL 
a a m m s 0 0 s 0.. m n . . . . 5-l
General . . . . . . . . . . . . . 
..-.- m.s.ma.la m s 0 -.....- . . . . 5-l
SMDR Programming Options . . . 0
 
D -. . . . D e
 e -. -.. m -. -. . 5-l
6. SMDR LOGS AND DATA 
ROUTiNG . m e s . s s, . . . s s s m 0 . . . . . 6-l