
Managing MultiMedia Calling
Multimedia Applications Server Interface
258
Administrator’s Guide for Avaya Communication Manager
November 2003
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 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.
Interactions & Unsupported Features
We can generalize feature interactions to some extent. For example, since there are no buttons available
to a MASI terminal, any feature that requires a button is also not available. MASI cannot support features
that require the user to dial a trunk access code for a MASI remote trunk, or a feature access code other
than AAR/ARS. The MMCX dial plan may contain only those feature access codes that are supported.
Note the following CAUTION.
CAUTION:
DO NOT ADMINISTER the following features! The following features are not supported
for use over the MASI link, and Avaya cannot be responsible for the results if you attempt
to administer them.
Unsupported Call Center features
•
ASAI — You must not administer a MASI terminal in an ASAI domain. MASI terminals and
MMCX trunks are not monitored by ASAI. It may be possible for a MASI terminal to place a call
to a Communication Manager station that is part of an ASAI domain. ASAI will not be blocked
from controlling this call, but there may be unpredictable results. The same is true for calls
originating from an ASAI domain terminating at MASI terminals, and for ASAI-monitored hunt
groups that contain MASI terminals.
•
Automatic Call Distribution — You must not include a MASI terminal extension as part of an
ACD hunt group. You must not mix MASI administration with anything related to ACD,
including Outbound Call Management and PASTE.
•
Call Vectoring — You must not include MASI terminal extensions in any step of a vector.
Unsupported Basic features
•
Bridged Call Appearances — You must not administer a bridged appearance that involves a
MASI terminal.
•
Call Coverage — You must not administer a MASI terminal in the coverage path of an Avaya
Communication Manager station.
•
Call Forwarding — You must not forward a Communication Manager station to a MASI terminal.
•
Call Pickup — You must not administer a MASI terminal as part of a pickup group.
•
Intercom — You must not administer MASI terminals as members of any type of intercom group.
Содержание Communication Manager
Страница 320: ...Setting Up Telecommuting Training Users 320 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 416: ...Managing Group Communications Observing Calls 416 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 502: ...Administering Media Servers SNMP Agents 502 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 602: ...Phone Reference Internet Protocol IP Softphones 602 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1338: ...Screen Reference Vector Directory Number 1338 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1832: ...Glossary and Abbreviations Z 1832 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1854: ...Index X 1854 Administrator s Guide for Avaya Communication Manager November 2003...