QueueMetrics > Running QueueMetrics

Waiting and Duration problems in Realtime monitoring

(1/4) > >>

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:

--- Quote from: QueueMetrics on August 30, 2007, 14:40:44 ---(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

--- End quote ---

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:

--- Quote from: QueueMetrics on September 01, 2007, 18:26:24 ---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?


--- End quote ---

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?

Navigation

[0] Message Index

[#] Next page

Go to full version