WARMTRANSFER / CALL QUALITY
CUCM Call Quality
2026-09-14 — 2026-09-20 · America/Chicago
Deterministic report · No AI used · WT-REPORT-1.1 · Generated 2026-08-10T12:00:00.000Z
Quality records204CMR rows in this selection
Devices8distinct device names
Median jitter11 msn=192
95th-pct jitter25 msn=192
95th-pct latency95 msn=192
Loss0.99%pooled lost / (received + lost)
Median MLQKav3.94n=175
No media received125.9% of selected records
No voice-quality metrics2914.2% of selected records
Jitter distribution
Records with media received and a readable jitter value.
Median11 msn=192
75th percentile14 msn=192
90th percentile19 msn=192
95th percentile25 msn=192
0–9 ms82 42.7%
10–19 ms92 47.9%
20–39 ms18 9.4%
40–79 ms0 0.0%
80 ms or more0 0.0%
Latency distribution
Records with media received and a readable latency value.
Median38 msn=192
75th percentile46 msn=192
90th percentile89 msn=192
95th percentile95 msn=192
0–49 ms166 86.5%
50–99 ms25 13.0%
100–199 ms1 0.5%
200–399 ms0 0.0%
400 ms or more0 0.0%
Loss distribution
Records with media received and a non-zero received-plus-lost denominator.
Median0.07%n=192
75th percentile0.12%n=192
90th percentile6.27%n=192
95th percentile7.30%n=192
0%30 15.6%
>0–0.99%136 70.8%
1–2.99%0 0.0%
3–9.99%26 13.5%
10% or more0 0.0%
MLQKav distribution
Records carrying a numeric MLQKav inside varVQMetrics.
Median3.94n=175
75th percentile3.98n=175
90th percentile4.00n=175
95th percentile4.00n=175
below 2.00 0.0%
2.0–2.9922 12.6%
3.0–3.490 0.0%
3.5–3.99124 70.9%
4.0 and above29 16.6%
Devices, worst first
Top 20 devices by 95th-percentile loss among their own scored records. Aliased by field: extensions, devices.
| Device | Extension | Scored records | 95th-pct loss | Median jitter | Median MLQKav |
|---|---|---|---|---|---|
| DEVICE-1 | DN-1 | 24 | 8.03% | 12 ms | 3.94 |
| DEVICE-2 | DN-2 | 25 | 7.60% | 14 ms | 3.92 |
| DEVICE-3 | DN-3 | 25 | 7.31% | 14 ms | 3.92 |
| DEVICE-4 | DN-4 | 24 | 0.13% | 9 ms | 3.94 |
| DEVICE-5 | DN-5 | 25 | 0.13% | 10 ms | 3.94 |
| DEVICE-6 | DN-6 | 23 | 0.13% | 9 ms | 3.96 |
| DEVICE-7 | DN-7 | 25 | 0.12% | 10 ms | 3.94 |
| DEVICE-8 | DN-8 | 21 | 0.10% | 10 ms | 3.96 |
Calls joined to their quality records
Aliased by field: calling and called numbers and extensions, devices. An alias names the same value everywhere in this report.
175 CDR records read (175 in CDR file 1). 202 of 204 CMRs joined to 168 calls. 2 CMRs have no CDR; 0 share a key with several CDRs; 0 lack a key. 7 CDRs have no CMR.
Calls by loss, highest first
Up to 50 calls. Loss is pooled over the call’s CMRs; jitter and latency are the highest any of its CMRs recorded; MLQKav is the lowest. Start time is the CDR’s origination, in America/Chicago. Cause is the CDR’s destination cause, or its originating cause when that is 0.
| Started | Calling | Called | Originating device | Terminating device | Duration | Cause | CMRs | Loss | Max jitter | Max latency | Lowest MLQKav |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-09-18 10:29 | DN-1 | DN-9 | DEVICE-1 | DEVICE-9 | 77 s | 16 | 1 | 8.35% | 28 ms | 89 ms | 2.80 |
| 2026-09-17 18:41 | DN-1 | DN-10 | DEVICE-1 | DEVICE-9 | 143 s | 16 | 1 | 8.03% | 22 ms | 89 ms | — |
| 2026-09-16 13:46 | DN-1 | DN-11 | DEVICE-1 | DEVICE-9 | 118 s | 16 | 1 | 7.73% | 28 ms | 89 ms | 2.80 |
| 2026-09-20 10:19 | DN-2 | DN-12 | DEVICE-2 | DEVICE-9 | 127 s | 16 | 1 | 7.73% | 28 ms | 89 ms | 2.80 |
| 2026-09-14 14:45 | DN-2 | DN-3 | DEVICE-2 | DEVICE-3 | 75 s | 16 | 2 | 7.60% | 25 ms | 98 ms | 2.75 |
| 2026-09-19 15:24 | DN-1 | DN-13 | DEVICE-1 | DEVICE-9 | 102 s | 16 | 1 | 7.46% | 22 ms | 89 ms | 2.80 |
| 2026-09-14 13:06 | DN-3 | DN-14 | DEVICE-3 | DEVICE-9 | 78 s | 16 | 1 | 6.59% | 28 ms | 101 ms | 2.65 |
| 2026-09-15 13:26 | DN-2 | DN-15 | DEVICE-2 | DEVICE-9 | 98 s | 16 | 1 | 6.53% | 28 ms | 95 ms | 2.60 |
| 2026-09-19 10:59 | DN-3 | DN-16 | DEVICE-3 | DEVICE-9 | 107 s | 16 | 1 | 6.53% | 28 ms | 95 ms | — |
| 2026-09-20 14:05 | DN-1 | DN-8 | DEVICE-1 | DEVICE-8 | 125 s | 16 | 2 | 6.47% | 25 ms | 86 ms | 2.65 |
| 2026-09-14 18:31 | DN-2 | DN-17 | DEVICE-2 | DEVICE-9 | 73 s | 16 | 1 | 6.27% | 22 ms | 95 ms | 2.60 |
| 2026-09-18 15:04 | DN-3 | DN-18 | DEVICE-3 | DEVICE-9 | 82 s | 16 | 1 | 6.27% | 22 ms | 95 ms | 2.60 |
| 2026-09-17 10:09 | DN-2 | DN-19 | DEVICE-2 | DEVICE-9 | 147 s | 16 | 1 | 6.04% | 28 ms | 95 ms | 2.60 |
| 2026-09-16 18:21 | DN-2 | DN-20 | DEVICE-2 | DEVICE-9 | 123 s | 16 | 1 | 5.82% | 22 ms | 95 ms | 2.60 |
| 2026-09-20 15:54 | DN-3 | DN-21 | DEVICE-3 | DEVICE-9 | 132 s | 16 | 1 | 5.82% | 22 ms | 95 ms | 2.60 |
| 2026-09-19 14:45 | DN-2 | DN-3 | DEVICE-2 | DEVICE-3 | 105 s | 16 | 2 | 3.84% | 25 ms | 92 ms | 2.70 |
| 2026-09-17 09:30 | DN-3 | DN-8 | DEVICE-3 | DEVICE-8 | 60 s | 16 | 2 | 3.71% | 19 ms | 98 ms | 2.75 |
| 2026-09-18 09:50 | DN-2 | DN-7 | DEVICE-2 | DEVICE-7 | 80 s | 16 | 2 | 3.69% | 19 ms | 92 ms | 3.92 |
| 2026-09-14 09:10 | DN-1 | DN-3 | DEVICE-1 | DEVICE-3 | 70 s | 16 | 2 | 3.67% | 19 ms | 92 ms | 2.70 |
| 2026-09-14 14:35 | DN-4 | DN-2 | DEVICE-4 | DEVICE-2 | 65 s | 16 | 2 | 3.50% | 25 ms | 86 ms | 2.65 |
| 2026-09-20 09:40 | DN-3 | DN-7 | DEVICE-3 | DEVICE-7 | 130 s | 16 | 2 | 3.42% | 19 ms | 92 ms | 2.70 |
| 2026-09-16 09:00 | DN-1 | DN-2 | DEVICE-1 | DEVICE-2 | 120 s | 16 | 2 | 3.40% | 19 ms | 92 ms | 2.70 |
| 2026-09-17 09:20 | DN-5 | DN-3 | DEVICE-5 | DEVICE-3 | 140 s | 16 | 2 | 3.37% | 19 ms | 86 ms | 2.65 |
| 2026-09-16 14:25 | DN-5 | DN-2 | DEVICE-5 | DEVICE-2 | 115 s | 16 | 2 | 3.24% | 25 ms | 86 ms | 4.00 |
| 2026-09-16 09:50 | DN-6 | DN-1 | DEVICE-6 | DEVICE-1 | 110 s | 16 | 2 | 3.14% | 19 ms | 80 ms | 2.60 |
| 2026-09-19 09:10 | DN-1 | DN-3 | DEVICE-1 | DEVICE-3 | 100 s | 16 | 2 | 3.14% | 19 ms | 86 ms | 2.65 |
| 2026-09-14 11:28 | DN-4 | DN-22 | DEVICE-4 | DEVICE-10 | 64 s | 16 | 1 | 0.13% | 8 ms | 24 ms | 3.98 |
| 2026-09-15 10:19 | DN-2 | DN-23 | DEVICE-2 | DEVICE-9 | 97 s | 16 | 1 | 0.13% | 12 ms | 34 ms | — |
| 2026-09-18 18:01 | DN-5 | DN-17 | DEVICE-5 | DEVICE-10 | 73 s | 16 | 1 | 0.13% | 8 ms | 24 ms | 3.98 |
| 2026-09-19 17:52 | DN-3 | DN-24 | DEVICE-3 | DEVICE-9 | 106 s | 16 | 1 | 0.13% | 12 ms | 34 ms | 3.94 |
| 2026-09-14 13:56 | DN-5 | DN-25 | DEVICE-5 | DEVICE-10 | 68 s | 16 | 1 | 0.13% | 13 ms | 29 ms | 3.96 |
| 2026-09-15 12:47 | DN-3 | DN-26 | DEVICE-3 | DEVICE-9 | 101 s | 16 | 1 | 0.13% | 5 ms | 39 ms | 3.92 |
| 2026-09-14 15:24 | DN-1 | DN-27 | DEVICE-1 | DEVICE-9 | 72 s | 16 | 1 | 0.13% | 6 ms | 34 ms | 3.94 |
| 2026-09-17 16:13 | DN-5 | DN-28 | DEVICE-5 | DEVICE-10 | 139 s | 16 | 1 | 0.13% | 14 ms | 24 ms | 3.98 |
| 2026-09-18 12:57 | DN-2 | DN-29 | DEVICE-2 | DEVICE-9 | 81 s | 16 | 1 | 0.13% | 6 ms | 34 ms | 3.94 |
| 2026-09-14 17:52 | DN-3 | DN-30 | DEVICE-3 | DEVICE-9 | 76 s | 16 | 1 | 0.12% | 11 ms | 39 ms | 3.92 |
| 2026-09-20 16:23 | DN-4 | DN-31 | DEVICE-4 | DEVICE-10 | 119 s | 16 | 1 | 0.12% | 15 ms | 49 ms | 4.00 |
| 2026-09-16 11:18 | DN-4 | DN-32 | DEVICE-4 | DEVICE-10 | 114 s | 16 | 1 | 0.12% | 8 ms | 24 ms | 3.98 |
| 2026-09-17 17:02 | DN-2 | DN-33 | DEVICE-2 | DEVICE-9 | 146 s | 16 | 1 | 0.12% | 12 ms | 34 ms | 3.94 |
| 2026-09-20 18:51 | DN-5 | DN-20 | DEVICE-5 | DEVICE-10 | 123 s | 16 | 1 | 0.12% | 8 ms | 24 ms | 3.98 |
| 2026-09-19 11:28 | DN-4 | DN-34 | DEVICE-4 | DEVICE-10 | 94 s | 16 | 1 | 0.12% | 9 ms | 49 ms | 4.00 |
| 2026-09-16 15:14 | DN-2 | DN-35 | DEVICE-2 | DEVICE-9 | 122 s | 16 | 1 | 0.12% | 6 ms | 34 ms | 3.94 |
| 2026-09-19 13:56 | DN-5 | DN-15 | DEVICE-5 | DEVICE-10 | 98 s | 16 | 1 | 0.12% | 14 ms | 24 ms | — |
| 2026-09-20 12:47 | DN-3 | DN-36 | DEVICE-3 | DEVICE-9 | 131 s | 16 | 1 | 0.12% | 6 ms | 34 ms | 3.94 |
| 2026-09-16 09:10 | DN-7 | DN-4 | DEVICE-7 | DEVICE-4 | 130 s | 16 | 2 | 0.11% | 15 ms | 44 ms | 3.90 |
| 2026-09-15 18:51 | DN-5 | DN-37 | DEVICE-5 | DEVICE-10 | 93 s | 16 | 1 | 0.11% | 7 ms | 29 ms | 3.96 |
| 2026-09-16 17:42 | DN-3 | DN-38 | DEVICE-3 | DEVICE-9 | 126 s | 16 | 1 | 0.11% | 11 ms | 39 ms | 3.92 |
| 2026-09-19 09:20 | DN-8 | DN-4 | DEVICE-8 | DEVICE-4 | 110 s | 16 | 2 | 0.11% | 5 ms | 39 ms | 3.90 |
| 2026-09-15 14:15 | DN-8 | DN-7 | DEVICE-8 | DEVICE-7 | 105 s | 16 | 2 | 0.11% | 10 ms | 44 ms | 3.90 |
| 2026-09-18 14:25 | DN-8 | DN-6 | DEVICE-8 | DEVICE-6 | 85 s | 16 | 2 | 0.11% | 11 ms | 39 ms | 3.90 |
Device pairs
Up to 20 pairs of the CDR’s originating and terminating devices, highest pooled loss first.
| Originating device | Terminating device | Calls | Loss | Median jitter | Median MLQKav |
|---|---|---|---|---|---|
| DEVICE-2 | DEVICE-3 | 2 | 5.15% | 25 ms | 2.75 |
| DEVICE-3 | DEVICE-8 | 1 | 3.71% | 5 ms | 2.75 |
| DEVICE-2 | DEVICE-7 | 1 | 3.69% | 5 ms | 3.92 |
| DEVICE-1 | DEVICE-2 | 1 | 3.40% | 15 ms | 2.70 |
| DEVICE-1 | DEVICE-3 | 2 | 3.39% | 15 ms | 2.70 |
| DEVICE-5 | DEVICE-3 | 1 | 3.37% | 15 ms | 2.65 |
| DEVICE-5 | DEVICE-2 | 1 | 3.24% | 9 ms | 4.00 |
| DEVICE-6 | DEVICE-1 | 1 | 3.14% | 15 ms | 2.60 |
| DEVICE-1 | DEVICE-8 | 2 | 2.33% | 10 ms | 3.90 |
| DEVICE-1 | DEVICE-9 | 16 | 2.05% | 11 ms | 3.94 |
| DEVICE-2 | DEVICE-9 | 17 | 1.97% | 14 ms | 3.94 |
| DEVICE-3 | DEVICE-7 | 2 | 1.83% | 5 ms | 3.90 |
| DEVICE-4 | DEVICE-2 | 2 | 1.67% | 10 ms | 3.90 |
| DEVICE-3 | DEVICE-9 | 17 | 1.62% | 12 ms | 3.94 |
| DEVICE-7 | DEVICE-4 | 1 | 0.11% | 4 ms | 3.90 |
| DEVICE-8 | DEVICE-4 | 2 | 0.11% | 4 ms | 3.90 |
| DEVICE-8 | DEVICE-6 | 1 | 0.11% | 10 ms | 3.90 |
| DEVICE-8 | DEVICE-7 | 2 | 0.11% | 10 ms | 3.92 |
| DEVICE-4 | DEVICE-10 | 16 | 0.09% | 11 ms | 3.96 |
| DEVICE-5 | DEVICE-10 | 18 | 0.08% | 8 ms | 3.96 |
Records not joined
CMRs with no single CDR (2)
| Written | Device | Extension | Reason |
|---|---|---|---|
| 2026-09-20 17:41 | DEVICE-5 | DN-5 | no CDR carries its key |
| 2026-09-20 17:51 | DEVICE-8 | DN-8 | no CDR carries its key |
CDRs with no CMR (7)
Only some endpoints write CMRs, so a call between endpoints that write none has no quality record.
| Started | Calling | Called | Originating device | Terminating device | CDR file |
|---|---|---|---|---|---|
| 2026-09-14 10:10 | DN-39 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-15 11:11 | DN-41 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-16 12:12 | DN-42 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-17 13:13 | DN-10 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-18 14:14 | DN-43 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-19 15:15 | DN-44 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
| 2026-09-20 10:16 | DN-33 | DN-40 | DEVICE-10 | DEVICE-11 | CDR file 1 |
Calls with more CMRs than established (1)
More than 2 CMRs on one CDR. The knowledge base documents more when an SCCP call is held and resumed; this file does not say whether a call was held. These calls are still joined above.
| Started | Originating device | Terminating device | CMRs |
|---|---|---|---|
| 2026-09-17 14:55 | DEVICE-2 | DEVICE-8 | 3 |
Not established
- Which leg of a call a CMR belongs to is not established in the knowledge base. A CMR is not matched to the originating or terminating side, and when several CDRs share its key it is reported as unmatched rather than assigned to one of them.
By hour of day
Local hour, all selected dates combined. Records with no readable dateTimeStamp are not shown here.
| By hour of day | Records | Median jitter | 95th-pct latency | Loss | Median MLQKav |
|---|---|---|---|---|---|
| 09:00 | 32 | 5 ms | 92 ms | 1.78% | 3.90 |
| 10:00 | 14 | 13 ms | 95 ms | 1.91% | 3.94 |
| 11:00 | 19 | 9 ms | 95 ms | 0.39% | 3.98 |
| 12:00 | 18 | 5 ms | 46 ms | 0.06% | 3.92 |
| 13:00 | 17 | 14 ms | 101 ms | 1.28% | 3.98 |
| 14:00 | 35 | 10 ms | 92 ms | 1.13% | 3.92 |
| 15:00 | 17 | 6 ms | 95 ms | 1.24% | 3.94 |
| 16:00 | 16 | 14 ms | 49 ms | 0.06% | 3.98 |
| 17:00 | 19 | 12 ms | 46 ms | 0.07% | 3.94 |
| 18:00 | 17 | 8 ms | 95 ms | 1.41% | 3.96 |
By day
Local date. Records with no readable dateTimeStamp are not shown here.
| By day | Records | Median jitter | 95th-pct latency | Loss | Median MLQKav |
|---|---|---|---|---|---|
| 2026-09-14 | 28 | 11 ms | 98 ms | 1.34% | 3.94 |
| 2026-09-15 | 29 | 10 ms | 49 ms | 0.29% | 3.94 |
| 2026-09-16 | 29 | 11 ms | 92 ms | 1.30% | 3.94 |
| 2026-09-17 | 30 | 11 ms | 95 ms | 1.02% | 3.94 |
| 2026-09-18 | 29 | 11 ms | 92 ms | 0.86% | 3.94 |
| 2026-09-19 | 28 | 9 ms | 92 ms | 1.13% | 3.94 |
| 2026-09-20 | 31 | 12 ms | 92 ms | 1.00% | 3.94 |
By extension partition
directoryNumberPartition (or directoryNumPartition), where the file populates it.
| By extension partition | Records | Median jitter | 95th-pct latency | Loss | Median MLQKav |
|---|---|---|---|---|---|
| WT-CHI | 76 | 9 ms | 49 ms | 0.07% | 3.94 |
| WT-DAL | 76 | 14 ms | 95 ms | 2.47% | 3.92 |
| WT-PHX | 52 | 10 ms | 47 ms | 0.06% | 3.96 |
Coverage
- FICTIONAL SAMPLE DATA — generated without customer records or bearer tokens.
- This file has 48 columns, consistent with CUCM release 14 or 15.
- This file spells the extension column "directoryNumber" and its partition "directoryNumberPartition".
- 8 records carry video metrics, not read past presence.
- 7 records carry headset metrics, not read past presence.
- 10 records carry local or remote session identifiers, not read past presence.
- A CMR is written when a device involved in a call goes on-hook: an IP phone or an MGCP gateway. A call can have more than one CMR — one per device, more when an SCCP call is held and resumed — so a row is one device’s view of one call’s media, never a call by itself.
- A row whose numberPacketsReceived is 0 or unreadable received no media. It is excluded from jitter, latency and loss statistics and counted separately as no media received.
- Loss is numberPacketsLost divided by numberPacketsReceived plus numberPacketsLost, reported as unknown when that sum is 0.
- A row with an empty varVQMetrics cell, or no numeric MLQKav inside it, is counted as no voice-quality metrics rather than scored.
- MLQK and MLQKav are Cisco’s Mean Listening Quality K-factor, computed by the phone or gateway itself and read out of the varVQMetrics cell; this file carries no separate MOS column.
- Video, headset (SN, Metrics) and session-identifier (localSessionID, remoteSessionID) columns are read only to say whether a row carries them. Their values are not carried into this report.
- A file that mixes a second header line, or a row whose cdrRecordType is not 2, partway through is refused rather than partly read: the export may hold both CDR and CMR rows together, and this reader does not guess which rows are which.
- FICTIONAL SAMPLE DATA — generated without customer records or bearer tokens.
Definitions
- Quality record
- One CMR row: one device’s view of one call’s media, not a call.
- Loss
- numberPacketsLost / (numberPacketsReceived + numberPacketsLost), pooled across scored records for a tile or a bucket; unknown when that denominator is 0.
- Scored for loss
- numberPacketsReceived is greater than 0: the record recorded some media.
- MLQK / MLQKav
- Cisco’s Mean Listening Quality K-factor, read out of the varVQMetrics cell. This file has no separate MOS column.
- No media received
- numberPacketsReceived is 0 or unreadable. Excluded from jitter, latency and loss statistics; counted separately.
- No voice-quality metrics
- varVQMetrics is empty, or carries no numeric MLQKav. Excluded from the MLQKav measures; counted separately.
- Percentiles
- Nearest-rank percentile of known values. Missing values are excluded and the contributing count is printed beside the result.
- Device ranking
- The 95th percentile of a device’s own scored-record loss values, worst first. A device with fewer than 5 scored records is listed separately rather than ranked.
- CMR
- Written by an IP phone or an MGCP gateway when it goes on-hook. A call can have more than one CMR.
- CUCM version family
- Inferred from the column count: 44 columns is release 12.5(1); 48 is release 14 or 15. This file: 48 columns, release 14 or 15.
- Method version
- WT-REPORT-1.1; deterministic calculations; no language-model processing.
- Join key
- A CMR belongs to the CDR with the same globalCallID_callManagerId and globalCallId_callId. Knowledge base: cucm-call-management-records-global-call-id-join, cucm-call-management-records-example-two-cmrs.
- CMRs per CDR
- More than one CMR can exist for one CDR. Knowledge base: cucmcdr-more-than-one-cmr-can-exist-per-cdr, cucmcdr-cdr-and-cmr-are-different-records. At most 2 for one call. Knowledge base: cucm-call-management-records-up-to-two-per-call. More when an SCCP call is held and resumed. Knowledge base: cucm-call-management-records-sccp-hold-resume.
- CMR side
- Not established. A CMR is not placed on either side of its call.