Is it possible to suppress the 500ms delay in the /v2/analytics/conversations/summary endpoint during active trunk failover in the Asia/Singapore region?
Error: Gateway Timeout (504) on real-time aggregation service
The 15 active BYOC trunks show correct SIP stats, but the reporting layer lags significantly when routing shifts to secondary carriers.