Post dial delay (PDD) is the silence a caller hears between finishing dialing and the first ring — in SIP, the time from sending the INVITE to receiving the first 180 Ringing or 183 Session Progress. Carriers commonly treat under about seven seconds as acceptable; North American callers notice around five. Predictive dialers feel it worst: pacing assumes consistent setup.
If calls sit in dead air for five seconds before ringing, the cause is often downstream of your PBX — measure at the edge to prove which side owns it. PDD accumulates across every switch and carrier standing between your INVITE and the far handset — which is why the durable fix is route quality, not a config flag.
What counts as normal post dial delay
The industry’s working threshold is surprisingly generous. Telnyx states it plainly: most carriers consider anything under 7 seconds an acceptable amount of PDD, and most will not troubleshoot PDD below that line. Perception varies by geography, too — Twilio notes North American callers typically notice delays around 5 seconds, while regions like South Africa commonly see 10+ seconds without complaint.
A human caller tolerates a few seconds of silence. A dialer floor cannot. Predictive pacing algorithms time their dials against expected call setup, so inconsistent PDD skews the math on every cycle — and the setup delay lands inside metrics like agent wait and abandonment before anyone thinks to blame the route. Matt Florell, the VICIdial project lead, called this out directly in his Astricon call-progress-analysis material: carrier post-dial delay can cause problems for CPA in dialer deployments. If your floor is chasing pacing symptoms, start with the VICIdial troubleshooting guide — and check PDD before retuning campaigns.
How PDD builds hop by hop
No single box “adds the delay.” Call setup is a relay: your switch sends the INVITE, your carrier looks up a route for the destination, each intermediate carrier in that route makes its own routing decision and forwards the request, and the terminating switch finally alerts the handset. Every carrier and network element in that setup path can add time. The more elements a route traverses, the more places delay can enter before ringback ever starts.
The documented causes cluster into a short list:
- Signaling interpretation differences. Destination networks handle SIP setup differently — especially whether ringback is conveyed via 180 Ringing or 183 Session Progress with early media. Mismatches here stretch the silent gap.
- Missing or silent ringback. Some far networks return ring indication late, or return audio that is simply silence — the call is progressing, but the caller hears nothing, which reads as PDD.
- Distance and endpoint type. Geographic distance adds setup time, and non-geographic endpoints — satellite phones being the extreme case — add much more.
- The far end itself. The terminating carrier may not yet have ring indication to pass back, and wireless devices with poor signal are slow to alert at all.
Notice what is not on that list: your codec choice, your audio quality, your bandwidth. Those govern the call after it connects — jitter, latency, and MOS are a separate diagnosis. PDD is purely a signaling-path problem.
How to measure post dial delay in SIP
Pull a packet capture at your own network edge and read two timestamps: when the INVITE left, and when the first 180 Ringing or 183 Session Progress came back. That interval is your PDD. A 100 Trying in between does not stop the clock — it only confirms the next hop received the request; the caller is still sitting in silence until a ringing response arrives.
Measuring at the edge also settles the blame question in one step. If the gap sits between the agent’s dial action and the INVITE actually leaving your server, the delay is inside your own stack — dialplan processing, DNS, or an overloaded box — and no carrier ticket will fix it. If the INVITE leaves promptly and the 180/183 is slow to return, the delay is downstream on the route.
Two readings matter, not one. Average PDD tells you how the route behaves normally; the spread tells you what your dialer is fighting. And know what you are looking at when setup fails outright: an INVITE answered by an error such as 503 Service Unavailable is a failed call, not a slow one — count it separately or it will poison your PDD numbers.
What your PDD numbers say about the route
PDD is one of the few externally visible clues about what a route looks like inside. A carrier terminating traffic over direct routes has few elements in the setup path. A wholesale or least-cost route can pass through several intermediaries, and each one is another routing decision — another place setup time can enter. That is why operators watch PDD when evaluating routes: long and highly variable setup times suggest a longer, more complicated path to the destination.
Read the signal with discipline. High PDD on one destination usually means that route is long or troubled; high PDD across the board means your carrier’s routing generally involves more intermediaries than you are paying to tolerate. Our SIP trunk provider evaluation checklist makes PDD one of its seven questions for exactly this reason: a provider that cannot tell you its PDD numbers is not optimizing them.
How to reduce post dial delay
Ranked from your desk outward:
-
Rule out your own stack first. The edge capture above takes minutes. If the INVITE is slow to leave, fix the local cause and re-measure before opening any ticket.
-
Check early-media and ringback handling. Confirm which ringing response your carrier actually returns per destination — 180 versus 183 with early media — and that your equipment renders ringback for each. Silent progress reads as delay to the caller even when signaling is on time.
-
Escalate with data, not adjectives. Carriers commonly decline to chase PDD under the ~7-second convention, so bring INVITE-to-ringing timestamps, affected destination prefixes, and averages alongside worst cases. Specific evidence gets routing fixes; “calls feel slow” gets a shrug.
-
Fix the structure: route quality. Config changes trim the edges, but the setup path itself sets the floor. Fewer intermediaries means fewer places for delay to enter — which makes carrier choice the structural fix.
SIPNEX sits in that last category, so weigh the bias accordingly: we are an FCC-licensed carrier running dialer traffic every day. Put any provider — us included — on a live trunk and let your own captures decide.
Frequently asked questions
What is an acceptable post dial delay?
Under about seven seconds, by common carrier convention — Telnyx notes most carriers will not troubleshoot PDD below that line. Perception is stricter than policy: North American callers typically notice delay around five seconds. Dialer operations hold a tighter bar still, because pacing algorithms depend on consistent setup times, so they care about the spread of PDD as much as the average.
How do I measure post dial delay in a SIP trace?
Timestamp the INVITE leaving your edge, then the first 180 Ringing or 183 Session Progress returning — that interval is the post dial delay. A 100 Trying does not count; it only acknowledges receipt, and the caller still hears silence. Capture at your own network edge so you can tell local delay (slow INVITE out) from route delay (slow ringing response back).
Does high post dial delay mean a bad route?
It can be — read it as a clue, not a verdict. Every carrier and network element in the setup path can add time, so routes with more intermediaries have more places for delay to enter, and direct routes have fewer. Long, variable PDD on a single destination points at that route; long PDD everywhere points at how your carrier routes in general.
Why does post dial delay hurt dialers more than regular callers?
Because predictive pacing assumes consistent call setup. A human caller shrugs off a few silent seconds; a pacing algorithm dialing against expected setup times misjudges every cycle when PDD swings, and the damage surfaces as abandonment and idle agents. That is why dialer floors measure PDD deliberately — average and spread — instead of waiting for callers to complain.
If setup delay is costing your floor contacts, measure it, then fix the structure: direct routes, monitored PDD, dialer-grade trunks — (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.