QueueMetrics > Running QueueMetrics

Cluster and call recordings.

(1/1)

trymes:
I recently set up a new QM server that monitors two Asterisk servers in a cluster. The queue_log data is properly written to the QM DB by qloaderd, and everything works just fine, except I have no access to recorded call files.

So, I have mounted the /var/spool/asterisk/monitor directories via NFS and specified the locations in the configuration.properties file. I can successfully browse and copy files from the NFS directories via the command line. However, when I click on the magnifying glass icon for call details while the NFS shares are mounted, QM hangs and does not pull up the details (the popup opens, but no data is populated). If I unmount the NFS shares, QM is once again responsive.

What have I done wrong?

Tom

mirkox:
Hi Tom,

can you copy here how you configured configuration.properties in order to get recordings from the two machines?
Also, are the recordings divided by day?

Mirko

trymes:
Thanks Mirko. I have included the relevant portion of the cluster setup below. The recordings are indeed stored by day, and I had not changed the audio.server directive before (I presumed that "by day" would have been the default). Anyhow, I just changed it to "audio.server=it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay" and it has not resolved the issue.

Tom


--- Code: ---# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API
cluster.servers=server1|server2

cluster.server1.manager=tcp:admin:elastix456@10.100.1.2
cluster.server1.queuelog=sql:P002
cluster.server1.monitored_calls=/mnt/server1/
cluster.server1.callfilesdir=
cluster.server1.audioRpcServer=
cluster.server1.agentSecurityKey=
cluster.server1.websocketurl=ws://10.1.1.2:8088/ws
cluster.server1.rtcWebBreaker=false

cluster.server2.manager=tcp:vBetW45J3092htgxbwl:amp111@192.168.0.3
cluster.server2.queuelog=sql:P001
cluster.server2.monitored_calls=/mnt/server2/
cluster.server2.callfilesdir=
cluster.server2.audioRpcServer=
cluster.server2.agentSecurityKey=
cluster.server2.websocketurl=ws://192.168.6.3:8088/ws
cluster.server2.rtcWebBreaker=false

--- End code ---

mirkox:
Hi Tom,

you should specify also the audioRpcServer field.

cluster.server1.audioRpcServer=
cluster.server2.audioRpcServer=

Probably the same you haave in default.audioRpcServer, otherwise give a look here for details: http://manuals.loway.ch/QM_UserManual-chunked/ch22.html

The one for you should be it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay; also if the recordings are divided by day you can set year, month, day variables in the path in order to make the search way faster, especially with remote mounts:

example:
cluster.server1.monitored_calls=/mnt/server1/%YY/%MM/%DD

     %YY → the 4-digit year when the call was made
    %MM → the 2-digit month when the call was made
    %DD → the 2-digit day of month when the call was made
    %SE → in a clustered environment, the server name (all lower case)
    %QU → the queue name (all lower case)

trymes:
To be clear, are you suggesting that I set:


--- Code: ---cluster.server1.audioRpcServer=it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay
cluster.server2.audioRpcServer=it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay
--- End code ---

I cannot copy the default.audioRpcServer setting, as there is no such line in the configuration file.

Thanks for the tip on the call path variables!

Tom

Navigation

[0] Message Index