Does anyone know why RTCPeerConnection fails with 403 Forbidden when scaling up concurrent users in JMeter 5.6.2? I am running a load test from Asia/Singapore to validate softphone capacity. The test plan uses the genesys-cloud-webrtc-sdk version 2.1.0. Initial token acquisition via /api/v2/oauth/token works fine, and low concurrency (10 users) connects successfully. However, pushing to 50 concurrent virtual users triggers immediate failures on the WebSocket connection to wss://api.mypurecloud.com/api/v2/analytics/events/realtime. The error log shows WebSocket connection failed: 403. I have verified the bearer tokens are valid for the duration of the test. The Retry-After header is not present, which suggests this might be a capacity limit rather than a rate limit. I am using the default JMeter thread group with a ramp-up period of 5 seconds. Is there a specific header or parameter missing in the WebSocket upgrade request that causes this under load? I have checked the X-Genesys-Client-Version header and it matches the SDK. Any insights on handling this specific 403 scenario during high-concurrency WebRTC tests would be appreciated. I suspect it might be related to the platform API throughput limits for signaling.