Why does the secondary BYOC trunk returns a SIP 403 Forbidden immediately after the primary trunk fails? The primary trunk is registered and healthy, but when forced down, the failover logic triggers and the next call attempt hits the carrier with this error.
Environment details:
- Genesys Cloud Version: 2024-06
- BYOC Trunk A (Primary): Registered, healthy
- BYOC Trunk B (Secondary): Registered, healthy
- Outbound Routing: Failover strategy configured
- Carrier: Telstra Business SIP
The SIP trace shows the INVITE reaching the carrier, but the 403 response lacks a specific reason phrase. Have others seen this behavior with Telstra SIP trunks?