Messages

1

Running QueueMetrics / Re: Adding a column to an exsisting report

« on: December 18, 2015, 02:07:39 »

Has there been any change in this situation in the four years since the original post?  I have exact same problem to solve: adding a column (for DNIS) to the detail report?

2

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!

3

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?

4

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?

5

QueueMetrics installation / Re: [queuemetrics] context and FreePBX

« on: November 22, 2010, 18:33:23 »

if you create an extensions_queuemetrics.conf file and include it in freePBX's extensions_custom.conf, you will not and cannot break freePBX even when freePBX does version upgrades. 

6

QueueMetrics installation / Re: [queuemetrics] context and FreePBX

« on: November 19, 2010, 18:43:40 »

I am using QM 1.6.2 in conjunction with freePBX 2.8.x.x. in a hot seating environment and it works like a charm pretty much out of the box [although I still reverted back to the "echo" for queue logging].  The other note I would make is that when you have a complex set up [12 different queues and 100+ agents], using the QM mechanism for logging in and out and joining queues is much more practical and user friendly than the freePBX approach, but that is just one person's opinion.

7

General Asterisk configuration / Re: PAUSE code includes an amigous reason code know as: "-" - Is this a bug?

« on: November 08, 2010, 18:05:19 »

I would like to second this.  It is annoying to have to have floor managers chase down agents who have paused without a reason.  As a temporary workaround, we had to implement a test in the dial plan that simply rejects the pause if it comes without a reason.

I think in general that QM needs to think about being able to tighten up Administrators abilities to battle bad input from Agents.  In a perfect world, everyone follows instructions and policies to the letter.  In our real world where we have hundreds of agents and a significant number of them are temporary employees, there are lots of opportunities for agents to make mistakes possible [some deliberately gaming the system, some just careless].  But basically if you give an Agent a textbox to fill in [like for the extension they want calls coming to in a hot seat environment] or you give them select boxes with "-" or " " as an option, mistakes will be made and some of them can be crippling.  We need to be able to either eliminate or greatly reduce the possibilities to make these errors.

8

Improving QueueMetrics / Re: Checks on Add Member

« on: November 02, 2010, 16:52:07 »

I had not thought of that but I think that sounds like a very good idea!  I was originally thinking of having the extension selection made from a select box rather than a text field, where the select box might come from an extensions table in the database... maybe like the queues and agents, the extensions could start with a wizard filler tool from the dial plan [of course I see the problem that different distributions keep extension data in different files]. ... but you idea of a default extension would be a good start!

9

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...]

10

Running QueueMetrics / Re: Color of graphs in QM

« on: October 27, 2010, 15:42:42 »

histograms are shades of blue but pie charts are either shades of light grey [or in some cases non existent]

11

Running QueueMetrics / Re: Agent showed in the queue, even if softphone is closed

« on: August 21, 2010, 01:36:09 »

from asterisk CLI a simple SIP SHOW PEERS will tell you if someone has turned off their extension. 

12

Running QueueMetrics / Re: Agent showed in the queue, even if softphone is closed

« on: August 13, 2010, 22:38:11 »

still would be very useful to have functionality for a supervisor to log off agents.  you are correct that discipline is needed but even then, accidents still happen.

13

Running QueueMetrics / Re: Random Realtime Report Data missing

« on: August 13, 2010, 22:36:29 »

using ADDMEMBER... so I suppose it is truly weird! 

14

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.

15

Running QueueMetrics / Re: qloader stops reporting to quemetrics after 24 hours

« on: June 13, 2010, 16:05:46 »

change daily to weekly or monthly in the log file.  if you do choose to rotate less frequently, you will want to change the rotate parameter so it keep less of the past files.  for example:

/var/log/asterisk/queue_log{
   missingok
   rotate 5
   weekly
   create 0640 asterisk asterisk
   postrotate
       /usr/sbin/asterisk -rx 'logger reload' > /dev/null 2> /dev/null
   endscript
}

you might want to consider differentiating between log files so the queue_log is on a different rotation to all the other asterisk log files.  you could then omit the section for queue_log so that it never rotates at all if that is an attractive option for you.