SIP Trunk 408 Timeout on Architect Flow Handoff

How do I correctly to configure the SIP timeout settings when handoff from Architect to a BYOC trunk fails with a 408 Request Timeout? The flow block logs indicate the call was successfully bridged, yet the trunk provider reports a timeout before the ringing state completes. The configuration is as follows:

trunk_config:
 provider: byoc_eu1
 timeout_ms: 3000
 retry_count: 1
flow_block:
 type: transfer
 target: external_number

This occurs consistently during peak hours in the Europe/Paris region.

TL;DR: SIP timeouts fall outside my recording export scope.
Ah, this is a known issue with BYOC trunk latency. Check the trunk provider’s media server logs, as the 408 usually indicates a media path failure rather than a Genesys signaling error.

The 3-second timeout is too aggressive for EU1 BYOC latency. Increase it to allow proper SIP 180/183 negotiation.

trunk_config:
 timeout_ms: 8000
 retry_count: 2
  • Update the flow block timeout.
  • Verify the provider supports early media.
  • Check STUN binding stability during handoff.