Mitel SMART L CALL CONTROLLER Hardware Installation Manual

							SECTION MITL8350-047-l OO-NA 
Searching 
4.07 The Dialer monitors for rotary or DTMF dialing on its subscriber 
side and compares any subscriber dialed digits against one of 
two data bases that may be programmed into the Dialer. This compari- 
son is called “searching”. The data base in use is made up of 15 ,. 
“search tables”. After comparison, the Dialer will decide on one of the 
following actions: 
* 
1) Call must go on DDD Network. 
2) Call must go on OCC Network. - 
3) Call is preferred to go on OCC Network, but failing that, will go 
on DDD Network. 
4) Call is denied. 
5) Dialer is “cut-through” (i.e., 
no dialer activity-digits pass 
through directly). 
6) The dialed sequence will access the speed call directory stored 
in the SMarT-lTM Dialer, and, as a result, it will outpulse the 
telephone number stored in that location. 
4.08 In the ‘wait for digits’ mode, all dialed digits are processed 
through the ‘search tables’. The results of the comparison will 
be a trigger to perform one of the above actions. There are two sets of 
15 tables in all and they can be used to compare against up to 15. 
dialed digits. For example, the first table (one digit table) is checked 
after the first dialed digit. If a match is found, the searching for the 
first digit stops. The second table (two digit table) is checked after the 
second digit, and so on, until a match is found with an action that 
terminates the comparisons. 
Note: The two sets of search tables mentioned above are known as 
the Primary and Alternate search tables. Each trunk in the 
Dialer may be programmed to use either the Primary or the 
Alternate search tables for examination of a dialed digit string. 
Primary search tables (the normal default setting) are as- 
sumed in remaining text. 
4.09 Each entry in a search table consists of a group of digits (called 
for ease of reference, a ‘template’) that is compared to the 
dialed sequence along with an additional single digit (called the 
‘action’). The action is a single digit that represents a specific ‘action’ 
to be taken by the Dialer when dialing is completed. The action digits 
are collected, and, on completion of dialing, are performed according 
to the programming. -r 
TEMPLATE DESCRIPTION 
4.10 The ‘template’ section of a table may consist of ordinary digits 
or special digits as listed in Table 1 below. The single digits 
Page 14  
						

							SECTION MITL8350-047-l OO-NA 
used for ‘actions’ and their meanings are listed in Table 2 below. One 
‘action’ digit must be used with each template. 
Note: MNEM. in the Table below means mnemonic and is used to 
describe templates in the paragraphs that follow below. 
TABLE 1: TEMPLATE DIGITS 
7 
DIGIT DESCRIPTION 
o-9,* To be matched against the same digit in 
the dialed sequence. 
#O Compare against ‘#‘. 
DIGIT MNEM. DESCRIPTION 
#l l/O Compare against ‘1’ or ‘0’. 
#4 n 
Compare against any digit from 2 through 
9. 
#9 
X Compare against any digit. 
TABLE 2: ACTION DIGITS 
DIGIT DESCRIPTION 
0 
1 
2 
3 
4 
5 
6 
7 
8 
9 
lll 
#l 
#2 
#3 
#4 
#5 
#6 
#7 
#8 
#9 
#C PREFER ROUTE 0 (PRO) 
PREFER CALL TO GO ON ROUTE 1 
PREFER CALL TO GO ON ROUTE 2 
PREFER CALL TO GO ON ROUTE 3 
FORCE CALL TO GO ON ROUTE 0 (FRO)? 
FORCE CALL TO GO ON ROUTE IT 
FORCE CALL TO GO ON ROUTE 2jy 
FORCE CALL TO GO ON ROUTE 3T 
SELECT CALL TO GO ON ROUTE 0 (SRO)“ft 
SELECT CALL TO GO ON ROUTE l-F? 
SELECT CALL TO GO ON ROUTE 2Tt 
SELECT CALL TO GO ON ROUTE 3Tf 
DENY 
SPEED CALL 
DIAL ALL DIGITS THAT USER DIALED AND CUT 
THROUGH (NO ROUTING) 
SECURITY ACCESS CODE 
ABSORB WHAT HAS BEEN ENTERED AND CUT 
THROUGH (BYPASS) 
ALL DIGITS HAVE BEEN DIALED IN PHONE NUMBER. 
AN ACTION MUST BE ENCOUNTERED (e.g., ROUTE 
SELECTED) BEFORE THE #6 ACTION 
DO NOTHING 
PREFER DEFAULT ROUTE (x24) 
DELETE THIS TEMPLATE FROM SEARCHING TABLE 
LIMITED PROGRAM ACCESS CODE FOR SPEED CALL 
PROGRAMMING BY SUBSCRIBER  
						

							SECTION MITL8350-047-l OO-NA 
