QueueMetrics forum
QueueMetrics => General Asterisk configuration => Topic started by: smileyphase on October 21, 2010, 15:50:43
-
I'm experiencing an odd issue - we had to briefly change a system clock at one point, and there may be some calls which have not been removed.
The system is not running in DB mode, so I don't think I can clear it from the queue_log table. How should this be cleared?
thx,
SP
-
Do you have such values in the reports or in the realtime screen?
-
It's in the realtime screen
-
Ok so just leave as they are. it may be that some calls that were active wehn you changes the clock may have incorrect timestamps, but they should be a very small number.
-
So it doesn't affect reports?
This is very annoying for everyone to see all the time, is there no way to remove those records?
-
But did you change the clock JUST ONCE or do you change it all the time?
-
Time was changed once, and then changed back. This is not a routine occurence, and has happened a handful of times in the past few years. We can restrict time changes to after-hours.
SP
-
I think this would be a better choice :-)
I mean, deleting calls leads to improper reporting in any case.
-
What would be the better choice? Leaving 3 dead calls on permanent display on the supervisor screens and wallboards for all time to come, or removing 3 erroneous calls among the thousands processed daily? I can guarantee those three calls won't affect any business decisions.
Is there no way to remove those calls? Where does the data come from?
Thx!
-
Yes absolutely - find the uniqueid of the calls (click on the call detail) and delete all calls with that uniqueid from the queue_log table.