Avaya Communication Manager, Руководство администратора, Страница: 260 / 1854

Managing MultiMedia Calling
Multimedia Applications Server Interface
260 Administrator’s Guide for Avaya Communication Manager
November 2003
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.
•
Music on Hold — Music on hold will only be available if an Avaya Communication Manager
station has placed the call on hold.
•
Override — Executive override does not work towards MASI terminals.
•
Priority Calling — Priority calling is not supported for calls to or from MASI terminals.
•
Ringback Queueing — Ringback Queueing is not supported for MASI terminals.
•
Send All Calls — MMCX has an autonomous SAC function. See Call Redirection for more
information.
•
Tenant Partitioning — All MASI terminals exist in tenant 1, and you cannot change the tenant
number.
•
Time of Day coverage — As with all coverage, Avaya Communication Manager does not control
coverage of the MASI terminal.
•
Transfer out of AUDIX — A MASI terminal cannot use *T to transfer from AUDIX to another
MASI terminal.