HTTP 503 Service Unavailable
Can anyone clarify why the Outbound API returns 503 when the primary BYOC trunk drops, even though the secondary is registered? We see the SIP 408 failover trigger, but the dialing queue does not resume automatically. Is there a specific retry logic missing in the campaign configuration?
the documentation actually says 503s during byoc failover are transient. the outbound engine pauses to verify trunk health. you need to implement exponential backoff in your app’s retry logic, not expect immediate resume. check the platform api status codes for specific retry-after headers.
You need to check your BYOC trunk health checks in Genesys Cloud admin, as the platform handles failover differently than Zendesk’s simple list imports. The 503 is likely a config mismatch on the secondary trunk registration, not just a retry issue.