Mitel Voice Processing Solutions Instructions Manual

a? 5733 
Page 4 of 4 
VoiceMemo Release G.OA and later 
Step 
The system displays the possible actions. 
prompt: (H) Set signal hi 
(L) Set signal lo 
(W) Wait signal hi 
(V) Wait signal lo 
(P) Sleep 
(C) Send access code 
(S) Send string 
(R) Read string 
(Y) Wait string 
(F) Flush device 
(D) Display actions 
(X) Exit 
Response: The letter of the action that you want to add to the command sequence. 
Most of the action selections will prompt you for more information, 
such as the signal to set or wait...

Create a New MESA-Net Async 
Hardware Type CP Page 1 of 3 
VoiceMemo Release 
G.OA and later 
This procedure describes how to create a completely new hardware type. This is not the 
same as assigning a number designation to a pre-programmed (default) hardware type, 
which is described in Cl? 5732. 
Prior to starting this procedure, you must have the documentation for the 
communication device that will use this hardware type so that you know what actions 
are required to originate and answer calls. See...

cl? 5710 
Page 2 of 3 
VoiceMemo Release 6.OA and later 
Step 
7. Define the originate actions. 
Select: (0) Originate call 
Jr0m.t: ORIGINATE CALL 
(H) Set 
signal hi 
(L) Set 
signal lo 
(W) Wait signal hi 
(V) Wait signal lo 
(P) Sleep 
(C) Send access code 
(S) Send string 
(R) Read string 
(Y) Wait string 
(F) Flush device 
(D) Display actions 
(X) Exit 
Response: The letters of the actions that are required to originate a connection 
using this hardware type, one at a time. 
Most of the action...

cl? 5734 
Page 3 of 3 
VoiceMemo Release 6.OA and later 
Step 
12. Verify the settings in the new hardware type. 
Select: (S) Show Types 
The system displays the actions in the hardware type that you just created. Review 
the display to make sure that it is correct. If necessary, repeat any of the above steps 
to make changes. 
13. Exit to the Hardware Type Menu to save your changes. Reference 
Dot. RN. A  

The Network Node Table stores information that is essential for the local node to 
communicate with other nodes on the network. The table contains one entry for 
each node on the network, and that entry contains information such as the remote 
node number and its phone number or II? address. This chapter provides detailed 
information about the fields in the Network Node Table and how they are used by 
MESA-Net Async and MESA-Net TCP/IP. 
It is very important that you plan out your MESA-Net network...

Configuring‘the Network Node Table 
etwor 
I 
i Node Number 3 q Node Name 5an Jose 
I 
I TCP/IP Connection Ya 
IP 
Address 
I 
i Hardware Type 2 
s String 
(access code) 4082941192 
I 
/ Parallel Link Delay 10 
0 Maximum Links 4 
s 
1 Analog AMIS Connection Ya Access- N 
Figure 5- 1 Sample Network Node Table Configuration 
Worksheet 
Worksheet 
Node Number: The number of the node for this entry. Each MESA-Net node on 
the network must be represented by a unique number. You can use numbers from 
1 
to 8...

Configuring the Network Node Table 
The “Send Access Code” originate action in the Hardware Type causes the local 
node to dial this string. The examples later in this chapter demonstrate how to 
formulate the string that is necessary to reach a remote node. 
Hardware Type: The device number, 
1-7, of the Hardware Type that MESA-Net 
Async sofrware must use to communicate with the node. 
For MESA-Net TCP/IP nodes, the hardware type is always ETHERNET. There is 
no hardware type for AMIS nodes, since AMIS...

Configuring the Network Node Table 
San Jose’ 
New York 
ommunication 
Denver 
(303) 868-5442 Answer 
(312) 865-4321 
5109MNET 
Figure 5-1 Sample MESA-Net Async Modem 
The Network Node Table entries for San Jose are: 
NODE NAME PROTO 
STRING HARDWARE 
2 Chicago ASYNC 3128654321 2 = CONCORD 
4 New York ASYNC 21268943217 2 = CONCORD 
6 Denver ASYNC 3038685442 2 = CONCORD 
The Network Node Table entries for Chicago are: 
NODE NAME PROTO STRING 
HARDWARE 
-.h 
1 San Jose ASYNC 4089233311 2 = CONCORD 
4 New...

ConfiguringtheNetworkNodeTable 
2 Chicago ASYNC 3128654321 
2 = 
CONCORD Y 15 1 
6 Denver ASYNC 3038685442 
2 = 
CONCORD Y 15 1 
ork 
Figure 5-2 shows a network in which some of the nodes are connected using MESA- 
Net Async over modems and some are connected using MESA-Net TCP/IP over 
Ethernet. 
Seattle 
2-Module Series 6 
Server Boston 
Originate 
San Jose 
2-Module Series 6 
Server 
IP Address 154.22.4.55 
Figure Sample odem 
and Ethernet Network 
The Network Node Table entries for San Jose are:...