Skip to main content

Cisco CUCM QoS: MOS, Conceal Ratios, and VoIP Detective Call Quality Reporting

Call quality is critical in any Cisco Unified Communications environment. Understanding the metrics that affect voice performance — including MOS, concealment ratios, jitter, latency, and packet loss — is essential for UC engineers.
This article explains how Cisco phones report call quality, why these metrics matter, and how VoIP Detective enhances troubleshooting with rich CMR reporting — including its powerful Network Quality Search feature.

What Is QoS (Quality of Service)?

Quality of Service (QoS) refers to the policies and techniques used to ensure predictable, high-quality audio in a VoIP environment.
QoS prioritizes voice traffic across the network so that voice packets arrive on time, in order, and without loss.
The most common QoS-impacting issues in Cisco environments include:

  • Jitter – Variation in packet arrival time, often caused by congestion.
  • Latency – Delay between sending and receiving audio packets.
  • Packet Loss – Missing audio packets, resulting in choppy sound or gaps.

Cisco phones generate metrics to help quantify these factors. Older models, such as the 7900 series, report MOS (Mean Opinion Score), while newer phones, like the 8800 series, report concealment metrics.

MOS (Mean Opinion Score): The Legacy Cisco Metric

Before newer QoS scoring methods existed, Cisco phones (notably the 7900 series) used the Mean Opinion Score (MOS) to represent call quality.
MOS ranges from 1 (poor) to 5 (excellent), representing a user’s perceived audio quality.

Below are screenshots from VoIP Detective, looking at the call quality data as reported by some older model phones – 7900 series and an ATA. You will notice that various MOS scores are reported.

While MOS worked well historically, it was not always precise for modern codecs like Opus or advanced concealment techniques. Cisco eventually introduced a more accurate measurement system.

Conceal Ratio: The New Standard for Cisco Call Quality

Newer Cisco phones — including the 8800 and 7800 series — emphasize metrics like Conceal Ratio over legacy MOS scores (though some models, like the 8800 series, may still report MOS alongside these). They report metrics like:

  • Conceal Ratio – Percentage of audio frames that required reconstruction due to packet loss (often including cumulative, interval, and maximum values).
  • Jitter
  • Latency
  • Packet Loss

Beyond basic MOS, Cisco also uses a K‑Factor algorithm to estimate what’s called ‘MOS LQK,’ and it’s tightly correlated to concealment metrics.

MOS LQK, K-Factor, and How Cisco Estimates Audio Quality

Newer Cisco endpoints no longer generate a simple MOS score like older 7900-series phones.
Instead, they use a more modern method based on the K-Factor, which estimates audio quality using a perceptual model. In CMRs, this appears as MOS LQK (Listening Quality – K-Factor). It represents how “good” the audio likely sounded to the user over the past few seconds.

Because MOS LQK reacts slowly, Cisco also provides concealment metrics that measure real packet-loss recovery in real time:

  • CCR – overall concealment during the call
  • ICR – concealment measured in 3-second intervals
  • SCS – “severely concealed” seconds, meaning audio was likely distorted

These metrics often reveal problems before MOS LQK drops.

VoIP Detective displays both MOS LQK and conceal ratios, giving engineers a clearer view of real-world quality than MOS alone. More information on K-Factor and MOS LQK is available here.

Below are more screenshots from VoIP Detective, looking at the call quality data reported by newer phones. Here you can see that MOS is de-emphasized, in favor of various conceal ratios.

A high Conceal Ratio indicates the phone is frequently repairing missing or late packets — a strong sign of poor network performance.
Even though end users may not always notice concealment, the Conceal Ratio gives engineers detailed visibility into network degradation.

Codec Influence and Practical Call-Quality Thresholds

Different codecs handle impairment differently. For example, G.711 has a higher “perfect-quality” MOS baseline than compressed codecs like G.729. Wideband codecs (Opus, iSAC, etc.) may also conceal loss more effectively, which is why conceal metrics are usually more reliable than MOS when diagnosing issues.

Here are simple thresholds voice engineers commonly use:

  • CCR (Cumlative Conceal Ratio) < 2% → excellent 2–5% → minor impairment > 5% → noticeable degradation
  • ICR (Interval Conceal Ratio) spikes above ~8–10% → burst loss or jitter
  • SCS (Severly Conceal Ratio) greater than a few seconds → audible distortion
  • MOS LQK
    ≥ 4.2 (G.711) → very good
    Low minimum values → brief but severe impairment

