Avaya Communication Manager Administrator's Manual page 239

•
MASI path — The Integrated Services Digital Network (ISDN) B-channels between MMCX
and Avaya Communication Manager in a MASI environment. Paths are used for voice and data
connections between Avaya Communication Manager and MMCX.
•
MASI signaling link — ISDN D-channel used to transport a new ISO protocol called the MASI
protocol between Avaya Communication Manager and the MMCX.
•
MASI terminal — The representation in Avaya Communication Manager of MMCX terminals
in a MASI environment.
•
MMCX interface — PRI interface for connecting an MMCX server to other public, private or
wide area network (WAN) switching systems or equipment that is part of the public network.
Similar to a Communication Manager trunk group. These may include non-MASI trunks
connecting Avaya Communication Manager and the MMCX.
•
MMCX trunk — The representation in Avaya Communication Manager of trunk or network
facilities terminating on MMCX. For purposes of MASI, they are called "interfaces."
Planning for MASI
Before you start to administer MASI, you should make a plan for how to do it. Among the configurations
on the following pages, there is probably one that matches the configuration of your system fairly closely.
You might want to either write on these pages, or draw up your own configuration. It may help you if you
have already determined trunk group and signaling group numbers, unused extensions, and so on. The
following are things you need to consider:
•
Establish the dial plan on the MMCX to agree with that of Avaya Communication Manager. If
you use Universal Dial Plan and MMCX, you may need to make adjustments for the MMCX dial
plan.
•
Find unused extensions and trunk group numbers. You need:
— one trunk group number for each ISDN-PRI connection to the MMCX.
— one signaling group number for each MASI node and an unused Communication Manager
extension for the signaling group.
— one unused Communication Manager extension for the Near-End Path Termination
number for all MASI Paths to this ECS. You can use the same number for all MASI nodes
in the domain.
— two unused MMCX extensions for the nearpath and tscnum arguments to the
command. This is the command you use to administer MASI on the MMCX.
MASI configurations
There are several ways to set up combinations of MASI nodes and DEFINITY servers.The following
figures depict several possible configurations.
Administrator's Guide for Avaya Communication Manager
November 2003
Managing MultiMedia Calling
Multimedia Applications Server Interface
chgmasi
239