{"code":"bad_request","message":"Trunk 'SG-BYOC-04' is not authorized for outbound routing to destination '+6591234567'. Check trunk capabilities and number mapping."}
We are encountering a persistent 403 Forbidden error when initiating outbound calls via the /api/v2/communications/calls endpoint. This issue is isolated to our Singapore region BYOC trunks (specifically IDs ending in 04 and 09). The same API call succeeds on our US-based trunks.
The trunk configuration shows ‘Outbound’ capability is enabled, and the specific DNIS is correctly mapped in the number management console. SIP registration logs show a healthy 200 OK from the carrier proxy. However, the Genesys platform API rejects the request before signaling leaves the edge.
We have verified the JWT token has the communications:calls:create scope. The issue started after the recent platform update in the APAC region. Is there a new validation rule for BYOC trunk authorization in the outbound routing logic? We need to know if this is a configuration drift on our end or a platform bug affecting specific carrier profiles in the Singapore edge cluster.
Thanks for the help.