QueueMetrics > Outbound and QueueMetrics

More 1.6 integration issues

(1/2) > >>

peterbokune:
Greetings,

We're using the queueDial.agi script with some success presently for outbound queues.  When we moved to 1.6 we kept the agi script because it seemed to work and there were enough other other variables changing.  I'm looking to correct this now.

First issue:  Local/xxxx@ext vs. Agent/xxxx

I understand I can change the property to rewrite the entries with:

--- Code: ---# Rewrites Local/XXX@ext channels in the format Agent/XXX
default.rewriteLocalChannels=true

--- End code ---
Do I need to do anything to the legacy entries in the database when I make this change (and restart queuemetrics)? Obviously I have to update each agent's configuration, but we really don't want to lose their data with this change.

Second issue:  ADDMEMBER/REMOVEMEMBER vs. Asterisk

Presently most agents log into multiple queues depending on which skillset they're supporting plus the overflow queues.  The agents log to each queue in via a GUI app on their phone (Aastra) which updates ASTDB.  We also have agents who are static members of other queues.  Is there a problem with agents continuing using this interface?

Thanks!

Configuration:
asterisk 1.6.2.7
freepbx 2.7 (could update to 2.8, if it matters)
aastra xml 2.3.0
queuemetrics 1.6.0.3 (installed on separate system than PBX, if it matters)

QueueMetrics:
1. no you do not need to update anything

2. try to log them on and off and see if the statuses are shown correctly on the RT page. If they do, ity means they work fine.

peterbokune:
The logging on/off works perfectly.  Statuses update right away.

As for the agent definitions I didn't have such luck.

default.rewriteLocalChannels=true

I also defined the agents in QM as  Agent/XXXX and restarted.    Nothing showed up even though agents were logged in.  I reverted the changes and everything came back for me.

The definitions for the agents are Local/XXXX@from-queue which is clearly different than the Local/XXXX@ext as you note in the example so I assumed you were parsing out the XXXX and using that for the agent, but not so.

I can keep our agents defined as Local/XXXX@from-queue as that appears to be a cosmetic difference from Agent/XXXX. 

Or am I missing something?

QueueMetrics:
Try and post the lines that get added for ADDMEMBER and REMOVEMEBER so we can check what is written.

peterbokune:
I missed the step of adding the agents as members to the queues in QueueMetrics.  This explains why our reporting failed to show active agents.

Issues here are resolved and happy!

Thanks!

Navigation

[0] Message Index

[#] Next page