Call Connectivity Issues

We are currently investigating a small subset of reports that some users are having call connectivity issues with their Webphones while using the Chrome Browser.

We will update our status page with further details as our investigation progresses.

Our team is continuing to investigate the issue relating to the inability to launch the Webphone successfully within the Chrome Browser.

Through our thorough investigation thus far, we have identified that the root of this issue is indeed isolated at the browser level. As a result of our diligent efforts, we have identified the steps required to mitigate this issue have been comprehensively outlined in the following article: https://docs.natterbox.com/docs/webphone-launch-issues-in-chrome-on-windows

We will update our status page with further details as our investigation progresses.

The investigation has identified the CTI error message displayed does not affect call initiation or acceptance; calling functions are working as normal.

An ongoing UI issue with the headphone icon on CTI, though visible, is not affecting any calls if your Webphone is open and registered. We're diligently investigating this.

If you are unable to make or receive any calls please do contact the customer support team.

As our investigation into resolving the UI error message on the CTI progresses, we have identified that while using the CTI within the Chrome browser some users are encountering an issue related to the headset icon (Red Dot). During this situation, users engaged in calls may experience an issue whereby the Dial Pad is not visible and users may have the inability to mute calls.

We are continuing to investigate further and we will update our status page with further details as our investigation progresses.

We are still actively investigating the issues related to using the Chrome browser. Whilst this investigation continues we advise that you use the Edge browser as a workaround.

We will continue to update our Status page as things progress.

We have identified a workaround to the CTI issue which was being induced by a Chrome update.

Chrome enables new features and experimental flags with each update and many of these are enabled by default, which can interfere with our application and Salesforce. The flag in question is the "Experimental third-party storage partitioning" Chrome Flag, which was enabled by default with a Chrome update beginning gradually in Chrome v115.

Please see our knowledge article with the required steps :

https://docs.natterbox.com/docs/webphone-launch-issues-in-chrome

Should you require any additional assistance, please do reach out to the Natterbox Support Team. [support@natterbox.com]