Need some help troubleshooting SIP trunk registration failures in us-east-1. The genesyscloud_sip_trunk resource applies successfully, but the trunk status flips to FAILED with SIP 403 Forbidden in the logs. Using Terraform v1.6.4 and GC Provider v1.32.0. The authorization_user is generated via random_password and matches the UI config exactly. Any ideas on hidden validation rules?
if i remember correctly, sip trunk auth failures usually stem from the authorization secret not being updated in the provider after a password rotation, so verify the secret matches the latest api response and check for any leading/trailing whitespace in the terraform variable.
The way I solve this is by adding a depends_on to the trunk resource so the auth secret fully propagates before the registration check hits. The race condition between TF apply and SIP register is documented here: https://developer.genesys.cloud/api/docs/sip-trunk-auth-race-condition.