Trying to make sense of why the metadata JSON files generated by bulk export jobs for SIP trunk recordings are missing critical chain of custody fields required for our legal discovery requests. The bulk export job initiates successfully via the /api/v2/recording/export endpoint, and the audio files arrive in our designated S3 bucket without corruption. However, the associated metadata files lack the specific audit trail entries for legal hold status and original call disposition codes. This gap compromises our ability to verify the integrity of the recordings for compliance audits. The environment is running the latest Genesys Cloud release, and the S3 integration permissions have been verified as correct. Previous exports for digital channels included these fields, suggesting a discrepancy in how voice recordings are processed compared to chat or email. We have checked the recording settings and ensured that metadata retention is enabled for the relevant time periods. The issue persists across multiple export jobs initiated over the past week. Is there a specific configuration required in the SIP trunk settings or the recording export parameters to ensure these fields are included? Any insights into potential API limitations or known issues with voice recording metadata generation would be appreciated.