/mcpInteraction Feature To record alarms for the MCID feature in the Local Syslogs, you must configure alarms in Cisco Unified Serviceability. Under Local Syslogs, enable alarms for the Informational alarm event level. When the MCID feature is used during a call, the system logs an SDL trace and a Cisco Unified Communications Manager trace in alarms. You can view the Alarm Event Log by using Cisco Unified Serviceability. The traces provide the following information: • Date and time • Type of event: Information • Information: The Malicious Call Identification feature is invoked in Cisco Unified Communications Manager • Called Party Number • Called Device Name • Called Display Name • Calling Party Number • Calling Device Name • Calling Display Name • Application ID • Cluster ID • Node ID For more information about alarms and traces, see the Cisco Unified Serviceability Administration Guide at http://www.cisco.com/c/en/us/support/ unified-communications/unified-communications-manager-callmanager/ products-maintenance-guides-list.html. Alarms The Cisco ATA 186 analog phone ports support MCID by using the feature code (*39). Cisco ATA 186 analog phone ports Malicious Call Identification Restrictions Table 48: Malicious Call Identification Restrictions Restriction Feature Cisco Unified Communications Manager supports only the malicious call identification originating function (MCID-O). Cisco Unified Communications Manager does not support the malicious call identification terminating function (MCID-T). If Cisco Unified Communications Manager receives a notification from the network of a malicious call identification, Cisco Unified Communications Manager ignores the notification. Malicious Call Identification Terminating (MCID-T) function Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 491 Receiving Calls Malicious Call Identification Restrictions