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 ... 45 46 [47] 48 49 ... 202
691
Thanks Barry! :)
I guess that if you charge 1$ for each time this question has been raised, you are going to have a neat second income  ;D

692
 ;D

693
MySQL storage and Qloaderd/Uniloader / Re: MySQL performance issues
« on: August 09, 2011, 10:26:47 »
It is weird that this happens - it is not supposed to since data is insert-only. Or do you have processes that edit/update that table?

694
This is so because, well, Asterisk queues are unaware of outbound calls. I would not know how to force the state as in_use.

695
We need the queue_log, not the CLI output  :)

696
Running QueueMetrics / Re: Pause Reaon Field (Real-time Monitoring)
« on: August 09, 2011, 10:22:02 »
 ;D

697
Running QueueMetrics / Re: it is normal this behavior?
« on: August 09, 2011, 10:21:20 »
I'd say that the blind transfer appears nowhere in the log, so there is no way for Qm to report it.

698
Running QueueMetrics / Re: working with outgoing calls
« on: August 09, 2011, 10:19:46 »
All right.  ;D

We have outbound agents and inbound agents, the inbound agents login with agentlogin, so they appear connected in real time page, and when they do pause, we can see the status and when i do my reports all those status appear on it so  I want to see my inbound agents in the same way as inbound agents.

 ???

You could create "fake" queues for them to appear under, so tehy can login to "q-123" when they use campaign "123".

699
Running QueueMetrics / Re: Logrotate & Queuemetrics Issue
« on: August 09, 2011, 10:18:17 »
You should use a sliding window that is a couple of hours longer than an agent's longest shift, e.g. if they do 6 hours, set it to s8 for safety. Consider that the longer the sliding window, the more load QM takes when running a report.

700
This is not something that is inferred from the log, so you have to configure it in Asterisk and then edit the queue-agent association in Qm assigning each agent to their level.

701
Running QueueMetrics / Re: Individual Agent Reports are not working
« on: August 09, 2011, 10:15:34 »
I would remove the agent's name form freePBX and just leave the code - Qm will do the replacement for you.

702
Please inspect the CSV file Qm generates ans check what is written there.

703
When I ran the queuePartialUpdater tool (found in /usr/local/qloader) against the file, it did not restore items that were greater than the current timestamp (aug 2, 2011), the missing data were for July 23 and July 24th, 2011...

Is there a workaround for this?

The QueueLogPartialUpdater is meant to overcome the "problem" the qloader has, that is that it only inserts NEWER lines.

Are you sure that you have lines in your file but they are not inserted in the DB? given your previous history, I would not be surprised if Asterisk just stopped writing to all files.


704
I am sure this is 100% caused by Queuemetrics install. It's probably that the yum repository doesn't configure the log rotate properly.

THIS IS A BUG. PLEASE FIX.

The handling of the full log is completely outside the scope of QM and left to the distro.

705
This is not a bug - as it is not normal for a call center to have calls that waiter 45 minutes, QM thinks they are an anomaly and hides them. This can be fully configured as explained here: http://queuemetrics.com/faq.jsp#faq-030-disappear

Pages: 1 ... 45 46 [47] 48 49 ... 202