BYOC Trunk Failover Latency Spikes in APAC Region

Looking for advice on optimizing the failover response time for our 15 BYOC trunks in the Singapore region. The current setup triggers a 200ms delay when the primary carrier drops packets, causing noticeable audio gaps.

The /api/v2/analytics/reporting/query endpoint shows clean metrics, but the actual SIP INVITE retry logic seems to be stalling at the edge. We are using Genesys Cloud Java SDK 11.5.2 for monitoring.

Has anyone tuned the outbound routing rules to bypass the default health check interval? Need to reduce this latency under 50ms.

This is caused by default SIP retransmission timers being too aggressive for APAC latency. Adjust the outbound routing group settings to increase the initial INVITE timeout to 4000ms. This allows the packet loss to resolve before triggering the failover logic, reducing the perceived audio gap without needing SDK changes.