Messages

1

QueueMetrics installation / Re: Upgrade from 1.6.1.2 to 1.7.1.13

« on: December 15, 2011, 14:17:08 »

Anyone have any ideas?  The upgrade went through correct, I had to add a bunch of fields to the tables.  Fortunately, the call volume is minimal this time of year, but in the next two weeks we'll be back up to normal and need to have this working.

Thanks

2

QueueMetrics installation / Upgrade from 1.6.1.2 to 1.7.1.13

« on: November 23, 2011, 05:16:31 »

We finally got around to upgrading our install, and after adjusting the database issues by adding the necessary fields, etc. we're getting the following error when attempting to run any report:


Database access error.  -  <p> - Exception: it.loway.tpf.common.exceptions.TechException - Errore file/DB: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'data5' in 'field list' - at it.loway.app.queuemetrics.asterisk.logs.analyzers.AnalizzaLogMysql.createTemporaryFile(AnalizzaLogMysql.java:500) - at it.loway.app.queuemetrics.asterisk.logs.analyzers.AnalizzaLogMysql.loadLogInfo_classic(AnalizzaLogMysql.java:250) - at it.loway.app.queuemetrics.asterisk.logs.analyzers.AnalizzaLogMysql.loadLogInfo(AnalizzaLogMysql.java:200) - at it.loway.app.queuemetrics.caricamento.caricaCoda.runDataAnalysis(caricaCoda.java:281) -

TIA,

Carlos.

3

Improving QueueMetrics / Re: Selection of Time for Last x days

« on: May 26, 2010, 18:47:47 »

The options on the top row - Today | Yesterday | The day before yesterday correctly go from 00:00 to 23:59, but the options in the bottom row : Last day | Last 7 Days | Last 30 Days | Last 90 days go from "now" back in 24 hour periods.

If I run the reports now at 12:41 local time here's what I get:

 - Today - May 26, 00:00 to May 26 2010, 23:59
 - Yesterday - May 25, 00:00 to May 25 2010, 23:59
 - The day before yesterday - May 24, 00:00 to May 24 2010, 23:59
 - Last day - May 25, 12:41 to May 26 2010, 12:41 -
 - Last 7 Days - May 19, 12:41 to May 26 2010, 12:41
 - Last 30 days - April 26, 12:41 to May 26 2010, 12:41
 - Last 90 Days - February 25, 12:41 to May 26 2010, 12:41

The options that start with Last are going back in 24 hour periods from "now" rather than starting from the end of yesterday, and going x days back.

I would also add that a Last month would be helpful as well, using the last complete calendar month that has passed.  If I ran Last month today, I would expect to see all of April.

4

Improving QueueMetrics / Re: Selection of Time for Last x days

« on: May 21, 2010, 14:00:12 »

If I click Lat 7 days at 07:59 server time

I really don't expect to have :

Period start date: May 14 2010, 07:58 
Period end date: May 21 2010, 07:58 

I would expect to see:

Period start date: May 13 2010, 00:00 
Period end date: May 20 2010, 23:59 

5

Improving QueueMetrics / Selection of Time for Last x days

« on: May 20, 2010, 16:16:42 »

I think that the reports for Last day, 7 days, etc. should automatically select 00:00 to 23:59 for the time start/end as well as selecting the previous day for hte period end date and going back from there. 

If I select Last 30, I expect to see from Yesterday back 30 days, not 30 24 hour periods from now

Thanks.

Carlos.

6

Running QueueMetrics / Re: Wildcards - driving me crazy

« on: May 20, 2010, 15:21:19 »

No, I don't have each of the sub-queues defined manually.  I have the queues, as I listed them.  The ones that start with Queue - xxxx, those are the ones that the agents use to login to.

Ok, so I guess this means that I still need to define them manually elsewhere, just so that the wildcards work?

I was under the impresison that the wildcard would allow the filtering of the raw data.

7

Running QueueMetrics / Wildcards - driving me crazy

« on: May 19, 2010, 21:23:10 »

I'm having some really strange things happening with the reports.  I previously had statically assigned queues in each of the groups, but as we started to add queues, i thought I would attempt to clean up the long list of queues.  However, it seems that I'm having some problems with the wildcards, and the subqueues.  These reports just don't seem to make sense, we're seeing calls disappear, etc.

What I've noticed is that I can't have a wildcard value after the "." when defining the queues.  It works correctly when using the 9001*|9101*, but when it's used after the "." for the subqueues, is where we seem to have a problem.

I have the following queues:
Alias = Direction = Queue(s)

These Alias definition work, and all the values are properly displayed as expected:
 - 00 - All = Undefined = 9001*, 9101*, 9201*, 9601*, 9800*, q-*
 - 01 - All Inbound = In = 9001*, 9101*, 9201*, 9601*
 - 01 - All Outbound = Out = 9800*, q-*

