Introducing Azure Communication Services Call Diagnostics feature for web applications!
Published Jul 16 2021 01:45 PM 5,185 Views

Introducing Azure Communication Services Call Diagnostics feature for web applications!


Today we are happy to announce that the Call Diagnostics feature is available in ACS web Calling SDK to help you to build applications with improved management of in-call experience quality. Many factors can influence the call quality: poor network, hardware issues, low volume, OS and permission errors, freezes, etc. You, as a developer, might not know about a specific issue affecting specific call quality or reliability. Microsoft constantly monitors and analyses technical parameters of calls and exposes hints within API.  You can use the tips to provide a better experience to your users. For example, you can suggest in UI (or force) to turn off the camera if bandwidth is not enough for both audio and video simultaneously. Or tip the user that they speak while being muted. The SDK does not have access, collect or analyze any personal data.

Screen Shot 2021-07-15 at 3.38.48 PM.png

Here are the diagnostics the Azure Communications Services JS SDK exposes:

  • Someone is on the video call and can’t see or hear the other party.
  • Someone is speaking while being muted.
  • Someone is experiencing bad video quality.
  • If your device is not connected to a network.
  • If during a call the WiFi signal goes on and off.
  • Low bandwidth, no internet connection.
  • All speakers are unplugged.
  • All microphones are unplugged.
  • Camera, microphone, speaker failures.
  • Permission’s errors.

Let go deeper to the Call Diagnostic APIs, which supports two types of modalities:

  1.    Media (audio, video, screen-sharing). Examples: noSpeakerDevicesEnumerated, speakingWhileMicrophoneIsMuted,  noMicrophoneDevicesEnumerated, cameraFreeze, cameraStartFailed, cameraStartTimedOut, microphoneNotFunctioning, microphoneMuteUnexpectedly, screenshareRecordingDisabled, microphonePermissionDenied, cameraPermissionDenied.
  2.   Network (everything related to user’s network). Examples: noNetwork, networkRelaysNotReachable, networkReconnect, networkReceiveQuality.

The exhaustive list of available call diagnostics per each group could be found in our documentation - Call diagnostics.

Call diagnostics is an extended feature of the core Call API. It's very simple to add the Call diagnostic feature to your app:




const callQualityApi = call.api(Features.Diagnostics);




Now all you need to do is subscribe to an event listener and once the diagnostic has been received, you will get a call-back.
'diagnosticChanged', diagnosticChangedListener);'diagnosticChanged', diagnosticChangedListener);




For more details on implementation please go to official documentation - Call diagnostics.

If you don’t have an active web application, you can download the web sample with already built-in diagnostics from our GitHub and run it.


Supported platforms


Call Diagnostics feature is available in JS Calling SDK starting 1.2.0-beta.1 and supported on the following desktop and mobile browsers:


  • Safari
  • Edge
  • Chrome

The User Facing diagnostics for other platforms (iOS, Android, Windows) are on roadmap




There is no additional fee for call diagnostics.


Getting started


Check out our getting started guides:


Give us your feedback


Your feedback is our main factor in prioritizing work items. Please share your ideas, opinions, and suggestions on our GitHub. We appreciate your help!


Version history
Last update:
‎Aug 23 2021 03:01 PM
Updated by: