Does anyone understand why the Analytics API v2 query for conversation metrics returns null values for conversation_uuid when filtering by specific BYOC trunk IDs in the AP-Southeast-1 region? We are managing 15 active trunks, and while standard PSTN calls populate the UUID correctly, calls initiated through our AI Bot flows connected to these trunks consistently show gaps in the metadata. The JSON response lacks the linking key required for downstream reporting dashboards.
The issue appears isolated to the integration point between the Architect bot flow and the carrier failover logic. When the primary trunk drops and the secondary carrier takes over mid-session, the analytics engine fails to stitch the SIP leg with the bot interaction event. We are using the standard /api/v2/analytics/conversations/query endpoint with a 24-hour window, yet the bot-specific metrics remain unaggregated despite successful call completion.
We need a reliable method to correlate these bot interactions with their originating trunk IDs for compliance reporting. Is there a specific header or configuration flag required in the BYOC trunk settings to ensure the Analytics engine captures the full context? The current workaround involves manual log correlation, which is unsustainable for our volume.