Is it possible to bypass the default SIP registration rate limits when performing high-concurrency load tests against Genesys Cloud US1?
We are currently validating our SIP trunk capacity using JMeter 5.6 with the SIP plugin. The goal is to simulate 500 concurrent SIP registrations within a 30-second window to stress-test the inbound routing logic. However, the test fails immediately after reaching approximately 40 concurrent threads. The Genesys Cloud SIP servers respond with 403 Forbidden errors for the registration requests, citing “Rate Limit Exceeded” in the response headers.
The environment details are as follows:
- Region: US1
- Tool: JMeter 5.6 with SIP plugin 3.2
- Target: Genesys Cloud SIP Trunk (Port 5060)
- Scenario: Parallel SIP REGISTER requests from unique IP addresses (simulated via loopback proxies)
We have verified that the SIP trunk configuration in the Genesys admin portal allows for the expected number of concurrent calls, but the registration phase itself seems to be throttled aggressively. Standard API rate limits are documented, but specific limits for SIP signaling messages are not clearly defined in the developer documentation.
How can we configure the SIP trunk or adjust the JMeter test to successfully register 500 concurrent endpoints without triggering 403 Forbidden errors?