Saltar al contenido
Glosario November 2026 6 lectura de minutos

What Is Post-Dial Delay (PDD)?

Post-dial delay (PDD) is the wait between dialling and the first sign a call is progressing, such as ringing. See how SIP measures it and why it matters.

D
November 2026
Última actualización

Respuesta rápida

Post-dial delay (PDD) is the time between the end of dialling and the first indication of what is happening to the call, such as ringing. In SIP, RFC 6076 measures the equivalent, Session Request Delay, from the INVITE to the first provisional response other than 100 Trying, and says it is similar to the post-selection delay in ITU-T E.721.

Post-dial delay is the silence after you dial. A caller presses call and for some number of seconds hears nothing before the line starts to ring. For a person it is an irritation. For a dialer placing thousands of calls it is a measurable property of every route, and a change in it is worth noticing: RFC 6076 says a change in the delay measured on failed setups might indicate problems in downstream signalling functions.

The Definition

ITU-T E.600 defines post-dialling delay as the time interval between the end of dialling by the user and the reception by the user of the appropriate tone or recorded announcement, or the abandon of the call without tone. It adds that on ISDN the equivalent is called post-selection delay, measured until the first message indicating call disposition is received, which is an alerting message when the call is successful.

For SIP, RFC 6076 defines the Session Request Delay (SRD). For a successful setup it runs from the first bit of the initial INVITE to the last bit of the first provisional response. That is usually a response other than 100 Trying; in some cases a 200 is the first status message received, and then the 200 is used. For a failed setup it ends at the first provisional response or at a failure response, which the RFC describes as a 4XX (other than the 401, 402 and 407 challenge codes), a 5XX or possibly a 6XX. RFC 6076 says SRD is similar to the post-selection delay defined in ITU-T E.721, that it is measured at the originating user agent, that it is reported in seconds, and that successful and failed setup delays must not be combined into one figure.

Cómo funciona

  1. The dialer sends an INVITE toward the carrier.
  2. The carrier answers with 100 Trying, which RFC 6076 does not treat as the stop of the clock.
  3. The call progresses through the network. The first meaningful sign, usually a provisional response such as 180 Ringing, stops the clock.
  4. The time in between is the delay.

An Example

This is an illustration with invented numbers. A route returns ringing 2.5 seconds after the INVITE on most calls. After a carrier change the same destinations return ringing after 7 seconds. Nothing is "down", calls still connect, but each call now ties up a line for longer before anyone can answer. Reported separately for successful and failed attempts, as RFC 6076 requires, the change is easy to see. Averaged together with fast failures, it can disappear.

Why It Matters for Outbound and Inbound Teams

Delay adds time to every call, and across a large campaign time is the resource a marcador predictivo exists to use well: every second a line spends in setup is a second it is not in a conversation. The delay is a property of the route and carrier, not of the dialer, which is why carrier quality is worth watching in its own right. DialerBee's BYOC trunk monitoring includes post-dial delay alongside ASR, average call duration and estimated MOS per trunk, and a trunk that falls below your configured quality threshold can fail over to a backup carrier.

It also connects to abandonment. When a dialer has dialed ahead of agent availability, an answered call that finds no agent free is an abandoned call. Unusual setup times on a route are worth investigating alongside any pacing settings. The Guía de ajuste del marcador predictivo covers the settings side. For the carrier-side basics, see Troncal SIP.

Measuring It Sensibly

  • Report successful and failed setups separately. RFC 6076 says not to combine them.
  • Segment by destination and carrier. A route-level problem hides inside an all-traffic average.
  • Use percentiles as well as averages. A few very slow setups matter to the people who experience them.
  • Know where the clock stops. A tool that stops at 100 Trying measures something different from one that stops at ringing.

Preguntas frecuentes

What is a normal post-dial delay?

There is no universal figure, because it depends on the route, destination and network. Measure your own baseline per carrier and destination and watch for changes from it.

What stops the clock in SIP post-dial delay?

Per RFC 6076, the clock stops at the first provisional response other than 100 Trying, typically ringing. If a 200 is the first status message received, the 200 is used. For failed attempts it stops at the first provisional response or a failure final response.

Is PDD the same as call setup time?

They are closely related but not identical. Post-dial delay stops at the first progress indication such as ringing, not when the call is answered. Always check where a tool stops its clock.

Why must successful and failed PDD be reported separately?

RFC 6076 says they must not be combined. Failed attempts often return quickly and would pull an average down, hiding slow successful setups.

Can a dialer reduce PDD?

Not by itself, since the delay mainly comes from the route and carrier. A dialer can reveal it by monitoring per trunk and can route around a slow carrier where multi-carrier routing is configured.

Related terms and guides: Troncal SIP, marcador predictivo, tasa de abandono, Guía de ajuste del marcador predictivo.

Fuentes

Lecturas relacionadas: Códigos de error SIP en llamadas salientes: 403, 486, 503 y más · Answer Seizure Ratio (ASR) · Network Effectiveness Ratio (NER)

Términos relacionados

¿Listo para ver DialerBee en acción?

Solicite una demostración en vivo de 15 minutos o comience una prueba gratuita de 14 días: sin presentaciones, sin compromiso. Las llamadas empiezan en cuanto su propia troncal SIP o PBX está conectada y aprobada.

Prueba gratuita de 14 días · crédito de IA gratuito · sin tarjeta · 11 idiomas · BYOC · controles que apoyan el cumplimiento

Ver el sitio completo en inglés →