Avaya Communication Manager Administrator's Manual page 238

Managing MultiMedia Calling
Multimedia Applications Server Interface
Before you start
CAUTION:
Avaya Communication Manager offers a wide range of features, and MMCX users may
want to take advantage of this. In some cases, these features will operate as expected.
However, some features are not supported for use over the MASI link, and their behavior
is unpredictable. You may cause harm to your system by attempting to use these features.
The Interactions section contains a list of features, and lists those features that are
absolutely not supported for use with MASI. If you administer features on the DO NOT
ADMINISTER list, Avaya cannot be responsible for the result.
For purposes of administration, there are feature buttons and groups of users that you must not administer
with MASI terminal extensions. There are also features that you simply cannot administer for a MASI
terminal, because the software does not allow it.
About this document
The following section describes the Multimedia Applications Server Interface (MASI), and provides
instructions on how to set it up, including administration and monitoring. It also includes a section on
troubleshooting.
You need to use both the DEFINITY® Server system administration terminal (SAT) and the MMCX
administration terminal to administer MASI. This document describes what you need to do at the
DEFINITY® Server SAT. It also occasionally mentions administration that you must do at the MMCX
administration terminal. For more detailed MMCX information, see the MMCX System Administrator's
Guide & Technical Reference Manual.
List of terms
This is a list of terms that are specific to MASI, or that have meanings in the context of MASI that are not
standard.
•
chgmasi — The command you use to administer MASI at the MMCX administration terminal.
•
Interserver — Connections between MMCX terminals on different MMCX servers/nodes.
•
MASI domain — A MASI domain consists of Avaya Communication Manager and one or more
MASI nodes that share the same dial plan. That is, the extension numbers on the MMCX are
known to Communication Manager, and fit in the Communication Manager dial plan.
•
MASI interworking — MASI interworking refers to the completion of a voice connection
within Avaya Communication Manager, involving at least one MASI terminal and a MASI path.
•
MASI link — The connection between the MMCX and Avaya Communication Manager.
•
MASI node — A single MMCX server. You may connect more than one MASI node to a
Communication Manager. Each node has a separate number. This node number needs to be
consistent whenever referring to a specific MMCX server.
•
MASI non-interworking — MASI non-interworking refers to the completion of a call by
MMCX, not involving a MASI path.
238 Administrator's Guide for Avaya Communication Manager
November 2003