Topics

1

QueueMetrics installation / The requested resource (/queuemetrics/) is not available

« on: July 01, 2012, 21:35:05 »

tried to upgrade from 1.7.x to current version.  everything seem to go fine but QM will not start with the above error.

looking in logs, catalina.out looks normal.

in the localhost.log file, there is this:

SEVERE: Exception starting filter BalancerFilter
java.lang.NoClassDefFoundError: org/apache/commons/digester/Digester
   at org.apache.webapp.balancer.RulesParser.createDigester(RulesParser.java:65)
   at org.apache.webapp.balancer.RulesParser.<init>(RulesParser.java:43)
    ........
Caused by: java.lang.ClassNotFoundException: org.apache.commons.digester.Digester
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
   ... 30 more

this is followed by:

INFO: LowayTransactionController: [859CBC2C16236FEF75F08FD6D0EF0C14] [ERR] The verb 'qm_realtime2_ds' does not allow the creation of a new sessions.
Jul 1, 2012 7:16:30 PM org.apache.catalina.core.ApplicationContext log
INFO: LowayTransactionController: [859CBC2C16236FEF75F08FD6D0EF0C14] [ERR] The verb 'qm_realtime2_ds' requires a ke y that the current user does not hold.
Jul 1, 2012 7:16:30 PM org.apache.catalina.core.ApplicationContext log

...... [this shows up multiple times]

How do I get this back on track??

Thanks!

2

QueueMetrics installation / Yum Install Failure

« on: July 28, 2011, 08:58:02 »

CentOS 5.6 PiaF on a x86_64 server

this was a straight yum install queuemetrics

 queuemetrics.noarch 0:1.7.1.0-84


Install appears to go without a problem. 
Database created ok.  However, when I browse to the home page I get page not found.

catalina.out log shows error:

Jul 28, 2011 12:51:12 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jul 28, 2011 12:51:12 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 189932 ms
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/usr/local/queuemetrics/tomcat/webapps/webdav
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tomcat-docs from URL file:/usr/local/queuemetrics/tomcat/webapps/tomcat-docs
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /balancer from URL file:/usr/local/queuemetrics/tomcat/webapps/balancer
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Jul 28, 2011 12:51:12 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL file:/usr/local/queuemetrics/tomcat/webapps/jsp-examples
Jul 28, 2011 12:51:13 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path  from URL file:/usr/local/queuemetrics/tomcat/webapps/ROOT
Jul 28, 2011 12:51:13 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL file:/usr/local/queuemetrics/tomcat/webapps/servlets-examples
Jul 28, 2011 12:51:13 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /queuemetrics from URL file:/usr/local/queuemetrics/webapps/queuemetrics-1.7.1.0
Jul 28, 2011 12:51:13 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jul 28, 2011 12:51:13 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jul 28, 2011 12:51:13 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/30  config=/usr/local/queuemetrics/tomcat/conf/jk2.properties
Jul 28, 2011 12:51:13 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1230 ms
Jul 28, 2011 12:51:23 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /queuemetrics
Jul 28, 2011 12:51:23 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/usr/local/queuemetrics/tomcat/conf/Catalina/localhost/queuemetrics.xml




the log file starts with an error which seems to stop tomcat from ever getting started:

2011-07-28 00:51:12 StandardContext[/balancer]Exception starting filter BalancerFilter
java.lang.NoClassDefFoundError: org/apache/commons/digester/Digester
   at org.apache.webapp.balancer.RulesParser.createDigester(RulesParser.java:65)
   at org.apache.webapp.balancer.RulesParser.<init>(RulesParser.java:43)
  ......


Now what?

3

Running QueueMetrics / database and ui out of sync

« on: June 23, 2011, 21:53:39 »

I have a system that has been running fine for several weeks. Yesterday for no apparent reason all the reporting stopped being current.  Loader is running fine and call data and agent logins etc are being recorded in the log file and then subsequently showing up in the data base more or less instantly.  However, mealtime reports are not reflecting any activity past a certain time even though all subsequent events have been put in the database correctly.

