Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							Automatic Route Selection and Toll Control
sequence. For example: An FX trunk is installed between two cities,
permitting calls to be placed between the two as if they were local
calls. A caller in one of the cities placing a call to the other city would
dial the distant area code, unaware that the system will automatically
select the FX routing. for the call. The Modified Digits Table would
therefore instruct the system to delete the dialed area code from the
dialing sequence when the FX route was chosen by the ARS package.
Note: The system will not automatically delete or insert any digits. The
digits to be inserted or deleted must be specified by the CDE program-mer..
5.21The Modified Digit table contains four fields:
Entry Number:This nonprogrammable field lists the entry
numbers 1 through 100. The entry number is used in route
definition.
Quantity to Delete: This programmable field defines the num-
ber of leading digits that the system must delete from a valid
digit string prior to outpulsing. A maximum of 25 digits may be
specified.
Digits to be Inserted:This programmable field defines the
digits and dial tone markers which are to be inserted in place of
the digits deleted by the previous field. These digits are there-
fore prefixed to the modified valid digit string, and outpulsed
over the trunk. The digits may be telephony digits 0 through 9,
and for DTMF trunks 0 through 
9, SC and #. The field can be
programmed with up to 38 characters (i.e., combinations of
digits and special markers, where a special marker represents
one character, such as 
~1). The following dial tone markers may
be inserted:
*cl = Pause for five seconds
~2 = Wait for dial tone
~3 = Switch to DTMF for all further dialing on this call
+I = Do not display further modified digits on sets or
SMDR
35 = Pause 10 seconds
~6 = Insert calling party identity
~7 = Insert dialed account code
++8 = Insert node ID
To generate 
* on a trunk, st)c must be inserted.
Note:
Analog Networking special markers 
(~6, ~7, ~8) are not avail-
able with Generic 1002.I
Comments:This programmable field permits the CDE pro-
grammer to enter any comment desired against each entry
number. The maximum length of the comment is 20 characters.
Page 31 
						

							SECTION MITL91 Q9-Q94-220-NA
