SIP Trunk Failover Dropping Calls During BCP Schedule Override

Voice & Telephony
1

The disaster recovery routing’s failing with a 408 Request Timeout once the business continuity schedule override activates for the Pacific holiday calendar. Failover logic pushes through the /api/v2/routing/emergencyflows endpoint, but the secondary SIP trunk stays silent while primary capacity drops to zero. A similar routing loop came up in an October community post, so a 30-second delay patch got applied to the SIP INVITE retry, though it’s doing jack all for actual call delivery.

  • Genesys Cloud v2024.08.03
  • SIP Trunk Provider: Twilio Elastic SIP Trunking
  • Architect Flow: Emergency_Failover_v4
  • SDK: Java 2.2.1
  • Override Window: 2024-11-28T23:00:00Z to 2024-12-01T07:00:00Z
  • Last SIP trace: INVITE sip:emergency@trunk2.com SIP/2.0 : 408 Request Timeout after 12s
2 
{
 "failover_sync": "async",
 "timeout_ms": 8000
}

The 408 timeout happens because BCP override locks the SIP handshake. Switch to async mode. It usually clears the hang. Watch for edge cases where shift swaps clash holiday calendar on v2.18. Queue just drops calls if you don’t lower wait window.