We currently have queuemetrics 1.* working on Asterisk 1.6., since we just bought a new server we decided we should update everything. So we downloaded Elastix 2.3.0, which comes with CentOS, Asterisk, and a few other dependencies, and tried to install Queuemetrics using 'yum install queuemetrics'. First of all, everything installed, but now we have been dealing with this unfamiliar asterisk error. We ensured that the dbtest check out as well as the AMI. All is well as far as that goes. Then we started checking into extensions_queuemetrics.conf and realized that we needed to include it in extensions.conf. After we did that this is the error that we are receiving when we try to log an agent on:
-- Executing [20@queuemetrics:1] Answer("Local/20@queuemetrics-b28c;2", "") in new stack
-- Executing [10@queuemetrics:1] Answer("Local/20@queuemetrics-b28c;1", "") in new stack
-- Executing [10@queuemetrics:2] Wait("Local/20@queuemetrics-b28c;1", "10") in new stack
-- Executing [20@queuemetrics:2] NoOp("Local/20@queuemetrics-b28c;2", " "QM: Logging on Agent/6877 to extension 6877@from-internal made by 'Agent/6877'" ") in new stack
== Spawn extension (queuemetrics, 20, 3) exited non-zero on 'Local/20@queuemetrics-b28c;2'
== Spawn extension (queuemetrics, 10, 2) exited non-zero on 'Local/20@queuemetrics-b28c;1'
Oddly enough Queuemetrics has a green alert that says the operation successfully completed, but asterisk still shows that no one is logged in. I checked out so many posts and none of them answered my queuestion. Let me restate it for clarification: We are trying to log an agent into asterisk via Queuemetrics and while Queuemetrics shows that the action completed Asterisk doesn't recognize any agents logged in. Any help would be appreciated.
