Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Marquis

Pages: [1] 2
1
Running QueueMetrics / Re: ACD attempts clarification
« on: April 02, 2008, 13:08:51 »
Quote from: QueueMetrics on February 14, 2008, 12:37:07
This is filed as bug #268.


Is there any update on when a fix might be available for this?  I'm pretty sure I'm running up against the same issue.

2
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 24, 2007, 22:26:51 »
And you'd win that beer.  I must've changed it a some point and didn't realize that I had.  The configuration that I'm running right now is inherited from a much older config (might even have originated in a 1.2.x, but I can't be certain).

Anyway, it is good that it's fixed. :)

Thanks for the help.

3
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 12, 2007, 12:21:00 »
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.

4
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 10, 2007, 19:59:31 »
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?

5
Running QueueMetrics / Re: Recorded calls no longer available
« on: September 10, 2007, 13:29:56 »
FWIW, I can confirm that 1.4.2 works just fine with respect to recorded calls.  Thanks for the quick fix.

6
Running QueueMetrics / Re: Recorded calls no longer available
« on: September 06, 2007, 16:04:08 »
Quote from: QueueMetrics on September 06, 2007, 15:36:16
We are checking this issue. Filed as bug #201.
We would be happy if you could try and put those files in a local directory and see if it will work or not.


It still does not work with local files.

7
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 06, 2007, 16:00:54 »
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.

8
Running QueueMetrics / Recorded calls no longer available
« on: September 06, 2007, 01:20:12 »
If I try to listen to record calls in any 1.4.x version of QueueMetrics, I get the message:  "Illegal file access: missing grant or missing file name"

In a parallel 1.3.5 instance, this works fine.  These files are remote via NFS, but the permissions are fine (I even changed them to 666 just in case, but no change).

Help?

9
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 06, 2007, 01:15:13 »
This still is not working for me.   :(

10
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 05, 2007, 13:55:17 »
OK, thanks.  I just grabbed the 1.4.1 tarball, and I will test it ASAP and respond back here.

11
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: September 04, 2007, 21:14:05 »
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?


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?

12
Running QueueMetrics / Re: Waiting and Duration problems in Realtime monitoring
« on: August 30, 2007, 21:14:19 »
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

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?

13
Running QueueMetrics / Waiting and Duration problems in Realtime monitoring
« on: August 29, 2007, 23:34:41 »
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?

14
Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue
« on: August 22, 2007, 19:21:09 »
OK, I now understand what's going on.  If I change realtime.members_only to 0, then I get the behavior I would expect.

15
Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue
« on: August 22, 2007, 13:21:22 »
If that is by design, then I would claim it is horribly flawed.  You aren't really getting per-queue stats unless you get the "Show members only" data.  Is there by any chance some way to modify my XML-RPC query so that's what i get?

Pages: [1] 2