Feature Reference
Malicious Call Trace
1602
Administrator’s Guide for Avaya Communication Manager
November 2003
Controlling MCT
The first controlling terminal to respond to an MCT alert becomes the controller for the call. Alerting on
any other controlling terminals stops.
To begin trace of an incoming call using the Malicious Call Trace feature, the controller dials the 3-digit
equipment location of the incoming trunk.
During alerting, the controller’s display shows the message “MALICIOUS CALL TRACE REQUEST.”
While this message displays, no information on incoming calls displays.
When the controller pushes the MCT-Control button, information displays identifying the called party.
When the controller pushes the button again the remaining MCT information displays.
MCT collects and displays three types of information, calling information as follows:
•
If the call originated inside the system or on the same node within a DCS network, the calling
number displays.
•
If the call originates outside the system and an Integrated Services Digital Network (ISDN)
calling number identification is available on the incoming trunk, then the calling number displays.
Otherwise, the incoming trunk-equipment location displays. In this case, the user must call the
connecting media server or switch.
For all calls, Communication Manager displays the called number, the activating number, whether the
call is active, and identification of any other parties on the call.
Deactivating MCT
The controller deactivates MCT by dialing the MCT-Deactivate FAC. Deactivation frees resources
involved in the trace that were blocked. When all parties hang up, the MCT Voice Recorder disconnects.
Administering MCT for ISDN notification
The following describes how to administer the ISDN MCT notification for an ISDN trunk group
(public-ntwrk, tandem, tie, or access).
Display the System-Parameter Customer-Options screen and ensure that ISDN is enabled.
One of the following must be set on the DS1 screen:
•
If the DS1 is connected to the public network in Australia, set
Country Protocol
field to
2
.
•
For a private network of servers running Communication Manager, set
Country Protocol
to
1
and
Protocol Version
to
a.
Avaya recommends this if DCS features are used in the
private network.
•
For a private network of servers running Communication Manager, set
Peer Protocol
to
q-sig
. (
Peer Protocol
appears on the DS1 screen when
Signaling Mode
field is
isdn-pri
,
Connect
field
is
pbx
, and
Interface
field is
peer-master
or
peer-slave
.)