Instruction manual

Page 1964 of 3156 Malicious Call Trace
553-3001-306 Standard 10.00 January 2002
Calling Party Privacy
Incoming calls to stations having the Malicious Call Trace feature enabled
will continue to include the Terminal Number (TN) of the calling party in the
Malicious Call Trace record, even if the caller has requested Calling Party
Privacy.
Conference Call
When a station or console that is on the conference loop activates the MCT
feature, the trace record shows only the conference loop number and
conference number as the ORIGTN, and the Terminal Number (TN) of the
station or console that activated the feature as the TERTN. No information on
the other parties in the conference is given.
History File
The MCT records are stored in the History File if it has been defined as a
maintenance (MTC) user in LD 17.
Meridian 911
The Malicious Call Trace (MCT) feature is modified to be supported on ACD
sets. ACD sets are allowed to have the Malicious Call trace Allowed (MCTA)
Class of Service and a Trace (TRC) key defined. The feature is activated via
pressing the MCT key or dialing a MCT access code.
Meridian Mail
The Malicious Call Trace (MCT) feature is modified to be supported on
Automatic Call Distribution (ACD) sets. ACD sets are allowed to have the
MCTA Class of Service and a TRC key defined. The feature is activated via
pressing the MCT key or dialing a MCT access code.
Enhanced Malicious Call Trace
Autodial Tandem Transfer
Enhanced Malicious Call Trace implements the ability to send a call trace
request to the CO and provides the possibility to record the call using a
recorder. This feature also uses the Centrex/Trunk Switchhook Flash feature;
the same enhancement applies to the Autodial Tandem Transfer feature.