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

Pages: [1] 2 3 ... 6
Running QueueMetrics / Re: Cluster and call recordings.
« on: January 28, 2015, 14:27:10 »
To be clear, are you suggesting that I set:

Code: [Select]

I cannot copy the default.audioRpcServer setting, as there is no such line in the configuration file.

Thanks for the tip on the call path variables!


Running QueueMetrics / Re: Cluster and call recordings.
« on: January 27, 2015, 14:32:11 »
Thanks Mirko. I have included the relevant portion of the cluster setup below. The recordings are indeed stored by day, and I had not changed the audio.server directive before (I presumed that "by day" would have been the default). Anyhow, I just changed it to "" and it has not resolved the issue.


Code: [Select]
# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API



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?

Running QueueMetrics / Re: FreePBX(AsteriskNow) transfer
« on: October 15, 2012, 14:32:51 »
I am now struggling with this exact problem. As you all have pointed out, it's a side-effect of the fact that FreePBX uses local channels for the queues, which is generally a Good Thing®. However, I am a little uncomfortable with just deleting the "COMPLETEDAGENT" entry from the queue_log, as it leaves a portion of the call leg "lost", and if the call was transferred to another agent, wouldn't you like to be able to see that call and report on it?

I wonder if it wouldn't make sense to modify the way this is currently being done. When we add the "TRANSFER" line, we create the problem that one call has two termination reasons. There are two ways to resolve this:

1.) Delete the second termination reason.
2.) Add entries that "begin" a second call that will be terminated by the eventual "COMPLETEDAGENT" entry.

Your original solution implements #1, but I think it might be better and simpler to implement #2. This would eliminate the cron job and also have the side benefit of allowing us to see the transferred portion of the call and report on it. If the transfer was to another agent, the agent's information could be used, and if it was transferred to an outside person, it could be shown as a call to an agent named "Outside Number" or similar.



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,


BTW, the friendly names are working for me, but I still don't like the fact that FreePBX has given me no choice but to use them.

Thanks for providing the update to QM to handle this.


I see your point, but if you do not configure a friendly name in the extension setup for FreePBX, your CallerID will not properly show the caller's name.

While I would like to see an option in FreePBX that would control this behavior, it does not appear to be forthcoming. As such, I can't embrace a solution that would require me to modify the FreePBX code every time I perform an update to FreePBX and then hope that changes in that version do not break my modifications.

In fact, the solution proposed by QM could even be viewed by some as preferable, as using the friendly name allows you to see when the agent  changed, so you are not counting Susie Jones' calls in when viewing Bill Johnson's (because Susie used to have Bill's extension).

Any updates here? I sent an e-mail to Lorenzo on Thursday buti have not heard back.


Is there a ballpark timeframe available for an update to QM that will work properly with FreePBX 2.8 and later? The change to FPBX that changed the queue_log entries such that they were written using the friendly name occurred over a year ago, and as major distributions upgrade the version of FreePBX shipped by default, I think more people will be encountering this issue.

I am just hoping for an idea if I should expect a fix in a few days, weeks, months, or years.

Many thanks,


PS: I don't know how Loway is proposing to modify QM to accommodate this change, but I think it would be nice to be able to assign multiple friendly names to one agent, such that calls for both "Jane Smith" AND "Bill Jones" will be shown for the same agent, as Jane Smith was at extension 130 until May, but then she quit and Bill Jones replaced her at the same extension.

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 / Re: Individual Agent Reports are not working
« on: September 21, 2011, 16:06:06 »
The reason I ask, BTW, is that my instance of QM currently shows 13 agents as being logged in to my queue, while Asterisk via "show queue" only reports 8.

I'm sure I'm just missing something here, but....

Running QueueMetrics / Re: Individual Agent Reports are not working
« on: September 21, 2011, 15:27:07 »
Since the logon and logoff events are not written to the log using the agent's friendly name, won't that cause problems with QM?

Or is it smart enough to figure that out?

Running QueueMetrics / Re: Individual Agent Reports are not working
« on: September 19, 2011, 17:24:29 »
You could do the translation at the agent level in QM.

Can you be more specific?

We have tried adjusting the agent definition to match the name instead of the extension, but then QM does not see the logon/logoff events and incorrectly reports who is actually logged in/out.


Pages: [1] 2 3 ... 6
# 2019-02-11