Messages

16

Running QueueMetrics / Re: stuck/hung calls with 1.4.4?

« on: September 04, 2008, 14:22:23 »

Running 1.4.21.2 now w/ QueueMetrics 1.4.6 and it appears if someone hangs up before being answered, QueueMetrics thinks the call is still there. Thus ending up with a hung/stuck call. Any ideas? Am I missing some kind of setting?

queue_log shows an enter queue but nothing else.

1220530572|1220530568.78|6001|NONE|ENTERQUEUE||312XXXYYYY

Thanks,
Scooby

17

QueueMetrics installation / callfile.dir question

« on: September 04, 2008, 00:04:13 »

Tonight I am upgrading to Asterisk 1.4.21.2 and a new dialplan. We get quite a few calls so we wanted to break them out by date to make them more manageable. I'm guessing I will need to write something custom to get the sound files to work. All we are doing is placing the files in the directory by US date. For example, todays files would be placed in:

/var/spool/asterisk/monitor/20080903/

Any chance I can make this work somehow with the callfile.dir setting?

Thanks in Advance,
Scooby2

MixMonitor(/var/spool/asterisk/monitor/${STRFTIME(${EPOCH},,%Y%m%d)}/sales-${UNIQUEID}.wav|v(0)V(0))

18

Scripting QueueMetrics / Re: Wallboard Example script

« on: August 31, 2008, 07:24:09 »

I tested this script today and all went well, except that nothing is happening or displayed as expected at the "Calls Waiting" and the "Agents Status" area. I could see a display of Agents logged on/Available or on a call below as expected.

I'm getting the same thing so I am thinking something with the XML changed. I will post if I get it figured out. I plan on taking a deeper look when I get a chance.

19

Running QueueMetrics / Re: 1.4.5 issue

« on: August 28, 2008, 05:51:37 »

Any details on the remote authentication or how to use it?

20

Running QueueMetrics / Re: 1.4.5 issue

« on: August 28, 2008, 05:46:37 »

Looks like the dbversion table got modified but the dbupdate is not altering it. I renamed dbversion to dbversion.old and then created the new table and inserted the value and it now works.


