What is the reason the GET /api/v2/analytics/interactions/query endpoint is failing to return detailed SIP failure codes for our BYOC trunks? We are running a standard Genesys Cloud deployment in the APAC region, specifically managing 15 trunks across Singapore and Jakarta. The issue arises when we attempt to query interaction data filtered by trunk_id during periods where our primary carrier triggered a failover to the secondary provider. The API response returns the interaction count, but the sip_failover_reason field is consistently null, even though the SIP logs clearly show 503 Service Unavailable events from the primary carrier. We need this data to generate accurate carrier performance reports for our quarterly SLA reviews. The request payload includes the correct time range and filters for type: voice and trunk_id. We have verified that the user account has the view:analytics and view:trunk permissions. Is this a known limitation of the analytics engine regarding BYOC failover metadata, or is there a specific query parameter we are missing to expose these low-level SIP signaling events? Any insight into how to capture actual failover triggers in the reporting layer would be appreciated. We cannot rely on manual log parsing for high-volume trunk diagnostics.
The documentation actually says… BYOC failover metrics require specific dimension filters. standard interaction queries often miss these low-level SIP details. try adding routing_trunk to your dimensions.
{
"dimensions": [
"routing_trunk",
"interaction_type"
]
}
check if the trunk ID changes during failover.