The Malicious Call Trace feature provides network-wide tagging capability of malicious calls.
The Malicious Call Trace feature provides a record of malicious calls in the SMDR records. Each time the Tag Call feature is invoked, a Malicious Call Indication (MCI) request is sent, and two SMDR records are generated: the standard SMDR call record, and an MCI SMDR record. The MCI SMDR record is identical to the standard SMDR call record with an additional 'Tag Call Identifier' in the Account Code field. For internal calls, the party tagging the call is also identified in the Call Completion Status field of the MCI SMDR record.
When the Tag Call is accepted, a Malicious Call Indication is sent, "Thank You" is shown on the set display of the user that tagged the call, and a Malicious Call Trace SMDR record is generated when one of the parties goes on-hook. If the Tag Call is not accepted, "Not Allowed" is displayed (non-display sets: re-order tone is heard; user must dial the Call Hold-Retrieve Feature Access Code to return to the call) and no SMDR records are generated.
Malicious calls can be recorded using the Record-A-Call feature (when available).
CAUTION: Tagging a non-malicious call may result in fines or other penalties.
Once a call is tagged, the MCI is sent to all applicable nodes in the network and an MCI SMDR record is generated on all nodes involved in the malicious call. For incoming calls through NSU PRI, embedded PRI, or embedded BRI tagged by the PBX user, an MCI request is also sent to the CO.
Note: You cannot limit MCI notification to a single node, but you can prevent notification to the CO (see Programming).
Malicious Call Trace is only supported on the following hardware/trunks:
|
Hardware/trunks |
Protocol |
|
Embedded E1 PRI |
Euro ISDN |
|
NSU E1 PRI* |
Euro ISDN |
|
Embedded BRI |
EN 300 130-1 V1.2.4 |
|
IP trunks |
BTNR188 version 7, section 16, subsection 3.28.1. |
|
XNET trunks |
BTNR188 version 7, section 16, subsection 3.28.1. |
|
T1/E1 DPNSS |
BTNR188 version 7, section 16, subsection 3.28.1. |
|
Embedded T1/E1 |
QSIG (in a Mitel-specific extension). |
|
NSU T1/E1 |
QSIG (in a Mitel-specific extension). |
* Malicious Call Trace is not supported on the NSU T1 PRI or the PRI card.
Applies to markets that conform to ETSI standard EN 300 130-1 V1.2.4 (Malicious Call Identification Supplementary Services).
Applies only to two-party active calls.
Cannot tag a call in dialing state.
Cannot tag calls on hold.
Cannot tag calls when in a conference call.
Cannot tag calls with a Feature Access Code when another call is on soft Hold.
Applies to internal and external calls.
If SMDR records for a particular call type are disabled, no Malicious Call Trace records are generated. For example if the call is internal and Internal SMDR records are disabled, then no SMDR records are written for the call.
If a tagged call is rehomed to its secondary (or primary) ICP, the Malicious Call Indication is lost.
Malicious Call Trace requires Release 5.1 or later on all nodes of the network. This ensures proper propagation of the MCI to all nodes.
To enable Malicious Call Trace:
SMDR Options form
Set "Account Code Reporting for Internal Calls" to "Yes".
Set "Tag Call Reporting" to "Yes".
In the "Tag Call Identifier" field, enter the value you want to appear in the SMDR Malicious Call Trace records (must conform to the Account Code format).
Class of Service
Options form
Set the following for the applicable Class of Services for the users:
Set "SMDR Internal" to "Yes".
Set "SMDR External" to "Yes" (unless calls between clusters are not allowed).
Digital
Link Descriptors form (PRI or BRI connections only)
Set "Send Malicious Call Indication to PSTN for Tagged Calls"
to "Yes".
See Tag Call.
