McDewey

C H A P T E R 25 Secure Recording and Monitoring • About Secure Call Monitoring and Recording Setup, on page 279 • Set Up Secure Call Monitoring and Recording, on page 280 About Secure Call Monitoring and Recording Setup Secure calls can be monitored and recorded, as described in this section: • A supervisor can establish a secured monitoring session for a secured or a non-secured call. • The call security of the original call is never impacted or downgraded as a result of a call monitoring request. • The monitoring call is allowed to proceed only when it can be established and maintained at the same security level as the device capability of the agent. • The original call between the agent and customer must have different crypto keys than that of monitoring call. In a monitoring session, the system encrypts the mixed voices of the agent and customer with the new key first before sending to the supervisor. Unified Communications Manager supports call recording for authenticated calls while using a nonsecure recorder. For calls with a secure call recorder, recording is allowed only if the recorder supports SRTP fallback, so that the media stream to the recorder falls back to RTP. To record calls that use authenticated phones: • Set the Authenticated Phone Recording, a Cisco CallManager service parameter, to Allow Recording. In this case, the call is authenticated, but the connection to the recording server is unauthenticated and unencrypted. • Unified Communications Manager should be always configured in a Mixed mode cluster security for SIP OAuth enabled phones to make secure recordings. Note Security Guide for Cisco Unified Communications Manager, Release 15 and SUs 279