95119: Conversation Intelligence does not support encrypted recordings

This warning appears when you try to create a Conversation Intelligence Transcript from a Voice Recording that was encrypted with Voice Recording Encryption. Conversation Intelligence can't decrypt encrypted recordings, so it can't transcribe them directly.

• Voice Recording Encryption is enabled on the project or subaccount, which means new Voice Recordings are encrypted with your public key after they are created.
• The transcript request uses a Twilio Recording SID in source_sid, but the referenced recording is encrypted. Conversation Intelligence can't create a Transcript from an encrypted Twilio-hosted recording.
• The media file provided for transcription is still encrypted. External recordings must be accessible for download during transcription, and encrypted recordings aren't supported.

• Decrypt the recording outside Twilio by using your private key together with the recording's EncryptionDetails from the Recording resource.
• Store the decrypted audio in your own external storage and create the Transcript with media_url instead of source_sid. Conversation Intelligence supports external recordings through a publicly accessible or time-limited pre-signed URL.
• Use an unencrypted recording when you want to create a Transcript directly from a Twilio Recording SID.
• Make sure the external file stays accessible for the full transcription job and returns an HTTP 200 response when Conversation Intelligence fetches it.

• Voice Recording Encryption
• Conversation Intelligence Transcript Resource
• Conversation Intelligence (classic) overview