Administrators can monitor the quality of customer calls by using a set of metrics. This monitoring helps administrators identify and fix network issues (e.g., congestion) and analyze how these changes to network configuration affect call quality. As a result, service providers and resellers can ensure that the quality of service they provide meets the requirements defined in their customers’ SLAs (Service Level Agreements).

Call quality is determined by these metrics:

  • Delay – the delay in voice packet delivery from source to destination;
  • Jitter – the variability in time it takes for voice packets to reach their destination;
  • Packet loss – the number of voice packets not received by the destination;
  • MOS (Mean Opinion Score) – the average rating of voice quality on a scale from 1 to 5, where 5 indicates the highest quality.

PortaSIP collects metrics during or at the end of customers’ calls. This depends on their phone configurations. PortaBilling analyzes the collected data and determines the call status: good, fair or poor. An administrator sees the call status in the customer’s xDRs. Call quality details for the call participants are available in the xDR details.

Let’s have a closer look at how it works.

Metrics collection

Link copied to clipboard

Call quality values are sent in RTCP (Real-Time Transport Control Protocol) messages:

  • receiver reports (RTCP RR), and
  • extended reports (RTCP XR).

RTCP XR reports contain a wider set of quality parameters (e.g., packet loss rate, delay, MOS, etc.). However, user phones must support RTCP XR reports according to RFC 3611 and be configured to send them.

RTCP collection flow

When a call is authorized, PortaBilling checks whether call quality monitoring is enabled for the customers (or customer sites) involved in the call. If at least one party has monitoring enabled, PortaSIP collects quality reports from both parties.

After a call is established, the user phones exchange media streams via the RTPProxy. They also send RTCP RR/RTCP XR reports to the RTPProxy, which forwards them to the Call quality tracker. This PortaSIP component retrieves and aggregates the metric values from the RTCP RR/RTCP XR messages, and records them in the database.

User phones can also send aggregated call quality values at the end of the call if they support call quality summary reports in accordance with RFC 6035.  PortaSIP receives these reports in PUBLISH messages for all calls and forwards them to the Call quality tracker. The tracker uses the summary reports only for calls in which call quality monitoring is enabled for at least one party. It extracts the metrics and records them in the database. Metrics obtained from the summary reports take precedence over those collected from the RTCP RR/RTCP XR reports.

Call status identification

Link copied to clipboard

A call can have a status of good, fair or poor. The criteria for call statuses are defined in call quality profiles. A call quality profile includes thresholds for call quality metrics that describe each call status. An administrator configures a call quality profile and assigns it to customers/customer sites whose call quality they wish to monitor (e.g., business or premium customers). PortaBilling sets call statuses only for customers who have assigned call quality profiles.

quality thresholds definition

To determine the status of calls, PortaBilling retrieves metric values from the Call quality tracker every 10 minutes. PortaBilling matches these metric values against the thresholds defined in the customer’s call quality profile and then assigns a call status based on the worst metric value. The resulting call status is identified by a color-coded marker in the customer’s xDRs:

  • Green for good quality Green for good quality;
  • Yellow for fair quality Yellow for fair quality;
  • Red for poor quality Red for poor quality.
  • No indicator means that either a call quality status has not yet been assigned or the voice quality monitoring was disabled for the customer at the time of call authorization.

call quality details

The administrator can view metric values for call participants in the xDR details. They can also filter xDRs by call quality status for further analysis.

The call quality details are available only if you filter the xDRs by the “Voice calls” service on the Search xDRs panel.

Resellers can configure call quality profiles and receive call quality details for their customers via the API.

Call quality monitoring is supported for calls made within the network, calls to or from external numbers, and complex calls involving call forwarding, call transfer, and call pickup.

With this ability to monitor call quality, administrators can:

  • Analyze current quality and take actions to improve it;
  • Identify network issues and fix them;
  • Analyze how network configuration changes influence call quality;
  • Retrieve call quality statistics via the API to create reports in external systems.

End users receive better service quality due to proactive administrators.

Implementation specifics

Link copied to clipboard
  1. To process call quality metrics from RTCP RR/RTCP XR reports, the media stream between the phones must pass through the RTPProxy. This is not required if the phones send call quality summary reports in SIP PUBLISH messages. PortaSIP receives these summary reports through the Subscription manager.
  2. The Call quality tracker instance is required to process RTCP RR/RTCP XR and call quality summary reports. You can deploy it on any SIP server. The Call quality tracker must reside on the private IP. Only one instance of the Call quality tracker per PortaSIP is allowed.
  3. PortaBilling retrieves metrics from the Call quality tracker every 10 minutes. Therefore, call status is not displayed immediately after call termination.
  4. PortaBilling queries the replica database to show the metrics in the xDR browser. This imposes an additional load on the database.
  5. If an admin enables call quality monitoring during an ongoing call, metrics are not collected for that call.
  6. The call status depends on the settings in effect at the time PortaBilling retrieves the metrics. If the thresholds in a call quality profile are modified, or a different profile is assigned to the customer before the metrics are retrieved, PortaBilling uses the updated settings to determine the call status.
  7. If a customer with call quality monitoring enabled joins an ongoing call (e.g., via attended transfer), PortaSIP starts collecting quality metrics for all call legs from that moment. Metrics for the preceding portion of the call are not available.

Known limitations

Link copied to clipboard

For inter-site calls and for complex calls, such as call forwarding and call transfer, xDRs provide call quality details only for the participant associated with that xDR. To obtain full quality information about a call, review the xDRs for each call participant.

Docs for
What's new
Admin manuals
Handbooks
UI help
Developers documentation
Back to main menu