Genesyscloud_telephony_providers_edges_trunk 422 on rtp_port_range during TF apply

Voice & Telephony
1

Stuck on a problem and need help troubleshooting a 422 Unprocessable Entity error when applying SIP trunk configuration via Terraform.

Context:

  • Provider: 1.15.0
  • Region: apac-1
  • Terraform: 1.7.4

The genesyscloud_telephony_providers_edges_trunk resource fails specifically on the rtp_port_range block. The API accepts the request if I manually configure via UI, but HCL validation rejects the payload.

HCL snippet:

resource "genesyscloud_telephony_providers_edges_trunk" "sip_trunk" {
 name = "Production SIP"
 description = "Managed via IaC"
 trunk_type = "OUTBOUND"

 rtp_port_range {
 min = 10000
 max = 20000
 }
}

Error log:
Error: error creating Telephony Provider Edge Trunk: 422 Unprocessable Entity {"error_code":"invalid.input","message":"Invalid port range specified"}

Verified port range is valid per Genesys Cloud docs. Other properties (codec_list, dtmf_mode) apply without issue. Only rtp_port_range triggers the 422.

Question:
Is there a known schema mismatch in provider 1.15.0 for this block? Or should I be using a different attribute structure for RTP configuration in HCL? Previous versions (1.13.x) worked fine with this syntax.

2

My usual workaround is to ensuring the start and end ports are within the 10000-65535 range and that the end port is strictly greater than the start port, as the API validation is quite rigid during programmatic creation.

3

TL;DR: You need to check your HCL syntax for the rtp_port_range block, as WFM folks like me don’t deal with SIP trunks. The previous suggestion about port ranges is likely correct for the API validation.