Just noticed that genesyscloud_sip_trunk resource fails during terraform apply with 400 Bad Request on AU-1 BYOC. Environment details: Provider v1.22.0, Region AU-1. The HCL block is minimal, only setting name, description, and state to ACTIVE. No error details in the API response body, just generic 400. Previous deployments of genesyscloud_user and genesyscloud_routing_queue work fine with same provider version and credentials. Checked genesyscloud_sip_trunk documentation, no specific AU-1 restrictions mentioned. Attempted to deploy via GC CLI genesys cloud sip-trunks create with identical parameters, same 400 error. Suspect issue might be related to sip_domain or media_address validation on BYOC environment. No sip_domain resource created yet, expecting TF to handle it. Log snippet: Error: Error creating SIP Trunk: 400 Bad Request. Provider logs show POST /api/v2/telephony/sip/trunks returning 400. No additional error message in response body. Tried adding media_address explicitly, still 400. Removed description, still 400. Seems like name field validation is failing, but name is unique and valid. Any ideas on what might be causing this? Is genesyscloud_sip_trunk fully supported on AU-1 BYOC with provider v1.22.0? Need to deploy SIP trunks for external PSTN connectivity, stuck on this error. Appreciate any insights or workarounds. Will provide full HCL block if needed. Note: genesyscloud_sip_line also fails with same 400 error when referencing the trunk ID, but trunk creation is primary blocker. Checked support articles, no relevant findings. Assuming this is a known issue or configuration constraint on BYOC. Please advise.
The problem here is…
SIP trunks need specific BYOC attributes.
The API rejects minimal configs.
Check the platform API docs for sip_trunk.
You likely need connection_id.
Add that to the HCL.
Retry the apply.
This looks like a missing mandatory field in the HCL configuration. The connection_id is required for BYOC deployments to link the trunk to the specific edge instance. Without it, the API cannot validate the topology.
Add the connection_id parameter to your genesyscloud_sip_trunk resource. Verify the ID in the Genesys Cloud UI under Admin > Routing > Connections. This aligns with the platform API schema for AU-1 regions.