QueueMetrics forum
QueueMetrics => QueueMetrics installation => Topic started by: AB_FCR on October 15, 2012, 21:36:35
-
I just sent a similar question to support, but was hoping to get a wider audience. I use queuemetrics in a fairly busy call center, that is about to get busier during the holidays. Support previously suggested that I could try out astmanproxy to help lessen the load on the AMI, that other users have had good success with it.
I was wondering if anyone had any guidance to get astmanproxy working with queuemetrics. When I try to pass commands now I receive a "QueueMetrics cannot send the command to the PBX" error.
-
I am aware that we have a few clients using proxies, though I'm not sure this is exactly AstManProxy.
-
Well if anyone has any suggestions, including other proxies to use Id be grateful. I do not understand the AMI well enough to really move forward.
-
The error received in the AMI tester is, edited slightly.
AMI URL: tcp:login:password@192.168.1.1:5038
Problem: AMI query failed
Exception: it.loway.tpf.common.exceptions.TechException Stack trace: Error TCP connecting to: 192.168.1.1:5038 timeout: 2000ms
Exception: it.loway.tpf.common.exceptions.TechException Stack trace: Unknown ACM version: 'Asterisk Call Manager/1.27 ' at it.loway.app.queuemetrics.asterisk.manager.DataSources.AstManagerThroughSocket.openSocket(AstManagerThroughSocket.java:131) at it.loway.app.queuemetrics.asterisk.manager.DataSources.AstManagerThroughSocket.openDataSource(AstManagerThroughSocket.java:53) at it.loway.app.queuemetrics.asterisk.manager.AstManager.connectFromUri(AstManager.java:73)
AMI Dialog took 220 ms
-
I understand you patched AstManProxy to go past this error - what did you change?
-
I got your email, so Im pretty sure you already know this. But for anyone else that may be interested I had to change the proxy banner and the proxy version to get this to work inside of astmanproxy.
Inside the makefile i changed the version to read as 1.0 instead of 1.27. Also I changed the Proxy_Banner to say "Asterisk Call Manager" instead of "Asterisk Call Manager Proxy".
-
Thanks - so if we add detection of "Asterisk Call manager proxy" we know we can ignore the version.
This makes it easy to fix!