How does malicious call identification (MCID) differ between a standard call and a conference call?

A.
There is no difference.

B.
The CDR is not flagged in a conference call.

C.
There is no MCID-O message to the PSTN in a conference call.

D.
There is no message to the Cisco CallManager administrator in a conference call.

Explanation:
Introducing Malicious Call Identification
Malicious Call Identification (MCID), an internetwork service, allows users to initiate a sequence of events when they receive calls with a malicious intent. The user who receives a disturbing call can invoke the MCID feature by using a softkey or feature code while connected to the call. The MCID service immediately flags the call as a malicious call with an alarm notification to the Cisco CallManager administrator. The MCID service flags the call detail record (CDR) with the MCID notice and sends a notification to the off-net PSTN that a malicious call is in progress. The system supports the MCID service, which is an ISDN PRI service, when using PRI connections to the PSTN. The MCID service includes two components:
MCID-O-An originating component that invokes the feature upon the user`s request
and sends the invocation request to the connected network. MCID-T-A terminating component that receives the invocation request from the connected network and responds with a success or failure message that indicates whether the service can be performed.
NoteCiscoCallManager supports only the originating component at this time Conference Calls
When a user is connected to a conference, the user can use the MCID feature to flag the call as a malicious call. CiscoCallManager sends the MCID indication to the user, generates the alarm, and updates the CDR. However, CiscoCallManager does not send an MCID invoke message to the connected network that might be involved in the conference.
Reference:
http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_administration_guide_chapter09186 a