Lucent Technologies 8.2 User Manual

Issue 1

April 2000

Features and technical reference 

1422

Malicious Call Trace 

Once MCT is activated, information on the call is collected and alerts users in the 
group. The alert is not a call, so it is not affected by queues at the user’s terminal. 
If an MCT Voice Recorder is connected, it begins recording the conversation.

Any Bridging, Conference, or Intrusion tone connected to parties on the 
connection are temporarily removed while the MCT Voice Recorder 
connects.

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 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 switch.

For all calls, the system displays the called number, the activating number, 
whether the call is active, and identification of any other parties on the call.

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.