Why does the /v2/voice/trunks endpoint returns a 403 Forbidden error specifically when traffic fails over to secondary BYOC trunks in the Asia/Singapore region? The primary trunks function correctly, but the secondary ones reject SIP INVITE requests immediately after the failover trigger.
Steps to reproduce:
- Configure two BYOC trunks for the Asia/Singapore region with identical SIP credentials.
- Set up an outbound routing policy with the primary trunk first and the secondary trunk as failover.
- Simulate a primary trunk outage by disabling the SIP registration.
- Initiate an outbound call through the Architect flow.
- Observe the 403 error in the call logs and the /v2/voice/trunks API response.
The error message indicates ‘Invalid SIP credentials,’ but the credentials are verified correct. This issue occurs consistently across all 15 trunks in the region. Is there a known limitation with BYOC failover logic in this region? Any insights into the underlying cause would be appreciated.