Mitel Voice Processing Solutions Instructions Manual

							Working with Tellabs Equipment 
Dataplexer directly to the Xplexer without any dialing. Calls from the network to 
Long Island are routed through the New York Xplexer to channel 2 of the 
Dataplexer, through the modems, and then to the Long Island answer link. The 
Long Island node can now use the standard Tellabs hardware type, and Long Island 
access codes change from telephone numbers to Xplexer/Dataplexer addresses. The 
node tables shown in Example 2 are amended as follows (changes in italics): 
The Network Node Table entries for San Jose are: 
B-G 
Node Number: 3 4 6 
Node Name: Long Island New York Denver 
String: 
4/1.2 411.7 611.7 
Hardware type: 
1 1 1 
Access (Y/N) : Y Y Y 
The Network Node Table entries for Denver are: 
Node Number: 
Node Name: 
String: 
Hardware type: 
Access (Y/N): 1 
San Jose 
l/O.7 
1 
Y 
3 
Long Island 
4i1.2 
1 
Y 
4 
New York 
411.7 
1 
Y 
The Network Node Table entries for New York are: 
Nodp Number: 
Node Name: 
String: 
Hardware type: 
Access (Y/N) : 1 
San Jose : 
l/O.7 
1 
Y 
I 
3 6 
Long Island Denver 
4/I.2 611.7 
1 1 
Y 
Y 
The Network Node Table entries for Long Island are: 
Node Number: 
1 4 6 
Node Name: San Jose 
New York Denver 
String: 
l/O.7 411.7 611.7 
Hardware type: 1 1 1 
Access (Y/N) : Y Y Y  
						

							Working with Tellabs Equipment 
in 
P= 
This section provides two examples of modifying default hardware types to meet the 
needs of a particular site. These examples are based on Figure B-2. 
(To long llslan 
A hardware type that routes all network calls to Long Island through Channel 2 of 
the New York node’s Dataplexer, then over the modem connection, must be created 
to allow other nodes to call the Long Island answer link. The originate actions of 
this hardware type, which we will call Hardware Type 4, are a combination of the 
Tellabs and Concord Dialaccess 296 Modem default hardware types. 
The answer and disconnect actions in Hardware Type 4 will be used by all nodes 
other than Long Island. Answer and disconnect actions are dependent on the local 
device, and since all other nodes on this network have Tellabs equipment, the answer 
and disconnect actions for this hardware type are identical to the Tellabs protocol. 
In fact, the Tellabs default hardware type will be modified to create Hardware Type 
4. 
The action strings for the new hardware type are shown below. Tellabs originate 
actions are in italics. Since all calls to Long Island from other network nodes must 
be routed through channel 
2 of the New York Dataplexer, the “send access code” 
step in the default Tellabs originate actions is modified to “send string.” The string 
is the address 4/l .2, meaning “Node 4 (New York)/composite link 
1 .Dataplexer 
channel 2.” 
After the call reaches channel 2 of the New York node, it is passed on to the Concord 
Dialaccess 296 modem, which must dial up the modem that is connected to the 
answesi link of the Long Island node. To allow the originating node to direct the 
New York modem to perform these s the originate actions of the Concord 
Dialaccess 296 modem default hardware type (shown in boldface) are appended to 
the end of the Tellabs instructions. 
When the “send access code” step is performed, the originating system instructs the 
New York modem to outdial the telephone number of the modem attached to the 
Long Island answer link. The telephone number can be hard-coded as a string, 
rather than as an access code, but the “read access code” step allows the network to 
use this hardware type to communicate with other satellite systems through the New 
York node, if necessary. 
B-7  
						

							Working with Tellabs Equipment 
riginate Actions 
r 
- 
- 
j 
; 
7 
3 
3 
10 
11 
12 
13 
14 
15 
16 
17 
18 
19 
20 
21 
- 
Action 
Send string 
Sleep 
Flush device 
Sleep 
Yeend string 
Sleep 
Read string 
send string 
Sleep 
Send string 
Sleep 
Flush device 
Send string 
Send access code 
Send string 
Flush device 
Read string 
Flush device 
Sleep 
Read string 
Sleep Parameter 
,r 
?/I.2 
,onnected 
;MC
 
iTZ
 
ITDT 
Ifrom Network 
Node Table) 
,r 
RING 
CONNECT Timeout 
seconds 
) seconds 
? seconds 20 seconds 
3 seconds 
j seconds 
15 seconds 
20 seconds 
5 seconds 
4 
nswer Actions 
I I I 
; 
4 Read string connected 
0 seconds 
B-8  
						

							Working with Tellabs Equipment 
