Administrator's Guide

Multimedia Applications Server Interface
Issue 5 October 2002 297555-233-506
Step 11 — Verify administration
Make test calls from MultiVantage to MMCX, ensure that you can indeed place
and receive calls.
Call an unattended MASI terminal. Verify that the call goes to AUDX. Retrieve
the call from the MASI terminal. Verify that all works as expected.
MASI command permissions
If you are the super-user for your system, you can restrict other administrative
logins from changing MASI administration. To do this, use the
change
permissions (login-ID)
command. Enter y in the Additional Restrictions field,
then move to the Restricted Object List page of the screen.
You may restrict the following MASI-related objects:
■ masi-path-parameters
■ masi-terminal
■ masi-trunk-group
■ masi-tsc
Detailed description of features
AAR/ARS
MMCX can take advantage of advanced routing features for voice-only calls to
the public switched telephone network (PSTN) or a DEFINTY system private
network. Users must enter the AAR/ARS access code before the rest of the dialed
digits. MASI will route the call over the MultiVantage private network (AAR) or
the public network (ARS), based on the digits supplied by the MMCX user.
Routing patterns must contain only trunk groups that actually terminate on the
Avaya MultiVantage solution. Calls from one MMCX to another do not use
AAR/ARS. Authorization codes are not supported.
Call Detail Recording
Using the MASI link, MultiVantage is able to track call detail information for
calls made using MMCX terminals and interfaces. CDR records all calls
originating from or terminating at a MASI terminal. MASI CDR does not record
ineffective call attempts when all MASI paths are busy.
The Resource Flag value of 8 indicates a MASI call. This field appears in
unformatted, int-isdn, expanded and customized CDR formats. For formats other
than these, you can determine that a call involves a MASI terminal or trunk by the
TAC, dialed number or calling number fields.