Avaya Communication Manager Administrator's Manual page 308

Managing MultiMedia Calling
Avaya Communication Manager tracks calls to MASI terminals that follow the autonomous
coverage path from the MASI terminal. MMCX calls redirected to Communication Manager
stations contain display information.
MASI terminals that dial AUDIX directly, or that place calls to MASI terminals that cover to
AUDIX, do not receive ringback if all AUDIX ports are busy. Instead, these callers see a
message the called party is busy, and the call drops.
Transfer
MASI terminals cannot transfer calls to Communication Manager stations, and cannot transfer a
call to another MASI terminal if the call involves a Communication Manager station.
Conferencing
Conferences can involve both MASI terminals and Avaya Communication Manager stations,
and either one may initiate the conference. Communication Manager stations participate in such
conferences in voice-only mode. If an MMCX user initiates a conference that involves
Communication Manager stations, the conference will drop when the initiator drops from the
call. If a Communication Manager station initiates the conference, that station may drop without
affecting the other conferees.
Status tracking - terminals and trunks
Avaya Communication Manager tracks the active/idle status of all MASI terminals, and monitors
traffic over MMCX interfaces.
Trunk groups
For MASI purposes, there are two kinds of trunk groups: the ISDN-PRI trunk groups that serve
as paths for establishing calls between Avaya Communication Manager stations or trunks and
MASI terminals or interfaces, and the remote trunks that are interfaces from the MMCX to other
entities. Each MASI remote trunk group appears to Communication Manager as a single unit,
with no concept of members within the group.
Note:
You cannot test, busy out, or release MASI remote trunk groups, since you
Note:
cannot dial a MASI remote trunk TAC from the Avaya DEFINITY Server. The TAC
merely identifies the trunk to Avaya Communication Manager for purposes of
status and CDR records.
You cannot administer MASI trunks as part of Communication Manager route patterns.
308 Administrator Guide for Avaya Communication Manager