QueueMetrics > Running QueueMetrics
Is it possible to see Extension being called as it's ringed?
QueueMetrics:
--- Quote from: torontob on April 08, 2011, 15:20:16 ---That's why maybe QM should start reading EVENTs. I always wondered why you chose Queue Logs?
Is it because different versions of Asterisk change Events output and it would have been ton of work to keep up?
Thanks
--- End quote ---
It is a ton of work to keep up with differences in the queue_log as well. ;-)
The idea is that QM is decoupled from Asterisk, so it does not cause additional load on the server.
torontob:
But it's also so easy to add an:
--- Code: ---exten = _X.,n,System(echo "Ringing" >> /var/log/asterisk/queue_log)
--- End code ---
to incoming context and so it adds the Ringing line to Queue log. This can be easy work-around rather than reading events and only other change is to be made on the java-script running the dashboard to pick this up. Probably if the 5 second is lowered to 1 or 2 seconds then this feature would make more sense as it's time sensitive.
-Bruce
QueueMetrics:
It is true, if you have Local agents; not so easy for other ones. Maybe using a queue macro?
Anyway it is an interesting idea....
torontob:
So let's add it as a quick feature (to be enhanced in future version) and assign it a bug #. ;)
QueueMetrics:
We basically have the logging in place, it is called AGENTATTEMPT and was before Asterisk standardized on RINGNOANSWER.
See http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s23.html - "23.6. Enabling ACD call attempts recording on Asterisk 1.0 and 1.2".
The problem is that if there are both, tracking does not work.
So we should probably add a config option that turns off RINGNOANSWER reading (if you manually added AGENTATTEMPT) and it should be working fine.
We track this as bug #1299.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version