Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CDR - Showing Calls lasting 10 hours - Why? 2

Status
Not open for further replies.

discomonkfish

Technical User
Sep 2, 2003
50
GB
I have a Definity G3Si V4 which is showing some calls that are lasting 10 hours on our call logger. I have looked back to see if someone had changed the date or time but no joy. Any ideas why this would happen?
 
discomonkfish
I've had this problem in the past. First check to see if the station is a modem and it's stuck. My own modem was connected to a PBX for 3 WEEKS. If it's not a stuck modem the call logger might have missed the disconnect message.

Hope this helps
ED

1a2 to ip I seen it all
 
Thanks....its a data module..the extension in question is an analogue extension in a hotel.
 
I've had this problem too and it happens when there is some type of glitch in the system. My CDR always shows 10 hours and like 32 minutes for 3-4 calls per month. I called the CDR Vendor and they said it's something going on in the switch that happens from time to time but I haven't been able to figure out why. Since it's so rare I've just been tolerating it.
 
The Avaya CDR format time/duration stamp has positions for hour and minute of call hour, minutes, and tenths of duration in the format of HHMMHMMT. If a call exceeds 9 hours 59 minutes and 9 tenths (or 9 horus 99 minutes and 9 thenths, I forget which) the PBX issues a call record of HHMM9999 or HHMM95999 for the call duration up to that point, and then an additional call for the 'balance' of the call duration until the end of the call. The call accounting is expected to be able to add them together for the actual duration, but many do not. If the call extends for more than one 10 hour period, you will have multiple 9999 duration records, and the one 'ending' record.

This is usually caused by a hung trunk of some kind--caller dials outside number, gets autoattending, decides to abandon call, hookswitches, dials internal extension and hangs up. The trunk is is on-hold, and the far-end didn't disconnect the trunk.
 
The problem is the hotel room where the phone is is unoccupied. There has been no calls made from the room. I thought it might be because the time may have been reset on the switch or that the recent power cuts they have experienced have caused it?
 
Veramark - DNT tech support explained to me this happens sometimes when a call is placed just before midnight and the call continues past midnight. That's at least what I remember them saying. I asked the same question a year or so ago.

Thanks,

Wildcard
 
You are also correct about power failure or date/time change. If there is a call in progress at the time the date/time is changed, you'll get one of those 9999 records, but you should only get one.
 
I thought about the time but it doesn't seem to correlate as some of the calls are throughout the day. Its affecting 2 rooms. I thought it might be the analogue phone not being set to Time / Break recall but one of the phones affected is a digital set.

I also thought it could be what Jgideon posted regarding a trunk that's hanging. Could it be to do with a disconnect setting on the trunk? Calls are routed through a normal trunk with least cost routing on it. (within the route plan digits are inserted before the number).
 
The DEFINITY produces a CDR record when an call is ended.

UNLESS THE CALL DURATION LAST LONGER THEN 36000 SECONDS then a record is produced for the first ten hours of the call. And a separate call record for the time from second 36001 untill the end. And this will continue for every 10 hours untill the call is disconnected.

I had this happen at customer sites were there was toll fraud.

Please let me know if the information that was provided is helpfull.
Edwin Plat
A.K.A. Europe
 
The number dialled is known to the customer so I don't think its toll fraud. But I will check.
 
I had a situation one time where it looked like a station was connected like that. If I recall correctly I busied out the port and then released it and it cleared.
 
There is no way that the 10 hour calls are fraud or actual long calls because it's happened on my station for a call that was like 2 minutes long!
 
We have also had CDR showing calls of multiple 10 hour periods. We noticed the problem only occured when the Conference facility was being used. A single user would initiate an International call to multiple parties and conference them all together. If they then leave the conference, depending on the configuration of your switch, the call can stay in place. If the disconnect request is then not properly received from the network, the trunk port will remain active on the system and not drop the call even though all parties have long gone.
 
we had the problem at a customer that the trunk wasn't released. Phone was on hook but was still generating CDR outputs of 10 hrs.
Difficult to check if it is a Definity problem or provider problem, at least it was very pricy for the customer.

John
 
Does the Definity store its call records somewhere (like a buffer or such like?) or is it all output real time with no history kept on the switch. It would be useful if I could see what the raw data is to find out if it is the switch or the front of house system corrupting the information. Obviously the hotel won't want their FOH system disabling while we attach a printer to it. Thanks guys!
 
The definity has a very small buffer. Depending on your volume it may last for a couple minutes to a couple hours before being overwritten. Don't know what you are using for collecting the cdr output, but if you have the old data you could probably just search through it and see what you can find.
 
Thanks Bobg1, how do I get to the buffer? Do you have the commands I need?
 
If you are already collecting cdr info the buffer will be empty, as the info has already gone out to your cdr device.
If you had a failure on your cdr device, then the system would hold in buffer what should be going out, hopefully giving the device enough time to reset, so once the connection came back up it would dump what it has (which aint much)
So from the original post, you obviously are collecting the info so there would be nothing to find in a buffer.
 
How do I view the buffer (assuming there isn't a CDR device attached)? What are the commands?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top