Why does this setting prevent our custom AppFoundry integration from maintaining stable SIP registrations with Genesys Cloud PSTN endpoints? We are deploying a multi-tenant telephony bridge that relies on direct SIP trunking for specific legacy hardware integrations. The environment is configured with Genesys Cloud Platform version 2024.1, and our backend service utilizes the Go SDK version 1.42.0 for initial OAuth token acquisition before falling back to SIP credentials for media path establishment.
Upon initial deployment, the SIP registration succeeds. However, within a 15-minute window, the Genesys Cloud SIP server returns a 403 Forbidden response during the re-registration attempt, causing the trunk to drop into a failed state. The error payload indicates an authentication mismatch, despite the credentials remaining static and verified via the Admin console. We have confirmed that the IP allow-list is correctly configured and that NAT traversal settings are aligned with our public-facing load balancer.
The issue appears correlated with our OAuth token refresh cycle. When the client credentials token refreshes, the subsequent SIP re-registration fails, suggesting a potential desynchronization between the platform’s authentication context and the SIP stack’s credential validation. Has anyone encountered similar behavior where platform-level auth refreshes invalidate active SIP trunk sessions? We are attempting to determine if this is a known limitation of the SIP trunking API or a misconfiguration in our token handling logic.