CREATE TABLE `dbversion` (
  `version_id` int(11) NOT NULL default '0'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

new:

CREATE TABLE `dbversion` (
  `version_id` int(11) NOT NULL default '0',
  `lic_version` varchar(45) NOT NULL default '',
  `lic_approved` varchar(45) NOT NULL default '',
  `plex_id` varchar(70) NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

21

Running QueueMetrics / Re: 1.4.5 issue

« on: August 28, 2008, 05:33:41 »

I did do that. It says my database is upto date. Was something left out?


The database is currently up-to-date.
You are now ready to run QueueMetrics. Click here to start.

I click that link and it gives the same error.

22

Running QueueMetrics / 1.4.5 issue

« on: August 27, 2008, 06:53:47 »

I tried upgrading to 1.4.5 tonight and it is giving me the following. I made sure that everything got an OK on the dbtest and that the database was up-to-date. I am very interested in what kind of external authentication is supported. LDAP by chance?

The only thing I can pick out of this is the: Unknown column 'lic_approved' in 'field list'.

Thank you,
Scooby2

"Errore tecnico nella classe 'it.loway.app.queuemetrics.autenticazione.start'. -- Inner Exception -- - Exception: it.loway.tpf.common.exceptions.TechException - Stack trace: - Problema DB: java.sql.SQLException: Unknown column 'lic_approved' in 'field list' - at it.loway.tpf.SQL.selectScalare(Unknown Source) - at it.loway.app.queuemetrics.autenticazione.start.doRun(Unknown Source) - at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequest(Unknown Source) - at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequestWrapper(Unknown Source) - at it.loway.tpf.transaction.servlets.LowayTransactionController.doGet(Unknown Source) - at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) - at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) - at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) - at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) - at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) - at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) - at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) - at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) - at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) - at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) - at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) - at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) - at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) - at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) - at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) - at java.lang.Thread.run(Unknown Source) - -- End Inner Exception -- - "

23

Running QueueMetrics / Re: stuck/hung calls with 1.4.4?

« on: August 26, 2008, 18:56:13 »

It is an old version. I am trying to build a 1.4.21.2 system but we are currently at 1.2.15 on a system that cannot be upgraded. It was a commercial release from a company but they went out of business. Changing binaries causes everything to break.

I am going to be testing the 1.4.21.2 system live for the first time tomorrow night and then will put it live over the weekend if it works. Last time I tried upgrading to 1.4.x the system crash so I am hoping a new server fixes that problem. 

24

Running QueueMetrics / stuck/hung calls with 1.4.4?

« on: August 25, 2008, 20:47:33 »

We recently upgraded from 1.3.1 to 1.4.4. Since upgrading, we have been experiencing what appears to be phantom stuck/hung calls in Queuemetrics. Has anyone else experienced this?

The issue this morning was a call showed in the queue for over 10 minutes yet the phones were not ringing and there was no way to answer the call. Queue log shows it was an agent dump but the call continued to appear for over 10 minutes. This is the fourth time this has happened since upgrading. Unfortunately this is the first time someone recorded the number so I could check the queue log.

Any ideas?

Thanks,
Scooby

1219670692|1219670687.106056|sales|NONE|ENTERQUEUE||8125555309
1219670769|1219670687.106056|sales|Agent/113|AGENTDUMP|

25

MySQL storage and Qloaderd/Uniloader / Re: asterisk queue_log directly to mysql

« on: August 13, 2008, 22:49:02 »

If you look at the queue_log table, it should be trivial seeing which fireld is which. On the other side, I personally do not recommend having Asterisk log directly to MySQl, because:
1. It's more likely for a networked MySQL to be down than not to be able to write lto a local file. In a sense the local file acts as a "local buffer" and "natural backup".
2. qloaderd syncs with usually one second or less of delay, so ut should not change much.

Feel free to share your experience, whether you succeed or not

Maybe its just our current setup. Currently it is set to log to the queue_log file and then machine B that runs Queuemetrics, nfs mounts that directory on the machine A and qloaderd runs from machine B to mysql on localhost and Queuemetrics talks to localhost.

If my Asterisk upgrade to 1.4.x ever works, I will try running qloaderd on the Asterisk box and then have Queuemetrics connect to that. That should be fast enough.

26

Running QueueMetrics / Re: Couple questions moving from 1.3.1 to 1.4.4

« on: August 13, 2008, 22:06:58 »

Which browser are you using? we test on IE 6/7, Firefox, opera 8 and 9. And I've never seen that error. 

This is from Firefox 3.0.1 on Mac.

27

MySQL storage and Qloaderd/Uniloader / asterisk queue_log directly to mysql

« on: August 13, 2008, 00:55:54 »

We want to have Asterisk write directly to MySQL to make the Realtime page more Realtime. Should I take the Queuemetrics queue_log schema and try and get the data into that or can Queuemetrics look at a table and map columns? Asterisk 1.6 is going to support writing the queue_log directory to MySQL, so I figured I should get a head start on figuring it out.

28

Running QueueMetrics / Re: Couple questions moving from 1.3.1 to 1.4.4

« on: August 12, 2008, 22:59:10 »

and again..

In console when trying to click on buttons in the Realtime page I get the following two errors over and over:
Warning: Error in parsing value for property 'cursor'.  Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 74
Warning: Error in parsing value for property 'cursor'.  Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 259

29

Running QueueMetrics / Re: Couple questions moving from 1.3.1 to 1.4.4

« on: August 12, 2008, 22:35:42 »

Replying to myself...

I showed them how to change the yellow/red alerts in the queue configuration so that made them happy. Now if there was a way to default the Realtime page to just show active queues, I would be a happy camper.

Thanks!

30

Running QueueMetrics / Couple questions moving from 1.3.1 to 1.4.4

« on: August 12, 2008, 21:30:26 »

Thanks for the excellent program! Besides the broken buttons on the Realtime page (javascript?), my team thinks the font color has changed and is wanting to have only active queues shown on the Realtime page as default.

I did not see anything to change colors or only show active queues on the Realtime page. Is there any way to change these? Are all the configuration options documented anywhere or is everything in the configuration.properties file?

Thank you,
Scooby2