Comparison of Cisco IP Phone Series Call Quality Metrics

Here’s a comparison of how different Cisco IP phone series report key call quality metrics in CUCM environments, including MOS and Conceal Ratio variations. This helps UC engineers understand differences in troubleshooting data from CMR records.

Phone Model Primary Metric Reported Values Example Issues Detected
6900 Series MOS 1 (poor) to 5 (excellent) General perceived quality; less precise for modern codecs like Opus
7900 Series MOS 1 (poor) to 5 (excellent) General perceived quality; less precise for modern codecs like Opus
8900 Series MOS + Conceal Ratio MOS 1-5; Cumulative %, Interval %, Max %; Jitter, Latency, Packet Loss Combines legacy MOS with detailed concealment for transitional environments
9900 Series MOS (K-factor) MOS LQK 1-5 averages/min/max; some concealment metrics Advanced MOS estimation for high-end models; detects frame loss effectively
7800 Series Conceal Ratio Cumulative %, Interval %, Max %; Jitter, Latency, Packet Loss High % indicates packet repairs (e.g., >5% = poor network); no MOS
8800 Series Conceal Ratio (emphasis) + MOS (optional) Same as above + MOS averages/min/max Detailed degradation visibility; combines legacy and new for mixed environments
9800 Series Conceal Ratio (emphasis) + MOS (for supported codecs) Cumulative %, Interval %, Max %; Jitter, Latency, Packet Loss; MOS 1-5 (e.g., min 4.1 for G.711) AI-enhanced audio quality detection; identifies noise, packet issues in modern SIP/CUCM setups

CUCM, CMR Data, and Why Reporting Matters

In additional to CDR files (more information on those here), Cisco CUCM generates CMR (Call Management Records) that contain all call quality metrics. CUCM’s CMR records are essential for analysis; explore the Cisco Unified Communications Manager Call Detail Records Administration Guide for raw data formats and troubleshooting tips.
Whether your phones report MOS or Conceal Ratios, the CMR files contain the raw data required for:

  • troubleshooting one-way audio, choppy calls, and dropouts,
  • identifying network segments with performance issues,
  • tracking jitter, latency, and packet loss trends,
  • verifying QoS is working correctly end-to-end.

But reviewing CMR files manually — or using default CUCM tools — is tedious and time-consuming.
This is where an advanced reporting solution adds tremendous value.

How VoIP Detective Improves CUCM Call Quality Reporting

VoIP Detective reads and processes the CMR data generated by CUCM and transforms it into intuitive, actionable reports.
Designed specifically for Cisco voice environments, VoIP Detective makes it easy for voice engineers to analyze call quality across MOS, Conceal Ratios, jitter, latency, and packet loss.

Powerful Call Quality Dashboards

VoIP Detective automatically interprets MOS and Conceal Ratio metrics, presenting:

  • all possible metrics for each logged call,
  • endpoints experiencing poor quality,
  • search by quality metric.

This allows engineers to quickly identify patterns and root causes that would be missed using CUCM alone.

The VoIP Detective Network Quality Search

One of the most powerful tools in VoIP Detective is the Network Quality Search, which allows administrators to search calls based on specific QoS thresholds.
You can filter calls by:

  • Jitter (e.g., show calls with jitter above 30 ms)
  • Latency (e.g., show calls with latency over 150 ms)
  • Packet Loss (e.g., show calls with more than 2% loss)

This gives engineers a laser-focused view of all problematic calls in their system, making it far easier to track down:

  • QoS misconfigurations,
  • WAN congestion,
  • local network bottlenecks,
  • faulty switches, APs, or cabling.

No other CUCM reporting tool combines MOS, Conceal Ratio, and QoS searching as effectively.

Why VoIP Detective Should Be Part of Every Cisco Voice Deployment

If your environment includes a mix of legacy Cisco phones that report MOS and modern phones that report Conceal Ratios, you need a tool that can normalize and interpret both.
VoIP Detective gives UC teams the visibility they need to maintain high call quality, troubleshoot faster, and gain full insight into jitter, latency, packet loss, and overall network performance.

For organizations running CUCM, VoIP Detective is the most complete, engineer-friendly call reporting tool available today.

Call Reporting for Call Center Managers

Call reporting for Call Center Managers

As the manager of a call center, you understand the importance of maintaining a high level of customer service. To achieve this, you need to monitor your call traffic and ensure that your agents are providing the best possible experience to your customers. This is where call reporting software comes in. In this article, we will discuss how VoIP Detective can help you as the manager of a call center that uses Cisco CallManager.

