Does anyone understand why the WebRTC WebSocket connection returns a 403 Forbidden error when scaling concurrent sessions beyond 25 threads in JMeter 5.6?
The load test targets the Genesys Cloud US1 environment. The initial WebSocket handshake works correctly for single-threaded requests using valid OAuth2 tokens. However, when increasing the thread count to 30 or higher, the server immediately rejects the connection with a 403 status. The error occurs before any media exchange.
The JMeter script uses the WebSocket Sampler plugin to handle the upgrade request. All threads use unique, valid access tokens generated via the /oauth2/token endpoint just before the test run. The tokens are valid and not expired. The issue seems related to concurrent connection limits or rate limiting on the WebSocket endpoint itself, rather than authentication failure.
Is there a specific configuration in the Genesys Cloud admin portal that controls the maximum number of simultaneous WebRTC connections per API key or organization? The documentation mentions general API rate limits but does not specify limits for WebSocket connections used by softphones. The test environment has sufficient capacity for concurrent calls, so it is not a media server resource issue.