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.


Messages - QueueMetrics

Pages: 1 ... 64 65 [66] 67 68 ... 202
976
QueueMetrics news / QueueMetrics 1.6.3 released
« on: December 23, 2010, 11:47:12 »
We have released QueueMetrics 1.6.3. This version includes a number of changes that will make your life easier as an administrator, and notably:

- Updates over yum do not lose the configuration anymore: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s02.html#TPF_PROPERTIES

- A new DbTest page lets you analyze the status of a current system and see the que_log table live - see http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s18.html#DBTEST

- A new report for Agent Occupancy: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s06.html

New features:
#1211 - When updating over yum, it is now possible to keep the license and properties
#1197 - Checked full compatibility with 1.8
#1188 - Script to refresh view of DB tables
#1189 - DBTester checking AMI connection
#1195 - Easier debug: show current configuration
#1201 - New Report: Agent Occupancy (AG09)

Error fixed:
#1192 - Page encoding popup agent's page
#1194 - Queue names not always decoded correctly
#1198 - Enlarging of all queue_log fields
#1202 - Agent MUST set a pause reason
#1210 - Taken/lost graph may be out of sync when you enter a report.
#1216 - Typo
#1218 - Optionally passing penalties to Addmember entries
#1219 - Broken image form Undefined group
#1217 - Correctly decoded call status for lost calls
#1209 - Improved working with filters and multi-stint calls


Read the full release here: http://queuemetrics.com/news.jsp#news-20101222-QM163



977
Lost licences / Re: Expired License
« on: December 23, 2010, 09:48:13 »
Most likely, the key has expired. Please send a full stack trace to our e-mail support line.

978
You need to create an outgoing route, like 9 + 340 + 12345678 that means, dial 12345678 on queue 340.

979
Improving QueueMetrics / Re: Automatic license Transfer
« on: December 22, 2010, 15:14:51 »
This is fixed in the upcoming version 163

980
Improving QueueMetrics / Re: Include Priority in Dynamic Agent Login
« on: December 22, 2010, 09:27:23 »
We actually fixed it yesterday - we tracked that as #1218.



981
Running QueueMetrics / Re: Vicidial y Queuemetrics.
« on: December 22, 2010, 09:24:04 »
Ok you need to upload data as "P002" from your "regular" asterisk server via qloaderd as well to the same table.

982
Running QueueMetrics / Re: Vicidial y Queuemetrics.
« on: December 21, 2010, 16:04:32 »
I see only the data that ViciDial generates, but nothing else.....

Try running

Quote
SELECT partition, count(*) FROM queue_log GROUP BY partition


And let's see if there is anything else in there.



983
QueueMetrics installation / Re: Call Waiting Tone
« on: December 21, 2010, 16:02:32 »
Interesting.... how are your agents members of the queue? Local/2345@from-internal? or SIP/1234?


984
Running QueueMetrics / Re: Vicidial y Queuemetrics.
« on: December 17, 2010, 09:46:55 »
Look at the DB table "queue_log" and make sure that you have data in both partitions.

986
General Asterisk configuration / Re: Queuemetrics and Asterisk 1.8
« on: December 15, 2010, 09:55:25 »
We have noted a few small issues, mostly with the logger. So basically it is, you may notice a few points you have to fix manually in the  dialplan. We are working on a quick guide and an updated extensions_queuementrics.conf for 1.8.

987
Lost calls are not per agent, they are in general! A lost call for an agent is a missed ACD attempt.

988
Running QueueMetrics / Re: Several Calls are showing Not Answer Yet
« on: December 13, 2010, 10:52:44 »
Try and see if a call that shows up as "unanswered yet" has all data duplicate.

989
Errcode 28 is MySQl parlance for: no space left on device.

See http://forums.mysql.com/read.php?21,113364,113442#msg-113442

You should make some room on the DB disk! :)

990
You can have this data in real-time, but with real-time data you have to keep track of calls that are incomplete now and will change status/duration/etc. once completed. So it is easier if you can do that on calls that are simply closed.

The XML-RPC is made for data exchange, so you basically have it all as arrays of strings in your target language. You could then reprocess data or simply dump it all to a DB.

There are a lot of XML-PRC queries you can make, so just choose what you need - see here: http://queuemetrics.com/manuals/QM_XML-RPC_manual-chunked/



Pages: 1 ... 64 65 [66] 67 68 ... 202