Open Forum

 View Only

 Understanding Endpoint voice quality Report and Media Relay Voice Quality Report

  •   1
  •   2
Megan Kalafut's profile image
Megan Kalafut 8x8 User posted 05-16-2025 10:23

For context, we have seemingly random issues with poor call quality where a call with a customer has poor sound quality, but then when they call again, 30 seconds later, the call is fine.  Or, the user goes to transfer the customer to a different extension, and then can't complete the transfer or stop it so the customer only gets hold music.

I have read through this: Interpret Call Quality Reports in Analytics for 8x8 Work

8x8 remove preview
Interpret Call Quality Reports in Analytics for 8x8 Work
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.
View this on 8x8 >

and this:

Analytics for 8x8 Work-Run a Call Detail Record report

8x8 remove preview
Analytics for 8x8 Work-Run a Call Detail Record report
In Analytics for 8x8 Work, use the Call Detail Record(CDR) to review the entire call journey from start to finish. This report is ideal for tracing a specific call to see how the call was routed, who answered, the call, the duration of the call, whether the call was on hold, and more.
View this on 8x8 >

and this:

Definitions for Call Detail Records in Analytics for 8x8 Work

8x8 remove preview
Definitions for Call Detail Records in Analytics for 8x8 Work
Call ID A unique call identification number that identifies all legs of the original call. Leg ID Identifies the leg of a call-a hop number such as 1 for direct, 2 for forwarded or transferred call for which this record refers to. Start Time The time a call starts.
View this on 8x8 >

However, I am struggling to understand some of the abbreviations and what it means.  I have one "Good" example and two "bad" examples:

Bad #1nt: - Customer that called in couldn't hear very well, so they hung up and called back, generating the "good" call below.

Local.PacketLoss

NLR:0% , JDR:0.27%

Local.Latency

RTD:110 , ESD:0

Local.Jitter

JBA:3 , JBR:0 , JBN:63 , JBX:100 , JB_ABSMAX:2000

Local.BurstGapLoss

BLD:255 , BD:20 , GLD:1 , GD:6860 , GMIN:16

Local.QualityEst

RLQ:93 , RCQ:93 , EXTRI:0 , EXTRO:0 , MOSLQ:4.4 , MOSCQ:4.4

Remote.TimeStamp

start:2025-05-16T15:54:20Z , stop:2025-05-16T15:54:43Z

Remote.SessionDesc

PT:0 , Desc:PCMU , SR:0 , FD:20 , FO:0 , FP:0 , PLC:0 , PPS:50

Remote.PacketLoss

NLR:0.2% , JDR:0.2%

Remote.Latency

RTD:116 , ESD:0

Remote.Jitter

JBA:3 , JBR:0 , JBN:63 , JBX:100 , JB_ABSMAX:2000

Remote.BurstGapLoss

BLD:73 , BD:10 , GLD:0 , GD:487 , GMIN:16

Bad #1 Media Relay Server:

Report[0].ToEndPoint.Relay

Packets:1113, Loss:0%, Jitter:0 ms,

Report[0].ToEndPoint.Time

Start:05/16/2025 15:54:21, Stop:05/16/2025 15:54:43

Report[0].FromEndPoint.Relay

Packets:1152, Loss:0%, Jitter:2 ms,

Report[0].FromEndPoint.Time

Start:05/16/2025 15:54:21, Stop:05/16/2025 15:54:43

Bad #2 Endpoint: User tried to transfer and was not able to, hung up, called back, and then transferred. 

Local.System

NAPC=0 MLO=0

Local.PacketLoss

NLR:0% , JDR:1.25%

Local.Latency

RTD:0 , ESD:0

Local.Jitter

JBA:3 , JBR:0 , JBN:100 , JBX:100 , JB_ABSMAX:2000

Local.BurstGapLoss

BLD:255 , BD:20 , GLD:1 , GD:5600 , GMIN:16

Local.QualityEst

RLQ:78 , RCQ:0 , EXTRI:0 , EXTRO:0 , MOSLQ:4 , MOSCQ:0

Bad #2 Media Relay:

Report[0].ToEndPoint.Relay

Packets:3387, Loss:0%, Jitter:0 ms,

Report[0].ToEndPoint.Time

Start:05/16/2025 16:26:05, Stop:05/16/2025 16:27:12

Report[0].FromEndPoint.Relay

Packets:491, Loss:0%, Jitter:2 ms,

Report[0].FromEndPoint.Time

Start:05/16/2025 16:26:05, Stop:05/16/2025 16:26:14

Good endpoint:

Local.PacketLoss

NLR:0.01% , JDR:0.03%

Local.Latency

RTD:100 , ESD:0

Local.Jitter

JBA:3 , JBR:0 , JBN:60 , JBX:100 , JB_ABSMAX:2000

Local.BurstGapLoss

BLD:255 , BD:20 , GLD:2 , GD:2220 , GMIN:16

Local.QualityEst

RLQ:97 , RCQ:97 , EXTRI:0 , EXTRO:0 , MOSLQ:4.5 , MOSCQ:4.5

Remote.TimeStamp

start:2025-05-16T15:54:58Z , stop:2025-05-16T15:58:56Z

Remote.SessionDesc

PT:0 , Desc:PCMU , SR:0 , FD:20 , FO:0 , FP:0 , PLC:0 , PPS:50

Remote.PacketLoss

NLR:0.02% , JDR:0.02%

Remote.Latency

RTD:100 , ESD:0

Remote.Jitter

JBA:3 , JBR:0 , JBN:60 , JBX:100 , JB_ABSMAX:2000

Remote.BurstGapLoss

BLD:255 , BD:3 , GLD:0 , GD:5872 , GMIN:16

Remote.QualityEst

RLQ:97 , RCQ:0 , EXTRI:0 , EXTRO:0 , MOSLQ:4.4 , MOSCQ:4.4

Good Media:

Report[0].ToEndPoint.Relay

Packets:11839, Loss:0%, Jitter:0 ms,

Report[0].ToEndPoint.Time

Start:05/16/2025 15:54:59, Stop:05/16/2025 15:58:56

Report[0].FromEndPoint.Relay

Packets:11883, Loss:0%, Jitter:2 ms,

Report[0].FromEndPoint.Time

Start:05/16/2025 1

Questions:

  1. What does NAPC and MLO mean in the context of "Local.system"?
  2. For Local or Remote Burst Gap loss, what do BD, GLD, GD, and GMIN mean?  I know BLD is based out of 255 for 8x8 softphones
  3. What does it mean if there is Remote Burst Gap Loss and not Local Burst Gap loss?
  4.  What does it mean if there is no loss on the media relay server voice quality report but there is on the endpoint voice quality report?

Thank you very much for whatever guidance you can give!

Alina Maxim's profile image
Alina Maxim

Hello Megan,

  1. NAPC = "No Audio Playout Count". This is an 8x8 proprietary variable to count the number of times we had no audio to play out to the speaker device.
    MLO = "Main loop overflow". This is an 8x8 proprietary variable to count the number of times the main loop thread took too long to process. It is an indicator that the CPU is overloaded, which will affect audio quality.
  2. These are all defined in RFC6035 (report format) and https://datatracker.ietf.org/doc/html/rfc3611#section-4.7.2 (report parameters)
  3. 4. It means that there was no packet loss on the upstream from the endpoint to the MRS, but there is packet loss on the downstream from the MRS to the endpoint.
    Best regards,
    Alina