ine P nal 
Action 
Set signal lo 
Set signal lo 
Sleep 
Set signal hi 
Set signal hi 
Sleep Parameter 
DTR 
RTS 
DTR 
RTS Timeout 
5 seconds 
2 seconds 
2 seconds 
CD (Carrier Detect) 
e# 
The originate actions of Hardware Type 5 are also a combination of the Tellabs and 
Concord Dialaccess 296 modems originate actions. This hardware type routes all 
calls from Long Island over the modem connection to Channel 3 of the New York 
node’s Dataplexer, then through the New York Xplexer to all other nodes. 
The answer and originate actions will be used by the Concord Dialaccess 296 
Modem at the Long Island node; it is easiest to modify the Concord Dialaccess 296 
Modem hardware type to create Hardware Type 5. 
The action strings for the new hardware type are shown below. Concord Dialaccess 
296 modem originate actions are in italics. Since all calls from Long Island to other 
network nodes must be routed through channel 3 of the New York Dataplexer, the 
“send access code” step in the default Concord Dialaccess 296 modem originate 
actions is modified to “send string,” anti the string is the telephone number of the 
modem attached to channel 3. 
After the call reaches channel 3 of the New York node, it is passed on to the Xplexer, 
which routes the call to the destination node on the network. To direct the New 
York Xplexer to perform these steps, the originate actions of the Tellabs default 
hardware type (shown in boldface) are appended to the end of the Concord 
Dialaccess 296 modem instructions. When the “send access code” step is performed, 
the Long Island node will send the address of the destination node to the New York 
Xplexer, which will perform all the necessary switching. 
B-V  
						

							Working with Tellabs Equipment 
riginate Actions 
1 
2 
3 
4 
c 
; 
17 
E 
C 
I 
1 
I 
1 
1 
1 
1 
, 
; 
T 
i 
1 
.O 
.l 
12 
13 
14 
1.5 
16 
17 
18 
19 
- 
- 
20 
21 
- 
Answer Actions 
Action 
2nd string 
leep 
‘end string 
Yeep 
%ah device 
Yend string 
Yend string 
Yend string 
FLush device 
Read string 
FLusb device 
Sleep 
Read string 
SLeep 
Send string 
Sleep 
Flush device 
Sleep 
Send access code 
Sleep 
Read string 
Action 
Send string 
Sleep 
Send string 
Sleep 
Flush device 
Read string 
Sleep 
Flush device 
Read string Parameter 
Nclr 
4TDT 
GY432I 
\f” 
RING 
CONNECT 
\I 
(from NetworE 
Node Table) 
connected 
--h 
Parameter 
SMC
 
AT
 
RING 
CONNECT seconds 
seconds 
?O seconds 
3 
5 
L 
i 
1 
; 
15 seconds 
?O seconds 
5 seconds 
J seconds 
2 seconds 
15 seconds 
2 seconds 
20 seconds 
Timeout 
5 seconds 
3 seconds 
0 seconds 
3 seconds 
20 seconds 
.-L 
Timeout 
B-10  
						

							r 
Working with Tellabs Equipment 
1 
2 
3 
4 
5 
6 
7 
8 
9 
10 
Action 
Set signal lo 
Set signal lo 
Sleep 
Set signal hi 
Set signal hi 
Sleep 
Send string 
Sleep 
Send string 
Sleep 
CD (Carrier Detect) Parameter 
DTR 
RTS 
DTR 
RTS 
ATZ
 
SMC
 Timeout 
5 seconds 
2 seconds 
2 seconds 
5 seconds 
3 seconds 
B-11  
						

							absorb 
digits, 6-6 
access codes, 6-6 
network node table, 5-2 
special considerations, 5-6 
Analog AMIS 
in network node table, 5-2 
answer actioons, defined, 4-l 
answer link 
change to originate, CP 5715 (4) 
area code 
in network dialing plan, 6-9 
baud rate 
configuring, CP 5712 (4) 
default, 4- 10 
recommended by hardware type, 4-10 
billing, 10-l 
broadcast mailboxes 
for transparent network messaging, 6- 
11 
function with MESA&et, 9-2 
message, 6-l 1 
name, 6- 11 
c 
checklist 
pre-installation, l-10 
communication devices, defined, 4-l 
communication parameters 
configuring, CP 5712 (4) 
compression rate, 8-3 
configuration 
task overview, l-8 
configure 
MESA-Net Async, CP 5735 (3) MESA-Net TCP/IP, CP 5’718 (2) 
network class of service, CP 5730 (8) 
network mailboxes, 9- 1 
network node table, CP 5719 (5) 
network queues, 7-l. CP 5729 (7) 
configuring failure counts, 4-10 
create 
digits translation table entry, CP 
5724 (6) 
prefur/node pairs, CP 5724 (6) 
dataplexers, B-l 
delete 
digits translation table entry, CP 
5725 (6) 
MESA-Net Async links, CP 5713 (4) 
preftinode pairs, CP 5725 (6) 
dialing plan, See network dialing plan 
dial-up connection, 3-3 
digits to absorb, 6-6 
and access codes, 6-6 
and local mailboxes, 6-6 
and same-length mailbox numbers, 6-7 
Lonfigure, CP 5724 (6) 
modify, CP 5727 (6) 
digits translation table 
create entry, CP 5724 (6) 
defined, l-4 
delete entry, CP 5725 (6) 
digits to absorb, 6-6 
explanation, 6-3 
modify entry, CP 5727 (6) 
node prefures, 6-3 
report, 10-5 
view, CP 5726 (6) 
with network dialing plan, 6-l 
direct connections, 3-2 
direct network addressing, 6-9 
disconnect actions, defined, 4- 1 
Index- 1  
						

							Index 
