Is it possible to configure specific SIP trunk headers via the genesyscloud_telephony_providers_edges_sipstation_extension resource without triggering auth errors?
Deploying a new SIP trunk configuration using Terraform provider v1.62.0. The genesyscloud_telephony_providers_edges_trunk resource applies successfully. However, the physical endpoint fails to register. Logs show a 403 Forbidden response on the initial OPTIONS request.
The credential store entry is correct. Verified via the Genesys Cloud CLI that the secret exists and is linked to the trunk. Manual registration via the UI works instantly. This suggests the Terraform deployment is not setting the required authentication context or is applying a default policy that blocks the specific IP range before the trunk config is fully active.
Environment:
- Genesys Cloud Org Region: us-east-2
- Terraform Provider:
v1.62.0 - OS: Ubuntu
22.04 LTS - CI/CD: GitHub Actions
Snippet:
resource "genesyscloud_telephony_providers_edges_trunk" "primary_sip" {
name = "Primary-SIP-Trunk"
status = "ACTIVE"
# ... standard config ...
}
The status is ACTIVE immediately after apply. But the endpoint sits in “Unregistered” state. No detailed error in the Terraform state file. Only the 403 in the telephony logs.
Is there a known race condition with credential propagation? Or is a specific sipstation parameter required for external trunk registration that is missing from the provider docs?