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 for, or the number of seconds to sleep, or 
the string to send/read. Select your choices from the menus to define the 
actions. 
9. If desired, change the Line Drop Signal. 
Select: 
(D) Line Drop Signal 
Prompt: SIGNAL TO SET/WAIT FOR 
(1) DTR 
(data terminal ready) 
(2) RTS (request to send) 
(3) BREAK 
(4) CT5 (clear to send) 
(5) DSR 
(data set readyk 
(6) RI (ring) 
(7) CD (carrier detect) 
Response: The number that corresponds to the serial communications signal that 
indicates a broken connection. 
10. Verify the settings in the modified hardware type. 
Select: 
(S) Show device 
The system displays the actions in the hardware type that you just modified. Review 
the display to make sure that it is correct, If necessary, repeat any of the above steps 
to make changes. 
11. Exit to the Hardware Type Menu to save your changes. Reference  
						

							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 Chapter 4 for detailed explanations of the 
components of a hardware type. 
Step Reference 
1. Reach the Hardware Type Menu. 
2. Select to create a hardware type. 
’ Select: (C) Create a hardware type 
Proqt: Module number on which to create hardware type 
(l-4): 
Response: Enter the number of the module, 1-4, on which you are assigning the 
hardware type. Menu Map 
13 
3. Assign a number to the hardware type. 
Proppt: pevice number to create (l-7): 
Response: Enter a number, from l-7, that you want to assign to the hardware type. 
Typically, you start with number 
1 for the first device and then 
increment the number assignment for additional devices. 
4. Choose not to use one of the pre-programmed hardware types. 
Prompt: Select a default hardware type? (y/n)[n]? 
Response: Enter n to heate a new hardware type. -ir 
The system displays the Create Hardware Type menu. 
5. Give the new hardware type a name. 
Select: (N) Name 
Prompt: 
Enter name for device: 
Response: A name (l-16 characters) for the device that will use this hardware type. 
6. Define the actions for the hardware type. 
Select: (A) Actions 
Prompt: 
Action Types menu 
Dot. Rw. A  
						

							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 selections will prompt you for more information, 
such as the signal to set or wait for, or the number of seconds to sleep, or 
the string to send/read. Select your choices from the menus to define the 
originate actions. 
8. Exit back to the Action Types menu when you have defined all of the originate call 
actions. 
9. Repeat steps 7 and 8 KO define the Answer Call and Disconnect Call actions. 
10. Exit back to the Create Hardware Type Menu. ” 
1. Set the Line Drop Signal. 
Select: 
(D) Line Drop Signal 
Prompt: SIGNAL TO SET/WAIT FOR 
(1) DTR (data terminal ready) 
(2) RTS (request to send) 
(3) BREAK 
(4) CTS (clear to send) 
(5) DSR (data set ready) 
(6) RI (ring) 
(7) CD (carrier detect) 
Response: The number that corresponds to the serial communications signal that 
indicates a broken connection. Reference 
Dot. Rev. A  
						

							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 before configuring 
the Network Node Table on each node. You must know the node number and 
phone number or II? address of each remote node, plus other information, before 
you can create an entry for the node. Be sure to completely fill in a section of a 
Network Node Table Configuration Worksheet for each remote node and one for 
the local node before starting to create entries in the table. (You should create an 
entry for the local node in the table as a reference, but set it to have access disabled.) 
e le nfi 
ee 
You configure the Nenvork Node Table using the Network Node Access Table 
Maintenance Menu, which is a submenu of the Network Maintenance Menu. The 
fields in the Network Node Table Configuration Worksheet correspond to the 
information you must enter when you create a new node entry. The fields are 
described below the sample worksheet. A blank worksheet for you to copy and use is 
at the end of this chapter. 
5-l  
						

							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 19 1, but the maximum number of nodes is 1500. 
Node Name: A descriptive name for the node (e.g. New York, Chicago) of up to 
13 
alphanumeric characters, including capitals and spaces. The node name is not 
required; MESA-Net software recognizes nodes by their numbers. 
Analog AMIS Connection: For all MESA-Net nodes, circle N. The AMIS Analog 
Networking optional feature also uses the node table for administered connections 
(where the message sender does not have to enter the node phone number), and you 
may want to include those connections in your planning. 
TCP/IP Connection: Circle Y for all remote nodes that the local node accesses using 
MESA-Net TCP/IP. 
II? Address: The II? address of the remote node, if it uses MESA-Net TCP/IP 
String: In MESA-Net Async, the string is the access code (usually the phone 
number) that is dialed by the local node to make a connection to the remote node. 
The string can be up to 
16 alphanumeric characters in length. 
5-2  
						

							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 connections are made from a phone 
port. 
Access: Circle Y (accessed enabled) for all nodes except the local node. If necessary, 
you can set access to N to suspend access to a node without deleting the node from 
the Network Node Table. 
When users try to make messages to a disabled node, they are informed that the 
destination is “not a valid remote mailbox number.” When you disable access to a 
node that already has messages queued, the MESA-Net software holds the messages 
until the Message Waiting Threshold is reached, and then sends receipts to all 
senders, informing them that their messages could not be delivered. Once receipts 
are sent, the messages are purged from the queue. 
Parallel Link Delay: (Requires the Parallel Links optional feature) Specify the 
number of minutes that an existing connection must be open before another link is 
established. Set this to 0 to have the originating node create a new connection as 
soon as the previous one succeeds. 
Maximum LUs: (Requires the Parallel Links optional feature) Specify the 
maximum number of links to be used to communicate to the remote node. 
-ri- 
e e 
This section presents Network Node Tables for two sample networks. The first 
example shows the Network Node Table for a MESA-Net Async network. The 
second example shows a combination MESA-Net Async and MESA-Net TCP/IP 
network. 
rk using odems 
Figure 5-l shows a network in which all nodes use identical modems for 
communications. 
5-3  
						

							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 York ASYNC 21268943217 2 = CONCORD 
6 Denver ASYNC 3038685442 2 = CbNCORD 
The Network Node Table entries for Denver are: 
NODE NAME PROTO 
STRING HARDWARE 
1 San Jose ASYNC 4089233311 2 = CONCORD 
2 Chicago ASYNC 3128654321 2 = CONCORD 
4 New York ASYNC 21268943217 2 = CONCORD 
The Network Node Table entries for New York are: 
NODE NAME 
PROTO STRING 
HARDWARE 
1 San Jose ASYNC 4089233311 
2 = CONCORD 
5-4 
ACCESS 
Y 
Y 
Y 
ACCESS 
Y 
Y 
Y 
ACCESS 
Y 
Y 
Y 
ACCESS 
Y PARALLEL LINKS 
DELAY MAX 
15 1 
15 2 
15 1 
PARALLEL LINKS 
DELAY 
MAX 
15 
2 
15 
I. 
15 1 
PARALLEL LINKS 
DELAY MAX 
15 1 
15 1 
15 1 
PARALLEL LINKS 
DELAY MAX 
15 I.  
						

							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: 
NODE NAME PROTO STRING 
HARDWARE ACCESS 
2 
Boston 
ASYNC 5081112222 
2 = CONCORD Y 
3 Seattle 
TCP/IP 143.191.5.22 0 = ETHERNET 
Y 
The Network Node Table entries for Boston are: 
NODE NAME 
PROTO STRING 
HARDWARE 
ACCESS 
1 San Jose ASYNC 
4082223333 2 = CONCORD 
Y 
3 Seattle ASYNC 6131112222 
2 = CONCORD 
Y PARALLEL LINKS 
DELAY MAX 
15 1 
15 2 
PARALLEL LINKS 
DELAY 
MAX 
15 
1 
15 
1 
5-5