This report identifies managed networks with the highest ratios of poor-quality Teams calls focusing only on network-level data so that an admin can isolate and fix local network issues under IT control — even for peer-to-peer calls — and improve end-user experience. It mainly uses metrics that point to network specific problems:
- Call Setup Failures
- Mid Call Failures
- Sent Quality Event Ratio
- ReceivedQualityEventRatio
Benefits of using the Page ?
- Identify Managed Networks with Network related Call Problems
- Analysis of sending / receiving streams on Devices on the Network. Are outbound issues more common than inbound, or are they balanced?
What
Four main items determine the criteria for listing networks.
- Calls where the sentQualityEventRatio exceeds 2%
- Calls where the receivedQualityEventRatio exceeds 2%
- Calls experiencing CallSetupFailure
- Calls experiencing MidCallFailure
What are these metrics?
- sentQualityEventRatio: Percentage of streams where the sending endpoint reported quality affecting events (like high jitter, packet loss, or even CPU issues).
- receivedQualityEventRatio: Percentage of streams where the receiving endpoint reported quality affecting events.
- CallSetupFailure: Client has problems to establish a connection to join a Teams Call
- MidCallFailure: The client was disconnected or received a message that Teams is attempting to reconnect to the meeting.
Examples
- High sent ratio + low received ratio: Problem likely on the user’s outbound path (local network, Wi-Fi, VPN, or device CPU).
- Low sent ratio + high received ratio: Problem likely on remote user’s outbound path or your inbound network.
- Both high: General network issue (e.g., corporate WAN, ISP ,...). Device is unlikely the reason.
Components on the Page
The Time Picker allows users to specify a particular timeframe. Please note that if a period longer than 14 days is selected, the data will be capped accordingly. In this case, the original start date is retained, and the end date is set to 14 days after the start date.
KPIs
- Total User Calls: Total Number of User Calls across all identified managed networks
- Impacted User Calls: Total Number of Impacted User Calls across all identified managed network. Impact means that one of the mentioned condition is true
- Mid Call Failures: Number of User Calls with Mid Call Failures
- Setup Call Failures: Number of User Calls with Setup Call Failures
- Firewall Block Exception: Number of User Calls where MissingFWIPBlockExemptionRule got triggered. The issue could be related to either firewall and network reasons or other events where the call setup was unsuccessful.
- Non-Standard Audio Port: Number of User Calls using non-standard audio ports
Grid
