QueueMetrics > Running QueueMetrics

Using clustering

(1/1)

tonils:
I have the following setup
sip01, sip02, sip03, sip04: four Asterisk servers supporting agents ourbound calls
pbx01: an asterisk server providing PBX functions and inbound calls
qm01: QM 1.6.0.2 server

The agents phones are registered to one of the sip servers (which one is determined by the extention number) so there is a random distribution of agents across the four servers.

All the QM logic is on pbx01. When an agent logs in, they select pbx01 and click the "Log on" button. The display reports "Agent is currently logged on..". This information is in partition P006. Pausing and log out also works this way. When the agent makes a call, the call comes from one of the sip server (partition P001-P004).

The agent's calls are only visible on the agent page when the sip server that made the call is selected. Is there a way to get a "consolidated view" on the agent page?

Tony

QueueMetrics:
How is your database storage set up?
It may be because QM tries to conserve resources when running agent page reports.

tonils:
Not too sure what you mean by "How is your database storage set up?"

I have one MySQL server (qm01) with qloaderd.pl on each server (sip01, sip02, sip03, sip04 and pbx01) writing to uniquie partitions (P001, P002, P003, P004, P006 respectivly) in the same queue_log table. I have the magic "default.queue_log_file=cluster:*" in my config file and each of the server setup in "cluster.servers=sip01|sip02|sip03|sip04|pbx01" so "cluster.sip01.queuelog=sql:P001", "cluster.sip02.queuelog=sql:P002", etc

Is that what you are asking?

Tony

QueueMetrics:
Yes that was the information I was looking for,

At the moment, it is not possible for the agent to look on other partitions but the main one.
We are adding this as a feature request - code #1106

Navigation

[0] Message Index