Waiting and Duration problems in Realtime monitoring

[Marquis]

For some reason, both of these fields are never populated on my system.

I can see the calls when they are either in progress or waiting to be sent to an agent, and the Entered column has the correct time.

Any ideas?

[QueueMetrics]

(I suppose we are speaking of the Realtime page, note the Live one.)

There might be two different reasons:
1. you are speaking of outgoing calls. This is by design (of Asterisk) not having the connect time.
2. if this happens on incoming calls as well, very likely there is some timing problem with QM: see http://queuemetrics.com/faq.jsp#faq-032-timezones

[Marquis]

(I suppose we are speaking of the Realtime page, note the Live one.)

There might be two different reasons:
1. you are speaking of outgoing calls. This is by design (of Asterisk) not having the connect time.
2. if this happens on incoming calls as well, very likely there is some timing problem with QM: see http://queuemetrics.com/faq.jsp#faq-032-timezones

Yes, I am talking about the Realtime page.  I am also definitely talking about incoming calls.

I have actually gone through the timezone faq, as I previously had a problem with QueueMetrics showing the time to be an hour off.  This was, however, resolved before I posted this message.

Any other ideas?

[QueueMetrics]

If you are running 1.4 and use a default time zone offset, the cause might be a bug we just founfd that is fixed in 1.4.1 due next week. Could this be the case?

[Marquis]

If you are running 1.4 and use a default time zone offset, the cause might be a bug we just founfd that is fixed in 1.4.1 due next week. Could this be the case?

Well, I am running a pre-release version of 1.4.1 that Lorenzo gave me August 22nd.  Is this bug something that has been fixed since then?  If so, then it is entirely likely it is the same issue.  Any chance of getting another prerelease snapshot to test with?

[QueueMetrics]

We just released it - the website will be updated later today.

[Marquis]

OK, thanks.  I just grabbed the 1.4.1 tarball, and I will test it ASAP and respond back here.

[Marquis]

This still is not working for me.   

[QueueMetrics]

I think I need you to send over a few screenshots of what is going on.
For maximum ease of understanding, the best thing is to take a screenshot where you are seeing:
- QM realtime page
- A shell window showing "tail -f /var/log/asterisk/queue_log"
so it's very easy to match whta is going on with the last lines of the queue_log.

See http://astrecipes.net/index.php?n=251 for how to submit an error.
Thanks.

[Marquis]

I can send this information over, though I'm not sure what the queue_log is going to prove.  It sees the entry of the call into the queue and also sees when it is answered by an agent, but is not calculating the Waiting time of a call in queue or the Duration of a call that's connected to an agent.

[QueueMetrics]

A screenshow where we see the queue_log and a call showing 0 when it's not would be pretty helpful.

[Marquis]

Here's a section of the queue_log that does not show any duration:

1189447039|110a2108-6868030a-13c4-46e54cef-2dc42376-6bd2@compuware.com|brad-q|NONE|ENTERQUEUE||71841
1189447040|110a2108-6868030a-13c4-46e54cef-2dc42376-6bd2@compuware.com|brad-q|Local/18887@queuemembers|CONNECT|1|1189447039.844
1189447080|110a2108-6868030a-13c4-46e54cef-2dc42376-6bd2@compuware.com|brad-q|Local/18887@queuemembers|COMPLETECALLER|1|40|1

And it's not that it should a zero, it shows nothing in the Duration column (and likewise for a call that is waiting, the Waiting column is blank).

I can post a screenshot if you'd like, but where?

[QueueMetrics]

It looks correct - are you sure you didnt by chance set:

liveclock.enable=false

in configuration.properties?

[Marquis]

OK, that's exactly the problem.  However, I didn't set it that way.  It must be disabled by default.  It might be nice if the description for this parameter mentioned that waiting time and duration will not be displayed if set to false.

Thanks for the idea, anyway, that definitely fixes the problem.

[QueueMetrics]

This is strange, I'd bet a beer that it was set

Code: [Select]

true in all releases we have done so far - anyway what's nice is that the problem is now fixed.