Mitel SX-200 DIGITAL Pabx General Description Manual

							Automatic Route Selection and Toll Control
TABLE 5-6
ARS ROUTE PLANS TABLE
CDE TERMINAL DISPLAY
TIMEZONE
01
02
03
04
05
06
01DAY ZONE 1DAY ZONE 2
START HOURROUTE LISTSTART HOUR
6-QUITZ-ROUTE NUM8-DELETE
iOUTE LISTSTART HOURROUTE LIST
9-O-ENTER
l-DAY ZONE 3
ATTENDANT CONSOLE DISPLAY
TIME
ZONEDAY ZONE 1DAY ZONE 2DAY ZONE 3
START HOURROUTE LISTSTART HOUR
R!XJTE LISTSTART HOURROUTE LIST
H F7XOR GROUPq Fe>DELETEq ifCJ>q F()>ENTERARS Digit Strings Tables (CDE Form 26)
5.20The ARS Digit Strings tables consist of one primary and one
nested table. The nested table is accessed from the primary
table by pressing the “SHOW STRINGS” 
softkey on the Attendant Con-
sole or CDE terminal. (Note: If no leading digits are entered on the
primary table, the nested table cannot be accessed.) The primary table
permits the programming of leading digit information. Actual digit
strings and routing information for each of the leading digit entries is
programmed on the nested table.
Page 5-13 
						

							Automatic Route Selection and Toil Control5.21The primary table is shown in Table 5-7, and the nested table in
Table 5-8. The primary (leading digits) table is comprised of
three fields, as follows:
Leading Digits: This is essentially the same as a Trunk Group
access code, such as the number 
“9”, but may be any digit
combination the customer desires to be analyzed. A maximum
of 100 leading digit combinations may be specified.
Return Dial Tone: This field allows a simulated dial tone to be
returned to the call originator, after the “dial 9” access code for
trunks has been received by the system, since the Central
Office dial tone is not returned until digit analysis has been
completed and a trunk seized. A YES or NO value is entered via
the appropriate 
sof-tkey on the Attendant Console or CDE termi-
nal. The default value is NO.
RestrQed COR Group:This field is optional, and may be
programmed with a COR Group number between 1 and 50.
Programming a COR Group number in this field will define
which group members will NOT be permitted to dial the speci-
fied leading digits. If access to specified leading digits is un-
restricted, the field is left blank. For example, if all users are
permitted to dial the leading digit 
‘9”, the field would be left
blank. If only those peripheral devices tagged as COR 
1 are
permitted to dial a given leading digit combination, the COR
Group must list ALL 
CORs EXCEPT COR 1.5.22The nested form specifies the actual digit strings which are to
be analyzed. The form is comprised of four fields; the fourth
field being subdivided into two. The fields are:
Digits to be Analyzed:Each line in this programmable field
constitutes one entry. Digits programmed in this field are used
by the system in conjunction with the leading digits to select
the appropriate Route. The following wiidcard digits may be
specified to simplify entering the digit strings:
0NOX
*NlX. 
x.where N is any digit from 2 through 9 and X is any digit from 0
through 9.
NOX and 
NlX may ONLY be used at the BEGINNING of the digit
string; X may ONLY be used at the END of the digit string. The
wildcard digits allow for the following cases: (1) To cover rout-
ing for any area code NOT SPECIFICALLY ROUTED, NOX and 
NIXfollowed by seven digits would cover all unspecified area
codes. (2) NOX-555-1212 and 
NIX-555-1212 covers routing for
all free directory assistance calls. (3) If routes are to be se-
lected based on office codes, blocks of office codes can be
specified, as, for example, 82X, 83X, etc. The system sorts digit
Page 5-14 
						

							Automatic Route Selection and Toll Control
