QueueMetrics > Running QueueMetrics

Is it possible to see Extension being called as it's ringed?

<< < (3/4) > >>

torontob:
Hmmm....We are using Asterisk 1.6.x. I didn't change any of the settings so basically I should see which Agent is ringing but that is not happening.

Did you say there is a parameter I have to set to off (AGENTATTEMPT) for this to work on Asterisk 1.6? What is the name of the parameter in the configuration.properties file?

Thanks

QueueMetrics:
No there is an old patch for Asterisk 1.0 and 1.2 but we do not recommend running it on 1.6.

QueueMetrics:

--- Quote from: QueueMetrics on April 13, 2011, 09:10:07 ---We basically have the logging in place, it is called AGENTATTEMPT and was before Asterisk standardized on RINGNOANSWER.

--- End quote ---

After giving this a bit of consideration, this is not very easy to do, because
a macro can only be called when an agent answers, and so this is not
generalizable. We can of course make it work for LOCAL channels, or we could
write a very simple, trivial patch to the app_queue module, but this would make
deployment of a QM system a bit more complex for "canned" systems, and this is
not what we would like to do.


On the other side, people are interested in ringing to know whether the call is
being mis-routed or agents are not answering thus causing delays. We already
have this information, so this is something that we are going to implement as
issue #1306.


If a call, while unanswered, has failed attempts, I would display the name of
the agent that was called without success and maybe the duration or the number
of failed attempts. These would be displayed in red. This way you get kind-of
the same information you have when ringing.

torontob:
That is very much needed and brilliant. In fact the aim of this feature like you said is to see if a call is misrouted or not. And that is what we get from Supervisors. They continuously ask where the call went. With that kind of information, we should be in much better shape.

When do you expect this bug to resolve?

Regards

QueueMetrics:
I expect this to be a part of the next release (in about one month or two).
BTW, the basic plumbing at the parser level has been written last week; we will also allow "ringing" in case you are able to configure it at the Asterisk level.
 

Navigation

[0] Message Index

[#] Next page

[*] Previous page