Quick question about screen recording metadata when calls are routed through specific BYOC configurations in the ap-southeast-1 region. We have recently audited our recording compliance reports and noticed that screen share sessions initiated via our secondary carrier trunk lack the correct carrier_id attribute in the recording metadata payload. This causes discrepancies in our downstream analytics. Is this a known limitation with BYOC trunk routing in this region, or is there a specific configuration in the outbound routing rules that forces the metadata to default to the primary trunk identity? We are using Genesys Cloud version 2023-09 with the latest recording SDK.