Clarification on BYOC Trunk Failover Metrics in QM API

  • Anyone know why the Quality Management API returns incomplete recording metadata for calls routed via secondary APAC BYOC trunks during failover events?
  • The primary trunks function correctly, but the secondary endpoints consistently trigger 408 Gateway Timeouts when querying the /api/v2/quality/recordings endpoint.
  • This behavior persists across multiple carrier configurations despite verified SIP registration status and correct outbound routing rules.
  • The latency spikes suggest a potential synchronization issue between the failover logic and the analytics reporting pipeline.