[VoiceOps] Easy ways to measure PDD
ivan.kovacevic at startelecom.ca
Tue Apr 21 16:02:37 EDT 2015
That's exactly what we do. And the only other twist, since we work with a
lot of dialer traffic, is that the originator may hang up before
180/183/200 come through. So the whole 20-30 second non-connected call may
To operationalize the data and make it actionable, we measure prevalence of
8+second PDD (arbitrary) calls by provider. If it exceeds 20% (also
arbitrary) in any 15 minute interval we flag it, run some examples and send
to the NOC team to investigate/escalate with the provider.
We have just started doing this, and have gone from being driven by
client-reported issues to proactively chasing after providers to fix it…
and we are definitely starting to see some improvements, as well as
The hope is we can further tighten the parameters to keep the offending
calls to sub 10%.
Vice President, Client Services
Star Telecom | www.startelecom.ca | SIP Based Services for Contact Centers
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex
Sent: Tuesday, April 21, 2015 3:51 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] Easy ways to measure PDD
Our practice suggests that it's perfectly safe to measure time difference
between processing of initial INVITE and either (a) non-100 1xx response
(either 183+SDP or 180) or (b) final affirmative answer (2xx).
On 04/21/2015 03:45 PM, Calvin E. wrote:
> Regarding the other discussion of what PDD is in SIP signalling versus
> real human experience, it all depends what you're looking for and how
> you're willing to find it.
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
VoiceOps mailing list
VoiceOps at voiceops.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps