Interpret Call Quality Reports in Analytics for 8x8 Work

Interpret Call Quality Reports in Analytics for 8x8 Work

Overview

Analytics for 8x8 Work is an excellent call quality reporting tool. Correctly interpreting call quality reports will help you troubleshoot call quality issues on your 8x8 services. The following Q&A provides some insight into the more difficult portions of call quality reports. For more information on using Analytics for 8x8 Work, see the online product documentation.

Frequently Asked Questions

How do I interpret calls that last 30 seconds or more that show very high packet loss (40% loss or above)?

Calls that last more than 30 seconds that show very high packet loss are false positives. In these cases, there is no actual packet loss. Calls with true high packet loss would not last more than a few seconds. 

How do I interpret calls with a Quality Score of good or excellent, but that actually had quality issues?

For a call with a rating of good or excellent that actually had poor quality, there are two possible scenarios:

  1. If the original call stream from the public switched telephone network (PSTN) is poor, such as a bad cell phone connection on the other side, the current technologies would not detect this if the IP stream is solid (meaning that the IP side between the underlying carrier and the end-user is fine, but the original content is bad). These cases should be reported to the underlying carrier for investigation. The underlying carrier will determine if the issue was one bad call, such as a bad cell connection, or a bigger issue such as a problem PSTN switch in a particular market. When the issue lies with the underlying carrier, action will be taken by the underlying PSTN carriers.
  2. It is important to pay attention to the net packet loss ratio (NLR%) and jitter buffer discard ratio (JDR%) portions of the report even for good or excellent calls.

A call might be rated with an overall Quality Score of good, although the call experienced a 3% loss within a short period of time (e.g., 5 seconds in a 5-minute call). It is important to take into account the gap and loss density. Although a call may have an overall rating of good, a sudden burst of 3% packet loss in a period of 5 seconds may produce poor call quality. The same call with a 3% loss evenly distributed over the course of the call would sound good for the entire time.

How do I see what kind of loss was experienced?

To find out what kind of loss was experienced (evenly distributed or in bursts), click the red plus sign + next to the Call Quality Detail report to get advanced details (EndPoint Voice Quality Report). Look for the Burst Loss Density (BLD). The range will be 1 to 100 for desk phones such as Poly. The range will be 1 to 255 for 8x8 Work for Desktop, 8x8 Work for Mobile. The closer the number is to 100 (or 255 in the case of 8x8 Work for Desktop) will indicate that the loss happened in a burst (sudden loss of data, creating a gap or horrible quality for a short period). The smaller the number is will indicate that the loss was evenly distributed (or the loss did not happen as much during the bursts). As an example, you see a call quality report that says Local.BurstGapLoss BLD:99.6. A BLD of 99.6 would indicate that the loss happened in a burst. This screenshot displays where to find the BLD information in the report.

A screenshot of a computer

AI-generated content may be incorrect.

Analytics for 8x8 Work depends on the device endpoint reporting what it receives. Since the data flows through the 8x8 iPBX, how can we get an accurate picture of how good a call is without having metrics reported by the 8x8 iPBX in addition to the end devices?

The phone will know if the data sent by the 8x8 iPBX is received properly (in the right order, without much latency, etc.), but how does 8x8 Work Analytics know how well the 8x8 iPBX is receiving packets from the phone? If the reporting is based on the device endpoints, it seems that this only provides half of the call quality picture.

There are two parts to call quality reports: one from the endpoint perspective, and one from the server (Media Relay Server) perspective. To see the details of the report from the server side, click the red plus sign + next to the Call Quality Detail report to open the Endpoint Voice Quality Report. Then, click Next. The information from the media relay server is found on the Media Relay Server Voice Quality Report.

A screenshot of a computer

AI-generated content may be incorrect.

    • Related Articles

    • Are SMS reports available in Analytics for 8x8 Work?

      Question Are there any reporting options for SMS activity in Analytics for 8x8 Work? Applies To Analytics for 8x8 Work SMS Answer Currently, reporting options in Analytics for 8x8 Work are limited to call activity and endpoint availalbility. ...
    • Run Call Log Reports in 8x8 Admin Console

      Objective Admins have access to detailed call log reports. You can run these reports at any time or schedule them on a regular basis. Scheduled reports will be sent to your designated email address. Applies To Call Log Reports Admin Console Procedure ...
    • What lists and reports can I export from 8x8 Admin Console, Contact Center, or Analytics?

      Question What lists and reports can I export from 8x8 Admin Console, Configuration Manager for Contact Center, or Analytics? Applies To Admin Console Configuration Manager for Contact Center Analytics for 8x8 Work Analytics for Contact Center Agent ...
    • 8x8 Work Analytics: New Call Queue Dashboard Comparison

      Overview The new 8x8 Work Analytics Queues dashboard is being introduced to centralize all Queue data in one place, without the need to navigate between multiple reports and dashboards. This new Queues dashboard will report on both real-time and new ...
    • Unable to Create or Schedule Reports in Analytics for 8x8 Work

      Symptom Unable to create or schedule reports in Analytics for 8x8 Work. Applies To Analytics for 8x8 Work Legacy Reports Resolution As of Analytics for 8x8 Work 2.1.2, users are unable to create or schedule reports using Schedule Reports. When trying ...