Note: T These will force the call onto the selected route if possi- 
ble. If not possible, the call will not be completed. Redial and 
retry attempts will be directed to the same selected route. 
TT These will not dial out the ‘select’ digits and will start 
comparisons over again from the first digit. 
Dialer begins dialing out upon encountering any of the above 
search table actions with the exception of #I, #4 through #7, 
and #9. 
OTHER COMPARISONS 
4.11 In addition to comparing the dialed digits to the search tables, 
three other comparisons are made. The first digit dialed is 
checked for a match against the Centrex Access digit. Every digit after 
the first dialed digit (prior to call completion) is checked to see if it is 
the ‘restart’ character (i.e., the restart character allows the user to start 
dialing again to correct mistakes). Lastly, after the Dialer has finished 
dialing, any further digits dialed by the user are compared to the ‘redial 
on Route #0’ and ‘redial on the same route’ digits. If a match occurs in 
this case, the call will be dropped and redialed while the telephone 
remains off-hook (i.e., the Dialer releases and re-seizes the line). 
4.12 This allows extreme flexibility in the use of the Dialer. It also 
means that any mode of operation (other than the cut-through 
mode on initialization) requires some programming. 
ROUTES 
4.13 The four routes (listed in Table 2) are called ROUTE #0 through 
ROUTE #3. These can be assigned either to the DDD Network or 
the OCC Network. Each route can be selected by programming the 
search tables accordingly, and each has its own access method. For 
example, to access the DDD Network, the user waits for the dial tone 
and then dials. To access the OCC Network, the user would perform 
the following steps: 
1) Wait for dial tone 
2) Dial the ‘access code’ (OCC phone number) 
3) Wait for further dial tone 
4) Dial the ‘authorization code’ 
5) Dial the ‘destination number’ (called party) 
4.14 All of the above steps can easily be associated with a route and 
dialed automatically by use of the access control sequences 
(see 4.25). 
Page 16  
						

							SECTION MITL8350-047-l OO-NA 
