Avaya Communication Manager Administrator's Manual page 1603

One of the following must be set on the ISDN-BRI Trunk Circuit Pack screen:
•
If the ISDN-BRI is connected to the public network in Australia, set Country Protocol field
to 2 .
•
For a private network of servers running Communication Manager, set Interface to
peer-master or peer-slave .
Considerations
•
If the originator of the call disconnects, MCT drops; if the recipient of the call disconnects, MCT
does not drop.
•
Except for Emergency Access to the Attendant, features that normally display information do not
do so on a controlling telephone. Otherwise, these features function normally until MCT
deactivates.
•
Do not use FACs to activate MCT because the process takes users too long.
•
Visually Impaired Attendant Service (VIAS) voices-out display information for MCT activation,
but not for MCT control.
•
MCT information on an active malicious call is lost during a server failure.
•
When directing a trace to an adjacent server/switch, consider the following:
— The malicious caller may hear a warning tone as a result of the intrusion.
— You may lose continuity on the trace because the person activating MCT on the second
server/switch may not be the MCT controller.
•
If a malicious call comes in on a non-ISDN trunk, the controller needs the telephone number for
the connecting media server and a cross-reference of system-trunk port numbers (including DS1
channel number, if appropriate) not the trunk equipment locations at the connecting media server.
Be sure that they have this information.
•
The following are the system initiated operations for MCT:
— Conversation Recording — After the user activates MCT, the system attaches a MCT
Voice Recorder, if available, to record the conversation, if available.
— Historical Recording — After the user activates MCT, the system records the
MCT-information that you can subsequently retrieve via the MCT History report.
Interactions
•
Bridged Call Appearance
If a user at a primary extension receives an indication call, then a telephone with a bridged call
appearance of this extension can bridge on to the call. For an MCT-Activate button push, if the
currently active extension is a bridged appearance, the system records the primary extension as
the MCT recipient.
For an MCT-Activate FAC, the user dials the number of the telephone with the bridged call
appearance that is actually on the call, instead of the bridged number. However, the system logs
the primary extension as the recipient. Likewise, for self-originated MCT activations via FAC, the
system logs the primary extension as the MCT recipient provided that the recently held
appearance is a bridged call appearance. When you activate MCT for yourself, dial # or wait for
interdigit time-out.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Malicious Call Trace
1603