Messages

2971

Realtime Live / Read this first: running Realtime Live

« on: April 15, 2007, 18:04:51 »

The realtime live support in QueueMetrics 1.3.4 is EXPERIMENTAL - use it at your own risk. We would like to hear from you on how to improve it and problems you should encounter.


The Realtime Live feature lets you monitor one or more Asterisk servers through their Manager interface, letting you know the state of queues, callers and agents in real-time. This data is loaded straight from Asterisk, so it should always reflect the current status, and is meant as a complement and not a replacement of the existing Realtime panel. This happens in the context of QueueMetrics' security model, so you can fine-tune who can see what on your system.

This feature is at the moment unrestricted in terms of monitored agents, but the one implemented in 1.3.4 is a time-limited version that will be improved in future versions.

Starting Realtime Live
First of all you have to configure all of your server to allow access from QueueMetrics through their Manager API. You should change the /etc/asterisk/manager.conf file in order to allow access to the server running QueueMetrics and to define an user/password pair for QM to connect.
The following example opens an account for a user called queuemetrics with password bingo:

Code: [Select]

[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

[queuemetrics]
secret=bingo
read=system,call,log,verbose,command,agent,user
write=system,call,log,verbose,command,agent,user
Once that is set up, you should edit the configuration.properties in QM in order to set up the members of the cluster:

Code: [Select]

# Cluster to poll for RT data
# list of pipe-separated members of the cluster
cluster.servers=aleph|trix

cluster.aleph.manager=tcp:queuemetrics:bingo@10.10.3.5
cluster.trix.manager=tcp:admin:amp111@10.10.3.100

The cluster.servers property tells QM this cluster is made up of two boxes which names are aleph and trix. We then create the connection strings, that look like tcp:username:password@servername. You can have as many cluster members as you like.

Now, install QM 1.3.4 and make sure your user has the security key RTLIVE.  Restart QueueMetrics.

To access the realtime live page, click on Realtime, then on the Live tab. That's it. You should see all activity (for selected queues, as always) on all members of the cluster.

In the case you should find some strange behaviour, you can see a raw copy of the data Qm is reading by accessing the page /queuemetrics/dbtest/mgr.jsp. If you report any error on this new functionality, make sure to add a printout of the mgr.jsp page so we can debug what went wrong.

Outbound queues
The new realtime live page is able to monitor outbound queues as well as inbound queues. To do this you have to use the new queueDial.agi script that comes with 1.3.4 and use the following calling syntax:

Code: [Select]

; dial con detection
exten => 426,1,Set(CDR(accountcode)=QDIALAGI)
exten => 426,2,DeadAGI(queueDial.agi|30|Local/21@sip|queue-out|Agent/101)

It is very important that the queueDial.agi is run through a channel marked QDIALAGI, as this is needed by QM in order to avoid pulling channel information out of all active channels (this means avoiding drowning Asterisk in manager queries on a busy system).

Limitations
There are a few known limitations to this page:

• No wait/call time breakdown.
• No agent call back extension shown
• No coloured alarms at all
• The layout of the page surely need improving
• The page in in English only at the moment and cannot be translated

We expect to fix all those issues with time and your input.

2972

QueueMetrics installation / Re: Database Connection

« on: April 13, 2007, 08:44:25 »

Hi Alex,
you actually did 99% now....

Set the default log file as follows:

Code: [Select]

default.queue_log_file=sql:P01
And your QM will pull data from partition P01 of the database instead of reading the standard log file!

2973

QueueMetrics installation / Re: Database Connection

« on: April 12, 2007, 12:12:29 »

Hello Alex,
do not worry, you are almost there

First, you have to decide on which machine the MySQL database for QM will be. Keeping it on the TrixBox machine is just fine. So you have to copy it manually from where it is installed to the TrixBox machine, create the access grants for it and change the connection JDBC URI from the Windows box. Restart QM and check that QM is working with it.

After this, you have to edit the qloader.pl file installed on TrixBox to point data uploading to your local database. Do the same procedure, restart Qloaderd and check that the file /var/log/asterisk/qloader.log contains no errors.

Now check that when a new row is appended to the queue_log file of TrixBox, a new line appears on the queue_log table of the QM database; you can run a query like this just to be sure:

Code: [Select]

select partition, queue, count(*) as n_records
from queue_log
group by partition, queue
order by partition, queue

This will show all partitions in use (you should have only one) and whatever queues you are running. If this shows no results, there is a problem with qloaderd not uploading your queue_log data.

Now go back to the QM machine, go find QM's configuration.properties under WEB-INF, change the property where you see the path to "sql:P01" (if "P01" is your partition) and run a report. You should now be seeing data flowing.

PS. if you download the package qloaderd from http://queuemetrics.com/download/qloader-1.2.tar.gz there is adetailed doc file included.
 

2974

Improving QueueMetrics / Re: Converting time in 1 single unit

« on: April 11, 2007, 11:32:02 »

The reports should be all in H:MM:SS or in hours (decimal).
We will consider having one single format fo r all, though where we use hours is because you would likely have 15,234:12:18 hours, so just typing 15,234 is easier to read.

2975

QueueMetrics installation / Re: Database Connection

« on: April 11, 2007, 11:29:59 »

Hello Alex,
if you need to have QM monitor an Asterisk on a different server, you need to install the qloaderd script on the Asterisk server to send data to the MySQL database used by QM. You can have the QM database anywhere, though we usually suggest it to keep on the QM box instead of the Asterisk box.

My suggestion is:
- first set up QM so that it can process files locally, and so you know that it's working
- once it's set up, install the qloaderd script on the Asterisk box to send data to QM

2976

Running QueueMetrics / Re: Listening of recored monitor call – Not working

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

Likely the association with GSM files is wrong, so the browsers do not know which program to use to play the file.

Suggestions:
- Use the Wav49 format if your clients are Windows machines - that's the same as GSM but works out-of-the-box
- Check the file content-types associations

2977

General Asterisk configuration / Re: Queue Metrics and Trixbox 2

« on: April 10, 2007, 13:27:37 »

We have had a few delays, hope it's ok by the end of this week. Knut (the person in cahrge of TrixBox) is sick.

2978

QueueMetrics installation / Re: Database Connection

« on: April 10, 2007, 13:25:41 »

Hello Alex,
when installing QueueMetrics, did you run the install script to preload the database? anyway, you can find the database schema in queuemetrics\WEB-INF\README as the file queuemetrics_sample.sql . Just load that into the newly created database using a MySQL client like PhpMyAdmin and everything will be fine - the error you get now means that permissions are OK at last.

2979

QueueMetrics installation / Trixbox Credentials

« on: April 05, 2007, 10:14:05 »

Anyway, you can use the following data to create a new database on a TrixBox default box:

MySQL user: root
MySQL password: passw0rd

With these you can create a new database, and create users for it to access it through the local LAN.

2980

QueueMetrics installation / Re: Database Connection

« on: April 05, 2007, 10:12:12 »

Not sure I get this directly: do you want to install QueueMetrics on the same server as Asterisk or on a different server?

If you need to install it  on the same server as Asterisk, just type:

Code: [Select]

wget -P /etc/yum.repos.d http://yum.loway.it/loway.repo

yum install queuemetrics

And it will be installed automatically for you.

2981

Running QueueMetrics / Re: Agent Filters and Agents in Reports Not Right

« on: April 05, 2007, 10:06:56 »

You mean the Asterisk side is okay but QM somehow messed things up while importing? I believe it would be useful if you could send over a copy of your agents.conf file to the support line to see if somehow it contains some weird character. Never seen anything like that before

2982

Improving QueueMetrics / Re: Option to "show" days with 0 calls

« on: April 04, 2007, 17:30:30 »

Added to the idea tracker.

2983

Improving QueueMetrics / Re: Report based on call duration

« on: April 04, 2007, 17:29:24 »

Nice solution. +1 karma from me

2984

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

« on: April 04, 2007, 17:28:07 »

If the three queueus you refer to in a previous post are inbound queues, whet you should do is create three aliases for outbound queues, so that you will be able in the future to query QM for inbound calls or outbound calls separately.

We usually suggest to create numeric aliases for outbound queues, so if you have an agent who whorks on multiple queues, they can easily input the outbound queue to track the call under using their telephone keyboard.

Imagine your agent sitting at extension 123 wishes to make an outbound call to be logged as outbound activity (i.e. not a personal call) - they would key in 93005555551234 where:
- 9 is the extenal line for outbound queues
- 300 is the outbound queue to log the call under
- 5555551234 is the PSTN number to dial.

As outbound queues are not physical entities but merely a logging convention so that QM can find that data, they do not need being configured anywhere in Asterisk, but just in QueueMetrics. In asterisk you will only have to change the dialplan to run the queueDial.agi file.

I hope this helps.

2985

Running QueueMetrics / Re: CallerID absed Queues / Stats

« on: April 03, 2007, 08:18:26 »

This should do the trick of adding "91" to your callerid:

Code: [Select]

exten => ....
exten => _X.,1,Set(CALLERID(num)="91-${CALLERID(num)}")
exten => ....