Looking for advice on mitigating the 2-second delay in the /v2/predictiverouting/queues endpoint when traffic shifts to the secondary BYOC trunk in Asia/Singapore. The latency correlates directly with SIP registration updates during our scheduled failover drills.
Our current 15-trunk setup handles high concurrency, and this delay causes immediate queue overflow warnings in Architect. Is this a known limitation of the failover logic or a configuration issue with the trunk health checks?