You may find yourself in a situation where, if you’ve not interacted with the Sharpen application through a Chromium-based browser (Google Chrome, Chromium, Microsoft Edge Chromium), audible alerts are not received. As a result of the Google change referenced below, Chrome requires that the user has interacted with the website, or uses the website often to enable audible alerts. This article describes how to work around the issue.
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes
Steps to reproduce:
If you’ve not run into the issue, but are curious as to its impact, it can be easily reproduced by performing the following steps.
Launch Sharpen Q or Sharpen connect
Once the page is loaded right click in any empty space within the browser and choose “reload”
Place an inbound call to the destination test user
Notice that you will be visually, but not audibly alerted
Fix
Method 1
Explicitly allow [*.]sharpencx.com to play sounds
This method requires setting once. If browser settings are cleared, or the browser is re-installed, you may have to perform these steps again.
Open Google Chrome (or Chromium-based browser)
Enter chrome://settings/content/sound into the URL bar
Click the “Add” button to the right of the “Allow” section
Type [*.]sharpencx.com and click “Add”
Close the browser and relaunch
Method 2
Interface with the browser
This method requires no change, but does risk effectiveness based on user interaction
Due to the nature of Google’s change, the philosophy concludes that websites should not automatically play audio to users unless they are actively engaged. It registers this activity based on interactivity with the browser. Simply clicking on any element within the website after logging in will allow audio to flow freely.