Topics

1

Running QueueMetrics / Magic wand ?

« on: July 02, 2012, 19:54:05 »

Hi

I don't undersatnd where and how to configure QM so it can talk to Asterisk via AMI, and so having the wand working.

Right now I always get a "QueueMetrics cannot send the command to the PBX." error.

Thanks

2

MySQL storage and Qloaderd/Uniloader / Qloaderd missing some ADDMEMBER/REMOVEMEMBER

« on: December 14, 2011, 18:13:20 »

Hi

I've been experiencing from time to time random "holes" in our queue_log data. I mean, agents login/logoff, action is recorded on asterisk's queue_log logfile, qloaderd syas that it has loaded all data but the data never appears in MySQL. Any idea on how to debug this issue? I cannot find a way to reproduce it at will

3

MySQL storage and Qloaderd/Uniloader / Create reports from different partitions

« on: October 18, 2011, 16:30:43 »

Hi

is there a way to have the quick reports sucking data from a specific partion, based on the queues? I mean, I have a single QM installation getting data from different Asterisk servers, everyone with its qloaderd with a different partition set (P01, P02, P03 etc). In custom reports I can choose sql:P02 for instance but the quick reports do not work like that, at least until you did a custom report using your custom partition.
Is there a way to set the partition for the queu/report/user logged in?

Thanks

4

Outbound and QueueMetrics / queueDial.agi and outbound caller ID

« on: November 09, 2007, 14:00:45 »

Forewords:
we are running a freepbx installation where we configured every agent that needs outcoming call to have an own caller id displayed on customer's phones. I did this by configuring the "Outbound CID" in the extensions configuration page. Now, this works perfectly with normal outbound calls.

Enter queueDial.agi: I've configured it to work correctly (following queuemetrics website instructions) and it works as expected (calls are reflected in statistics) but now the Oubound CID field is completely ignored, and everyone is appearing with same, default number. What do I have to touch to fix this?

5

Improving QueueMetrics / Queues timeouts report

« on: October 30, 2007, 10:57:02 »

Usually in a callcenter installation, you have more queues in which a call can pass through if it isn't answered by the first queue. And a queue in a dialplan can have more than one failover

So my suggestion is to have a visualization of failover's statistics.
For example, something like this:

QUEUE 1000

Timeouts to queue 1010: 45
Timeouts to queue 1011: 21
Timeouts to queue 1012: 10
Timeouts to queue 1013: 37

6

QueueMetrics installation / QM, ATTEMPTS patch and strange statistics

« on: October 26, 2007, 16:44:15 »

Hi

we have an Asterisk 1.2.24 installation with the ATTEMPTS patch to app_queue.c and a recompiled Asterisk, and in general it works.
Anyway, I have noted a very strange behaviour. Situation:
- queue with 4 agents, everyone is busy talking
- asterisk console reports this:

Local/707@from-internal/n (dynamic) (In use) has taken 1 calls (last was 191 secs ago)
Local/708@from-internal/n (dynamic) (In use) has taken 3 calls (last was 330 secs ago)
Local/705@from-internal/n (dynamic) (In use) has taken 4 calls (last was 282 secs ago)
Local/704@from-internal/n (dynamic) (In use) has taken 17 calls (last was 138 secs ago)


so these are 4 SIP channels and Asterisk know that the 4 are busy.
- I have the

ringinuse = no

option in the appropriate queue in queues.conf but nonetheless ATTEMPTS are appended to the queue_log! This is the really annoying, that makes ATTEMPTS statistics completely useless in my QM installation: if all agents are busy, as said, and a new call enter the queue, an ATTEMPT is recorded for EVERY agent, every N seconds where N is the "retry" value in queues.conf.
This doesn't have to work like this, agents are busy because they are talking, not because they are rejecting calls/not answering. Anyone experiencing something similiar?
Is my configuration wrong somehow? or is this considered "normal"? I repeat: asterisk correctly detect if th sip channel is in use or if it isn't.

7

MySQL storage and Qloaderd/Uniloader / Qloaderd 1.7 and Asterisk HEARTBEAT problem

« on: October 26, 2007, 13:28:19 »

Hi all

since I've upgraded to qloader.pl 1.7 it happens a strange thing: when the Asterisk is quiet and it's only writing HEARTBEAT events in the queue_log, qloader loads these events in mysql, as it should. But then when traffic starts again in Asterisk, if the queue_log was rotated (as always happens on weekends), the script cannot detect the new file and so it's always inserting HEARTBEAT events in asterisk. So to solve I've to stop the script, delete all HEARTBEAT events in mysql and restart qloader.pl.

This didn't happen with older qloader, as far I can remember... do I have to send a signal to the script when rotating the logs?