
I thought PDD / Post Dial Delay was the time between the caller dialing and the caller hearing ringback. If that is correct you will *never* get PDD info out of Asterisk. Asterisk only tracks the time between dialing and answer. -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jesse Howard Sent: Tuesday, April 21, 2015 11:10 AM To: Richard Jobson; Peter Beckman Cc: VoiceOps Subject: Re: [VoiceOps] Easy ways to measure PDD Isn't this exactly what the timeout option in the dial command is for on Asterisk? You can both limit the maximum PDD and route advance/alert directly from your dialplan. To be honest, ASR and ACD have always been more telling from trending perspectives than PDD where I only care about PDD when it is overly long. What it was before the current delay is usually irrelevant for the most part especially since PDD tends to manifest for specific routes vs. the carrier in general. Jesse ________________________________________ From: Richard Jobson [richard at teraquant.com] Sent: Monday, April 20, 2015 11:16 PM To: Peter Beckman Cc: Calvin E.; VoiceOps Subject: Re: [VoiceOps] Easy ways to measure PDD Well if it needs to be real-time, it is not really a CDR function. Oracles Palladion/COM can do it out of the box. But there again you need to install a box. You can install it on VME. It will send you an SNMP trap or email in real-time as soon as the minute average KPI (e.g. PDD) is exceeded per trunk. And Oracle has a reseller who can make Palladion sing for its supper :) On 4/20/15, 5:02 PM, "Peter Beckman" <beckman at angryox.com> wrote:
On Mon, 20 Apr 2015, Richard Jobson wrote:
Do you have an SBC or switch that already measures this and outputs it with the CDR?
Nope.
Do you want to report on all PDD long-term? Or just one or two specific calls?
Long term. A handful of Asterisk servers. Looking for what Calvin E. suggested, except a tool that someone has already written. I can do what Calvin suggests, but interpreted scripts are no match for C compiled packet matching.
What Calvin suggests is something that would work for a PCAP file processed after the fact. I'm looking for something that would be able to catch the non-100 response for each INVITE and log it to a file or send a metric. Even if it has to wake up and parse a 80MB+ pcap file each run to find the PDD per Call-ID, then determine if that Call-ID has been reported. Lots of caching of data... it can be done, but speed is important and a scripting language is quick and dirty but unlikely to be fast and reliable.
Does Asterisk support logging or emitting metrics like PDD?
When a carrier jumps from <1 second Post Dial Delay to 20+ seconds Post Dial Delay I need (a) to know about it and (b) be able to demote them in my LCR in an automated fashion temporarily so I don't need to wake up and take care of my customers.
Beckman -------------------------------------------------------------------------- - Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ -------------------------------------------------------------------------- -
________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops