Running a callFlow query against the reporting endpoint and the response body is coming back with an empty data array. The Ohio BYOC trunk group is definitely carrying traffic right now. SIP traces show 200 OKs on the INVITEs, so the legs are connecting.
Architect v2024.3.1 is the version.
Here’s the query payload hitting /api/v2/analytics/reporting/query:
{
"report": "callFlow",
"interval": "2024-04-15T13:00:00.000Z/PT1H",
"groupings": ["trunkGroup"],
"filter": "trunkGroup.id eq \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\""
}
Response is a 200 OK, but the metrics object is totally hollow.
{
"data": [],
"metaData": {
"requestId": "req-99887766",
"status": 200
}
}
Checked the trunk group ID in the admin UI. It matches exactly. No trailing spaces. The pool is active, failover hasn’t tripped. Keepalives are firing every 30 seconds.
Tried swapping the filter to trunkGroup.name eq "Ohio BYOC Pool". Same result. Empty set.
Maybe the callFlow report doesn’t index BYOC legs the same way as PSTN? Or is this just a backend indexing glitch on the Ohio region? The queue is jammed with calls, but the dashboard is doing jack all.
Does the callFlow report require a specific metrics array to populate for BYOC trunks, or is the grouping logic broken?
Looking at the raw JSON response headers, there’s a x-query-time of 45ms. Fast enough to suggest it’s not a timeout issue.