Browser-based calling issues in Google Chrome 143

We have identified an issue affecting browser-based calling caused by a recent update to Google Chrome (version 143). Due to this change, the hold and unhold functionality is not working correctly. When a call is placed on hold and then resumed, the call may become inactive, resulting in a dead call and the user being stuck on the calling screen. This issue also impacts warm transfers and three-way calling, as they rely on the same underlying behavior. Our engineering team has successfully reproduced the issue and is actively working on a fix. We will provide an update as soon as a fix is available. Workaround: If you experience issues with hold, unhold, warm transfer, or three-way calling, please use the desktop application, which continues to work as expected.