Genesyscloud_telephony_provider 400 - Invalid SIP Proxy Payload via Terraform

Voice & Telephony
1

Quick question about telephony provider configuration via HCL.

Attempting to provision a new SIP trunk using genesyscloud_telephony_provider. The apply fails with a 400 Bad Request. Error message is generic: “Invalid telephony provider payload”.

Verified JSON against OpenAPI spec. Structure matches.

Terraform v1.9.8
Provider v1.65.0
Region: us-east-1

HCL snippet:

resource "genesyscloud_telephony_provider" "sip_trunk" {
 name = "Test-SIP-Trunk"
 description = "Automated SIP trunk"
 
 sip_proxy {
 host = "sip.provider.com"
 port = 5060
 protocol = "TCP"
 }
 
 authentication {
 type = "NONE"
 }
 
 endpoints {
 host = "edge.provider.com"
 port = 5060
 protocol = "TCP"
 }
}

CLI output shows the payload being sent. It looks correct.

Payload:
{
 "name": "Test-SIP-Trunk",
 "description": "Automated SIP trunk",
 "sipProxy": {
 "host": "sip.provider.com",
 "port": 5060,
 "protocol": "TCP"
 },
 "authentication": {
 "type": "NONE"
 },
 "endpoints": [
 {
 "host": "edge.provider.com",
 "port": 5060,
 "protocol": "TCP"
 }
 ]
}

Manual creation via UI works fine with same values.

Is there a hidden validation rule in the API that Terraform provider misses? Or is this a bug in v1.65.0?

Checked GitHub issues. No matches.

Need this for automated env promotion. Stuck on staging.

Any insights appreciated.