SEARCH EXAMPLES 
4.15 The following paragraphs describe the typical uses of the 
search tables when combined with routing data. Not all pos- 
sibilities are discussed since programming is very flexible. This exam- 
ple presumes that Route #O is used for the DDD Network and Route #1 
is used for the OCC private carrier. 
4.16 The examples associated with these descriptions list the digit 
to be entered in the template, followed by the action and a 
description. Digit definition and mnemonic use in the examples is 
defined in Tables 1 and 2 above. 
EXAMPLE 1: 1+ CALLS TO CARRIER 
TEMPLATE ACTION DESCRIPTION 
1 
5 (FRl) 
Any call starting with digit 1 
will be forced. onto Route #I. 
X 4 (FRO) Don’t care; any other first digit 
will force the call onto Route 
#O 
4.17 In the example above, FRl (Force on Route #I) is selected over 
PRl (Prefer Route #l) so that if the call fails (say, due to an 
OCC network problem), the call can only be retried on the same route. 
The retry is directed to another route only when the ‘action’ used is 
PRl. 
EXAMPLE 2: l+ CALLS TO CARRIER, 1+800 TO DDD 
TEMPLATE ACTION DESCRIPTION 
1800 4 (FRO) This is the fourth digit search 
table. All I+800 calls will go 
on the DDD Network. 
1 xxx 5 (FRl) All other I+ calls will go on 
Route #l (OCC). 
xxxx 4 
(FRO) After the fourth digit, any oth- 
er call will go on the DDD. 
4.18 The Dialer makes a pass through the search tables after every 
digit. Once it finds an explicit match, it stops. Therefore, the 
entry “1 x x x” stops the search before it arrives at the “x x x x” case. 
Notice that, in the example above, the Dialer holds off dialing until the 
fourth digit IN ALL CASES. To cause the Dialer to begin dialing after the 
first digit of a non l+ call, example 3 below would have to be pro- 
grammed. 
Page 17  
						

							SECTION MITL8350-047-l OO-NA 
EXAMPLE 3: BEGIN DIALING AFTER 1ST DIGIT 
TEMPLATE ACTION DESCRIPTION 
1 #7 (Nothing) 
X 4 (FRO) 
1800 
4 (FRO) 
First digit search table. 
Also in first digit table; this 
point accessible on non l+ 
calls only. 
Fourth digit table; put call on 
DDD. 
1 xxx 
5 (FRl) All other I+ calls go to Route 
#I. 
4.19 If the Dialer is programmed to assume that a I+ call will go on 
Route #I, it will begin dialing immediately after the first ‘1’. If 
the user, in fact, then dials 1+800, the Dialer will drop the call and use 
the Route #O access method (i.e., DDD) instead. This action is covered 
in Example 4 below. 
EXAMPLE 4: l+ CALLS TO CARRIER, 1+800 TO DDD 
TEMPLATE ACTION 
DESCRIPTION 
1 1 (PRl) First digit table; Assume Route 
#I, begin dialing (actually, be- 
gins accessing the OCC net- 
work). 
X 4 (FRO) Not a long distance number, 
route over DDD. 
1800 4 (FRO) Fourth digit table; since this 
action indicates the DDD route, 
the call will be dropped and 
restarted on the DDD network. 
4.20 The paragraphs above have covered PRn (prefer route) and FRn 
(force route). SRn (select route) is different in that the digits 
dialed to trigger the SRn are absorbed (not dialed out). The preferred 
method would be to have ‘~1’ to select Route #0 and ‘~2’ to select 
Route #I. 
ADDITIONAL SEARCH INFORMATION 
4.21 
A Speed Call ‘trigger’ code also exists. All digits dialed up to the 
speed dial ‘trigger’ are absorbed. The last one or two digits 
are 
used to select a speed call. For example, 1 Inn could be used to select 
from 100 speed call entries where the 11 is the ‘trigger’ and is ab- 
sorbed, while the ‘nn’ is the number of the speed call 
in memory to be 
dialed (nn = 00 to 99). Sequences can also be denied. 
Page 18  
						

							SECTION MlTL8350-047-l OO-NA 
4.22 The entry in Table 2 on page 15 for digit ‘#6’ called ‘ALL DIGITS 
DIALED’ causes an action that tells the Dialer that the user has 
finished dialing the called party, is ready to dial the ‘account code’, etc. 
Before encountering the #6, a previous search table must have se- 
lected a route and thus activated an Access Control Sequence (ACS). 
4.23 There are two exception actions. These are the ‘cut-through’ 
and ‘do nothing’ action digits. The ‘cut-through’ does exactly as 
it says. Whatever dialing is taking place finishes. The line is then 
reconnected. Screening stops at the search table containing the 
‘cut-through’ action (#3) and no Access Control Sequence is used. 
This action will quite often result in incompleted calls as only a few 
digits may have been dialed. It is not recommended for general use. 
The ‘dial and cut-through‘ action will cause the SMarT-lTM to begin 
dialing, reproducing the user dialed digits until it catches up with the 
last entry dialed, and then cut through. This method will access the 
DDD Network in most ap’plications and may be used instead of the 
Route #0 in the above examples. However, once a call has been made 
in this manner, it may not be redialed. ‘The method is not recom- 
mended for Centrex applications, or applications that require redialing 
or DTMF to rotary conversions. 
4.24 The ‘do nothing’ action allows the building of templates that 
match to any digit. This action stops the searching process 
until the next digit. 
ROUTE SELECTION 
4.25 There are six groups of data that control the route selection (or 
define the access method). These consist of the destination, 
access, authorization, account, Centrex numbers, and the Access Con- 
trol Sequence (ACS). These are defined as: 
1) 
2) 
3) 
4) 
5) 
6) DESTINATION NUMBER: 
The destination number is the called 
party number and is dialed by the user (1 to 23 digits). 
ACCESS NUMBER: This is the telephone number of the OCC, 
and is dialed by the SMarT-lTM unit (1 to 34 digits). 
AUTHORIZATION NUMBER: The authorization number is the 
user’s special code for access to the Carrier services and is 
dialed by the Dialer (1 to 34 digits). 
ACCOUNT NUMBER: The account number may be used to 
identify the calling party and is also dialed by the user (1 to 23 
digits). 
CENTREX NUMBER: The Centrex number is the sequence usu- 
ally used to access the desired Centrex service (1 to 34 digits). 
ACCESS CONTROL SEQUENCE (ACS): The ACS is a sequence 
of codes that instruct the Dialer on the details of accessing a 
particular route. These details include such items as ‘what to 
dial first’, ‘when to wait for dial tone’, etc.. The codes and their 
Page 19  
						

							SECTION MITL8350-047-l OO-NA 