strings in such a way that explicitly stated digit strings will be
routed to their routes, while all others will be covered by wild-cards. The ordering of digit strings is performed automatically
by CDE after each string is entered. If two routes are defined for
416 and 416-555-1212, CDE will ensure that the specific string
will occur first in the digits to be analyzed field. The number of
entries which can be made in this field is limited only by the
amount of available system memory.
Quantity to 
Follow:This programmable field specifies the
number of digits to be dialed AFTER the digits to be analyzed,
and may be specified as “UNKNOWN”. The advantage of speci-
fying the quantity to follow; i.e., 9-592 + 4 digits, is that when
the final digit is received, outpulsing can begin, and the DTMF
receiver can be dropped; if UNKNOWN is specified, the interdigit
time-out must occur before these happen, thus tying up PABX
resources for a longer time each call. The total number of digits
in this field, and the digits to be analyzed field, plus the leading
digits (from the primary table), must be no greater than 26
digits in length.
Account Code Required: This programmable field is used to
specify digit strings which are to be treated as “long distance”
in order to enforce the COS option “FORCED ACCOUNT CODE
ON LONG DISTANCE CALLS”. In Generic 1001, this field is also
for Room Status Restriction in Hotel/Motel applications, to re-
strict long distance calls. A caller with this COS option must
have entered an account code prior to dialing one of the des-
ignated digit strings. A YES or NO value must be specified.
Termination Type and Number: Digits dialed may terminate
on a Route, a Route List, or a Route Plan. These two subfields
combine to index where each valid digit string is to be found.
The’ first subfield is programmed with one of ROUTE, LIST, or
PLAN, depending on whether a Route, Route List, or Route Plan
is indexed. The second subfield contains the number of the
entry within the table referenced in the first subfield. For exam-
ple: Many destinations can be accessed only by direct distance
dialing (DDD). For such a destination, ROUTE is specified as the
Termination Type. Free calls such as the 555-1212 directory
assistance case (in North America) always terminate 
direct!y on
a Route for DDD. If several Route choices are available, a LIST is
specified as the Termination Type, if the choices do not 
verywith time of day. A Route Plan, with Day and Time Zone vari-
ations, is not required. This situation arises where an FX route
is always preferred over DDD. In a situation where multiple
Route choices are offered, with preferences depending on time
of day and day of the week. a termination type of PLAN -is
specified.
Page 5-15 
						

							Automatic Route Selection and Toll Control
TABLE 5-7
ARS DIGIT STRINGS TABLE - LEADING DIGITS
CDE TERMINAL 
DiSPLAY
LEADiNG DIGITSTED COR GROUP
.
6-QUIT7-LEADING DIG
ATTENDANT CONSOLE DISPLAY
LEADING DIGITSRETURN DIAL TONERESTRICTED COR GROUPINO
q Fl>q F2>q Fs>lNSERTq j4>fgF!j>
q F~>QUITq FT>LmDiNG DIGH Fa>DELETEEi FS>sHow STRINGS q FO>ENTERPage 5-16 
						

							Automatic Route Selection and Toll Control
TABLE 5-8
ARS PIGIT STRINGS - NESTED TABLE
CDE TERMINAL DISPLAY
l-ii-3-INSERT4-NOX5-x
6-WIT7-FIND STRING8-DELETE9-NlXO-ENTER
ATTENDANT CONSOLE DISPLAY
DIGITS TO BE ANALYZED
QTY TO FOLLOWACC CODE REQDTERM TYPE AND NUM
gJFl>q F2>a Fs>lNSERTq F4>NOxq F5>x
q Ffj>QUITq F-/>FIND STRINGq F8>DELETEq Fg>Nlxq F()>ENTERPage 
5-17/17 
						

							Automatic Route Selection and Toll Control
6. ARS OPERATION: GENERAL APPROACH
General6.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 AHS
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 follows 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.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.tothe 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-Page 
6-I 
						

							Automatic Route Selection and Toll Control
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 G-2/2 
						

							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 
MITL9i08-093-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 
MITL9108-093-
210-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-2OO@DIGITAL PABX installation company, it was decided, in conjunc-
tion 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:
eTrunk Group 1:Local Trunks, and Specialized Common Carrier
account, for calls to the 
Boca Raton plant.
8Trunk Group 2: Zone 2 WATS Trunks (covering area codes 613,
416, 705, 819, and 514)
eTrunk Group 3: Ottawa-to-Toronto FX Line
0Trunk 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:00 hours Saturday.
Page 7-1 
						

							Automatic Route Selection and Toll Control3.SCC is less expensive than Direct Distance Dialing during the
hours of 8:00 through 18:00 Monday through Friday, and 
08:OOthrough 12:00 hours Saturday.
7.06The following office codes are to be allowed:
Toronto: 47 1, 825, 678
Winnipeg: 786
Ottawa: All office codes
Boca Raton: 994.
Trunking network for this scenario is shown in Figure 7-l.
COR Assignments
7.07The employees at the company’s head office in Ottawa were
separated into COR groups for purposes of toll control.
7.08
COR 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 Local 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 
SC@ office, and free calls
to any area.
COR 
4: Technical Staff. This level can access the FX, Tie, and
Local Trunks. .
COW 5: 
A.dministrative Staff. This Ieve! can access the Tie, and
Local Trunks.
7.09For 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 remembered that toll control can be appfied 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 
7-2 
						

							Automatic Route Selection and Toll Control
AREA CODE 204
AREA CODE 3C5
k
i
I
co
$sx-200PABX305 994-8500BOCA RATON
FLORIDA
JFigure 7-l Trunking Network
S454RO A007E3Page 7-3