These do not work as expected, since the * is after the ".":
 - Inbound -AAA = In = 9001.AAA*, 9101.AAA*, 9201.AAA*, 9601.AAA*
 - Inbound - BBB = In = 9001.BBB*, 9101.BBB*, 9201.BBB*, 9601.BBB*
 - Inbound - CCC = In = 9001.CCC*, 9101.CCC*, 9201.CCC*, 9601.CCC*
 - Outbound - 111 = Out = q-1110000, q-111*
 - Outbound - 222 = Out = q-1110000, q-222*
 - Outbound - 333 = Out = q-3330000, q-333*

These also work in reports, but with the *, won't let the agents log in.
 - Queue - 9001 = In = 9001*
 - Queue - 9101 = In = 9101*
 - Queue - 9201 = In = 9201*
 - Queue - 9601 = In = 9601*
 - Queue - 9800 = Out = 9800*

Thanks in advance.

Carlos

8

Running QueueMetrics / Re: Undefined Call Direction

« on: May 18, 2010, 16:34:11 »

Yes, we have the direction on each of the queues.  The only location where we really can't define the direction is the All, which has inbound outbound.

I have the following queues:

Alias = Direction = Queue(s)

00 - All = Undefined = 9001*, 9101*, 9201*, 9601*, 9800*, q-*
01 - All Inbound = In = 9001, 9001.*, 9101, 9101.*, 9201, 9201.*, 9601, 9601.*
01 - All Outbound = Out = 9800, 980.*, q-*
Inbound -AAA = In = 9001.AAA*, 9101.AAA*, 9201.AAA*, 9601.AAA*
Inbound - BBB = In = 9001.BBB*, 9101.BBB*, 9201.BBB*, 9601.BBB*
Inbound - CCC = In = 9001.CCC*, 9101.CCC*, 9201.CCC*, 9601.CCC*
Outbound - 111 = Out = q-1110000, q-111*
Outbound - 222 = Out = q-1110000, q-222*
Outbound - 333 = Out = q-3330000, q-333*
Queue - 9001 = In = 9001
Queue - 9101 = In = 9101
Queue - 9201 = In = 9201
Queue - 9601 = In = 9601
Queue - 9800 = Out = 9800

The only place where Agents are assigned is the Queues that start the Alias with Queue.  

When I pull up the Reports on the Queues, the direction is there.  But, in any of the subqueue reports(Inbound - xxx, Outbound - xxx), the direction is missing.  In the All Inbound report, the direction is there for some of the calls, but for others, it's undefined.

This also brings up another question regarding the use of the wildcards, etc. but I'll start oanohter topic on that...

Thanks,

9

Running QueueMetrics / Undefined Call Direction

« on: May 17, 2010, 20:14:11 »

We have several inbound/outbound queues, and are noticing that the answered call direction is always showing undefined.  We have several main queues defined inobund/outbound, and our subqueues are working correctly.  Any ideas on what to look for?

Thanks,

Carlos.

10

Running QueueMetrics / Re: Split Audio Files

« on: April 08, 2010, 14:52:57 »

So in other words, we can specify queue/YYYY/MM/DD/filename where queue = queue.subqueue?

The only thing needed to be changed in the extensions would be the Set(MONITOR_FILENAME=, but then what would need to be changed in configuration.properties?

11

Running QueueMetrics / Re: Split Audio Files

« on: April 07, 2010, 14:18:30 »

Is there a way to do queue.subqueue/YYY/MMM/DDD/filename.wav?  The queue.subqueue would be sufficient, as we could setup ftp access to ertain folders for certain users.  If the client definition is all the way at the end, that's a lot of directories to add to the ftp access list...

Thanks.

12

Running QueueMetrics / Re: Split Audio Files

« on: April 06, 2010, 15:01:57 »

But that is at the recording file name, not the directory level.  I was hoping to have a directory level name, so that we can allow access to archive recordings by queue/subqueue. 

13

Running QueueMetrics / Re: Pausing Agents

« on: April 06, 2010, 15:00:09 »

Understood. 

Thanks.

14

Running QueueMetrics / Re: Queues and SubQueues in Reports

« on: April 06, 2010, 14:59:54 »

We are going to try and allow the customers logins, and use keys to limit the queue views.  Would there be duplicate information?  I was hoping that the subqueues would let us filter the information based on the queue/subqueue, and continue to have all the information. 

15

QueueMetrics installation / Re: Admin Logon

« on: April 06, 2010, 14:58:12 »

By using the subqueue as XXX99, we get to more easily breakdown the statistics per customer, and avoid having hundreds of queues created.  We may have 10 customers, with 50 DID's each.  I rather have 20 subqueues, than 500.  We only need to create new subqueues, if the customer wishes to track a specific subqueue.  We also have the DNIS, so we know how many calls came in to each DNIS.