Avaya Communication Manager Administrator's Manual page 345

Unsupported CM 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 can 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
CAUTION:
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 might 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 can 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.
Manual Message Waiting — You must not administer a manual message waiting button
●
(man-msg-wt) with a MASI terminal as the referenced extension.
Manual Signaling — You must not administer a manual signaling button (signal) with a
●
MASI terminal as the referenced extension.
Multimedia Applications Server Interface
Issue 2.1 May 2006 345