Could someone explain why our SIP trunk registration success rate drops to 40% when we simulate 500 concurrent agent logins?
We are running a capacity test on the US1 environment using JMeter 5.6. The goal is to validate the maximum concurrent registration load for our BYOC SIP trunks. The test setup involves 500 threads, each attempting to register a unique endpoint via the standard SIP REGISTER method.
At 100 concurrent users, the registration success rate is 100%. At 250 users, it stays around 95%. However, once we push to 500 concurrent requests within a 10-second window, the Genesys Cloud edge starts rejecting registrations with a SIP 403 Forbidden error. Sometimes we see a 408 Request Timeout.
The endpoints are configured correctly in the Architect flow for inbound routing, and the SIP trunk credentials are valid. We are using the default WebSocket transport for the edge connection. The error occurs before any call is placed, strictly during the registration phase.
Here is the SIP REGISTER request payload we are sending via JMeter:
{
"method": "REGISTER",
"uri": "sip:genesyscloud.com",
"from": "sip:[email protected]",
"to": "sip:[email protected]",
"call_id": "uuid-1234-5678-90ab-cdef",
"cseq": "1 REGISTER",
"contact": "sip:agent123@192.168.1.100:5060",
"max_forwards": "70",
"expires": "3600",
"authorization": "Basic dXNlcjpwYXNzd29yZA=="
}
Is there a hidden rate limit on SIP registration attempts per minute for BYOC trunks? The documentation mentions call capacity limits, but I cannot find specific details on registration throughput. We need to onboard 1000 agents simultaneously during peak shifts, so this bottleneck is critical. Any configuration changes or API endpoints that can help us tune the registration queue would be appreciated. We are currently on the latest US1 release.