Stuck on correlating screen recording events with BYOC trunk metadata. The /api/v2/recordings/screen endpoint returns data for 15 APAC trunks, but the sip_call_id field is null for 40% of records during failover events. This breaks our custom analytics aggregation logic in the Singapore timezone. The standard voice recording endpoints populate the carrier data correctly, suggesting a specific gap in the screen recording pipeline. How can we force the screen recording service to inherit the trunk context from the active voice session?