/mcpCDR Data CDR data provides the security status of each call leg from the phone endpoint to the conference bridge as well as the security status of the conference itself. The two values use two different fields inside the CDR database. CDR data provides termination cause code 58 (Bearer capability not presently available) when a meet-me conference rejects a join attempt that does not meet the minimum security level requirement. See the CDR Analysis and Reporting Administration Guide for more information. Interactions and Restrictions This section contains information on the following topics: • Cisco Unified Communications Manager Interactions with Secure Conference, on page 163 • Cisco Unified Communications Manager Restrictions with Secure Conference, on page 164 CiscoUnifiedCommunicationsManagerInteractionswithSecureConference This section describes Unified Communications Manager interactions with the secure conference feature. • To keep a conference secure, if a participant in a secure ad hoc conference puts a call on hold or parks the call, the system does not play MOH, even if the Suppress MOH to Conference Bridge service parameter is set to False. The secure conference status does not change. • In intercluster environments, if an off-cluster conference participant presses hold in a secure ad hoc conference, the media stream to the device stops, MOH plays, and the media status changes to unknown. If the off-cluster participant resumes a held call with MOH, the conference status may upgrade. • A secure MeetMe call across an intercluster trunk (ICT) will clear if the remote user invokes a phone feature such a hold/resume, which changes the media status to unknown. • Annunciator tones or announcements for Unified Communications Manager Multilevel Precedence and Preemption that play on a participant phone during a secure ad hoc conference change the conference status to nonsecure. • If a caller barges a secure SCCP phone call, the system uses an internal tone-playing mechanism at the target device, and the conference status remains secure. • If a caller barges a secure SIP phone call, the system provides tone-on-hold, and the conference status remains nonsecure during the tone. • If a conference is secure and RSVP is enabled, the conference remains secure. • For conference calls that involve the PSTN, the security conference icon shows the security status for only the IP domain portion of the call. • The Maximum Call Duration Timer service parameter also controls the maximum conference duration. • Conference bridge supports packet capture. During a packet capture session, the phone displays a nonsecure status for the conference, even if the media stream is encrypted. Security Guide for Cisco Unified Communications Manager, Release 15 and SUs 163 Basic System Security CDR Data