meanings used in the construction of an ACS are listed in Table 3 
below. This sequence may contain up to 34 characters. 
TABLE 3: ACCESS CONTROL SEQUENCE (ACS) CODES 
CODE 
I,0 
#O* 
#OO 
#Ol 
#02 
#2ab 
#3ab 
#4ab 
#5ab 
#6ab 
#7ab 
#8ab 
#gab 
#Dab 
2 
3 
4 
5 
6 
7 
8 
9 
## DESCRIPTION 
Dial that digit. 
Dial a ‘x’. 
Dial a ‘#‘. 
Dial a ‘#’ if the last dial digit was not ‘#‘. 
Wait for account code (does not dial account code). 
Pause. Continue after pause if a = 5. Fail to x58, x78 
if a = 0. 
High tone (570-680 Hz tone qetector). 
440 Hz tone detector. 
480 Hz ringback tone detector. 
400 Hz tone detector. 
350-620 Hz energy detector. 
Precise dialtone/ Hz detector. 
Wait for Not On Network (NON) tone. 
DTMF Detector 
Dial the destination number. 
Dial the access number. 
Dial the authorization code. 
Dial the account code. 
Dial the Trunk number (l-4 on the SMarT-lTM Dialer, 
1 or 2 on the SMarT-lATM Dialer). 
Cut through. Reconnect line. Dialing completed. 
Change to DTMF signaling. 
Dial the Centrex access code (may be different for 
each Route). 
End (used while programming). 
Page 20  
						

							SECTION MITL8350-047-IOO-NA 
TABLE 
4a: DETECTOR/TIMEOUT (a) CODES 
a MIN. TONE DURATION a MIN. TONE DURATION 
0 
MIN. Fail to x58 or x78 5 MIN. then continue 
1 200ms Fail to x58 or x78 6 200ms then continue 
2 400ms Fail to x58 or x78 7 400ms then continue 
3 1.0 Fail to x58 or x78 8 1.0 then continue 
4 2.55 Fail to x58 or x78 9 2.55 then continue 
TABLE 4b: DETECTOR/TIMEOUT (b) CODES 
b TIMEOUT/TONE NOT RCVD. b TIMEOUT/TONE NOT RCVD. 
0 
0 Seconds 6 12 Seconds 
1 2 Seconds 7 14 Seconds 
2 4 Seconds 8 16 Seconds 
3 6 Seconds 9 18 Seconds 
4 8 Seconds * 20 Seconds 
5 10 Seconds 
4.26 For example, the standard procedure for accessing the DDD is: 
1) Wait for dial tone 
2) Dial the destination number 
3) Wait for call connection, then talk 
This can be accomplished by programming the ACS with ‘#80327’. This 
group of digits translates to: 
1) #803 Wait for minimum duration of precise dial tone for up to 6 
seconds 
2) 2 Dial destination number 
3) 7 Cut through 
Since the dialer starts in the split condition, the cut through code must 
be entered to restore the connection so that talking can occur. 
4.27 An example for access to a typical carrier may require pro- 
gramming as outlined by the digits ‘#8033#625427’. These 
translate to: 
1) #803 Wait for minimum duration of precise dial tone for up 
to 6 
seconds 
2) 3 Dial access number 
3) #625 Wait for 400 ms of tone from OCC for up to 10 seconds 
4) 4 Dial the authorization code 
5) 2 Dial the destination number 
6) 7 Cut through 
i Page 21  
						

							SECTION MITL8350-047-1 OO-NA 
