Could someone explain why our BYOC Edge instances are consistently failing SIP trunk registration with a 403 Forbidden error, even though the credentials appear correct in the Genesys Cloud tenant configuration? We are deploying a premium AppFoundry integration that requires stable SIP connectivity across multiple regions. The Edge version is v2.5.1, and we are using the standard sip:write scope for the OAuth client.
The issue manifests immediately after the Edge restarts. Logs show the initial registration attempt succeeds, but subsequent keep-alive pings are rejected. We have verified that the SIP credentials stored in the Edge configuration are not stale and match the current tenant settings exactly. The problem persists across three distinct organizations within our multi-org setup.
We suspect this might be related to how the OAuth token is being refreshed for the SIP signaling layer, but the documentation is sparse on this specific interaction. Has anyone encountered a similar scenario where the initial handshake works but the session drops due to a permission mismatch or token expiry issue? Any insights into debugging the SIP signaling path within the BYOC architecture would be appreciated.