Skip to main content

Twilio Changelog

Additions and changes to the Twilio platform

Programmable Voice

Announcing Dual-Channel Voice Recordings by Default GA

Call recordings are now stored by Twilio in dual-channel by default for no additional cost, enabling you to process the individual participants of the call recorded. With this change, the recording audio files of a 2-party call will have two channels and contain the audio from each call leg in a separate channel. 

Prior to this release, customers needed to specify dual-channel to record each participant in a separate channel, and all audio mixed in a single channel was the default behavior. With this release, a new RequestedChannels query parameter can be used to specify whether the file should be downmixed to a single channel or downloaded as a dual-channel file. For backward compatibility, when RequestedChannels query parameter is not specified, the default download will be either mono or dual, depending on what was requested for the recording.

It’s possible to continue enabling single-party call recordings using the recordingTrack parameter to select whether the inbound or outbound audio tracks of the call should be recorded, and the recording file will always be mono and no additional tracks recorded. Voice recordings where dual-channel is not supported, such as TwiML <conference> noun and <record> verb, all audio will be mixed in a single channel file.

With this release, storing dual-channel recordings comes at no extra cost compared to single-channel storage.

Dual-channel call recordings by default is now available on all new accounts and will be gradually deployed on existing accounts.

Learn more about how it can help unlock intelligence from your recordings by increasing transcription accuracy. on the Twilio blog.