VBSS Streams Test

In general, A/V conferencing enables real-time audio and video communications between the Microsoft Teams users. However, most Microsoft Teams users use Video-based screen sharing (VBSS) for communication. The difference between VBSS and traditional screen-sharing has to do with the underlying protocols used, and what they excel at. Screen-sharing uses the remote desktop protocol (RDP), which is great at creating thousands of 1-to-1 sessions between users. VBSS use User Datagram Protocol (UDP) which helps in improving your video start times, the viewing quality of what you're watching (especially if what you're watching is moving fast), and overall reliability.

In environments where users use VBSS streams for communication, it becomes mandatory for the administrator to check the quality of the VBSS stream conferencing experience and the load on the Microsoft Teams so that administrators may proactively be alerted to abnormalities/technical glitches in the conferences. This is where the VBSS Streams test helps.

Using this test, you can easily figure out the total number of VBSS streams and the count of VBSS streams that were classified as poor, good and unclassified. Administrators can also figure out the reason on why the VBSS streams were classified as poor - is it due to high video frame rate? or high video local frame loss? or high video post Fec plr?

Target of the test : Domain-Microsoft Teams

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the monitored Domain-Microsoft Teams

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured. By default, this is portal.office.com
O365 User Name, O365 Password, and Confirm Password	For execution, this test requires the privileges of an O365 user who has been assigned the Service support admin role and is vested with the View-Only Audit Logs and Team administrator permissions. Configure the credentials of such a user against O365 User Name and O365 Password text boxes. Confirm the password by retyping it in the Confirm Password text box. While you can use the credentials of any existing O365 user with the afore-said privileges, it is recommended that you create a special user for monitoring purposes using the Office 365 portal and use the credentials of that user here. To know how to create a new user using the Office 365 portal and assign the required privileges to that user, refer to Creating a New User in the Office 365 Portal.
Lookup Domain	Specify the name of the domain that is to be monitored. For example, if the user wants to monitor the performance of eginnovations.com domain, then the domain name has to be keyed in as eginnovations.com in the Lookup Domain text box.
Domain Name, Domain User Name, Domain Password, and Confirm Password	These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server. In this case, in the Domain text box, specify the name of the Windows domain to which the eG agent host belongs. In the Domain User Name text box, mention the name of a valid domain user with login rights to the eG agent host. Provide the password of that user in the Domain Password text box and confirm that password by retyping it in the Confirm Password text box. On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of these parameters. By default, these parameters are set to none.
Proxy Host, Proxy Port, Proxy User Name, Proxy Password and Confirm Password	These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server. In this case, provide the IP/host name and port number of the Proxy server that the eG agent should use in the Proxy Host and Proxy Port parameters, respectively. If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the Proxy User Name and Proxy Password text boxes. Confirm that password by retyping it in the Confirm Password text box. If the Proxy server does not require authentication, then specify none against the Proxy User Name, Proxy Password, and Confirm Password text boxes. On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.
Show All Poor Streams	By default, this flag is set to No indicating that the detailed diagnosis for all the measures of this test will show only the Top N poor streams configured against the Show N Poor Streams parameter. Set this flag to Yes if you wish to view the detailed diagnosis of all poor streams identified by this test.
Show N Poor Streams	By default, this parameter is set to 10, indicating that the detailed diagnostics will report the top-10 poor streams. You can change the 'N' in Show N Poor Streams by specifying any number of your choice in this text 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
Unclassified streams	Indicates the number of video-based-screen-sharing streams that did not have sufficient data to be classified as good or poor.	Number
Total VBSS streams	Indicates the total number of video-based-screen-sharing streams.	Number
Poor streams due to high video post FECPLR	Indicates the number of video-based-screen-sharing streams where the Video Post Fec plr exceeds the pre-defined thresholds.	Number
Poor streams due to high video local frame loss	Indicates the number of video-based-screen-sharing streams that were classified as poor owing to Video Local Frame Loss.	Number	The detailed diagnosis of this measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams classified as poor due to high video local frame loss.
Poor streams due to high video frame rate	Indicates the number of video-based-screen-sharing streams that were classified as poor owing to high video frame rate.	Number	The detailed diagnosis of this measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams classified as poor due to high video frame rate.
Poor streams	Indicates the number of video-based-screen-sharing streams classified as poor.	Number	The detailed diagnosis of this measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams that are classified as poor.
Poor streams percentage	Indicates the percentage of video-based-screen-sharing streams that were classified as poor.	Percentage
Good streams	Indicates the number of video-based-screen-sharing streams that were classified as good.	Number

The detailed diagnosis of the Poor streams measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams that are classified as poor.

Figure 1 : The detailed diagnosis of the Poor streams measures

The detailed diagnosis of the Poor streams due to high video local frame loss measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams classified as poor due to high video local frame loss.

Figure 2 : The detailed diagnosis of the Poor streams due to high video local frame loss measure

The detailed diagnosis of the Poor streams due to high video frame rate measure lists the start time, end time, first UPN, second UPN, first IP address, second IP address, conference ID and the number of VBSS streams classified as poor due to high video frame rate.

Figure 3 : The detailed diagnosis of the Poor streams due to high video frame rate measure