Messages

16

Running QueueMetrics / Re: asterisk 1.8 queue_log

« on: September 15, 2011, 19:17:43 »

coolname: what changes did you make to FreePBX? I presume you modified [macro-agent-add]?

Is nothing is changed on the FreePBX end, what happens when an agent's name is changed?Say someone gets married and changes their last name. When I update the extension's FreePBX "Friendly Name" will I need to set up a new agent in QM? Won't this use up one of my licensed agents?

Or is QM going to modify how these things are tracked?

Tom

17

Running QueueMetrics / Re: Individual Agent Reports are not working

« on: September 15, 2011, 19:13:25 »

That isn't really much of a solution, unless I misunderstand you. Removing the Friendly Name from the extension is going to break intra-office CallerID, etc.

Tom

18

Running QueueMetrics / Re: Individual Agent Reports are not working

« on: September 14, 2011, 22:06:20 »

Just to add some more information, I think that the problem here is that the ADDMEMBER and REMOVEMEMBER events are still logged as "Local/132@....." where everything else is logged as "Friendly Name". The end result is oddities with QM.

Does anyone have suggestions as to how to better make this work?

Code: [Select]

+--------+------------+------------------+-----------+------------------------+----------------+------------------------+
| id     | time       | callid           | queuename | agent                  | event          | data                   |
+--------+------------+------------------+-----------+------------------------+----------------+------------------------+
| 700476 | 1313000368 | 1313000365.80084 | 400       | Local/290@from-queue/n | ADDMEMBER      |                        |
| 700477 | 1313000375 | 1313000373.80085 | 400       | Local/290@from-queue/n | REMOVEMEMBER   |                        |
| 700478 | 1313000435 | 1313000333.80078 | 400       | Jane Smith             | COMPLETEAGENT  | 5|86|1                 |
| 700479 | 1313000500 | 1312999933.79981 | 400       | Susie Jones            | COMPLETEAGENT  | 7|549|1                |
| 700480 | 1313000504 | 1313000499.80096 | 400       | NONE                   | ENTERQUEUE     | |                      |
| 700481 | 1313000504 | 1313000502.80097 | 400       | Local/134@from-queue/n | REMOVEMEMBER   |                        |
| 700482 | 1313000507 | 1313000499.80096 | 400       | Joe Johnson            | CONNECT        | 3|1313000504.80098|2   |
| 700483 | 1313000516 | 1313000137.80051 | 400       | Frank Smith            | COMPLETEAGENT  | 20|348|1               |
| 700484 | 1313000537 | 1313000534.80105 | 400       | Local/270@from-queue/n | REMOVEMEMBER   |                        |
| 700485 | 1313000540 | 1313000538.80106 | 400       | Local/290@from-queue/n | ADDMEMBER      |                        |

19

Running QueueMetrics / Re: asterisk 1.8 queue_log

« on: September 14, 2011, 18:51:04 »

This is somewhat related to my problems described here: http://forum.queuemetrics.com/index.php?topic=1294.0

The changes made to the Asterisk 1.8 table can be seen here (though it might not be lastest info): https://issues.asterisk.org/view.php?id=17082

I imagine that QM will need to be changed to adapt to 1.8, but FreePBX likely needs to be modified when not running on 1.8.

Tom

20

Running QueueMetrics / Re: Individual Agent Reports are not working

« on: September 14, 2011, 18:47:27 »

This is still going on. The code in FreePBX changed and the realtime queue_log is now populated with the name associated with that extension, instead of the extension number. I am uncertain if this is also true of non-realtime queue_logs. I am fairly certain that this is related to changes implemented to take advantage of the expanded realtime queue_log reporting offered in Asterisk 1.8. The changes show up with FreePBX 2.9.

Basically, log entries are no longer associated with the extension/channel number (ie: Local/240@from-queue), but now show "Bill Jones" instead. This screws things up for QM, as might be expected.

Nobody else has run into this with Asterisk 1.6, QM, and FreePBX 2.9?

21

Running QueueMetrics / tpf.properties

« on: August 24, 2011, 15: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?

Tom

22

Running QueueMetrics / Re: Individual Agent Reports are not working