The arrangement above allows for all sorts of combinations. In order 
to appreciate the range of possibilities, the five strings that can be 
dialed are named to coincide with typical applications. These names 
are really general purpose and have the properties as outlined in Table 
5 below. 
TABLE 5: GENERAL PURPOSE STRINGS/NUMBERS 
STRING 
DESTINATION 
ACCOUNT 
ACCESS 
AUTHORIZATION 
CENTREX 
PROPERTY 
First digits dialed by the user; passed 
through the search tables. 
Second item dialed by the user; can 
be substituted; can hold up dialing. 
Entered at programming time. 
Entered at programming time. 
Entered at programming time. 
4.28 It is evident that these strings can be assembled in any order in 
the ACS. They do not have to function in the manner that their 
titles suggest. For instance, a private carrier network requires an au- 
thorization code of 1234~~x5678, where the xxx is a code entered by 
the user to identify the account. 1234 could be assigned to the au- 
thorization string, 5678 to the Centrex string, and the route pro- 
grammed to accept a three digit fixed length account code. Then part 
of the ACS would be programmed with ‘459’ that translates to ‘Dial 
authorization, dial account, and dial Centrex’. 
SPEED CALLS 
4.29 The speed call entries have two associated parameters. These 
are the key and the route override. The key is a single digit that 
can selectively block dialing to any line. Note that all lines share the 
same speed call directory, and that any lines can be blocked from 
dialing any speed call number. The route override can force the call 
onto any of the four routes, or process the call through the search 
tables, or force the call to go out without any route selection 
(transparent). 
NOT ON NETWORK (NON) CHECKING 
4.30 Some networks return specific tones if the number requested is 
‘Not on Network’. The ACS has a programmable parameter that, 
if set, will make the Dialer wait for the programmed number of sec- 
onds, and, if a tone is detected, the call will be dropped. The destina- 
tion number will then be dialed using the Route #0 access method. In 
addition, the destination string is automatically entered in the search 
tables as FRO (Force Route 0), along with an expiry date tag. The date 
tag can be from 0 to 90 days in increments of ten days. Once 
Page 22  
						

							SECTION MITL8350-047-l OO-NA 
entered, all entries in the search tables that have expiry tags are 
decremented at midnight. Those tags that return to zero on decrement 
are cancelled. This means that, after the programmed number of days, 
the search tables would return to their original state. 
4.31 There is no parameter in the programming that controls DTMF 
to pulse conversion. if the Central Office type is programmed as 
rotary dialing, then any route access will start the call with rotary 
dialing. The ACS can have a ‘change to DTMF’ code 
that will instruct 
the Dialer that the signalling to the private carrier is to be performed in 
DTMF. Calls that have been ‘cut-through’ or ‘dial and cut-through’ due 
to a searching action will not perform DTMF to pulse conversion. 
4.32 Paragraphs 4.30 and 4.31 illustrate why Route #0 is recom- 
mended for use in accessing the DDD Network. 
CALL RECORDS 
4.33 Every time a call is terminated, the Dialer will output a call 
record to the Computer (RS-232) port. This output consists of a 
string of ASCII characters that describe the call. The format for the 
output is fixed so that the port can be connected to either a printer or 
to an external processor. The latter can use the data to generate 
statistics or call costing data. The printout can label the routes that are 
selected by using the appropriate programming. 
CENTREX OPERATION 
4.34 If the Centrex access digit is programmed, the Dialer will red- 
ognize the ‘outside line’ access code, routing all internal calls 
transparently. Note that all of the ACSs should be programmed to 
include the ‘dial the Centrex’ code. Each route has a separate Centrex 
string that would allow one to access WATS or FX groups, instead of 
regular trunks. 
CALL RECORDING OPERATION 
4.35 The SMarT-lTM Common Carrier Access Dialer and Call Control- 
ler can easily be programmed to send a printable call record to 
a variety of electronic storage devices. The call record indicates the 
originator of the call, the call duration, the dialed numbers, and other 
data. 
THIS CALL RECORD SHOULD NOT BE CONSIDERED A 
PERFECT RECORD OF THE CALL, NOR SHOULD IT BE 
CONSIDERED AS A LEGAL ENTITY. THERE ARE MANY 
CASES IN WHICH THE CALL RECORD PRODUCED BY THE 
SMarT-1 TM DIALER MAY DIFFER FROM THAT PRODUCED 
BY THE OCC. 
Page 23