How does the provider handle dtmf_mode validation on nice_cxone_sip_trunk when the API returns a 422 for rfc2833?
Checking the source code for 1.17.1 first. Validation list in the resource definition only has inband and sip_info. rfc2833 is missing from the allowed values in the schema struct.
"dtmf_mode": {
Type: schema.TypeString,
Required: true,
ValidateFunc: validation.StringInSlice([]string{"inband", "sip_info"}, false),
}
The 02:30 JST pipeline failed hard. Terraform 1.9.8 with nice-cxone 1.17.1 throws a 422 Unprocessable Entity on nice_cxone_sip_trunk. State backup’s clean.
Tried setting dtmf_mode to “rfc2833”. Provider rejects it locally before sending.
Manual API call via Postman works. Endpoint accepts rfc2833. Returns 200.
Switched to inband in TF config. Apply’s succeeding. Switched back to rfc2833 in state file manually. Plan shows no drift. Next apply fails with the same 422.
Logs show the payload would be correct if it got past validation:
{
"dtmf_mode": "rfc2833",
"name": "PROD-SIP-TRUNK-01",
"ip_allow_list": ["203.0.113.10"]
}
Error message from the provider crash: Validation failed: dtmf_mode must be one of [inband, sip_info].
API docs list rfc2833 as valid. Provider schema is out of sync.