Trying to make sense of why the call recording metadata in the bulk export JSON payload does not match the actual media duration for specific SIP trunk calls. The export job completes successfully with status 200, but the chain of custody audit shows discrepancies in the timestamp fields for calls routed through our legacy PSTN gateway.
The environment uses Genesys Cloud API version 2023-10, and the recordings are pushed to an S3 bucket for legal discovery. The issue appears only on calls exceeding 15 minutes where the SIP INVITE contains custom headers. The bulk export job ID is valid, and the S3 bucket policy allows all necessary write permissions from the service account.
Is there a known limitation with how the platform parses SIP headers for recording duration calculation in the bulk export module? We need the metadata to be exact for compliance audits. The error is not a failure, but a data integrity issue that breaks our automated verification scripts.