Quick question about the missing chain of custody data for WebRTC softphone sessions in our latest bulk export job.
We are running POST /api/v2/recordings/exports with a filter for recording_source=webrtc to support a legal discovery request. The resulting S3 bucket contains the audio files, but the accompanying metadata JSON lacks the participant_identity and session_start_timestamp fields. This breaks our audit trail requirements. The standard PSTN exports populate these fields correctly. Is this a known limitation for the digital channel exports, or is there a specific query parameter required to force the inclusion of these identity markers?