I have never seen qm do anything like this. Any ideas?

4

Improving QueueMetrics / Checks on Add Member

« on: October 29, 2010, 19:47:34 »

It would be REALLY good to have a validity check on the Add Member [& Remeove Member] functionality for agents that are hot desking.  Specifically, we need to have a check on the validity of the extension they are entering [or else make the extension selection a select box from valid extensions]. 

Here is the issue:  I have an agent  who sits down and logs in etc ...gets to add member and instead of typing '6008' for the extension on her desk, she types in '6088'.  The program executes the relevant part of the dial plan and "Local/6088@from-internal/n" gets added to 5 [out of a total of 13 queues].  There is no extension 6088.  Realizing her error [because she gets no calls as well as the fact that we have a script that pushes "Agent XXX logged in" to the phone's LCD display] she hits Add Member again using the correct '6008'.... so now the queue has two entries, one bogus.  The queue has "leastrecent" ring strategy with autofill.  Now two calls come in...first goes to 6088 where nothing happens, while second call gets answered at 6008.  Now 6088 is seen as first priority under least recent algorithm because it has not answered a call, the first call keeps retrying 6088 first while calls keep sliding by... angry client and wasted server resources. 

We cannot prevent every error but we should be able to prevent entry of non existent extensions.  I have other examples of unthinking/untrained agents [they enter the agent code as the extension etc...]

5

Running QueueMetrics / Random Realtime Report Data missing

« on: August 12, 2010, 17:03:00 »

Running QM 1.6.1 using dynamic members.  All works well except for one tiny nuisance: on the realtime page looking at the Agents currently logged in section, data on the extension sometimes is present, sometimes not.  There is no obvious consistent pattern.  For example, right now I have 12 agents logged in, two show up with their extension in the report ...bust as it refreshes, now 8 show up with extensions.  Each refresh is like a lottery as to which agents will show their extensions.

This is no major issue but it does seem like a small bug somewhere.

6

Running QueueMetrics / Quick way to log agents off of assigned queues?

« on: April 27, 2010, 23:06:36 »

Is there a quick way for a supervisor to log an agent out of his/her assigned queues?  It seems we often get agents who forget to log out when they leave and leaving them logged in creates a wide assortment of operational issues.  Obviously there are ways to do this [log in as the agent, manually log them off via asterisk CLI etc] but did I miss a nice simple way for a supervisor? Like a button to log off an agent etc?  If the answer is in the manual, I will accept the flame..

7

QueueMetrics installation / WHat happened to Pie Charts

« on: April 25, 2010, 23:52:29 »

Upgraded to 1.6.0.1 on two different systems and in both cases the pie charts on the reports pages disappeared.  All data is present and correct and other charts [bar charts] are also present and correct.  Any idea how to get them to reappear?

Running on standalone machines running Centos 5.4.

8

Running QueueMetrics / Real Time Calls Not Showing Up

« on: January 14, 2010, 18:06:05 »

Asterisk 1.4.x running on same machine as QM using MySQL database as the data source.

All events are properly showing up in queue_log file and in the MySQL DB table queue_log on a very timely basis.


On Real Time, having following issue(s):

Agents show up fine when they log in and log out so we can correctly see logged in agents.  However, when a call comes in, it shows up under "Calls Being Processed" while it is in the queue waiting for pickup [i.e. it sees the ENTERQUEUE correctly] but as soon as the call is picked up by an agent, the call disappears from the Real Time page.  The queue_log file and the queue_log table both show a correct "CONNECT" entry but no sign of the call on the page.  It is consistent in the sense that the Agent also shows up "green" [available] on the page.  Asterisk itself is handling everything just fine.

Data in all reports is just fine.  If you pull the report detail of the answered calls while the call is ongoing, it will correctly show up as an ongoing call.

Any ideas as to what is going on?