Mitel Voice Processing Solutions Instructions Manual

							Network Queue Parameters Report ............................................................ 10-S 
The Hardware Report ................................................................................ 10-8 
Other Configuration Reports ..................................................................... 10-9 
Real-time MESA-Net Reports ........................................................................ 10-9 
Network Queue Report .............................................................................. 10-9 
Network Link Query .................................................................................. 1 O-9 
Link Node Dump ...................................................................................... 10-9 
Network Statistics Reports ........................................................................... 10-10 
The Network Usage Report.. .................................................................... 1 O-l 0 
The Network Usage Summary Report ...................................................... 10-l 1 
Concord 296-2 Modem .................................................................................. A-l 
Concord DialAccess Modem ........................................................................... A-3 
Microcom Modem .......................................................................................... A-4 
TELLABS ....................................................................................................... A-5 
Direct Connect ............................................................................................... A-6 
Telebit Modem ............................................................................................... A-7 
XyLoGiC AnNeX ........................................................................................... A-S 
HT-P4004 DSU ............................................................................................. A-9 
Paradyne V.34 Modem ............................. ..~.......................” ........................ A-10 
US Robotics Courier V.34 Modem.. ............................................................. A-l 1 
orleing with l’ellabs Equipment 
Configuring Tellabs Multiplexer Equipment .................................................. 
B- 1 
Example MESA-Net Async Tellabs ‘Networks ................................................. 
B- 1 
Example 1: Network using Tellabs 
Dataplexer/Xplexers ............................... 
B-2 
Example 2: Tellabs Dataplexer/Xplexers and Modems Using Dial-Up 
Connections ................................................................................................. B-4 
Example 3: Tellabs Dataplexer/Xplexers and Modems Using Dedicated Phone 
Line Connections ......................................................................................... 
B-5 
Examples of Modifying Hardware Types ........................................................ B-7 
Example 4: Hardware Type #4 (To Long Island through New York) ........... 
B-7 
Example 5: Hardware Type #5 (From Long Island) ..................................... B-9 
List tigra 
Vi  
						

							Table of Contents 
en 
ist les 
Table l-l Overview of MESA-Net Tasks ............................................................. l-8 
Figure l-l Simple MESA-Net Topology .............................................................. l-l 
Figure l-2 Mixed MESA-Net Async and MESA-Net TCl?/II? Topology ............... 
l-3 
Figure 
l-3 Sample MESA-Net Call Flow .............................................................. l-7 
Figure 3-l MESA-Net Async Direct Connection .................................................. 
3-3 
Figure 3-2 MESA-Net Async Modem Connection.. .............................................. 3-3 
Figure 3-3 A Simple MESA-Net Async Network.. ................................................ 3-4 
Figure 3-4 MESA-Net Async with Multiple Links ................................................. 
3-5 
Figure 3-5 MESA-Net Async with Parallel Links.. ................................................ .3-6 
Figure 3-6 MESA-Net Async Load Share .............................. .I ............................. 3-7 
Figure 3-7 MESA-Net Async with Multiple Links and Parallel Links.. ................. .3-S 
Figure 4-I Hardware Types, Nodes, and Links.. ................................................... .4-2 
Figurl 4-2 Hardware Types for Comm-unications Devices ................................... .4-3 
Figure 4-2 Sample Hardware Types Worksheet.. .................................................. .4-S 
Figure 4-3 Sample Links Worksheet.. ................................................................. .4-13 
Figure 5-l Sample Network Node Table Configuration Worksheet.. .................... 5-2 
Figure 5-l Sample MESA-Net Async Modem Network.. ...................................... 
5-4 
Figure 5-2 Sample Modem and Ethernet Network ................................................ 
5-5 
Figure 6- 1 Example of MESA-Net Using the Dialing Plan and Digits Translation 
Table ............................................................................................... 6-l 
Figure 6-I Sample Planning Network Addressing Worksheet.. ............................. .6-2 
Figure 6-2 Name and Message Broadcast Mailboxes .......................................... .6-l 1 
Figure 7- 1 Interaction of Network Queue Thresholds ......................................... .7-2 
Figure B-l Sample Tellabs Network.. .................................................................... B-2 
vii  
						

							Figure B-2 Sample Tellabs 