VoIP Detective is a comprehensive call reporting software that integrates seamlessly with Cisco CallManager. It provides advanced call reporting features that enable you to track, analyze, and optimize your call center operations. With VoIP Detective, you can gain insights into your call center’s performance and make data-driven decisions to improve your overall customer service.
Let’s take a closer look at how VoIP Detective can help you as a call center manager.

1. Accurate Call Reporting
VoIP Detective provides accurate call reporting that enables you to track every call that comes into your call center. You can view detailed information about each call, including the caller ID, call duration, call time, and call type. This information can help you identify trends and patterns in your call center’s performance and make adjustments accordingly.

2. Real-Time Call Monitoring via Wallboard
VoIP Detective offers what we call a “Wallboard”, which can show you in a single window, the number of calls on hold, the number of agents talking, those that are idle, and more. By integrating directly with your Cisco UCCX call center, VoIP Detective can give you full visibility.

3. Historical Reporting
In addition to real-time reporting, VoIP Detective also provides historical reporting capabilities. This allows you to analyze your call data over a period of time, giving you insights into trends and patterns. With VoIP Detective, you can view reports on call volume, call duration, agent performance, and more. This information can help you identify areas for improvement and make data-driven decisions to optimize your call center’s performance.

4. Agent Performance Monitoring
VoIP Detective also provides agent performance monitoring capabilities. This allows you to track how your agents are performing and identify any areas where they may need additional training or support. With VoIP Detective, you can view reports on agent activity, such as call volume, call duration, and call handling time. You can also monitor call quality to ensure that your agents are providing the best possible service to your customers.

In conclusion, VoIP Detective is an essential tool for call centers that use Cisco Callmanager. Its real-time and historical reporting capabilities, agent performance monitoring, and wallboard features make it the perfect solution for managers who want to optimize their call center’s performance and provide the best possible service to their customers. If you’re looking for a call reporting software that can help you take your call center to the next level, VoIP Detective is the solution you’ve been searching for.

Easily perform packet captures, pull CUCM traces, and gather SIP logs using the Cisco RTMT

Easily perform packet captures, pull CUCM traces, and gather SIP logs using the Cisco RTMT

Generating logs for CUCM, SIP, or networking in general can be hard

Often when working with Cisco TAC (support) you’ll be asked to “pull trace logs” or perform a “packet capture”. This can often mean setting up a device that can capture packets on each end of the conversation, and actually capturing the ones and zeros between each endpoint (starting and stopping the capture at the same time on each end). This process can be quite frustrating, as you’ll usually need to have two devices built to do the capturing, and you’ll have to configure some network switchports to mirror the traffic (i.e. copy packets going to a phone or gateway to the packet capture device). Luckily, there is a better way.

Read More

Cisco Call Termination Cause Codes, Values and Descriptions

Cisco Call Manager’s main purpose is to route calls from one endpoint to another, usually called the originating device to the destination device. While doing this there are practically an unlimited amount of things that could go wrong. Cisco decided to use what they call a “call termination value” to explain what the issue was. This value is typically numeric, and refers to a preassigned value.

These codes are typically seen in CDRs (Call Detail Records) that are produced by CUCM. CUCM produces CDRs so that they can be read by analytic software (like VoIP Detective), to ultimately produce human readable reports. Read more about Cisco CDRs here.

oriCause_value

This means that the cause code was produced by the originating side. The originating side could refer to a phone that started the call, or the gateway that first received an inbound call (among other things).

destCause_value

This means that the cause code was produced by the destination side. The destination side could refer to a phone that received the call, or the gateway that received an outbound call (among other things). An example would be a destCause_value of

Below is the complete list of cause code values, and where appropriate, I’ve given some explanation as to the meaning.
Read More

Reading and Understanding CUCM CDR files

Reading and Understanding CUCM CDR files

CDR files – an overview

Cisco’s Unified Communications Manager (CUCM) is build to allow third party applications to provide call reports. This means that Call Manager will provide raw call logs, called CDRs (Call Detail Records) to whatever destination the engineer specifies. In fact, you can have up to three report destinations defined in Call Manager, allowing for multiple call reporting servers. Once you specify the address of your call reporting server inside of CUCM, it will begin pushing CDR files to that server. I believe it’s also important to mention that you can use the CDR Analysis and Reporting (CAR) to extract CDR files from CUCM. This will allow you to either manually review the CDR, or to manually feed it to a reporting / analyzing program.

Read More