QueueMetrics > MySQL storage and Qloaderd/Uniloader

Ast Primary & Failover instances w/ QM

(1/1)

WRP:
What is the best way to configure QM to deal with an asterisk primary server and failover server deployment scenario. We were going to have each server write to the same partition, but I'm concerned that the state of the failover server (which has the exact same queues and agents) could conflict with the primary server.

Our main concern is: when our secondary, failover PBX comes up, make the transition look transparent in QM. In other words, if the asterisk master dies and calls start routing to the second, let QM accurately show the secondary state, and then the primary once it comes back up.

Best approach?

WRP:
The part that mainly concerns me is this (from the documentation):

"Agent names must be unique throughout the call center; that is, you cannot have an Agent/101 work- ing on Asterisk server A and another Agent/101 working on Asterisk server B, as their data would be mixed and it would be quite hard to tell who did what."

Since our failover server has the same agents on it as the primary, I'm concerned that queue member join/leave activity on the failover server could potentially confuse QM.

QueueMetrics:
If they are failover, that is, they are never active at the same time, you can safely have them both write to the same partition, as long as the qloaders arent active at the same time.
 

WRP:
Is there an option that allows us to have the qloaders active at the same time?

QueueMetrics:
No if they write on the same partition, as they are adding "heartbeats" and are bnot designed to work together.

Navigation

[0] Message Index