and Modem Network . . . . . . . . . . . . . . . . . ~ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 
. . . 
Vlll  
						

							Table of Contents 
If you want to have a solid understanding of what is involved in administering 
MESA-Net, read this entire guide. 
If you want to read only those parts of the guide that directly apply to you, then first 
read the section “Overview of MESA-Net Tasks” in Chapter 
1. This section 
summarizes the MESA-Net tasks and points you tzo the reference material and 
procedures that describe the tasks. The section also provides a checklist of what 
arrangements you must make before MESA-Net- is installed. 
ix  
						

							MESA-Net is an optional feature for Centigram’s Series 6 Communications Server. 
It allows you to connect Series 6 Servers and 5.x AH? systems together to form a 
digital network. With MESA-Net, mailbox owners can make voice or fax messages 
for mailboxes on remote servers in the same manner as they make messages to local 
mailboxes. For example, a user can log into a VoiceMemo mailbox, make a message 
for several recipients, some local and some remote, and send that message. Users can 
also answer messages and forward (give) messages to users on remote nodes. Figure 
1-l shows a simple MESA-Net network. 
Simple MESA-bletTopology 
Seattle 
Series 6 Server 
The External Interface Card can 
be either an Expansion Serial 
Card or an Ethernet Card. 
San 
Jose 
2-Module Series 6 Server 5lcxnnnet.fh3 
Figure I-1 Simple -Net “fopobgy 
MESA-Net transmits messages in digital form, as opposed to actually playing 
messages over the phone lines to remote systems. Digital transmission increases 
throughput and preserves speech qualiT. 
MESA-Net provides two networking options: 
h4ESA-Net Async and MFBA-Net 
TCl?/Il?. 
MESA-Net Async uses dial-up or direct connections through serial ports 
and modems or multiplexers. MESA-Net TCl?/Il? supports TCl?/IP over lOBase-T 
I-1  
						

							Introduction to MESA-Net 
Ethernet. You can use both options in a single network to meet the requirements of 
each site. 
The building blocks of a MESA-Net network are Centigram servers. Each server 
functions as a node on the network. MESA-Net is scaleable so that it can work on all 
Series 6 server models, providing lower-cost, lower throughput networking on 
smaller servers and higher throughput messaging on larger servers, Each MESA-Net 
node is equipped with either serial cards or ethernet cards, and is connected to 
communications channels such as phone lines or a wide area network. 
MESA-Net Async connects Centigram servers together by means of direct 
connection, modems, and multiplexers (or any combination of these). MESA-Net 
Async is scaleable to support the varied requirements of different sites and networks. 
4B 
8 
8 
8 
@ For nodes with low network traffic volume, a simple MESA-Net Async 
installation enables two links. The node can connect to all other MESA- 
Net Async nodes on the network, but can only connect to two nodes at 
any given time. 
The Multiple Links (also called Link Enable) optional feature allows a 
node to simultaneously connect to as many as 16 nodes (32 for Model 
640 servers). This feature is useful at centralized hub nodes. 
The Parallel Links optional feature increases throughput by enabling 
multiple links between two nodes. The additional throughput can 
significantly speed up message delivery between high-traffic nodes. 
The MESA-Net Async LTad Share configuration for Model 640 servers 
provides fault-tolerance and balanced trafhc load. MESA-Net links can 
be installed in more than one module to share the load, and one module 
can continue to process network traffic if the others are out of service. 
MESA-Net TCI?/II? connects Centigram servers together using 1 OBase-T Ethernet. 
MESA-Net TCI?/II? can use an existing private network, or it can send messages over 
a public network. The high bandwidth of Ethernet connections allows for a large 
volume of network traffic, providing users with network service that is almost 
indistinguishable from local messaging. 
In order to use MESA-Net TCl?/IP, a Centigram server also must have the 
VoiceMemo TCP/IP Interface optional feature installed. This optional feature 
1-z  
						

							Introduction to MESA-Net 
