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 - Vide

Pages: [1]
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
QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics
« on: November 09, 2007, 17:11:42 »
Please clarify the second option you gave me  ;)

5
Realtime Live / Re: Read this first: running Realtime Live
« on: November 09, 2007, 14:10:34 »
Has this changed in QM 1.4.x? Do I need to enable clustering to use this live function?

6
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?

7
QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics
« on: November 09, 2007, 13:38:13 »
Damn... so this is the normal 1.2 behaviour?? But this makes attempts logging just...useless because there will be always big numbers.
Anyway, any idea if this option could be backported to 1.2.x? or we should start thinking about a 1.4 upgrade?

8
Improving QueueMetrics / Re: More flexible reporting
« on: October 30, 2007, 10:59:39 »
About point 1, it would be nice to see the complete historial of a call, for example though which queues did it pass, the times it waited etc etc

9
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

10
QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics
« on: October 30, 2007, 10:15:02 »
This is where tha patch was applied in apps/app_queue.c

1574         if (res) {
   1575                 /* Again, keep going even if there's an error */
   1576                 if (option_debug)
   1577                         ast_log(LOG_DEBUG, "ast call on peer returned %d\n", res);
   1578                 if (option_verbose > 2)
   1579                         ast_verbose(VERBOSE_PREFIX_3 "Couldn't call %s\n", tmp->interface);
   1580                 ast_hangup(tmp->chan);
   1581                 tmp->chan = NULL;
   1582                 tmp->stillgoing = 0;
   1583                 (*busies)++;
   1584                 return 0;
   1585         } else {
   1586 if ( qe->parent->strategy != QUEUE_STRATEGY_RINGALL ) {
   1587 ast_queue_log(qe->parent->name, qe->chan->uniqueid, tmp->interface, "AGENTATTEMPT", "");
   1588 }
   1589
   1590                 if (qe->parent->eventwhencalled) {
   1591                         manager_event(EVENT_FLAG_AGENT, "AgentCalled",
   1592                                                 "AgentCalled: %s\r\n"
   1593                                                 "ChannelCalling: %s\r\n"
   1594                                                 "CallerID: %s\r\n"
   1595                                                 "CallerIDName: %s\r\n"
   1596                                                 "Context: %s\r\n"
   1597                                                 "Extension: %s\r\n"
   1598                                                 "Priority: %d\r\n",
   1599                                                 tmp->interface, qe->chan->name,
   1600                                                 tmp->chan->cid.cid_num ? tmp->chan->cid.cid_num : "unknown",
   1601                                                 tmp->chan->cid.cid_name ? tmp->chan->cid.cid_name : "unknown",
   1602                                                 qe->chan->context, qe->chan->exten, qe->chan->priority);
   1603                 }


and this is an extract of queue_log

1193735323|1193735294.133081|7006|NONE|ENTERQUEUE||$CLIENT_CLID
1193735391|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735392|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735397|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735397|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735406|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735407|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735412|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735412|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735422|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735422|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735427|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735427|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735437|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735437|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735442|1193735294.133081|7006|Local/708@from-internal/n|AGENTATTEMPT|
1193735442|1193735294.133081|7006|Local/705@from-internal/n|AGENTATTEMPT|
1193735447|1193735294.133081|7006|NONE|EXITWITHTIMEOUT|1


705 and 708 where the only two agents logged in the queue 7006 and both of them were talking.

11
QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics
« on: October 29, 2007, 13:15:42 »
In this very queue, rrmemory, but it happens with fewestcalls as well.

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

13
MySQL storage and Qloaderd/Uniloader / Re: Qloaderd 1.7 and Asterisk HEARTBEAT problem
« on: October 26, 2007, 13:29:28 »
Nevermind, I didn't read previous posts, sorry

http://forum.queuemetrics.com/index.php?topic=125.0

14
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?

Pages: [1]