Messages

2956

Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup

« on: April 26, 2007, 15:11:26 »

I am still wondering what happens - can you please try this:
- remove the file /var/log/asterisk/agi-log.txt
- try placing exactly one call through queueDial and have the remote hangup

After this, have a look at the /var/log/asterisk/agi-log.txt file and posty the results you see.

What I think tentatively is this: the call goes through, but as the DIALSTATUS is filled, the call is repeated. Bt I cannot say much without having a look at the log....

2957

Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup

« on: April 26, 2007, 10:02:57 »

How do you set up the outgoing channel to handle the fail-over?

2958

Running QueueMetrics / Re: Reports - Display Average call length in minutes

« on: April 26, 2007, 09:13:03 »

It's not possible at the moment, but if anybody else is interested, we'll add it to the TODO list. If that is really important for you, you may consider a customization job from us.

2959

MySQL storage and Qloaderd/Uniloader / Re: queue_log table fields

« on: April 26, 2007, 09:11:27 »

That's good

2960

Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup

« on: April 26, 2007, 09:10:38 »

This is strange: queueDial.agi is being used on hundreds of sites.... Can you be a bit more precise about which kind of channels you are using for dial out? and what happens in the dialplan on your error condition: does the queueuDial.agi terminate and pass control to other parts of the dialplan?

2961

QueueMetrics news / QueueMetrics 1.3.4 released today.

« on: April 18, 2007, 14:25:00 »

Today we release QueueMetrics 1.3.4. This release offers experimental realtime monitoring using the Manager API, that can be run for a single server or a cluster of servers.  This implementation is experimental, so it is not meant to be used in production environments. We created a special forum section to discuss this topic.

This release also adds a bit of functionality and fixes a number of bugs that were present in 1.3.3, and notably:

- EXPERIMENTAL realtime cluster support. This feature lets you poll a set of Asterisk server through the Manager API and create and unified view of their queue subsystem, as you usually do with QueueMetrics. (#75)
- The cluster support now tracks correcly outbound queues as well by using the updated queueDial.agi script (#76)
- A raw set of all calls processed and agent session can now be extracted through the XML-RPC interface. The Query URL is extracted as well. (#78)
- By popular demand, the length of the hourly call breakdown can be changed to any other interval, e.g. 30 minutes, 15 minutes, etc. (#79)
- A bug was fixed that made agents appear as UNK on the realtime page - it was introduced in 1.3.0 (#90)
- Companion utilities Qloaderd and QueueDial.agi have been updated as well


You can download the latest version immediately from the downloads page, together with the 98-page User manual. As an alternative, if you run RHEL/CentOS/TrixBox/AAH, you can install it automatically using yum - see the installation page.

If you would like to write a language pack for your native language, it's very easy and it only takes a couple of hours' work. See the Translating QueueMetrics document from the Downloads page.

We are looking forward to version 1.4 of QueueMetrics for major improvements, including a new high performance analysis engine.

2962

The tavern / Re: Where is it?

« on: April 18, 2007, 13:04:19 »

Shht.... It's supposed to be released later today

2963

MySQL storage and Qloaderd/Uniloader / Re: Odd character in database field

« on: April 17, 2007, 22:56:40 »

The first thing you should look at is if the queue_log line contains some weird characters. Then I would check that you have Qloader 1.3 installed, it contains some whitespace-trimming routines that should handle the case.If nothing works, we'll open up a new bug and fix this

2964

Running QueueMetrics / Re: Can a user change his password by himself?

« on: April 17, 2007, 22:52:48 »

No, the user cannot do this at the moment: we just added it to the wish list as bug #96. :-)

2965

General Asterisk configuration / Re: Managing Asterisk REAL queues and agents from QueueMetrics

« on: April 17, 2007, 22:52:10 »

Hello,
I confirm what you say: QueueMetrics was created as a read-only tool in order to avoid any impact on the server, where you may configure things in a thousand different ways. To create queues and agents, we suggest a decxente GUI, like Voiceroute's Druid.

Of course, you do not want to do all the work wtwice: so QueueMetrics has a way to pull data from an existing set of Asterisk config files an set up automatically: this is the Configuration Wizard you see in the main page.

2966

QueueMetrics installation / Re: Database Connection

« on: April 17, 2007, 22:49:38 »

I believe you simply have no queues defined!

2967

MySQL storage and Qloaderd/Uniloader / Re: queue_log table fields

« on: April 17, 2007, 16:11:07 »

Gee, if only all problems were so easy to solve

2968

MySQL storage and Qloaderd/Uniloader / Re: queue_log table fields

« on: April 16, 2007, 14:34:11 »

Aren't you querying the wrong queue(s)? if you were, everything would be fine, but no data would show up....

2969

Outbound and QueueMetrics / Re: Installing outbound queues for Asterisk on TrixBox

« on: April 15, 2007, 18:54:27 »

The AGI shall be put in Asterik's AGI directory, usually as /var/lib/asterisk/agi-bin/queueDial.agi - see http://queuemetrics.com/faq.jsp#faq-014-agi for help in having it start.

Then you will use a dialplan like the following....

Code: [Select]

exten => _9XXX.,1,SetVar(MY_QUE=${EXTEN:1:3})
exten => _9XXX.,2,SetVar(MY_NUM=${EXTEN:4})
exten => _9XXX.,3,SetVar(MY_AGENT=${CALLERIDNUM})
exten => _9XXX.,4,NoOp,Ag: ${MY_AGENT} N: ${MY_NUM} Q: ${MY_QUE}
exten => _9XXX.,5,MixMonitor(Q-${MY_QUE}-${UNIQUEID}.wav|b|)
exten => _9XXX.,6,DeadAGI(queueDial.agi|${MY_NUM}|Zap/g0/${MY_NUM}|q-${MY_QUE}|Agent/${MY_AGENT})
exten => _9XXX.,7,Congestion
So that your agents will type 9 123 555555 to dial 555555 on outbound queue q-123. This makes it possible for all agents to use different outbound queues.

Please make sure that the queueDial.agi actually runs, as Asterisk is not very clear on whether it's actually executing it or what

2970

General Asterisk configuration / Re: Queue Metrics and Trixbox 2

« on: April 15, 2007, 18:50:22 »

It seems like it's the season for a bad flu here.... 2 people will be in sick leave tomorrow :-(