Instruction manual

Page 1960 of 3156 Malicious Call Trace
553-3001-306 Standard 10.00 January 2002
If the initiator hears overflow tone, the call trace has failed for one of the
following reasons:
• The station does not have Malicious Call Trace Allowed (MCTA) Class
of Service (CLS)
• The station is not established on an active call, or
• The system could not allocate a print register to store the trace
information.
An attendant can activate Malicious Call Trace (MCT) only from an
Attendant Console by using the Trace (TRC) feature key. When the Trace
(TRC) key is pressed, the system prints a trace report on the source party, the
destination party, or both, depending on whether the source key, the
destination key, or both keys are active.
The MCT record identifies the source or destination (or both) by printing S or
D (or both) prior to the time and date stamp of the record.
Enhanced Malicious Call Trace (EMCT)
With EMCT, the above feature provides the following enhancements:
• Malicious Call Trace is supported on Central Office (CO), Direct Inward
Dial (DID) trunks.
• The alarm has a flexible ring timer, allowing a user-selectable range of
from 0-15 minutes instead of being fixed at 15 minutes.
• The malicious call can be recorded by using a recording trunk.
• The call trace record can be printed on any Serial Data Interface (SDI)
port when MCT is defined as a user. It is also written to the history file.
Note: If MCT is not defined, the record is still printed on the
maintenance TTY(s) only.
• The format of the call trace record tells you whether the call type is
internal or external. The record identifier is either MCI for internal or
MCE for external.
The user may configure an alarm to ring for a flexible period of time (0-15
minutes) for both internal and external calls. If the alarm DN goes off hook,
it stops prior to the flexible alarm timer expiring.