Vicidial y Queuemetrics.

[emel_punk]

Queuemetrics its perfect. and our clients are very happy. But happiness is lastless. Now i need to join stadistics with  vicidal. with another asterisk and ive been folllowing the manuals about that. so QM connects perfectly to my vicidialserver,  extract my agents and so. on  i Also  configured vicidal to record the log into  QM database. and great. But ..... when i want to check out the calls  from a Queue in the QM web , shows nothing. Ive checked  the Database -> queue_log and the calls are there.

So  what could it be?

here is the config i did on configuration.properties:


cluster.servers=pixies|mudhoney

cluster.mudhoney.manager=tcp:usuario:clave@10.0.50.14
#cluster.mudhoney.queuelog=sql:VIC
cluster.mudhoney.queuelog=sql:PO1
cluster.mudhoney.monitored_calls=z:/qm_streamcall/server_mudhoney
cluster.mudhoney.callfilesdir=/media/mudhoney/monitor
cluster.mudhoney.audioRpcServer=
cluster.mudhoney.agentSecurityKey=

cluster.pixies.manager=tcp:usuario:clabv@127.0.0.1
cluster.pixies.queuelog=sql:P002
cluster.pixies.monitored_calls=z:/qm_streamcall/server_trix
cluster.pixies.callfilesdir=
cluster.pixies.audioRpcServer=
cluster.pixies.agentSecurityKey=





Thanks !!!

[QueueMetrics]

Look at the DB table "queue_log" and make sure that you have data in both partitions.

[emel_punk]

what do you mean with partition? the two servers?
ive checked queuemetrics DB->queue_log table
and this is what  ive found.


http://i279.photobucket.com/albums/kk121/emel_punk/fotoqm.jpg


my calls from the other server are there in QM.

[QueueMetrics]

I see only the data that ViciDial generates, but nothing else.....

Try running

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

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

[emel_punk]

this is the mysql output:

mysql> SELECT partition, count(*) FROM queue_log GROUP BY partition;
+-----------+----------+
| partition | count(*) |
+-----------+----------+
| P01       |       26 |
+-----------+----------+
1 row in set (0.00 sec)

[QueueMetrics]

Ok you need to upload data as "P002" from your "regular" asterisk server via qloaderd as well to the same table.

[emel_punk]

Hi there.

I,ve been trying to do that my vicidial insert the queue log into my mysql  database  as P01. But i dont see that option on vicidial. also i dont know how can i set it up that especific parameter.
so i change the next line in configuration properties.

cluster.blackflag.queuelog=sql:P01

so ive guess that now i can see my info into QM but it doesnt.

also ive try to follow the manual, to CHeck MYSQL database status. ive set up my user  and added USR_MYSQL  to User key but i dont see any mysql new page on edit settings.

so any helps :

[marcos]

Hi.

I'm just reading your first post and I've found something strange:

cluster.servers=pixies|mudhoney

cluster.mudhoney.manager=tcp:usuario:clave@10.0.50.14
#cluster.mudhoney.queuelog=sql:VIC
cluster.mudhoney.queuelog=sql:PO1
cluster.mudhoney.monitored_calls=z:/qm_streamcall/server_mudhoney
cluster.mudhoney.callfilesdir=/media/mudhoney/monitor
cluster.mudhoney.audioRpcServer=
cluster.mudhoney.agentSecurityKey=

What I'm reading is that the cluster.mudhoney.queuelog key is set to sql:PO1 ... where O is an O not a zero...
Could be that the problem?

Thanks,
Marco.

[emel_punk]

No it doesnt work.

 

[QueueMetrics]

What is the situation now?

[emel_punk]

well its the same from the beggining.
ive just check  the manual an wanted to make sure everything was as it should be following the manual.
and still no worked. plus i wanted to activate mysql info page with plugin USR_MYSQL for admin user and aitn work either.

I have all vicidial info in queue_log table:

running this :

mysql>  SELECT partition, count(*) FROM queue_log GROUP BY partition;
+-------------+----------+
| partition | count(*) |
+-------------+----------+
| P000      |      410 |
| P01        |       50 |
+------------+----------+
2 rows in set (0.03 sec)

where P01 its vicidial.



 

[QueueMetrics]

Yes you have data in the database, and this is good.

Likely, you have to set:

default.queue_log_file=cluster:*

So that QM knows it's working with a cluster.

[emel_punk]

Thanks!!!!!!!!
It worked !!!
 

[QueueMetrics]