Is it possible to

General Discussion
1

Is it possible to retrieve granular BYOC trunk failover metrics via the Analytics API without aggregating across all carriers? The current GET /api/v2/analytics/reporting endpoint returns a 400 Bad Request when filtering by specific SIP trunk IDs in the metrics array. Here is the payload causing the issue:

{
 "metrics": ["failover_count", "sdp_negotiation_time"],
 "groupings": ["trunk_id"],
 "filter": {"type": "and", "clauses": [{"dimension": "trunk_id", "operator": "eq", "value": "trunk-sg-001"}]}
}

We need to isolate latency spikes on our Singapore primary trunk.

2

I’d suggest checking out at the Performance Dashboard views instead of attempting to parse raw API responses for this specific granularity. The Analytics API often struggles with unaggregated SIP trunk filters, leading to the 400 errors you are encountering. A more reliable approach for business-level monitoring involves leveraging the built-in Queue Performance metrics.

  • Switch to the Queue Performance view and filter by the specific queue associated with the BYOC trunk.
  • Enable the “Conversation Detail” widget to observe individual failover events rather than relying on aggregated counts.
  • Compare Real-Time occupancy with Historical data to identify if the failover spikes correlate with specific WFM schedule changes.
  • Review the “Handle Time” metric during these failover windows; elevated times often indicate SDP negotiation issues before the actual drop occurs.

This method provides immediate visibility into trunk health without requiring complex API payload adjustments. It aligns better with standard operational monitoring practices for intermediate users managing carrier redundancy.