provides a single point of configuration for all TCP/II’ applications on Centigram 
servers, such as MESA-Net TCP/Il? and OneView. 
et 
2. 
You can use both MESA-Net Async and MESA-Net TCI?/II? in a MESA-Net 
network. Connections between any two nodes can be either MESA-Net Async or 
MESA-Net TCP/II?, but not both. Figure 
l-2 shows a network that uses both 
MESA-Net options. 
Topology using MESA-Net Async 
and MESA-Net TCP/lP 
Seattle Boston 
2-Module geries 6 Server 
l-Module Series 6 Server 
San Jose blodule Series 6 Server 
- 1 MESA-Net 
Async 
ii4 Modem 
Router a- 
Figure l-2 
lopology 
Terms related to MESA-Net are described in this section. Most of these concepts 
are discussed in more detail in later chapters. 
l-3  
						

							Introduction to MESA-Net 
et-work Dialing Plan 
The VoiceMemo dialing plan has characters to support network mailboxes. If an N 
or I’ precedes a number in a dialing plan position, it means that all mailboxes 
represented by that position are network mailboxes, and will be processed by the 
MESA-Net sohare. See Chapter 6 for more information about the network dialing 
plan. 
Digits Translation Table 
The Digits Translation Table determines which messages go to which node. All 
network messagei are compared to this table before being sent to the appropriate 
node. See Chapter 5 for more information about the digits translation table. 
Network Queues 
Network messages are stored in local network queues until they are transmitted to 
remote nodes. Separate queues are kept for urgent and batch (non-urgent) messages 
to each remote node. Messages are queued until a message threshold is reached and a 
message delivery time window is open. The local node then initiates a connection 
with the appropriate remote node. See Chapter 7 for more information about 
network queues. 
inks for MESA-Net Asyne 
MESA-Net Async uses dedicated ports on serial cards for answer and originate links. 
As the names imply, an originate iink is used to initiate commtinications with 
another node on the system, and an answer link is used to accept calls from the 
originate links of other nodes on the system. You can configure up to 
16 links per 
node (32 in Model 640 servers with the MESA-Net Async Load Share optional 
feat&e). MESA-Net Async uses these links to determine how to set up and break 
down connections between nodes. SeT Chapter 4 for more information about links. 
Hardware Type 
Each answer and originate link is assigned a hardware type (device driver) that allows 
MESA-Net to use different kinds of equipment to establish communications 
between nodes. Each hardware type contains the name of a hardware communication 
device and so&ware instructions to set up, establish, and disconnect a telephone call 
to a remote system. 
MESA-Net includes defaulr hardware types for many popular devices, including 
Hayes-compatible modems. You can also create custom hardware types. You can 
define up to seven hardware types per system and assign different hardware types to 
different links. See Chapter 4 for more information about hardware types. 
l-4  
						

							Introduction to MESA-Net 
Me 
To initiate a connection to a remote node, the local MESA-Net node must have all 
of the following information: 
the node number of the remote node 
whether the connection to the remote node is Async or TCI?/II? 
a 
the hardware type to use to reach the remote node (MESA-Net Async 
44 
.a 
the string that must be outdialed to reach that particular node, or the II? 
address of the node 
whether access to the remote node is enabled or disabled 
As described previously, MESA-Net uses the Digits Translation Table to find the 
node number of the destination node. The Network Node Table matches the node 
number of each remote node with its corresponding hardware type, outdial string 
(access code), and access status. See Chapter 5 for more information on the Network 
Node Table. 
ervice 
Network Classes of Service (NCOS) are used to control user privileges such as 
making or answering messages across the network. See Chapter 
8 for more 
information on Network Class of Service. 
et 
This section describes how a voice message flows through the MESA-Net network. 
From the sender’s point of view, if Name Broadcast mailboxes are used, there is no 
difference between sending a message tz a local mailbox and sending one to a remote 
mailbox. (Name Broadcast mailboxes provide name confirmation across the 
network.) When a user receives a message from a remote mailbox, he or she hears 
“Remote message from [name]” where [name] is the name of the remote mailbox 
owner. 
Figure l-3 is an overview of a message traveling from one node to another (San Jose 
to Boston). In this example, the dialing plan is configured such that mailbox 
numbers beginning with 8 are network numbers and that node 2 is Boston. In the 
discussion of the various MESA-Net functions in the following chapters, the inner 
workings of the network are discussed in more detail. 
The following paragraphs explain some of the processing shown in Figure 
more detail. 
l-3 in 
l-5