Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - QueueMetrics

Pages: 1 ... 51 52 [53] 54 55 ... 202
781
We have no way to duplicate this behavior on a Mac.

782
No but in case you have Local channels this is easy to set up, so we are working on a way to use the queue_log writing a custom RINGING state.
If you do not want/cannot setup Asterisk, you get the last called agent anyway, so most users will benefit from this without making any changes.

783
Ah now I understand! thanks for the very detailed explanation.
It looks like a bug to me. We are fixing it for the next release.
For your reference, this is bug #1313.




784
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.
 

785
No because the payroll is meant to be run centrally by a specialized use. What you can do is for them to run a report, so they can see when they logged on and off and then ask a supervisor to make changes if for some reason that ends up being incorrect.

786
You shoud see some difference between the ones you set up manually and the ones you import. If you want, post a screenshot of the agent config page for both.

787
You mean that if you add the key to the class it does not work? it is weird.,

788
You can do both - recording is usually enabled at the Asterisk level, and QM is able to retrieve those recordings when you see that call. This is usually easier to do:

http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s23.html#Listening_to_recorded_calls_using_QM

listening to live calls is also possible, but again this requres integration a the Asterisk level and it is a bit more complex - see e.g. http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s23.html#Listening_to_live_calls_Unattended_Call_Monitoring

If you look on the forums, you will see that many user suse either (or both) and were successful in setting them up.

790
Running QueueMetrics / Re: Outbound not being recorded
« on: April 27, 2011, 11:24:22 »
Looks like an Asterisk issue to me.

791
Just edit the class and add the key SUPERVISOR to it?


792
We basically have the logging in place, it is called AGENTATTEMPT and was before Asterisk standardized on RINGNOANSWER.

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.


793
Running QueueMetrics / Re: Reports not updating
« on: April 26, 2011, 10:34:27 »
So basically you could go to the text file instead for the moment?

794
Running QueueMetrics / Re: No live monitoring icon
« on: April 26, 2011, 10:33:33 »
If you need to have a longer-lasting wizard, you should use a longer page refresh time. Or maybe we should stop events when the popup is displayed? :)

795
Running QueueMetrics / Re: Outbound not being recorded
« on: April 26, 2011, 10:31:50 »
It looks correct so far.... is the file/files for MixMonitor created at all?
Which version of Asterisk is that?

Pages: 1 ... 51 52 [53] 54 55 ... 202