Meeting Quality Score Test

For users to have a seamless meeting experience, it is important to have good meeting quality. For overall quality of meeting to be called good, quality should be acceptable in all three parameters viz. audio quality, video quality and screen share quality. hat is the reason it is important to monitor all three of these aspects so that organization administrators have view of quality of meetings, and area which is lacking in quality. It helps them take corrective actions if certain aspect needs attention.

This test monitors the Zoom meetings and reports the metrics which provide the meeting quality score against all three of audio, video and screen share aspects.

Target of the test : Zoom

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the monitored account in Zoom.

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed, the default value is 12 hrs.
Host	The host for which the test is to be configured. By default, this is Zoom.us.
Client ID	When configuring the Zoom API, you should have created an API client with OAuth authentication. Each client app is assigned with a Client ID which you need to copy from client app configuration wizard and save down. Zoom API requires Client ID and Secret Token when calling REST APIs. To know more about how to create Client ID and Secret Token, refer to Setting up Zoom API
Client Secret	Secret Token is generated along with Client ID during API configuration. Each client app is assigned with a Client ID which you need to copy from client app configuration wizard. Zoom API requires Client ID and Secret Token when calling REST APIs. To know more about how to create Client ID and Client Secret, refer to Setting up Zoom API
Authorization Code	Authorization Code acts as an access token which tells Zoom on subsequent requests that current client has already been authorized. The Authorization Code is sent to client as string along with redirect URL once the client request has been authorized. In this text box, you need to specify the authorization code that you obtained during API configuration. For more details, refer to Setting up Zoom API
Redirect URL	In the authorization flow, the Zoom API request is first passed on to Zoom Auth Server. Once the authorization is successful, the client request is redirected back to URL provided by user in Redirect URL along with authorization code. Client can now hit the API with given authorization code to pull metrics.
API URL	Zoom offers globally accessible URL for Zoom REST APIs. To enable the eG agent to connect Zoom REST APIs and pull out metrics, this test should be configured with the accessible URL against this parameter. The default value of this parameter is https://api.zoom.us/v2/. Before using the APIs, first you need to create an API client, set up the authentication and authorization details as elaborated in topic Setting up Zoom API.
Show N DD	By default, this parameter is set to 50. This indicates that, by default, the detailed diagnosis of this test will display the details of only 50 events. If you wish this test to report details of all events, then specify "all" against this parameter.
Proxy Host and Port	If the eG agent need to communicates with Zoom via a proxy, then, you also need to configure the eG agent on the connector with the proxy server details. This will enable the eG agent to connect to the Zoom without a glitch, and pull metrics. To facilitate this communication. do the following: Specify the IP address/fully-qualified host name of the proxy server, against PROXY HOST. Specify the port at which the Proxy server listens for requests from the eG agent, against PROXY PORT. By default, both these parameters are set to none, indicating that the eG agent does not communicate with the Zoom via a proxy.
Proxy User Name and Password	Specify the Proxy username and password if proxy server is being used to connect with Zoom.
Confirm Password	Confirm the password by typing it in Confirm password box.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time the test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Bad audio	Indicates if the audio quality is in Bad range.	Number	Administrators need to identify the issues which are causing poor audio quality - key points like are users using Zoom audio or having third party carrier etc.
Poor audio	Indicates if the audio quality is better than Poor range but not in Fair range.	Number	Administrators need to identify the issues which are causing poor audio quality - key points like are users using Zoom audio or having third party carrier etc.
Fair audio	Indicates if the audio quality is better than Poor range but not in Good range.	Number	Although quality may be acceptable but administrators may need to further investigate how to improve the quality.
Good audio	Indicates if the audio quality is good.	Number
Bad video	Indicates if the video quality is in Bad range.	Number	Main reason behind poor video could be the bandwidth, they may need to investigate further it is bad for all the users or some of them, and take corrective actions accordingly.
Poor video	Indicates if the video quality is better than Poor range but not in Fair range.	Number	Main reason behind poor video could be the bandwidth, they may need to investigate further it is bad for all the users or some of them, and take corrective actions accordingly.
Fair video	Indicates if the video quality is better than Poor range but not in Good range.	Number	Main reason behind poor video could be the bandwidth, they may need to investigate further it is bad for all the users or some of them, and take corrective actions accordingly.
Good video	Indicates if the video quality is good.	Number
Bad screen share	Indicates if the screen share quality is in Bad range.	Number	An issue with meeting infrastructure could be attributes to poor screen share experience.
Poor screen share	Indicates if the screen share quality is better than Poor range but not in Fair range.	Number	An issue with meeting infrastructure could be attributes to poor screen share experience.
Fair screen share	Indicates if the screen share quality is better than Poor range but not in Good range.	Number
Good screen share	Indicates if the screen share quality is good.	Number