QueueMetrics > QueueMetrics installation

"The extension to monitor must be defined" error with live call monitor

(1/2) > >>

zulugrid:
I'm trying to get live call monitoring to work between QM 1.5.3 and Asterisk 1.4.22.

I have all of my agents/queues configured. I'm able to see calls under "Calls being processed" and they have the live call monitor icon. When I click the icon, it pops up a window with a URL like:

--- Quote ---http://server:8080/queuemetrics/qm/popup_audiomon.jsp#7224@from-internal&POPUP_server=&POPUP_direction=I&cachebreak=5731543721243012752940
--- End quote ---

This window has "Agent code" set to "local/", "Agent name" and "Agent extension" are blank, and a box to enter my extension. When I enter my extension and click "Monitor now", I get this error:

--- Quote ---The extension to monitor must be defined
--- End quote ---

Our agents come up like local/#7224@from-internal in QM, which I think is a bit different than most installations.

Any idea how I can "define the extension"? I currently have "-" as the terminal for each of my agents. Or any other ideas on what to try?

Thanks!!

QueueMetrics:
I think there is something wrong with the URL, so it basically dos not find the data it needs and aborts.

Can you try enablibg agent rewriting in the configuration, so that instead of local/#1234@context QM will see agent/#1234 ?

Also, if you could send over a piece of queue_log, we'd love to test it in our labs.

zulugrid:
Thanks for the quick response!

I modified the config to rewrite to agent/#1234, and modified an agent's Asterisk agent code to match, and then clicked the monitor icon. The window that came up had this URL, and is broken in the same way as before:
http://server:8080/queuemetrics/qm/popup_audiomon.jsp#7210&POPUP_server=&POPUP_direction=I&cachebreak=7881132531243344211116

A sample queue_log can be found at:
http://www.affinity4.com/misc/queue_log.zip

Thanks!

QueueMetrics:
I think that the problem is that the "#" is a magic symbol for HTML and should be encoded.

I am adding this as a bug #745 so we can have it fixed.

We have taken a snapshot of the file.

PS. are you using Fonality?

zulugrid:
We were using Fonality at one point, but use Elastix now. We ported some of Fonality's "neoagent" dial plan to Elastix.

Please let me know when this bug is fixed! Thanks!

Navigation

[0] Message Index

[#] Next page