Messages

2086

Outbound and QueueMetrics / Re: outboun calls

« on: February 27, 2009, 10:07:09 »

Not sure about the AsteriskDB part; you should see the called number in a lost call by running a report and looking on "lost calls".

If you don't, please post the queue_log piece for a failed outbound call.

2087

Running QueueMetrics / Re: Accessing specific reports without entering username/password

« on: February 27, 2009, 10:05:31 »

You can do three things:
1. post default credentials and have users use these
2. make a POST request that overrides the first page (I think it might work but I have to check)
3. create a PHP front-end that will make a query to QM and display stats coming up from QM; in this case your users would not need to interact with the main QM app.


 

2088

Running QueueMetrics / Re: phantom ABANDON calls!

« on: February 27, 2009, 10:03:56 »

Yes that's what I meant. In practice,m ths means that the RINGNOANSWER verb does not work as expected in a number of cases

2089

QueueMetrics installation / Re: upgrading to 1.5.1

« on: February 27, 2009, 10:02:12 »

No we want to keep supporting 1.4 for the moment, even if we deploy it on 1.5 usually.

2090

QueueMetrics installation / Re: upgrading to 1.5.1

« on: February 26, 2009, 09:02:50 »

Thanks.

2091

QueueMetrics installation / Re: yum instal and cant get connected

« on: February 25, 2009, 20:33:54 »

Looks like queuemetrics-tomcat is missing. This is strange, as this is a required dependency.
Try removing the packages queuemetrics and queuemetrics-tomcat and then installing them back again.

2092

QueueMetrics installation / Re: Migrated Trixboxes now I'm having MAJOR issues

« on: February 25, 2009, 20:32:19 »

SO likely you do not have qloaderd running on the new queue_log file

2093

QueueMetrics installation / Re: upgrading to 1.5.1

« on: February 25, 2009, 12:55:47 »

Do you see an error there as well? can you post the stack trace?

2094

Running QueueMetrics / Re: Agent logged off, but Asterisk failed to process the logoff.

« on: February 25, 2009, 12:55:21 »

Is the problem you are experiencing happening always or just sometimes?

2095

QueueMetrics installation / Re: upgrading to 1.5.1

« on: February 24, 2009, 15:13:35 »

Can you upgrade  to java 1.5? if you cannot, we are preparing a patch.

2096

QueueMetrics installation / Re: upgrading to 1.5.1

« on: February 24, 2009, 10:43:48 »

Which version of Java are you running? looks like a missing dependency on the system Java libraries. Are you running Java 1.4?

2097

Outbound and QueueMetrics / Re: outboun calls

« on: February 24, 2009, 08:47:32 »

You have to use 1.5.1 for that

2098

Running QueueMetrics / Re: Agent logged off, but Asterisk failed to process the logoff.

« on: February 24, 2009, 08:47:02 »

It seems to have correctly run the command:

Code: [Select]

asterisk -rx "agent logoff Agent/8109"
Of course this only works if your agent was Agent/8109; if it was - say - SIP/8109, you have to edit the dialplan in order to run the correct logo-off command.

2099

Running QueueMetrics / Re: Quality Assessment

« on: February 24, 2009, 08:43:51 »

Can you post a screenshot of your items AND the drop-down menu?

2100

QueueMetrics news / Release 1.5.1

« on: February 23, 2009, 12:13:38 »

QueueMetrics version 1.5.1 has been released today.

This version comes with a revised Agent's page that will empower your agents and give them better insight into the overall call processing that is happening system-wide. We also added improved tracking of outbound calls made by agents, and a set of features that are meant to smooth the transition to the Asterisk 1.6 platform. As a last important change, we now support the Oreka recording solution as an audio storage medium. This will be loved by those of you running the largest Asterisk deployments, who will be able to factor out call recordings from the main Asterisk server.

There is also a long list of new features and bugs fixed that should make this release interesting for most of you.

These are the major upgrades over the previous versions:
* Bug #498: QueueMetrics is now able to track lost outbound calls and will show outbound calls correctly as they are being placed in the Realtime page.
* Bug #586: Qloaderd tool lets you do partial upload of older queue_log data
* Bug #632: It is now possible to use Oreka for audio recordings.
* Bug #605: Now officially using the PolyVox translator's portal
* Bug #612: QM supports AMI version 1.1 for Asterisk 1.6
* Bug #633: New XML-RPC call to export audio files for a given call.
* Bug #575: Broadcast messages are now shown on the Agent's page.
* Bug #576: AGAW information (if present) will now be displayed on the Agent's page
* Bug #577: URLs can be launched automatically from the Agent's page
* Bug #582: Agents can have a visibility key - useful to fully partition QM for multi-tenant systems
* Bug #619: On the Agent's page it is now possible to do logins to all queues at once using ADDMEMBER. Useful for Asterisk 1.6.
* Bug #620: Assisted outbound dialing on the Agent's page
* Bug #621: Custom buttons that can lanch extenal URLs or trigger dialplan functions added to the Agent's page.
*Bug #600: All dialplan hooks of QM now receive the login of the user performing the call - useful for auditing

A number of bugs have been fixed also:
* Bug #608: Attempts would be counted incorrectly on calls with a wait time of less than 2 seconds.
* Bug #584: Error "StatementGeneratedKeyNotRequested" - this was caused by recent versions of the MySQL connector. Fixed.
* Bug #593: Asterisk call-id tracking: a config switch lets you see the Asterisk ID of the call on the details page.
* Bug #552: We now include a copy of Apache Xerces with QM.
* Bug #615: We use two-digit hours in all languages to make it easier sorting by date
* Bug #616: The MySQL storage monitor was broken in 1.5.0
* Bug #622: It was possible to create multiple users with the same login.
* Bug #84: QM now lists all days, even ones without activity, in the Daily Activity reports
* Bug #563/#569: the AGAW loader broke if there were no queues to process.
* Bug #583: The number of licenced agents will be hidden in the Licence page if tech info is turned off
* Bug #585: Config pages would sometimes see outdated information
* Bug #602: The "Attempts" -> "Lost calls" value was wrong in 1.5.0
* Bug #618: Queue names including wildcards would not work correctly in the Live page

In total, this release produces well over 150 different results and is available in 12 different languages.

You can download the latest version immediately from the downloads page.
http://queuemetrics.com/download.jsp

As an alternative, if you run RHEL/CentOS/TrixBox/AAH, you can install it automatically using yum - see the installation page.

The updated User Manual has been released jointly - you can download it or browse it online here: http://queuemetrics.com/manual_list.jsp

If you would like to write a language pack for your native language, it's very easy and it only takes a couple of hours' work. See the Translating QueueMetrics document from the Downloads page.

As always, we value your feedback on how to improve QueueMetrics to make it a better fit to your needs.


We have also prepared a couple of introductory articles to the new feature;
one about the new Agent's page:  http://forum.queuemetrics.com/index.php?topic=460.0 and the other explaining how to use the new Outbound calls mode at: http://forum.queuemetrics.com/index.php?topic=459.0