My config is not working... WebRTC softphone fails to initialize after Zendesk migration

My current config is completely failing… We are currently migrating a large European customer base from Zendesk to Genesys Cloud and I am hitting a wall with the WebRTC softphone integration. In Zendesk, our agents used the standard browser-based voice widget which worked flawlessly across Chrome and Firefox. Now, trying to replicate that experience using the Genesys Cloud WebRTC softphone, the genesys-cloud-webrtc SDK (version 5.12.0) consistently throws a MediaStreamError with code 1004 when attempting to initialize the audio context. The environment is Genesys Cloud EU1, and I have verified that all necessary permissions for microphone access are granted in the browser. The error log shows Failed to acquire microphone: Permission denied even though the site permissions are explicitly set to allow. I suspect this might be related to how we mapped the Zendesk agent groups to Genesys Cloud skill groups via the Predictive Routing API, but I am not entirely sure. The specific API endpoint failing is /api/v2/webusers/me/phone when checking the device status. I have tried clearing the cache, using incognito mode, and even switching to a different machine, but the issue persists. Is there a specific configuration in the Genesys Cloud admin console that needs to be enabled for WebRTC to work correctly after a migration? I am also wondering if the SSO setup using SAML attributes might be interfering with the token generation required for the WebRTC connection. Any advice on troubleshooting this specific error would be greatly appreciated. I want to ensure our agents have a seamless transition without any technical hiccups. The Zendesk workflow was so straightforward, and I am hoping Genesys Cloud can match that level of ease once we get this sorted out. I have checked the documentation on digital channel migration, but it does not explicitly cover this WebRTC initialization issue. Please let me know if there are any known issues with the current SDK version or if there is a workaround we can implement while waiting for a fix.