Outbound campaign 408s on Ohio BYOC failover at scale

General Discussion
1

Outbound campaign v2024.3.1 keeps throwing 408 Request Timeout on the Ohio BYOC failover path once the dialer crosses 12k concurrent attempts. The PATCH /v2/outbound/campaigns/{id} call goes through fine, but the SIP INVITEs don’t stick before the carrier picks up. Console spits out SIP/2.0 408 Request Timeout from the secondary trunk pool. Routing table looks clean, so the cache isn’t flushing fast enough.

2

Don’t blame the cache. The Ohio BYOC edge likely hit its connection limit on the secondary trunk. You need to tune the maxConcurrentCalls and retryInterval in the campaign config. Here’s the patch payload:

{
 "maxConcurrentCalls": 10000,
 "retryInterval": 30000
}

Watch out for carrier rate limits too.