« on: July 29, 2011, 19:50:27 »

After further diggin in MySQL, it appears that many events that were previously reported in the queue_log as "local/XXX@from-queue/n" are now reported with the agent's name, presumably from the extension's setup in FreePBX.

I will pursue this on the FreePBX side, unless someone here has a solution.

Tom

23

Running QueueMetrics / Re: Individual Agent Reports are not working

« on: July 29, 2011, 19:23:18 »

OK, I am having the same problem since upgrading to 1.7.1. I have gone into the configuration and verified that the agents are assigned as Main, Wrap, or Spill. If I click on the "Quick Activity Report" for today, I can see all of the calls, plus each agent and how many calls they have answered, average time, etc.

If I run and Agent report for today, nothing comes up. Oddly enough, if I run it for the past 30 days, some calls do come up. There is a chance that this could be related to a FreePBX upgrade from 2.7 to 2.8, but the dates do not seem to match up.

Any ideas?

Tom

24

QueueMetrics installation / Re: Echoing Logon/Logoff events to realtime queue_log

« on: January 20, 2011, 20:41:34 »

Can you point me to that? The manual still has the "echo" method I pasted above.

Tom

25

QueueMetrics installation / Re: Echoing Logon/Logoff events to realtime queue_log

« on: January 13, 2011, 22:15:18 »

I hate to answer my own question, but I'm guessing that the "QueueLog" application is the one that will be the answer to my question?

A specific entry that I ought to use for QM would still be helpful....

Tom

26

QueueMetrics installation / Echoing Logon/Logoff events to realtime queue_log

« on: January 13, 2011, 22:12:06 »

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,

Tom

27

Improving QueueMetrics / Re: Automatic license Transfer

« on: January 11, 2011, 16:59:32 »

Thanks for the change, I'm looking forward to taking advantage of it!

Two questions, though:

1.) This will not move current settings over to a new version? I'm thinking realtime queue_log, etc?
2.) I just updated to 1.6.3.1-74 from 1.6.3.0 via yum, and the license reverted to demo. Any idea why?

Many thanks,

Tom

28

Improving QueueMetrics / Re: Automatic license Transfer

« on: December 23, 2010, 14:36:14 »

Excellent? How will this be accomplished, If I might ask?

29

QueueMetrics installation / Re: [queuemetrics] context and FreePBX

« on: November 24, 2010, 15:08:58 »

That's accurate, but I still stand by my preference for not adding custom code unless necessary. While it is unlikely that you will break FreePBX, you might affect the dialplan in ways you don't expect and don't immediately notice, especially if you later upgrade FreePBX. This is less likely for things like ChanSpy, but for things like Queue login, you might end up doing things that undermine what FreePBX is designed to do.

To get right down to it, FreePBX is a pretty complex beast, and any custom additions to the dialplan increase the risk of encountering unusual behavior. For that reason I think it is best to avoid any custom additions WHEN POSSIBLE. Sometimes it isn't possible, and QM looks to be one of those times, but I want to dig a little deeper and see what options are out there that would allow me to add as little custom code as possible. I'm thinking of things like creating a context that echoes entries to queue log and then points to the built-in queue toggle, rather than recreating the wheel, etc.

Tom

30

Problems / Re: Not receving e-mails on followed threads.

« on: November 22, 2010, 15:52:46 »

I think that you will be unable to be delisted from the PBL. The IP Address range is blocked because Rackspace has a policy that outbound e-mail from that Address range should be authenticated and relayed through their server. You will need to configure your outgoing mail to relay through them.

From http://www.slicehost.com/articles/2009/11/4/rackspace-email-promotion#comment-10723:

It seems that those of us who are running mail servers on our slice(s) are all of a sudden in the Policy Block List (PBL) of Spamhaus because of a Rackspace policy.

“It is the policy of rackspace that unauthenticated email sent from this IP address should be sent out only via the designated outbound mail server allocated to rackspace customers. To find the hostname of the correct mail server to use, customers should consult the original signup documentation or contact rackspace Technical Support.”

Shouldn’t we have been notified for this change by Slicehost along with some advice on the steps we need to take?