2341
QueueMetrics installation / Re: java.io.FileNotFoundException
« on: August 29, 2008, 16:09:48 »
Tomcat is running as user tomcat - can you try running it as root, just for a test?
QueueMetrics professional call center suite for the Asterisk PBX
News:
Welcome to the new forum!
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.
2342
MySQL storage and Qloaderd/Uniloader / Re: MySQL 5 not working ?
« on: August 28, 2008, 16:53:34 »
Cool - we have to add this to the DB updater as well, so that it checks to see if there is an incompatible SQL mode.
2343
QueueMetrics installation / Re: java.io.FileNotFoundException
« on: August 28, 2008, 16:52:36 »
Which user is running the Tomcat process?
2344
QueueMetrics installation / Re: java.io.FileNotFoundException
« on: August 28, 2008, 14:35:21 »
See if this applies - I've never used Gentoo but this is a Tomcat setting:
http://astrecipes.net/index.php?n=227
http://queuemetrics.com/faq.jsp#faq-047-java_security
Basically if you look on the License page for the property java.security.policy, you find to what file it points to and try to delete it and restart.
http://astrecipes.net/index.php?n=227
http://queuemetrics.com/faq.jsp#faq-047-java_security
Basically if you look on the License page for the property java.security.policy, you find to what file it points to and try to delete it and restart.
2345
MySQL storage and Qloaderd/Uniloader / Re: MySQL 5 not working ?
« on: August 28, 2008, 14:30:10 »
I think this is the cause: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html
Try setting SQL mode to MYSQL40 in my.ini and see if this fixes your problems.
We are tracking this as bug#413.
Try setting SQL mode to MYSQL40 in my.ini and see if this fixes your problems.
We are tracking this as bug#413.
2346
QueueMetrics installation / Re: java.io.FileNotFoundException
« on: August 28, 2008, 14:21:06 »
My suggestion is to completely disable the Java Security module.
2347
Running QueueMetrics / Re: 1.4.5 issue
« on: August 28, 2008, 08:40:01 »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;
This is a major issue. we'll fix that ASAP.
We trace this as bug #443
2348
MySQL storage and Qloaderd/Uniloader / Re: MySQL 5 not working ?
« on: August 28, 2008, 08:38:43 »
What error do you get? we deploy a lot of systems on MySQL 5.
Can you post a screenshot of the error?
Can you post a screenshot of the error?
2349
Running QueueMetrics / Re: 1.4.5 issue
« on: August 27, 2008, 09:05:14 »
You did not run the database update tool - go to http://yourserver:8080/queuemetrics/dbtest to check and update your database.
2350
Running QueueMetrics / Re: stuck/hung calls with 1.4.4?
« on: August 27, 2008, 09:04:06 »
That is okay - it should surely be better.
2351
QueueMetrics news / QueueMetrics 1.4.5 released today
« on: August 26, 2008, 18:11:49 »
We are proud to announce that Queuemetrics 1.4.5 has been released.
This version improves Queuemetrics support for foreign languages and offers a mitigation for one of the most important problems call-centers administrators were facing, i.e. incorrect statistics for calls with missing records that would seem to go on forever. One other thing that was heavily improved is the new pure-dialplan outbound calling script, that offers better logging and requires no AGI overhead.
As always, we value your feedback on how to improve QueueMetrics to make it a better fit to your needs.
New features
New features:
- New pure-scripting solution is used instead of the old queueDial.agi script, thus solving a number of issues (#121, #220, #229)
- This version of QM may work with queueDial.agi, but the new script is needed for realtime outbound monitoring (#401)
- Updated documentation for outbound - see the version 2.0 of 'Tracing outbound calls through QueueMetrics in TrixBox' (#394)
- The EULA for QM must be approved on startup. If an incorrect version of the DB is detected, QM will not open and will show the "updating" page. (#374, #228)
- It is possible to force-close an ongoing call (see the user manual) (#399).
- An external auth source can be used for authentication. (#406)
- All audio files saved by Asterisk are now streamed correctly (you still need the correct codecs on the client machine though) (#427)
- New translations: Russian (#407), Spanish, Dutch (#430)
- Improved French translation (#410)
- New AEL dialplan example (#417)
Bugs fixed over the previous releases
- Bug #367: the agent filter would sometimes not work.
- Bug #240: some encoding problems with the French charset.
- Bug #389: English appeared twice in the language selection combo in 1.4.4, and the first instance was not working.
- Bug #391: In QA, the "score" was computed instead of the "average". Also the loader would sometimes crash on invalid data being fed.
- Bug #403: QM would go over and over to the DBTOOL page.
- Bug #262: Incomplete entities would not be closed when running in "cluster:" mode.
- Bug #414: "No filter" and "Passthrough" are now logged the same way.
- Bug #413: The "insert record" dialog would crash on some MySQL systems.
- Bug #426. The TrixBox 2.6 tutorial had a small mistake when showing agents.
The new outbound script
Nobody liked the old queueDial.agi script. Yes, it did the job, but it has always been quite complex to set up for first-time users. Also, its event logging was incorrect, so that the "connect" event of the outbound call was not seen correctly on the realtime page. As a last downside, it required forking a new process for each new call, so it posed scalability problems for the largest call centers.
Since version 1.4.5 of QueueMetrics (and if you run Asterisk 1.4), it is now possible to use a full-dialplan solution for outbound calling. It can be found in the extensions_queuemetrics.conf files under WEB-INF/mysql-utils/extensions-examples. By looking at it, you can see that the [queudial] or [queuedial-loggedon] contexts can be very easily changed to suit your needs, and there is no need to change the main outbound calling procedure.
A new tutorial has been created to show how to set up this new scripting solution with the ubiquitous TrixBox - you will find it here: TrixBox Outgoing 2.0.
New languages
Since release 1.4.5, QueueMetrics is also natively available in Russian and Dutch. A new Spanish translation has been added to better suit the taste of European users, and the French translation has been extensively revised.
If your native language is not supported yet - why not translating QueueMetrics? it just takes a couple of hours and it's very easy to do - see the Translator's guide.
Closing incorrect ongoing calls
It sometimes happens: Asterisk forgets to log some call-closure events. This leads to calls that seem to go on forever in the real-time log, and end up spoiling the averages of your historical stats.
Since version 1.4.5 (and if you are running with a SQL backend - but if you don't use it yet, you really should) it is possible for call-center administrators to force the closure of such anomalous calls so that they will go away from the real-time screen and will still appear in the reports but with a length that does not ruin your daily averages. Calls can be closed from both the historical and the real-time view.
This feature is of-course protected from a security key and must be manually enabled. In order to set this up, please download the latest version of the User manual - see section "Closing ongoing calls" on page 135.
How to upgrade from a previous version
If you installed originally using yum, you should simply type:
yum update queuemetrics
and then point your browser to http://myserver:8080/queuemetrics/dbtest to update the database.
You should then copy the web.xml and configuration.properties from the old release to the new one.
Do not forget to make a backup copy of the database before running the update (just in case...)
This version improves Queuemetrics support for foreign languages and offers a mitigation for one of the most important problems call-centers administrators were facing, i.e. incorrect statistics for calls with missing records that would seem to go on forever. One other thing that was heavily improved is the new pure-dialplan outbound calling script, that offers better logging and requires no AGI overhead.
As always, we value your feedback on how to improve QueueMetrics to make it a better fit to your needs.
New features
New features:
- New pure-scripting solution is used instead of the old queueDial.agi script, thus solving a number of issues (#121, #220, #229)
- This version of QM may work with queueDial.agi, but the new script is needed for realtime outbound monitoring (#401)
- Updated documentation for outbound - see the version 2.0 of 'Tracing outbound calls through QueueMetrics in TrixBox' (#394)
- The EULA for QM must be approved on startup. If an incorrect version of the DB is detected, QM will not open and will show the "updating" page. (#374, #228)
- It is possible to force-close an ongoing call (see the user manual) (#399).
- An external auth source can be used for authentication. (#406)
- All audio files saved by Asterisk are now streamed correctly (you still need the correct codecs on the client machine though) (#427)
- New translations: Russian (#407), Spanish, Dutch (#430)
- Improved French translation (#410)
- New AEL dialplan example (#417)
Bugs fixed over the previous releases
- Bug #367: the agent filter would sometimes not work.
- Bug #240: some encoding problems with the French charset.
- Bug #389: English appeared twice in the language selection combo in 1.4.4, and the first instance was not working.
- Bug #391: In QA, the "score" was computed instead of the "average". Also the loader would sometimes crash on invalid data being fed.
- Bug #403: QM would go over and over to the DBTOOL page.
- Bug #262: Incomplete entities would not be closed when running in "cluster:" mode.
- Bug #414: "No filter" and "Passthrough" are now logged the same way.
- Bug #413: The "insert record" dialog would crash on some MySQL systems.
- Bug #426. The TrixBox 2.6 tutorial had a small mistake when showing agents.
The new outbound script
Nobody liked the old queueDial.agi script. Yes, it did the job, but it has always been quite complex to set up for first-time users. Also, its event logging was incorrect, so that the "connect" event of the outbound call was not seen correctly on the realtime page. As a last downside, it required forking a new process for each new call, so it posed scalability problems for the largest call centers.
Since version 1.4.5 of QueueMetrics (and if you run Asterisk 1.4), it is now possible to use a full-dialplan solution for outbound calling. It can be found in the extensions_queuemetrics.conf files under WEB-INF/mysql-utils/extensions-examples. By looking at it, you can see that the [queudial] or [queuedial-loggedon] contexts can be very easily changed to suit your needs, and there is no need to change the main outbound calling procedure.
A new tutorial has been created to show how to set up this new scripting solution with the ubiquitous TrixBox - you will find it here: TrixBox Outgoing 2.0.
New languages
Since release 1.4.5, QueueMetrics is also natively available in Russian and Dutch. A new Spanish translation has been added to better suit the taste of European users, and the French translation has been extensively revised.
If your native language is not supported yet - why not translating QueueMetrics? it just takes a couple of hours and it's very easy to do - see the Translator's guide.
Closing incorrect ongoing calls
It sometimes happens: Asterisk forgets to log some call-closure events. This leads to calls that seem to go on forever in the real-time log, and end up spoiling the averages of your historical stats.
Since version 1.4.5 (and if you are running with a SQL backend - but if you don't use it yet, you really should) it is possible for call-center administrators to force the closure of such anomalous calls so that they will go away from the real-time screen and will still appear in the reports but with a length that does not ruin your daily averages. Calls can be closed from both the historical and the real-time view.
This feature is of-course protected from a security key and must be manually enabled. In order to set this up, please download the latest version of the User manual - see section "Closing ongoing calls" on page 135.
How to upgrade from a previous version
If you installed originally using yum, you should simply type:
yum update queuemetrics
and then point your browser to http://myserver:8080/queuemetrics/dbtest to update the database.
You should then copy the web.xml and configuration.properties from the old release to the new one.
Do not forget to make a backup copy of the database before running the update (just in case...)
2352
Running QueueMetrics / Re: stuck/hung calls with 1.4.4?
« on: August 26, 2008, 16:53:27 »
Which version of Asterisk are you running? an AGENTDUMP just tells the system that an agent refues a call, NOT that the call has hung up, so it would be just fine for QM to keep it open (as there is no log that says the call has ended).
2353
General Asterisk configuration / Re: LOCAL/agent_id@dialing_context/n uses many channels / g729 licenses
« on: August 26, 2008, 16:50:55 »
I am not really sure how G.729 licensing works, but that might be caused by the /n. On the other side the /n prevents channel names from collapsing, so it's probably needed.
2354
Outbound and QueueMetrics / Re: EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution
« on: August 24, 2008, 12:10:19 »
I guess the number called SIP/5551212 makes no sense, so it's rejected. I think it should be something like SIP/RIOTRU/5551212 or Zap/g0/5551212, doesn't it?
2355
QueueMetrics installation / Re: How to avoid agants logins?
« on: August 24, 2008, 12:07:49 »
Simply assign terminals to be queue members in the queue configuration, eg. set SIP/102 instead of Agent/47. Of course the Agent activity page in QM will be empty (no agent session, no pauses).