Messages

1

MySQL storage and Qloaderd/Uniloader / Re: Migrate 1.6.2 1.8 Issue

« on: April 24, 2012, 23:25:08 »

I've resolved the issues but I am seeing the following in the logs:

[FC50434CFFCC44B4771BCA09B04195EC] [ERR] The verb 'qm_realtime2_ds' requires a ke y that the current user does not hold.
[FC50434CFFCC44B4771BCA09B04195EC] 201204241721 Total run time for verb 'qm_realtime2_ds': 4 ms

What key(s) do I need to add? I've added the realtime key

thanks,
Paolo

2

MySQL storage and Qloaderd/Uniloader / Re: Migrate 1.6.2 1.8 Issue

« on: April 04, 2012, 16:11:12 »

That's exactly what I am doing. When I edit configuration.properties as follows, QM works as it did using Asterisk 1.6 where it's reading the information from the column named 'data' per the previous queue_log mysql schema. Now using 1.8 the information is written to the columns named data1, data2, data4 etc...  as the schema has changed so QM is not reporting anything.

default.queue_log_file=sql:asterisk|a18

sqlPreset.a18.table=queue_log
sqlPreset.a18.f_time_id=time
sqlPreset.a18.use_timestamp=false
sqlPreset.a18.f_call_id=callid
sqlPreset.a18.f_queue=queuename
sqlPreset.a18.f_agent=agent
sqlPreset.a18.f_verb=event
sqlPreset.a18.f_partition=
sqlPreset.a18.f_data1=data1
sqlPreset.a18.f_data2=data2
sqlPreset.a18.f_data3=data3
sqlPreset.a18.f_data4=data4
sqlPreset.a18.f_data5=data5
sqlPreset.a18.f_incr=id

When I edit configuration.properties as follows,  QM throws a SQL exception because the time_id field is now a char type when it used to be an int even though  sqlPreset.a18.use_timestamp=false.

default.queue_log_file=sql:-|a18

sqlPreset.a18.table=asterisk.queue_log
sqlPreset.a18.f_time_id=time
sqlPreset.a18.use_timestamp=false
sqlPreset.a18.f_call_id=callid
sqlPreset.a18.f_queue=queuename
sqlPreset.a18.f_agent=agent
sqlPreset.a18.f_verb=event
sqlPreset.a18.f_partition=
sqlPreset.a18.f_data1=data1
sqlPreset.a18.f_data2=data2
sqlPreset.a18.f_data3=data3
sqlPreset.a18.f_data4=data4
sqlPreset.a18.f_data5=data5
sqlPreset.a18.f_incr=id


Alert:
Database access error.  -  <p> - Exception: it.loway.tpf.common.exceptions.TechException - Errore file/DB: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.queue_log WHERE        (time >= '1333512000' AND time<='1333548294')     AND qu' at line 1 - at it.loway.app.queuemetrics.asterisk.logs.analyzers.AnalizzaLogAstRT.createTemporaryFile(AnalizzaLogAstRT.java:277) - at it.loway.app.queuemetrics.asterisk.logs.analyzers.AnalizzaLogAstRT.loadLogInfo(AnalizzaLogAstRT.java:171) - at it.loway.app.queuemetrics.caricamento.caricaCoda.runDataAnalysis(caricaCoda.java:285) - at it.loway.app.queuemetrics.caricamento.caricaCoda.doRun(caricaCoda.java:74) -

thanks,
Paolo

3

MySQL storage and Qloaderd/Uniloader / Migrate 1.6.2 1.8 Issue

« on: April 04, 2012, 00:11:41 »

Running QM 12.1.2 and 1.8.11 with queue_log realtime. I've altered the Asterisk queue_log table to reflect the 1.8 schema, but left the 1.4/1.6 'data' column as I didn't want to loose the information. I've altered the QM configuration.properties to point to the appropriate default.queue_log_file key to the 1.8 realtime analyzer which specifies data1, data2, data3 etc... columns

The problem I'm having is the QM is not reporting the new queue log data which is being written to the new data1, data2, data3 column on queries since the upgrade, but on older queries prior to the upgrade QM is reporting the data displayed in the Asterisk 1.6 'data' column. How do I resolve this as it seems QM is not reading the right column(s) even though it's configured as such.

thanks,
Paolo

4

Running QueueMetrics / Re: Main, Spill, Wrap

« on: March 22, 2010, 14:55:24 »

That's what I figured. How about adding it as a feature? Since you are allow agents to log into queues from QM it would seem logical to be able to access other agent/queue information in order to determine how the agent is logged in e.g. adding a penalty to the agent.

5

Running QueueMetrics / Main, Spill, Wrap

« on: March 19, 2010, 16:45:20 »

Is there a way to pass the classification of an agent as "Main, Spill, Wrap"  as a parameter when using the Add Queue Member button on the Agent page?  I would like to use it in order to add the user to the queue with a penalty. From what I can tell there is no way to do that so I was going to add some code to Asterisk to query the "code_possibili" table in order to figure out to which classification the agent was assigned for the particular queue.

thanks,
Paolo

6

Running QueueMetrics / Re: Asterisk Error Message on Agent Add Member

« on: March 09, 2010, 14:43:59 »

Yes the agent gets added and removed from the queue properly, but once QM closes the manager session it used to call that piece of the Add/Remove commands from the QM dial plan I see that error in the Asterisk CLI.

7

Running QueueMetrics / Asterisk Error Message on Agent Add Member

« on: March 08, 2010, 22:44:30 »

Every time we use the Add Member button on the live_agent.jsp page we see the following error in the Asterisk CLI:

[Mar  8 21:04:40] ERROR[16832]: utils.c:1175 ast_careful_fwrite: fwrite() returned error: Broken pipe
[Mar  8 21:04:40] ERROR[16832]: utils.c:1175 ast_careful_fwrite: fwrite() returned error: Broken pipe

It shows up for each queue an agent is added too. Any idea why and/or if we should be concerned? We are running Asterisk 1.6.17.

thanks,
Paolo

8

Scripting QueueMetrics / Re: Live Agent Screen

« on: March 05, 2010, 17:46:34 »

That will work.

thanks!

9

Scripting QueueMetrics / Live Agent Screen

« on: March 04, 2010, 17:17:17 »

How would I go about commenting out the "Log on" "Log off" button and renaming the "Add Member" "Remove Member" buttons to "Log on" "Log off". We don't need the agent login buttons. We only want to use the "Add Member" "Remove Member" functionality, but we just want to change the HTML label.

thanks,
Paolo

10

MySQL storage and Qloaderd/Uniloader / Re: Realtime queue_log

« on: February 10, 2010, 15:32:25 »

Would it be possible to see a beta? We are going to put a call center into production shortly and would be interested in using this functionality given our distributed architecture for the system.

thanks,
Paolo

11

MySQL storage and Qloaderd/Uniloader / Realtime queue_log

« on: February 01, 2010, 22:41:07 »

Is anyone using the queue_log realtime functionality in Asterisk 1.6.1 to write directly to the Queuemetrics queue_log table? I noticed that Asterisk doesn't like the field names for time_id, call_id, and unique_row_count. I see that the table can be altered and field names modified in the QueueMetrics configuration, but I'm hesitant to do in order to not create a mess for future upgrades. Will there be any future changes to accommodate this functionality such that it eliminates the need for qloader?

thanks,
Paolo