Avaya Communication Manager Administrator's Manual page 347

Hide thumbs Also See for Communication Manager:
Table of Contents

Advertisement

Attendant Trunk Group Busy/Warning Indicators — You cannot administer Busy/Warning
indicators for MASI trunks because they are not standard Avaya Communication Manager
trunks. However, you can administer these indicators for the trunk group administered for
MASI paths.
Attendant Trunk Identification — The attendant is not able to identify the trunk name via
button pushes.
Basic features
Abbreviated Dialing — A Communication Manager station can enter an MMCX extension
in an AD list. However, MASI terminals cannot use AD.
Administered Connections — MASI terminals must not be the originator nor the
destination of an administered connection.
Automatic Callback — Automatic callback does not work towards a MASI terminal.
Automatic Circuit Assurance — You must not administer a MASI terminal as an ACA
referral destination. You cannot administer ACA for MASI remote trunks.
Busy Verification of Terminals and Trunks — You cannot use Busy Verification for MASI
terminals or remote trunks.
Call Detail Recording — CDR Account Code Dialing and Forced Entry of Account Codes
are not supported for MASI terminals.
Call Park — The attendant can park calls at the extension of a MASI terminal, but users
can only retrieve these calls from a Communication Manager station, since MASI terminals
cannot dial the Answer Back FAC.
Data Call Setup — Avaya Communication Manager users cannot place data calls to MASI
terminals.
Facility Busy Indication — You can use FBI to track the status of MASI terminals. The FBI
button and indicator lamp must be on a Communication Manager station. You cannot use
FBI to track MMCX interfaces.
Facility Test Calls — Avaya Communication Manager users cannot make test calls to
MMCX interfaces.
Go to Cover — MASI terminals cannot activate this feature.
Leave Word Calling — The only valid LWC destination for a MASI terminal is AUDIX. You
cannot administer SPE-based LWC. MASI terminals cannot send LWC messages to
Avaya Communication Manager stations or to MASI terminals.
Loudspeaker paging — You can administer a MASI terminal as a code calling extension.
Malicious Call Trace — MASI terminals cannot initiate malicious call trace.
Message Retrieval — MMCX users can only retrieve messages through AUDIX
messaging.
Multimedia Applications Server Interface
Issue 2.1 May 2006
347

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents