---
title: "VoIP Route Quality: ASR, ACD, PDD & SIP Codes"
description: Learn how ASR, ACD, PDD, and SIP response codes help assess VoIP route quality by destination, traffic profile, and performance changes.
image: https://www.virtual-call.net/hubfs/AI-Generated%20Media/Images/International%20Voice%20Routing%20Network%20Nodes.png
---

[Skip to content](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#main-content)

- [Become a partner](https://www.virtual-call.net/become-a-partner)
- [My Login](https://my.virtual-call.net)
- [Support](https://support.virtual-call.com)

[![Virtual-Call your Communication Service Provider](https://www.virtual-call.net/hs-fs/hubfs/VC%20Logo/New/vcall_logo_transparent_white_840x252.png?width=840&height=252&name=vcall_logo_transparent_white_840x252.png) ![Virtual-Call your Communication Service Provider](https://www.virtual-call.net/hs-fs/hubfs/VC%20Logo/New/vcall_logo_400x120.jpg?width=400&height=120&name=vcall_logo_400x120.jpg)](https://www.virtual-call.net?hsLang=en)

- [English](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes)
- [Deutsch](https://www.virtual-call.net/de/blog/voip-routenqualitaet-asr-acd-pdd-sip-codes)
- [Português - Brasil](https://www.virtual-call.net/pt-br/blog/asr-voip-acd-pdd-codigos-sip)

- [Home](https://www.virtual-call.net)
- Cloud Products 
    - [Cloud PBX](https://www.virtual-call.com/cloud-pbx)
    - [SIP Trunk](https://www.virtual-call.com/sip-trunking)
    - [MS Teams Direct Routing](https://www.virtual-call.com/microsoft-teams-direct-routing)
- [Wholesale](https://www.virtual-call.com/wholesale)
- [About us](https://www.virtual-call.net/about-us)
- [Blog](https://www.virtual-call.net/blog)

###### 17 min read

# VoIP route quality: how to read ASR, ACD, PDD and SIP response codes

By: [Otto Kolbe](https://www.virtual-call.net/blog/author/otto-kolbe) on  Nov 20, 2026, 12:00:00 AM

[ASR VoIP](https://www.virtual-call.net/blog/tag/asr-voip) [ACD VoIP](https://www.virtual-call.net/blog/tag/acd-voip) [VoIP routes](https://www.virtual-call.net/blog/tag/voip-routes) [PDD VoIP](https://www.virtual-call.net/blog/tag/pdd-voip)

![Featured Image](https://www.virtual-call.net/hubfs/AI-Generated%20Media/Images/International%20Voice%20Routing%20Network%20Nodes.png)

**VoIP route quality cannot be measured by a single successful test call, the lowest rate, or one KPI in isolation. ASR, ACD, PDD, and SIP response codes show different aspects of voice traffic.**

**Analysed together and segmented by destination and traffic profile, they provide a much stronger basis for assessing how a route actually performs.**

A test call may connect quickly and sound clear. That is useful, but it still represents only one call.

For carriers and VoIP providers handling recurring voice traffic, the more useful question is: How does this route behave over time**,** across the destinations that matter to the operation, and under real traffic conditions?

That distinction matters because route performance is multidimensional. ASR helps describe answer behavior. ACD describes the duration of answered calls. PDD provides information about call setup. SIP response codes add signalling context.

The real value comes from reading them together.

For an overview of how calls move between carriers and reach the destination network, read our guide to [how wholesale voice termination works](https://www.virtual-call.net/blog/understanding-how-wholesale-voice-termination-works?hsLang=en).

 

### Content topics

[1. Why price and isolated tests are not enough to evaluate VoIP route quality](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#why-price-and-isolated-tests-are-not-enough)  
[2. Which metrics help you measure VoIP route quality?](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#which-metrics-help-you-measure-voip-route-quality)  
[3. PDD: How long does the call take to progress?](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#pdd-how-long-does-the-call-take-to-progress)  
[4. SIP response codes: add signalling context to the metrics](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#sip-response-codes-add-signalling-context-to-the-m)  
[5. Why one metric alone can lead to the wrong conclusion](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#why-one-metric-alone-can-lead-to-the-wrong-conclus)  
[6. Global average or destination-level analysis?](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#global-average-or-destination-level-analysis)  
[7. A practical framework for evaluating a VoIP route](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#a-practical-framework-for-evaluating-a-voip-route)  
[8. When should you investigate a VoIP route more deeply?](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#when-should-you-investigate-a-voip-route-more-deep)  
[9. VoIP route quality is a pattern, not a single number](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#voip-route-quality-is-a-pattern-not-a-single-numbe)  
[10. FAQ](https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes#faq)

## Why price and isolated tests are not enough to evaluate VoIP route quality

Cost matters in voice termination, particularly as traffic volume grows.

But a low rate does not show whether attempts are being answered as expected, whether call setup behaviour has changed, or whether a problem is concentrated in a particular destination.

A more consistent route assessment considers several dimensions:

- answer behaviour;
- duration of connected calls;
- call setup time;
- SIP signalling responses;
- performance by destination;
- changes over time;
- traffic profile.

Two routes can appear similar at the account level while behaving differently for a particular destination or traffic profile.

This is especially important when operations use different routes for different types of traffic. In Virtual-Call's own operation, call-centre and retail traffic can be directed to separate routes according to traffic profile rather than treated identically.

The principle is simple: One metric shows one aspect of the route. Several related signals reveal a pattern worth investigating.

Once route performance has been assessed, the commercial comparison also needs to reflect the intended traffic. Our guide explains how to [compare wholesale voice costs and negotiate routes](https://www.virtual-call.net/blog/wholesale-voice-costs-compare-negotiate-routes?hsLang=en).

## Which metrics help you measure VoIP route quality?

Four indicators provide a practical starting point:

1. **ASR,** to observe how many call attempts result in an answer;
2. **ACD,** to understand the average duration of answered calls;
3. **PDD,** to observe call setup behaviour;
4. **SIP response codes,** to add signalling context to the outcome.

None should automatically be treated as proof that a route is good or bad.

### ASR: What does the answer rate tell you?

ASR stands for Answer Seizure Ratio.

In simplified form:

ASR = answered calls ÷ call attempts × 100

ASR helps show how frequently attempts in a traffic sample result in an answer.

Suppose two routes serve the same destination with comparable traffic. If one starts showing a significant change in ASR, there is a signal worth investigating.

But a lower ASR does not automatically mean poor route quality.

Calls that are not answered, invalid destinations, recipient behavior, and traffic characteristics can all affect the result. That is why context matters.

Instead of asking only: “What is the ASR of this route?”

a more useful operational question is:

“Has the ASR changed from its normal pattern, and where is that change occurring?”

This turns ASR from a standalone score into a diagnostic signal.

### ACD: What can average call duration tell you?

ACD stands for Average Call Duration.

In simplified form:

ACD = total duration of answered calls ÷ number of answered calls

ACD describes the average duration of calls that were answered.

A meaningful change can justify an investigation. But, as with ASR, the metric needs context.

Low ACD does not automatically prove poor VoIP route quality.

Some traffic profiles naturally create shorter calls. Others generate longer conversations.

Therefore, an ACD result should be interpreted against comparable traffic rather than against an arbitrary number used for every route and destination.

The practical question is:

“Has ACD changed without a corresponding change in traffic behaviour?"

If it has, the route deserves a closer look.

![ASR, ACD, PDD, and SIP codes are used together to evaluate a VoIP route.](https://www.virtual-call.net/hs-fs/hubfs/AI-Generated%20Media/Images/White%20Background%20VoIP%20Metrics%20Infographic%20ASR%20ACD%20PDD%20SIP.png?width=1536&height=1024&name=White%20Background%20VoIP%20Metrics%20Infographic%20ASR%20ACD%20PDD%20SIP.png)

## PDD: How long does the call take to progress?

PDD stands for Post-Dial Delay.

It describes an interval during call setup and helps investigate situations in which an unusual amount of time passes before the caller receives call progress.

A change in PDD becomes particularly useful as a diagnostic signal when:

- It differs from the route's usual behaviour;
- It appears on specific destinations;
- It changes during particular periods;
- Comparable routes show different behaviour.

Here, too, the goal is not to assign a universal score.

It is to identify a meaningful change.

A route that normally behaves consistently and suddenly shows longer call setup on one destination is more informative than an isolated PDD number without historical or destination context.

## SIP response codes: add signalling context to the metrics

ASR, ACD, and PDD summarise behaviour.

SIP response codes help provide context about what happened during signalling.

This matters because two unsuccessful calls do not necessarily fail in the same way.

Consider some patterns an operations team might investigate:

- an unusual increase in 4xx responses;
- an increase in 5xx responses;
- a particular response is becoming more frequent;
- a change concentrated in one network or destination;
- a change in SIP responses occurring alongside a decline in ASR.

A SIP response can therefore help narrow the investigation. But the response by itself should not automatically be used to assign the root cause. For readers who need the protocol fundamentals first, see[What is SIP?](https://www.virtual-call.net/blog/what-is-sip?hsLang=en).

The important distinction is:

A SIP response is evidence from signalling. It is not, by itself, a complete diagnosis.

![SIP response patterns used to investigate changes in VoIP route performance](https://www.virtual-call.net/hs-fs/hubfs/AI-Generated%20Media/Images/Telecom%20B2B%20Infographic%20Investigate%20SIP%20Response%20Patterns.png?width=1536&height=1024&name=Telecom%20B2B%20Infographic%20Investigate%20SIP%20Response%20Patterns.png)

## Why one metric alone can lead to the wrong conclusion

Consider four scenarios.

### Scenario 1: ASR drops on one destination

The overall result has declined. When traffic is segmented, however, the change appears only in one country, network, or number range.

Changing the complete routing strategy before identifying where the problem is concentrated could lead to the wrong decision.

The useful signal is not simply:

“ASR is down.”

It is:

“ASR is down for this specific traffic segment.”

### Scenario 2: PDD increases during a particular period

A daily average may hide temporary changes. Once performance is segmented by time and destination, the issue may become easier to isolate.

Instead of concluding:

“The route is slow.”

The investigation can ask:

“When did call setup behaviour change, and which destinations were affected?”

### Scenario 3: A SIP response becomes more frequent

An unusual increase in a SIP response deserves attention. But that response should be considered alongside call records, destinations, and other signalling information.

The response directs the investigation. It does not replace it.

### Scenario 4: ACD changes with the traffic profile

Suppose ACD declines after a new outbound campaign begins.

Looking only at the average might suggest that route quality has deteriorated.

Looking at the traffic profile may reveal that the new calls are simply shorter by nature.

This leads to one of the most important rules when evaluating VoIP routes: a metric tells you where to look. It does not always tell you why something happened.

## Global average or destination-level analysis?

A global average answers a global question.

That can be exactly the problem.

When an operation distributes traffic across several countries, networks, or prefixes, good performance in high-volume destinations can make a localised change harder to identify.

Where the available data allows it, segment route performance by:

- country;
- destination;
- prefix;
- destination network;
- route;
- period;
- traffic profile.

This allows the operations team to move from:

“Has our VoIP route quality deteriorated?”

to:

“Where, when, and in which traffic segment did behaviour change?”

The second question is far more actionable.

## A practical framework for evaluating a VoIP route

The purpose of monitoring is not to collect more KPIs. It is to create enough context to recognise a significant change and investigate it properly.

### 1. Define the destinations that matter

Start with the countries, networks, or prefixes that account for relevant traffic or are operationally important.

A global average across many destinations may provide less insight than a focused view of the markets that actually matter to the operation.

### 2. Track ASR, ACD, PDD, and SIP responses

Do not select one metric in advance as definitive proof of route quality. Each indicator answers a different question.

### 3. Establish a baseline for comparable traffic

Compare similar destinations, routes, periods, and traffic profiles. The purpose is to understand what normal behaviour looks like for that specific operation.

![Seven-step framework for evaluating VoIP route performance using destinations, ASR, ACD, PDD, SIP responses, segmentation and call evidence](https://www.virtual-call.net/hs-fs/hubfs/AI-Generated%20Media/Images/VoIP%20Route%20Evaluation%20Workflow%20Infographic.png?width=1774&height=887&name=VoIP%20Route%20Evaluation%20Workflow%20Infographic.png)

### 4. Look for changes in behaviour

Signals may include:

- a decline in ASR;
- a material change in ACD;
- increased PDD;
- a different distribution of SIP responses.

Then, investigate where the change is concentrated.

### 5. Segment before drawing conclusions

Separate traffic by destination, network, route, period, and profile whenever the data allows it. This prevents a global average from obscuring a localised problem.

### 6. Collect real call examples

Percentages expose patterns. Specific calls provide evidence.

Record relevant examples with the corresponding destination, time, and signalling information so the abnormal pattern can be examined in context.

### 7. Investigate without assigning the cause too early

A change in route metrics is evidence that behaviour changed. It does not automatically prove where the cause sits.

Keep the diagnosis open until call records, signalling, and specific examples provide enough information.

## When should you investigate a VoIP route more deeply?

A dashboard becomes an investigation when a change is persistent, concentrated, or relevant to the operation.

Examples include:

- answer behaviour changing for one destination;
- PDD changing consistently;
- an unusual distribution of SIP responses;
- ACD changing without a corresponding change in traffic profile;
- specific calls showing unexpected behaviour.

Destination and traffic type matter here.

For example, Virtual-Call distinguishes international wholesale routing from local in-country voice services because regulatory and routing conditions can differ by country.

For international call center traffic, include caller identification and route compatibility in the investigation. Our guide to [international CLI requirements for call center traffic](https://www.virtual-call.net/blog/international-cli-call-center-traffic?hsLang=en).

Similarly, its commercial process requests destinations together with ASR and ACD parameters when assessing voice-termination requirements.<https://outlook.office365.com/owa/?ItemID=AQMkADJhNGEyZTVkLTY5YzAtNDI2ZC1hYzA5LTFjOWJjZTJlMDI5MwBGAAADBFpws%2fQBBEG8%2fwhy2kN0VwcAD%2fcm%2bc1Bs0WWA7IoEW5R0gAAAgEJAAAAD%2fcm%2bc1Bs0WWA7IoEW5R0gAFLaRJ8QAAAA%3d%3d&exvsurl=1&viewmodel=ReadMessageItem>

If a problem is already visible in particular calls, destinations, or signalling responses, the next step is a structured troubleshooting process rather than another generic test call.

 

## VoIP route quality is a pattern, not a single number

ASR, ACD, PDD, and SIP response codes make route behaviour more observable. But none should become an automatic verdict.

A stronger evaluation combines the indicators, compares equivalent traffic, segments the results, and looks for changes against the expected behaviour of that operation.

For teams managing recurring international voice traffic, this changes the question from:

“Did this route work?”

to:

“Does this route consistently deliver the performance our operation needs in the destinations that matter?”

That is a stronger basis for comparing routes, discussing performance with providers, and deciding when deeper investigation is required.

Looking to evaluate a wholesale voice route for your operation? Complete [our contact form](https://www.virtual-call.com/about-us/contact) with your target destinations, expected monthly volume, traffic profile, and current ASR and ACD, if available. The Virtual-Call team can use these details to assess which route options may fit your requirements.

 

## FAQ

1\. What is VoIP route quality? VoIP route quality describes how a voice route behaves across call answering, connected-call duration, call setup, and signalling. It should be evaluated across comparable traffic rather than through one metric alone.

2\. What is ASR in VoIP? ASR stands for Answer Seizure Ratio and expresses answered calls in relation to call attempts. It should be interpreted in the context of comparable destinations and traffic.

3\. Does low ACD mean poor VoIP route quality? Not necessarily. Call duration depends on traffic behaviour and call purpose. ACD becomes more useful when compared with similar traffic and historical behaviour.

4\. What does PDD mean in VoIP? PDD stands for Post-Dial Delay and describes an interval in the call setup process. Changes in PDD can help identify unusual setup behaviour.

5\. How do SIP response codes help evaluate VoIP routes? They add signalling context to call outcomes and help operations teams narrow an investigation when response patterns change.

 

 We connect you to the world! **🌍**

- [Tweet](https://twitter.com/share)

<https://www.virtual-call.net/blog/understanding-how-wholesale-voice-termination-works?hsLang=en>

## [Wholesale voice termination: how it works and what to assess](https://www.virtual-call.net/blog/understanding-how-wholesale-voice-termination-works?hsLang=en)

Wholesale voice termination enables carriers, VoIP operators, and service providers to route voice...

<https://www.virtual-call.net/blog/wholesale-voice-costs-compare-negotiate-routes?hsLang=en>

## [Wholesale voice costs: how to compare and negotiate routes](https://www.virtual-call.net/blog/wholesale-voice-costs-compare-negotiate-routes?hsLang=en)

Comparing wholesale voice costs requires more than placing two per-minute rates side by side. 

<https://www.virtual-call.net/blog/international-cli-call-center-traffic?hsLang=en>

## [International CLI for call center traffic: check before you activate](https://www.virtual-call.net/blog/international-cli-call-center-traffic?hsLang=en)

Your ASR drops, the campaign has not changed, and the upstream route reports filtering. You review...

##### About us

About us

Virtual-Call GmbH is your partner in communication services. Powerful and reliable. Since 2013, Virtual-Call has been providing best-in-class cloud telephony solutions to both domestic and international enterprises. We are proud to offer a wide range of services, including wholesale voice and SMS termination.

##### Products

Products

- [Cloud PBX](https://www.virtual-call.com/cloud-pbx)
- [SIP Trunking](https://www.virtual-call.com/sip-trunking)
- [MS Teams Direct Routing](https://www.virtual-call.com/microsoft-teams-direct-routing)
- [Wholesael Service](https://www.virtual-call.com/wholesale)

##### Company

Company

- [About us](https://www.virtual-call.net/about-us)
- [Contact](https://www.virtual-call.net/contact)
- [Blog](https://www.virtual-call.net/blog)

[![Virtual-Call - your Communication Service Provider](https://www.virtual-call.net/hubfs/vcall_logowithout_globus_transparent_840-x-341-1.png)](https://www.virtual-call.net?hsLang=en)

- [Data protection](https://www.virtual-call.net/data-protection)
- [Imprint](https://www.virtual-call.net/imprint)
- [Terms and Conditions](https://www.virtual-call.net/terms-and-conditions)

© 2026 Virtual-Call GmbH | Stettbachstrasse 6, 8600 Dübendorf, Switzerland

<https://www.linkedin.com/company/virtual-call/>

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Otto Kolbe",
    "url" : "https://www.virtual-call.net/blog/author/otto-kolbe"
  },
  "dateModified" : "2026-11-19T23:00:00.709Z",
  "datePublished" : "2026-11-19T23:00:00.000Z",
  "headline" : "VoIP Route Quality: ASR, ACD, PDD & SIP Codes",
  "image" : [ "https://www.virtual-call.net/hubfs/AI-Generated%20Media/Images/International%20Voice%20Routing%20Network%20Nodes.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.virtual-call.net/blog/voip-route-quality-asr-acd-pdd-sip-codes",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.virtual-call.net/hubfs/vcall_logo_400x120.jpg"
    },
    "name" : "Virtual-Call GmbH"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "VoIP route quality describes how a voice route behaves across call answering, connected-call duration, call setup, and signalling. It should be evaluated across comparable traffic rather than through one metric alone."
    },
    "name" : "What is VoIP route quality?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "ASR stands for Answer Seizure Ratio and expresses answered calls in relation to call attempts. It should be interpreted in the context of comparable destinations and traffic."
    },
    "name" : "What is ASR in VoIP?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Not necessarily. Call duration depends on traffic behaviour and call purpose. ACD becomes more useful when compared with similar traffic and historical behaviour."
    },
    "name" : "Does low ACD mean poor VoIP route quality?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "PDD stands for Post-Dial Delay and describes an interval in the call setup process. Changes in PDD can help identify unusual setup behaviour."
    },
    "name" : "What does PDD mean in VoIP?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "They add signalling context to call outcomes and help operations teams narrow an investigation when response patterns change."
    },
    "name" : "How do SIP response codes help evaluate VoIP routes?"
  } ]
}
```