This node refers to an EXPERIMENTAL time-limited feature present in QueueMetrics as of release 1.3.3. It is not meant to be used on production systems as it is simply EXPERIMENTAL at the moment. Use it at your own risk. A special licence will be needed once this feature will be officially released. All versions of QueueMetrics up to release 1.3.2 were meant to monitor one single instance of Asterisk, that is, you simply could not use them to “mix together” two or more queue_log files coming from different servers, as the results would have been unpredictable and quite possibly wrong. With 1.3.3, we add a new feature that makes it possible to consolidate multiple queue_log files, so that you monitor a “virtual queue” that is made up of a number of different queues residing on different physical servers. This will work for both historical and real-time reports, and is meant to be a major step forward making it very straightforward to build and monitor clustered, highly-reliable call-centers. To do this, we use the qloaderd process to upload data from different servers on different partitions on the same QueueMetrics database, and then we group the queue data together when running an analysis. This means we can leverage on the existing MySQL-storage infrastructure already in place and minimize the changes to the user interface needed to implement and run this feature. Setting up a sample system In this example, we imagine setting up a demo cluster made of three Asterisk servers, called A, B and C, while QueueMetrics and its MySQL database reside on server D. Continue Reading...

..to be completed…. Checking the database can be written to Checking if data is present in the database

1. connect to the QueueMetrics database using a MySQL shell or GUI
2. issue the following query: select partition, queue, count(*) as n_records from queue_log group by partition, queue order by partition, queue

+-----------+------------------+-----------+
| partition | queue            | n_records |
+-----------+------------------+-----------+
| P003      | myqueue          |         9 |
| P003      | NONE             |       121 |
| P003      | queue-abc        |      2096 |
| P003      | queue-test       |      1341 |
| P003      | UNK              |        17 |
| P01       | qq-group         |     33000 |
| P01       | cust-rajax       |       204 |
| P01       | NONE             |      8139 |
| rt        | NONE             |      8064 |
| rt        | q1               |      9216 |
| rt        | q2               |      9216 |
+-----------+------------------+-----------+
11 rows in set (0.16 sec)

It is very easy to install a new machine with Ubuntu or any other Debian-based distro using the PXE boot loader and fetching the distro right from the network (or from a local mirror). You will need a separate machine - likely another Ubuntu - to set up a TFTP server and to configure the boot option using a local DHCP daemon. If you have another DHCP daemon you have to turn it off, as a DHCP daemon supporting TFTP boot must be provided. You can install both the DHCP daemon and the TFTP server on Ubuntu using the following commands:

apt-get install tftpd-hpa
apt-get install dhcp3-server

If the XML-RPC interface of QueueMetrics is not working, i.e you get no meaningfiul response, you have to look up the catalina.out file in order to detect possible problems. Continue Reading...

This recipe explains how to set a new activation key in QueueMetrics. This applies to temporary keys you may request from the web site or to official product activation keys. To request a temporarty unlimited licence for QueueMetrics, please fill in the form at http://queuemetrics.com/sendDemoLicence.jsp Once you have obtained it, to insert the key into QueueMetrics you have to: Continue Reading...

It is quite easy to install QueueMetrics on Debian and Debian-derived systems, like the very popular Ubuntu: Continue Reading...

This meta-node contains information on how to install QueueMetrics on different Linux systems: Continue Reading...

It is sometimes necessary to completely remove Asterisk for one machine, for example because you need to install a newer version. Stop Asterisk and unload its modules The first thing you have to do is to stop Asterisk and unload the modules it may be using, e.g Zaptel’s. The following lines will brutally terminate Asterisk and kill all ongoing conversation. You have to kill safe_asterisk first, otherwise it will respawn Asterisk.

killall -9 safe_asterisk
killall -9 asterisk

[root@zebru]# lsmod | grep zaptel
zaptel                214820  2 wcfxo,wctdm
crc_ccitt               2113  1 zaptel

modprobe -r wcfxo
modprobe -r wctdm
..repeat for all zaptel submodules....
modprobe -r zaptel