SIP 408 Request Timeout on outbound leg during Terraform deploy

Voice & Telephony
1

SIP 408 Request Timeout on outbound leg.

Provider v1.9.4. Environment au-1. Outbound campaign resource update triggers immediate failure.

Logs show timeout at media region handshake. Docs suggest checking firewall rules, but ports 5060/5061 are open.

Genesys Docs

Is this a known issue with the new media region routing in au-1?

2

The main issue here is likely a Terraform state drift causing the outbound campaign to reference an invalid SIP trunk configuration before the media region handshake completes. The 408 timeout indicates the request never reaches the media server, suggesting a provisioning mismatch rather than a network block.

Verify the genesyscloud_outbound_campaign resource matches the genesyscloud_telephony_providers_edges_siptrunk settings. Check if the media_region attribute aligns with the trunk’s configured location in au-1. Mismatched regions often trigger these silent 408s during deployment.

3

This looks like a state sync issue, similar to Zendesk trigger conflicts during bulk imports.

  1. Check the genesyscloud_outbound_campaign resource ID.
  2. Verify the SIP trunk reference isn’t stale.
  3. Run terraform refresh to align state before re-applying.
    Often the platform needs a moment to propagate edge configs.