WebRTC softphone handshake failure affecting ServiceNow screen pop latency

Could someone clarify why the WebRTC softphone in Genesys Cloud (v2023.11) is returning a 408 Request Timeout during the initial SDP exchange, specifically when the X-GC-Session-ID header is missing from the WebSocket upgrade request? This timeout is causing a 3-second delay before the ServiceNow Data Action triggers the screen pop via the Architect flow, which is unacceptable for our compliance requirements in the London timezone. The issue persists across Chrome 119+ and Firefox 118, despite valid STUN/TURN configurations and confirmed firewall rules allowing UDP ports 5000-5999.