What is the correct way to handle SIP 486 Busy Here in Genesys Cloud Architect during high concurrency load tests?

JMeter script pushes 500 concurrent SIP INVITEs to US1 environment. Genesys Cloud returns 486 Busy Here after initial 200 OK. WebSocket connection count remains stable, but call capacity seems exhausted prematurely. Architect flow uses simple ‘Make a Call’ action with no complex routing logic.

What is the correct way to configure SIP trunk capacity or flow timeouts to prevent these premature rejections during peak load simulation?

This seems like a standard capacity ceiling rather than a configuration error.

{
 "trunk": {
 "max_concurrent_calls": 1000
 }
}

Check the trunk limits in Admin. The default is often lower than expected, causing 486s even with stable websockets.