|
Measures reported by MTMWHNetQtySmyTest
If your Microsoft Teams users complain of inaccessibility or poor audio/video call quality, you may want to check the quality of the network link to the Micorsoft Teams. A flaky or latent network connection to the Microsoft Teams server can sometimes deny users access to Microsoft Teams application. Also, sometimes, the calls/meetings may end abruptly before the users do so thus adversely impacting their overall experience with Microsoft Teams. To proactively figure out the reason behind such flaky network and to ensure Quality of Service at all times, administrators can periodically run the MTMWHNetQtySmyTest test.
This test when executed periodically reveals any break or slowness in the network connection to Microsoft Teams. Using this test, administrators can measure the user experience in terms of network quality and figure out the real reason behind poor network connections-is it due to jitter? or packet loss? or round trip? or audio degradation?
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 |
| MxmJitter |
Indicates the maximum jitter for stream. |
Milliseconds |
|
| MxPtLsRte |
Indicates the percentage of maximum packet loss for stream. |
Percentage |
|
| CnldSmplAvg |
Indicates the ratio of the number of audio frames with samples generated by packet loss concealment to the total number of audio frames for streams. |
Percentage |
|
| AvgRndTripMx |
Indicates the average of maximum network propagation round-trip time computed as specified in RFC3550 for streams. |
Milliseconds |
|
| AvgRndTrip |
Indicates the average of average network propagation round-trip time computed as specified in RFC3550 for streams. |
Milliseconds |
|
| AvgPtLsRt |
Indicates the average of average percentage of packets lost computed using 5 second interval for
streams. |
Percentage |
|
| AvgJitter |
Indicates the average network jitter for streams. |
Milliseconds |
Ideally, the value of this measure should be low.
The detailed diagnosis of this measure lists the Date, hour, first UPN, second UPN, First IP address, second IP address, conference ID, the list of participants, caller and callee ID, and the average jitter. |
| AvgAudDgtn |
Indicates the Average Network Mean Opinion Score degradation for streams. |
Number |
|
|