Context:
Just noticed that our Architect IVR flow is experiencing significant latency spikes when calls are routed through the secondary BYOC trunk during a failover event in the Asia/Singapore region. We manage 15 BYOC trunks, and the primary carrier is currently stable, but the failover logic to the secondary provider introduces a 2-3 second delay before the SIP invite is accepted. This delay causes the ‘Collect Input’ block to timeout prematurely, resulting in a 408 Request Timeout error in the call logs. The issue is specific to the secondary trunk’s SIP registration state, which seems to lag behind the primary during the switch-over.
Question:
Is there a way to adjust the timeout thresholds within the Architect flow to accommodate the increased latency associated with BYOC trunk failover? We are using the latest version of the Genesys Cloud platform, and the issue persists across multiple failover drills. The error occurs specifically when the call is transferred from the primary to the secondary trunk, and the IVR flow does not have enough time to process the SIP invite before timing out. Any insights on how to handle this scenario would be appreciated.