list mct-history

Last Updated : Apr 05, 2024 |

Use list mct-history to display the data associated with the Malicious Call Trace (MCT) feature chronologically, with latest to oldest data displaying the last 16 records.

MCT enables customers to collect information that could be used to identify a calling party whose conversation is deemed to have a malicious intent. Several scenarios are possible:

  • Communication Manager software records information about the caller, including the Calling Number whenever possible for incoming trunk calls. This information can be viewed using the Malicious Call Trace History report.

  • If the Communication Manager server is connected directly to a public ISDN that follows the ETSI protocol standard, Communication Manager software sends a message to the network requesting that the source of the incoming call be identified and the call be registered.

    1. If the public ISDN sends an acknowledgment, the ISDN Notification field on the MCT History report will show acknowledged.

    2. If the public ISDN sends a rejection (perhaps because the feature was not subscribed), the ISDN Notification field on the MCT History report will show rejected.

    3. If the public ISDN does not send any response, the ISDN Notification field on the MCT History report will show no response.

  • If the Communication Manager server is not connected directly to a public ISDN that follows the ETSI protocol standard, the ISDN Notification field on the MCT History report will display not sent. Note that this includes the following two cases:

    1. If the Communication Manager server is directly connected to a public ISDN that follows the Australian ISDN protocol standard (Country Protocol 2), the public ISDN is notified when MCT is activated, but the ISDN Notification field displays not sent.

    2. If the Communication Manager server is indirectly connected via a QSIG or DCS private network to a public ISDN that follows the ETSI or Australian ISDN protocol standard, a message is sent through the private network to the gateway server. The gateway server then notifies the public ISDN that MCT has been activated, but the ISDN Notification field displays not sent. Note that in the QSIG case, the private-network message is proprietary, so all servers between the user activating MCT and the gateway must be Communication Manager servers.

Syntax

list mct-history

list mct-history field descriptions

Field

Description

Date

The date of the occurrence.

Time

The time of the occurrence.

Contr Ext

Controlling Extension: The extension of the user who enabled the MCT control feature. The controlling extension user then has access (via display messages) to the information regarding the malicious call.

Active Ext

The extension of the user that activated the MCT feature.

Recorder Port

The port of a voice recorder being used to record the malicious call.

Redir From

For redirected calls, the party from which the malicious call was redirected (for example, coverage, forwarding).

Actual Party

The extension of the user who received the malicious call.

Parties on Call

The extensions of other parties connected to the malicious call when the MCT feature was activated.

ISDN Notification

Whether an ISDN notification was sent to the PSTN notifying them of the call, and whether the network responded.