01ITABLE 5-8
FORM 22 
- ARS MODIFIED DIGIT TABLE
ENTRY NUM
ClTY TO DELETEDIGITS TO BE INSERTEDCOMMENTS CDE TERMINAL DISPLAY
0102
03
04 
-05
06
07
08
09
10
11
92
I
l-2-3-4-TOP5-Boll-OM
6-OUIT7-ENTRY NUM8-DELETE9-O-ENTER
AaTENDANT CONSOLE DISPLAY
ENTRY NUM
QTY TO DELETEDIGITS TO BE INSERTEDCOMMENTS
01
gjFl>q F2>q F3>q F~>TOPq i%>BOTTOM
q F~>Qu[Tq FT>ENTRY NUMq F8>DELETEq FCJ>q FO >ENTERPage 32 
						

							Automatic Route Selection and Toll Control
ARS COR Group Definition Table (CDE Form 20)
5.22 The CORs of the peripheral devices are grouped within the
Class of Restriction Group Definition Table. 
These COR Groups
are referenced from the Route Assignment table and their contents are
interrogated to determine whether or not the calling device has in-
sufficient privilege to complete the call. Absence of the calling device’s
COR from a COR Group indicates to the system that the call CAN be
completed. A maximum of 50 COR Groups, each containing a maximum
of 25 members, can be programmed. COR members are numbered in
the range 1 through 25; COR Groups are numbered in the range 1
through 50. Refer to Table 5-9.
5.23The COR Group Definition Table has three fields:
COR Group: This is a nonprogrammable field which lists the
COR Group numbers 1 through 50.
COR Group Members:This programmable field is used to
specify which COR Group members are to be associated with
the specified Group Number. COR member numbers range from
1 to 25 and may be entered in any order (member numbers
must, however, be separated with spaces) or, where entries are
consecutive, in the format, for example: 1-13.
Page 33 
						

							SECTION MlTLOl O9-094-220-NATABLE 5-9
FORM 20 
- COR GROUP DEFINITION TABLE
CDE TERMINAL DISPLAY
COR GROUP
01
02
03
04
05
06
07
08
09
10
11
12COR GROUP MEMBERS (SEPARATE WITH SPACES)
01
2-3-4-TOPCOMMENTS5-BOlTOM
8-QUITI7-COR GROUP8-DELETE9-IO-ENTERATTENDANT CONSOLE DISPLAY
COR GROUP
01
q Fl>
q F(j >QUITCOR GROUP MEMBERS (SEPARATE WITH SPACES)COMMENTS
q Fz>QF3>B F~>T(-JPq Fs>BOTTOM
q F7>COR GROUPq i=8>DELETEq Fg>q FO >ENTERComments: This programmable field is used by the program-
mer to enter any 20-character-long reminder against each
Group Number.
Page 34 
						

							Automatic Route Selection and Toll Control
6. ARS OPERATION: GENERAL APPROACH
General
6.01The object of ARS is to choose one route a call may take from
one location to another, when several routes are available. The
ARS package, then, is the software program which instructs the sys-
tem on how to make the choice. The choice the system eventually
does make depends upon the parameters defined within it by the CDE
programmer. These are not arbitrary. The parameters are determined
by the needs of the SX-200 DIGITAL PABX.
6.02Programming the ARS features properly therefore requires (1)
an understanding of what the customer needs, and (2) what the
system must know to reflect those needs. It is important for the ARS
programmer to have a good understanding of the cost structure of the
different routes leading from the PABX to any called destination, since
it is largely on the basis of cost that the route selection takes place.
Programming Process 
- General
6.03In general, the ARS programming process foliows this plan:
1.Determine the customer’s needs. The needs of the customer
will determine what types of calls will be permitted by which
peripheral devices. Knowing this, the ARS programmer can as-
sign classes of restriction to the peripheral devices (CDE Form
9.
2.Determine the customer’s facilities. The ARS programmer must
know with what types of trunks the customer is equipped (CDE
Forms 14 and 15) and the relative cost of each to the customer.
3.Define CORs and COR Groups (CDE Form 20). and apply these to
Trunk Groups. The COR Group tables specify which classes of
restriction will be toll-denied on a given route.
4.Define Day Zones (that is, when rates will vary), Modified Digits,
Routes, Lists, and Plans.
5.Define Digit Strings. The Leading Digits and Digit Strings data
are most important, since these form the link between what the
set user dials, and what plan, list, or route is used.
6.Specify the maximum number of digits dialed by each COR. For
North America; UNLIMITED (no further programming required).
6.04Note that the ARS decision hierarchy, as shown in Figure 5-1, is
essentially the inverse of the programming procedure. The first
data programmed (COR members) are the last used in the ARS de-
cision. The last data programmed (Digit Strings and Leading Digits) are
the first used in the ARS decision, and point towards the required
route, route list, or route plan. The rationale for this dual approach to
Page 35 
						

							SECTIQN MITL91 Q9-094-220-NAthe ARS structure is this: From the system’s viewpoint, COR groups
and members define the “rank” of each user in importance to the
system. When ARS is given a digit string, it will ultimately accept or
reject the call on the basis of the rank of the peripheral device at-
tempting to make the call, but in order to do this, it must first deter-
mine how the desired call is to be routed. From a programming view-
point, it is necessary to identify who possesses what rank before
access to the various routes can be allowed or denied. In this way,
digit analysis programming must take place with the COR of the pe-
ripheral devices always in mind.
Page 36 
						

							Automatic Route Selection and Toll Control
7. APPLICATIONGeneral
7.01The implementation of ARS on the 
SX-200 DIGITAL PABX is a
2-stage process. First, data must be collected concerning the
customer’s needs and the facilities he possesses, such as trunk
groups. ‘From this data, the ARS plan can be formulated on paper (refer
to Section 
MITL9109-094-206-NA, Installation Forms). Second, the plan
must be transferred from paper to the system memory, through the
Attendant Console or CDE terminal (refer to Section 
MITL9109-094-
2 1 0-NA).
Scenario
7.02This scenario begins with the first stage of ARS implementa-
tion, namely, the data collection and ARS plan formulation
stage. For the purposes of this scenario, a fictitious company is estab-
lished.
7.03The company has two Canadian locations: its headquarters in
Ottawa, and a service office in Winnipeg. The company also has
(1) a plant in 
Boca Raton, Florida, (2) major accounts and suppliers in
the Toronto area, and (3) must be able to make international telephone
calls. The SX-200 DIGITAL PABX located in Ottawa is to be pro-
grammed.
Trunk Groups
7.04In consulting the traffic studies performed by the SX-200 DIGI-
TAL PABX installation company, it was decided, in conjunction
with the customer, that the PABX in Ottawa would be most 
cost-effective when connected to the public network via four trunk groups,
and an SCC (specialized common carrier) link. The trunk groups were
defined as follows:
0Trunk Group 1: Local Trunks, and Specialized Common Carrier
account, for calls to the 
Boca Raton plant.
0Trunk Group 2: Zone 2 WATS Trunks (covering area codes 613,
416, 705, 819, and 514)
0Trunk Group 3: Ottawa-to-Toronto FX Line
aTrunk Group 4: Two-way Tie Line to the Winnipeg office
7.05The cost guidelines which apply to these groups are:
1.Tie Lines and FX Lines are always less expensive than any other
trunk group.
2.WATS is less expensive than Direct Distance Dialing during the
hours of 
08:OO through 18:00 Monday through Friday, and 08:OOthrough 12:OO hours Saturday.
Page 37 
						

							SECTION MIITLSI 09-094-220-NA
3.SCC is less expensive than Direct Distance Dialing during the
hours of 8:00 through 18:OO Monday through Friday, and 
08:OOthrough 12:00 hours Saturday.
7.06The following office codes are to be allowed:
Toronto: 471, 825, 678
Winnipeg: 786
Ottawa: All office codes
Boca Raton: 994.
Trunking network for this scenario is shown in Figure 7-1.
COR Assignments
7.07The employees at the company’s head office in Ottawa were
separated into COR groups for purposes of toll control.
7.08COR numbers were assigned to the various workers as follows:
COR 1:Executive. The executive level can access all trunk
groups, including the international network.
COR 2: Upper Management. This level can access WATS, FX,
. Tie and 
Locat Trunks, and can access the SCC office.
COR 3: Middle Management. This level can access the FX, Tie,
and local trunks, and can access the SCC office, and free calls
to any area.
COR 4: Technical Staff. This level can access the FX, Tie, and
Local Trunks.
COR 5: Administrative Staff. This level can access the Tie, and
Local Trunks.
7.09 For all other stations not previously assigned, the following
COR was given:
COR 6: This level can access the internal network only.
Note:It should be remember.ed that toll control can be applied not
only to individual digit strings, but to trunk groups as well. An
example of this is described later in this scenario.
ARS Form Filling
7.10Because ARS involves trunks and trunk groups (both incoming
and outgoing), the SX-200 DIGITAL PABX forms concerning
trunks and trunk groups must first be completed before starting the
ARS tables.
Page 38 
						

							Automatic Route Selection and Toll Control
AREA CODE 204fWATS AND
IAREA CODE 305I
PAEX305 994-8500BOCA RATON
/L
KAO732ROE(Figure 7-l Trunking Network
Page 39 
						

							SECTION MITL9109-094-220-NA
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 1
through 3.
Step 1
7.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 the
system as to which digits should be outpulsed, 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 should
be 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.17
Complete the Route Plan 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.
Page 40