eG Monitoring
 

Measures reported by MTMWHVBSSStrmsTest

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 MTMWHVBSSStrmsTest 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 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?

Note:

This test uses Webhooks to collect metrics. Before running the Webhooks-based tests for Teams, make sure that the following pre-requisites are fulfilled:

  • Make sure that all the pre-requisites under Monitoring Office 365 are fulfilled;

  • Install and start the Webhooks service on the same system that hosts the eG agent.

  • A public HTTPS URL is required for the endpoint, so it can receive call records from Microsoft. To enable this transmission, make sure that the firewall is configured to allow traffic from the internet to the system hosting the Webhooks service. Also, make sure that the port at which the service listens is open.

  • Ensure that the Webhooks service is SSL - enabled.

  • The Microsoft Graph app should be configured with the User.Read.All Delegated Permission and the CallRecords.Read.All Application Permission; to know how to register the Microsoft Graph app on Azure Active Directory and assign permissions.

For more details on the above listed steps, refer to Pre- requisites for Monitoring Microsoft Office 365 Environments and Using Webhooks to Measure Call Quality documents.

Outputs of the test : One set of results for the monitored Microsoft Teams service.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
VBSUclfdStm Indicates the number of video-based-screensharing streams that did not have sufficient data to be classified as good or poor. Number Use the detailed diagnosis of this measure to know which VBSS streams were marked as unclassified. The start time, end time, first UPN, second UPN, first and second IP addresses, conference ID, segment ID, call type, participants, caller and callee of each unclassified stream is reported as part of detailed diagnosis, along with the number of times every stream was marked as unclassified.
VBSStms Indicates the total number of video-based-screen sharing streams. Number  
VBSStmPrVpF Indicates the number of video-based-screensharing streams where the Video Post Fec plr exceeds the pre-defined thresholds. 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, the list of participants, caller and callee ID, and the count of times that each stream was classified as ‘poor’ due to high video post FECPLR.
VBSPrVLsAv Indicates the number of video-based-screensharing 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, the list of participants, caller and callee ID, and the count of times that each stream was classified as ‘poor’ due to high video local frame loss.
VBSPrVFmeAv Indicates the number of video-based-screensharing 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, the list of participants, caller and callee ID, and the count of times that each stream was classified as ‘poor’ due to high video frame rate.
VBSPrStm Indicates the number of video-based-screensharing streams classified as poor. Number  
VBSPrPrcnt Indicates the percentage of videobased-screen-sharing streams that were classified as poor. Percentage  
VBSGdStm Indicates the number of video-based-screensharing streams that were classified as good. 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, the list of participants, caller and callee ID, and the count of times that each stream was classified as ‘good’.