Bot Analytics API omitting trunk_id for BYOC voice channels

Why does this setting in the Analytics API configuration prevent the trunk_id field from populating for interactions routed through our secondary BYOC trunks during carrier failover events?

“The trunk_id is only available for standard Genesys Cloud trunks. BYOC trunks require explicit metadata mapping in the Architect flow.”

We have 15 APAC BYOC trunks and the /api/v2/analytics/conversations endpoint consistently returns null for this field despite correct SIP registration.