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.

Topics - trymes

Pages: [1] 2
Running QueueMetrics / Cluster and call recordings.
« on: January 23, 2015, 17:48:02 »
I recently set up a new QM server that monitors two Asterisk servers in a cluster. The queue_log data is properly written to the QM DB by qloaderd, and everything works just fine, except I have no access to recorded call files.

So, I have mounted the /var/spool/asterisk/monitor directories via NFS and specified the locations in the file. I can successfully browse and copy files from the NFS directories via the command line. However, when I click on the magnifying glass icon for call details while the NFS shares are mounted, QM hangs and does not pull up the details (the popup opens, but no data is populated). If I unmount the NFS shares, QM is once again responsive.

What have I done wrong?


Running QueueMetrics / QM, FreePBX and Recordings stored by day
« on: November 29, 2012, 16:32:28 »
I thought I would post a summary of a major improvement that the FreePBX 2.10 upgrade has allowed, one that makes a major impact on QM users with many recordings.

Specifically, we have had our recordings all dumped into the /var/spool/monitor directory for years, and the number of recordings was causing a HUGE performance problem when retrieving the calls from the QM interface. Specifically, I wanted to implement the solution found at this link. Unfortunately, there was no good way to implement this with FreePBX 2.09 or earlier, so I was looking at crafting a script to run and place calls in folders after the fact.

Luckily, it turns out that the folks at FreePBX changed the call recording configuration for version 2.10, so now calls are automatically being placed in folders by year, month, and day. After moving all of our existing recordings into similar folders, I changed the settings in the configuration properties file, restarted QM, and was thrilled that the recordings now download almost instantaneously.

Please note, though, that the instructions in the link above will not work for FreePBX 2.10. First off, you do not need to make any changes to the dialplan, as the queue recordings are automatically stored by year, month, and day when running 2.10. Secondly, the chances to are slightly different.

Specifically, make these changes in
Code: [Select]

I hope that information is helpful to someone out there.


PS: Now do I have to do anything to ensure that these settings are preserved when updating?

Has anyone come up with a good method to upgrade the realtime queue_log table from 1.6 to the 1.8 format?

I believe that QM is ready to go with Realtime Queue Log and Asterisk 1.8, but my table is not!

Many thanks,


Running QueueMetrics / Agents showing as logged in when they are not.
« on: September 22, 2011, 21:58:34 »
I imagine that this is related to the "Friendly Name" issue with FreePBX 2.8 and newer, but I'll ask here anyway.

Running QM and FreePBX 2.9.x

Asterisk consistently reports fewer agents actually logged in than QM reports as being logged in. Right now I have one agent logged in and QM shows 15.

Is there any solution to this, or must I simply wait for a new version to come out?


Running QueueMetrics /
« on: August 24, 2011, 14:12:13 »
I have updated this file with my license code so I don't need to move the license manually each time I upgrade. I have a few questions, though:

1.) I presume that I should remove the "<param-value>" tags, no?
2.) Is it possible to add the logo parameter to the file as well, so that is updated when upgrading?


In the QM manual, a queue logon context is described that uses the following line to echo an event to the queue_log file:

exten => _422XX,3,System( echo "${EPOCH}|${UNIQUEID}|NONE|SIP/${EXTEN:3}|\AGENTLOGIN|-" >> /var/log/asterisk/queue_log )

Now, how would I accomplish the same thing with the built-in realtime queue_log in Asterisk 1.6+?

Many thanks,


Improving QueueMetrics / Trivial: Typo in extensions_queuemetrics.conf
« on: November 19, 2010, 20:17:14 »
This is really silly, but I thought I would mention it so it can be fixed, just so nobody is confused in the future. The file "WEB-INF/mysql-utils/extensions-examples/extensions_queuemetrics.conf" has a small typo in the note that precedes extension 10.
Code: [Select]
; extension 0 is a dummy end point
exten => 10,1,Answer

I presume it should read "; extension 10 is a dummy end point"?

No big deal, but thought I'd point it out.


QueueMetrics installation / [queuemetrics] context and FreePBX
« on: November 18, 2010, 19:22:23 »
I'm certain that this has been hashed out before, but it's still pretty unclear to me, so...:

We have QM installed on top of Elastix, which uses FreePBX. After reading the manual, it is obvious that the call monitoring and other features require a proper queuemetrics context. It also seems that tracking agent availability might not be possible without appending the login and logout events to the queue_log. I have a few problems, though:

1.) FreePBX is pretty complex in how it handles and constructs the dialplan. I feel more comfortable using their login/logout routines.
2.) The provided login/logout routines do not contemplate the recently added realtime queue_log storage. What would the proper command be for that?
3.) Does the sample QM context need tweaking for monitoring ongoing calls via chanspy for FreePBX systems? I can say for certain that it causes very strange behavior if you try to use it without configuring it properly.

Any insight appreciated.


Problems / Not receving e-mails on followed threads.
« on: November 17, 2010, 16:34:50 »
I am not receiving e-mail notifications when my followed threads receive a reply. I checked my settings and it seems to be proper.

Any ideas?


Improving QueueMetrics / Sort on call time/average call time
« on: November 17, 2010, 16:32:39 »
I'd like to be able to sort the agent list in reports based on the average call time and the total call time. Currently you can sort on Name and N. Calls.

Improving QueueMetrics / Automatic license Transfer
« on: November 03, 2010, 21:51:07 »
I am really sick of having to move my license into a new version of QM every time yum updates it. Why can't the license be stored in a Database or somewhere else that doesn't require manual intervention at every upgrade?

Just a thought,


QueueMetrics installation / Release notes for
« on: November 03, 2010, 21:46:52 »
I see is out, but I do not see any release notes. Where should I look?


QueueMetrics installation / QM 1.6 and realtime queue_log
« on: September 30, 2010, 20:23:10 »

Now to figure out how to enable and tell QM to use the realtime Queue_log in Asterisk 1.6....

Anyone got a pointer?


I am trying to install via yum on my Elastix 2.0 server, but I am running into an error during the installation process:
Code: [Select]
Do you agree to the above license terms? [yes or no]
/usr/local/queuemetrics/jdk-1.6.0_20-linux-i586.bin: ./install.sfx.22549: /lib/ bad ELF interpreter: No such file or directory
Failed to extract the files.  Please refer to the Troubleshooting section of
the Installation Instructions on the download page for more information.

I have been using QM for years now on an old Trixbox server, but I have finally gotten around to upgrading, but I am stuck at the install process due to this error.

One interesting note is that even though the "Do you agree to the above license terms? [yes or no]" question is in the output above, the process does not stop there and allow me to input an answer, it just proceeds right through without pausing.

Any thoughts?


I have an odd thing going on here and I can't tell if it's due to our installation or to QM.

In the reporting for a given day, if an agent signs in for 5 minutes, but receives no calls, their availability information is not shown in the reports. That information is only shown if they actually receive a call. An agent that is signed in for three hours, but receives no calls, will not appear in the report.

What is going on here?


Pages: [1] 2
# 2019-02-11