distribution lists 
adding network mailboxes, 9-1 
E 
ethernet card 
with MESA-Net TCP/IP, 2-l 
example 
simple MESA-Net Async network, 3-4 
examples 
network addressing, 6-12 
network dialing plan, 6-12 
node tables using Async and TCP/IP, 
5-5 
node tables using modems, 5-3 
failure counts 
configuring, CP 5712 (4) 
fault tolerance 
with MESA-Net Async Load Share, 3-6 
fax messages 
NCOS settings, 8-3 
full-duplex 
in MESA-Net Async, 3-4 
G 
group class of service 
across network, 8-1 i 
l-l 
hardware 
report, 10-8 
hardware types 
assigning, 4-2 
assigning to device numbers, CP 
5732 (4) 
assigning to links, CP 5712 (4) 
default, 4-3 
default settings, A- 1 
defined, l-4 
modify, CP 5733 (4) 
network node table, 5-3 
hardware types, defined, 4-l 
Index-2 
I 
inquire 
digits translation table entry, CP 
5726 (6) 
prefur/node pairs, CP 5726 (6) 
inquire about links, CP 5716 (4) 
instahation 
task overview, 1-8 
IP address 
network node table, 5-2 
L 
line drop signal 
defined, 4-6 
types monitored by MESA-Net 
software, 4-7 
line drop signal, defined, 4-1 
line groups 
and network dialing plan, 6-7 
links 
answer, defined, l-4 
change answer/originate assignment, 
CP 5715 (4) 
configuring, CP 5712 (4) 
delete, CP 5712 (4) 
originate, defined, l-4 
links, defined, 4-l 
list 
- digits translation table entry, CP 
* 5726 (6) 
load balancing 
with MESA-Net Async Load Share, 3-7 
load share 
configuring, CP 5710 (3) 
definition, 3- 1 
description, 3-6 
M 
mailbox message count 
with queued network messages, 9-2 
mailboxes 
configure network, 9-l 
modifying for MESA-Net, 9-l 
same-length numbers, 6-7  
						

							MESA-Net 
configuration reports, 10-5 
introduction to, l-l 
message flow, 1-5 
terms and concepts, 1-3 
MESA-Net Async 
access codes, 5-2 
configure, CP 5735 (3) 
configuring links, CP 5712 (4) 
configuring load share, CP 5710 (3) 
conf&uring parallel links, CP 5711(4) 
dial-up connection, 3-3 
direct connections, 3-2 
hardware options, 3-2 
introduction to, l-2 
load share, 3-6 
load share, definition, 3-l 
multiple links, 3-4 
overview, 3- 1 
parallel links, 3-5 
simple network example, 3-4 
with MESA-Net TCP/IP, 1-3 
MESA-Net Async hardware and links, 
confguring, 4- 1 
MESA-Net Async Load Share 
fault tolerance, 3-6 
load balancing, 3-7 
MESA-Net TCP/IP 
configuration, 2- 1 
configure, CP 5718 (2J 
hardware, 2- 1 
introduction to, l-2 
network usage, 2-l 
overview, 2-l 
with MESA-Net Async, l-3,2-2 
with private network, 2-l 
with public network, 2-l 
message broadcast mailboxes, 6-11 
message count threshold, 7-4 
modify 
digits translation table entry, CP 
5727 (6) 
hardware types, CP 5733 (4) 
prefixnode pairs, CP 5727 (6) 
module number 
with MESA-Net TCP/IP, 2-2 Index 
multiple links 
definition, 3- 1 
description, 3-4 
name broadcast, l-5 
name broadcast mailboxes, 6-11 
NCOS, See network class of service 
network addressing 
configuring, 6- 1 
examples, 6-12 
planning, 6-2 
worksheet, 6-2 
network billing, 10-l 
network class of service 
configuring, 8- 1 
default, 9-1 
defined, l-5 
feature descriptions, 8-1 
in mailbox creation, 9- 1 
maximum number, 8-l 
network data link 
report, 10-6 
network dialing plan 
addressing by area code and phone 
number, 6-9 
creating, 6-7 
defined, l-4 
examples, 6-12 
FJ character, 6-9 
P character, 6-8 
star prefer, 6-10 
uniform, 6-10 
variable-length network addresses, 6-8 
with digits translation table, 6-l 
network fax messages 
NCOS settings, 8-3 
network link 
data report, CP 5716 (4) 
report, 10-9 
serial port report, CP 5716 (4) 
network mailboxes 
adding to distribution lists, 9-l 
configure, 9-l 
network message counters, lo- 1 
Index-3