/mcpRestriction Feature MCID does not work across intercluster trunks because Cisco Unified Communications Manager does not support the MCID-T function. Intercluster trunks Cisco MGCP FXS gateways do not support MCID. No mechanism exists for accepting the hookflash and collecting the feature code in MGCP. Cisco MGCP FXS gateways MCID does not work over QSIG trunks because MCID is not a QSIG standard. QSIG trunks Cisco VG248 Analog Phone Gateway does not support MCID. Cisco VG248 Analog Phone Gateway MCID does not support SIP trunks. SIP trunks System does not support using MCID and Immediate Divert features together. Immediate Divert Malicious Call ID Troubleshooting To track and troubleshoot Malicious Call ID, you can use Cisco Unified Communications Manager SDL traces and alarms. For information about setting traps and traces for MCID, see the Cisco Unified Serviceability Administration Guide. For information about how to generate reports for MCID, see the Cisco Unified CDR Analysis and Reporting Administration Guide. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 492 Receiving Calls Malicious Call ID Troubleshooting