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 - QueueMetrics

Pages: 1 ... 68 69 [70] 71 72 ... 202
1036
Running QueueMetrics / Re: manual update QM
« on: November 15, 2010, 10:26:15 »
You have to delete a symlink that Tomcat adds under the /webapps directory that is used as a redirection.

1037
A large rewriting of the QA module will be out by the end of the year - january 2011.

1038
Running QueueMetrics / Re: Hotseating
« on: November 15, 2010, 10:23:51 »
You should add SIP devices to the queues, not Local channels (if you want to use hotdesking).

1039
QueueMetrics installation / Re: QM 1.6 and realtime queue_log
« on: November 15, 2010, 10:20:29 »
The main difference I have noticed here is that my column type is "char" not "varchar".  I'm no database expert but if asterisk is picky about column types this could cause it to fail.

I think this is completely undetectable at the client level. The only difference  is if you want to waste space but have faster access (CHAR) or save disk space at a light penalty (VARCHAR).


1040
QueueMetrics installation / Re: IVR Selection
« on: November 15, 2010, 10:18:40 »
I think you should contact our Support Services so we can inspect a piece of your queue_log.,

1041
QueueMetrics installation / Re: QUEUE = 'oo All' has no data
« on: November 15, 2010, 10:17:48 »
"00 All" is just a name - it could be "ABCD" as well. You have to make sure what its member-queues are :)

1042
MySQL storage and Qloaderd/Uniloader / Re: QM/Mysql hardware limit.
« on: November 15, 2010, 10:16:44 »
Thanks I think they will contact you.

1043
QueueMetrics installation / Re: QM 1.6 and realtime queue_log
« on: November 10, 2010, 10:48:54 »
Yes, but they accessed a client's system during development.
We plan to address this with a tutorial for 1.8.

1044
QueueMetrics installation / Re: IVR Selection
« on: November 10, 2010, 10:47:50 »
There have been a couple of fixes in 1.6.2.2.

1045
MySQL storage and Qloaderd/Uniloader / Re: QM/Mysql hardware limit.
« on: November 10, 2010, 10:47:19 »
You could use a separate server for agent reporting versus the main one. It could be linked to a read-only slave MySQL server in order to divide the load.
You could also tweak the agent lookback period in order to minimize data access.
Please get in touch with our Support Services so we can run some performance probes.

1046
I agree. This is a simple change, so I am submitting it for next release: We track this as issue #1202.

1047
No I mean we updated the bug :-) you will receive an email notification when the bug is fixed.

1048
It seems strange that the change has no effect. Try and setting the value to something extreme like 5 seconds and see if it impacts the calls you see (the will report OK on the reports so don't worry). If nothing happens likely you are editing the wrong file.

1049
That is because an agent always has an option to pause without a reason.


Pages: 1 ... 68 69 [70] 71 72 ... 202