QueueMetrics > Scripting QueueMetrics

QM.realtime issue - The result data is frozen

(1/1)

abressan:
Hi all!

I'm using the XML-RPC interface to get information about calls being processed and agents logged in. The goal is to show that data, nearly real-time, in a small widget that agents will have loaded in their computers.

All went fine for a day or so in my tests, but now the data that I get from the QM.realtime command got frozen: it's always coming exactly the same, and it's not reflecting what's really happening on Asterisk. No calls are being "detected", neither the agents logins or logoffs.

I don't get any error either, just the same static information all the time.

I did try resetting Asterisk (Trixbox), and also queuemetrics alone, to no avail.

I'm using just one server for Asterisk and queuemetrics (installed it on the Trixbox using yum).

any ideas about this?


Thanks a lot in advance!

Best regards,

Aldo

QueueMetrics:
First thing: if you look at the realtime page of QM, is data being shown as it happens or is it frozen?

Second thing: are you sure your XML-RPC lib is not caching the connection URL?

 

abressan:
The realtime page is not showing data.

I did try different ways to get data from XML RPC, both from Python and Java, and always got the same.

I also try shutting down TrixBox, and even ridiculous tests like asking for data when Trixbox was down... case in which, of course, I got only errors and no data.

However, I do believe that the problem is not with XML RPC itself, but with QueueMetrics not getting the data from Asterisk... probably some configuration problem with QueueLoader or something in that area.

This is happening after one day of correct working... so, definitely I have something wrong in my setup...

QueueMetrics:
I think so. You should see the realtime page working.

If it's not, likely it's one or more of the following things:
- you are asking for the wrong queue
- the qloaderd is not working
- the time on the Asterisk server is far off from the time on the QM server
- you are reporting from the wrong partition

Navigation

[0] Message Index