[cisco-voip] Another CDR question :)

[Philip Walenta]

I don't think it was connecting to an agent that got the CONNECT message to
appear, at least not for me.  

I remember going through this many times because if someone had called one
of these IVR's, and another call came in, the couldn't get that call because
the phone still thought it was in call proceed or similar state that doesn't
allow the "hold" and "answer" softkeys to come up.

Many IVR's (airlines in particular) don't send a CONNECT until they know
you're going to actually use the IVR (press a key etc) and thusly save
themselves money because the billing on the call doesn't start until the
phone company sees a CONNECT message.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voll, Scott
Sent: Thursday, February 09, 2006 10:10 AM
To: Ryan Ratliff; Ed Leatherman
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Another CDR question :)

Is there any way to fix that?

I have multiple issues with a PBX integration that it doesn't send DTMF
without the Connect message.  Any way to push the connect through?

Thanks

Scott

PS.  Thanks Ed for letting me high jack your thread. ;-)

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Wednesday, February 08, 2006 7:39 AM
To: Ed Leatherman
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Another CDR question :)

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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip