Just noticed that the genesyscloud_telephony_providers_edges_trunk resource fails to create during automated deployment. Running terraform apply on provider version 1.3.1 in AU-1 BYOC. The plan stage succeeds without warnings, but the apply step throws a 400 Bad Request error immediately after resource creation. This blocks our nightly CI/CD pipeline for telephony infrastructure updates.
The error response from the API indicates a validation failure on the sip_domains attribute. The payload being sent is valid JSON and matches the schema defined in the provider documentation. However, the edge environment rejects the configuration. The specific error message returned is: Error creating Telephony Provider Edge Trunk: 400 Bad Request: Validation failed for SIP Trunk configuration. No further details are provided in the standard Terraform output logs.
Configuration snippet causing the issue:
resource "genesyscloud_telephony_providers_edges_trunk" "main_trunk" {
name = "Main SIP Trunk"
enabled = true
sip_domains = ["acme.com"]
sip_connections {
name = "Primary Connection"
enabled = true
ip_address = "203.0.113.50"
port = 5060
protocol = "TLS"
transport = "TLS"
username = "sip_user"
password = var.sip_password
}
}
Environment details: AU-1 BYOC. Terraform provider 1.3.1. GitHub Actions runner. The same configuration applies successfully in our US-1 sandbox environment. The difference appears to be related to how the BYOC edge handles SIP domain validation or TLS certificate verification during the initial handshake. Is there a known issue with SIP trunk provisioning in BYOC environments? Or is there a specific attribute required for edge deployments that is missing from the standard provider schema? Need to resolve this to proceed with our telephony migration.