QueueMetrics > Running QueueMetrics
Realtime Monitoring showing 2 entries per dynamic agent
QueueMetrics:
No: the problem is that you should configure your Asterisk box so that the logging is consistent i.e. it always writes the same thing when it logs the same entity. Qm has no way of knowing that "Ron Bergin" and "local/15031" are the same thing.
perlmaster:
--- Quote ---Qm has no way of knowing that "Ron Bergin" and "local/15031" are the same thing.
--- End quote ---
Why doesn't it? Asterisk knows that they're associated.
--- Quote ----- Executing [login@agent-login:18] AddQueueMember("SIP/15031-098151d8", "test1|Local/15031@iso/n|||Ron Bergin") in new stack
--- End quote ---
--- Code: ---099asterisk101*CLI> queue show test1
test1 has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
Members:
Ron Bergin (Local/15031@iso/n) (dynamic) (Not in use) has taken no calls yet
No Callers
--- End code ---
--- Quote ---the problem is that you should configure your Asterisk box so that the logging is consistent i.e. it always writes the same thing when it logs the same entity.
--- End quote ---
I have no problem with that, as long as the Realtime Monitor displays the agent's real name.
So, what does QM require to accomplish my requirement? What syntax would I use when the agent logs in and when the queue call is delivered to their extension?
QueueMetrics:
What I would do is to log on the agent with the asterisk name of "Agent/15031", so that the logging is consistent from QM's point of view.
Then you define (in QM) an "Agent/15031" which name is "Ron B. (15031)", so that anywhere in QM you'll see the name that was defined in QM itself.
perlmaster:
I wish the fix was that simple, but that won't work for us.
Our agents don't always use the same extension. It's common for them to roam and use different extensions, so hard coding a user to an extension won't work. We need to have the ability for an agent to login to any extension and have that extension and their name displayed in the Realtime monitor in a single entry as opposed to the 2 entries that we currently have.
perlmaster:
Our agents are configured/identified in both agents.conf and QM by their employee number, not the extension number that they normally use which can differ from day to day.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version