What is the standard approach to interpret the increase in failed softphone connections that appear in the Performance Dashboard for our EU-West BYOC environment? The recent update to the WebRTC signaling protocol has resulted in a noticeable spike in agent login failures, which are not being categorized correctly in the standard agent status metrics. The error logs from the Architect flow indicate a 408 Request Timeout during the initial WebSocket handshake, yet the dashboard continues to report these agents as ‘Available’ for approximately 30 seconds before transitioning to an error state. This discrepancy creates significant noise in the real-time queue activity reports, making it difficult to assess true agent capacity. The issue appears to be isolated to agents using the desktop softphone client version 2023.10.0, while mobile clients remain unaffected. We have verified that the firewall rules allow UDP traffic on ports 50000-59999, and the STUN/TURN servers are responding within acceptable latency thresholds. Is there a specific configuration parameter within the Organization Settings that needs to be adjusted to align the dashboard’s error reporting with the actual WebRTC connection status? The current behavior suggests a race condition between the signaling completion and the status update propagation in the performance views.