Chapter 9: Managing MultiMedia Calling
Multimedia Applications Server Interface
The Multimedia Applications Server Interface (MASI) defines a protocol and a set of operations
that are used to extend Avaya Communication Manager feature functionality to a Multimedia
Communications Exchange (MMCX) system. MASI architecture fits the client/server model,
where Avaya Communication Manager functions as a server for MMCX clients. Examples of
features supported by MASI include call detail recording (CDR), AUDIX/INTUITY voice mail
integration, and Automatic Alternate Routing (AAR)/Automatic Route Selection (ARS).
MMCX can make use of both MASI features and MMCX autonomous features. Autonomous
features are those that MMCX provides, even if MASI is not enabled. This document does not
discuss them unless there is a consideration for MASI administration.
Some autonomous MMCX features:
Basic Call (Place/Drop)
●
Call Coverage
●
Conference
●
Transfer
●
Avaya Communication Manager/MASI features:
Basic Call (Place/Drop) - Avaya Communication Manager tracks the status of all calls
●
placed to or from a MASI terminal.
Call Detail Recording - Avaya Communication Manager tracks calls to and from MASI
●
terminals and can produce call records that indicate if a call uses MASI.
Call Coverage - Avaya Communication Manager tracks MMCX calls that are sent to
●
coverage. A Communication Manager coverage path can contain both MASI terminals and
Communication Manager stations.
Conference - Avaya Communication Manager tracks conference calls that involve MASI
●
terminals, if a Communication Manager station originates the conference. Conferences
that involve MASI terminals and Communication Manager stations are voice-only. If the
Communication Manager station originates the call, the caller can use the consultative
form of conference or transfer.
World Class Routing (AAR or ARS) - Calls from MASI terminals can take advantage of
●
Avaya Communication Manager World Class Routing capabilities.
Issue 2.1 May 2006
321