[cisco-voip] Another CDR question :)

[Ed Leatherman]

Thanks Ryan, that makes sense! Some of the calls specifically where to an
IVR system, and our long distance provider prompts for a PIN, which will
probably account all of those cases. Will do a bit more poking around on it
but that sounds like the cause.

On 2/8/06, Ryan Ratliff <rratliff at cisco.com> wrote:
>
> Many IVRs will not actually put the call into a Connected state until
> you reach an agent.  Also happens with carriers that ask you for a
> pin when dialing long distance, etc.
>
> I think Amex was one that generated a ton of cases back in the day
> because of dtmf issues when the voice path was established but the
> call wasn't yet connected.
>
> -Ryan
>
> On Feb 8, 2006, at 10:32 AM, Ed Leatherman wrote:
>
> Was looking through some CDRs to dig up some stats on a disputed long
> distance call.. Happened to notice there were a number of calls that
> had a dateTimeOrigination that was normal, a dateTimeConnect which
> was 0, and a dateTimeDisconnect that was normal and anywhere from 3
> to 20 sec later than the Origination Time. Does this mean the call
> failed to connect? duration on all those calls is also 0. the
> dateTimeConnect has me a little puzzled.
>
> --
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network Operations
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060208/5a1adfc0/attachment.html