WebRTC Edge Connection Refused on Custom BYOC Setup

Anyone know why the WebSocket handshake fails when routing through a custom BYOC edge? We are running a JMeter script to simulate 50 concurrent softphone connections. The connection drops immediately with a 403 error before any media is exchanged. The standard cloud edge works fine, but the private edge blocks the request.

Error: WebSocket connection failed: 403 Forbidden (Origin not allowed)

Is there a specific CORS or origin whitelist setting in the Edge configuration that needs to be enabled for custom domains?

3 Likes

Have you tried verifying the AllowedOrigins configuration in your BYOC edge settings? The 403 usually stems from a mismatch between the softphone’s origin header and the whitelist.

Setting Value
AllowedOrigins https://app.mypurecloud.com
WebSocketPort 443
1 Like