SIP Trunk provisioning failing with 400 Bad Request on genesyscloud_sip_trunk resource

Voice & Telephony
1

Looking for advice on a persistent deployment failure with the genesyscloud_sip_trunk resource. Running Terraform v1.7.4 with Genesys Cloud Provider v1.58.0. The environment is a dedicated instance in AWS Sydney.

The configuration attempts to define a new SIP trunk with basic security settings. The apply step fails immediately during the create operation. The error indicates a validation issue with the transport protocol, despite the HCL specifying TCP explicitly.

resource "genesyscloud_sip_trunk" "trunk_aus" {
 name = "Prod-SIP-AUS-01"
 description = "Primary inbound trunk"
 transport = "TCP"
 
 sip_domains {
 domain = "example.com"
 }
}

The API returns a 400 Bad Request. The response body suggests the transport field is invalid, yet the documentation lists TCP and UDP as valid options. No changes were made to the provider configuration recently. This blocks the CI/CD pipeline for the Australian region rollout.

Is there a known issue with the TCP transport enum in this provider version? Or is the API rejecting the payload format for new trunks in this specific region?

2

My usual workaround is to verifying the transport protocol string matches the API enum exactly. The Genesys Cloud API is strict about casing. Check if “tcp” or “TCP” is required. Also, ensure the TLS settings are not conflicting with the transport type.

  • API enum validation
  • TLS configuration
  • Terraform provider version