QueueMetrics > Running QueueMetrics

Agents aren't shown any longer on Real Time Reports

<< < (3/5) > >>

witekprytek:
I have very similar problem. I have fresh install of queuemetrics.
I do not see any Agents in Real Time Reports.My Agents logs on and off using queuemetrics csreen. I see it in asterisk console:

8            has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
   Members:
      Agent/11 (Not in use) has taken no calls yet
      Local/206@from-internal (dynamic) (Not in use) has taken no calls yet
   No Callers

Agent/206 is logged from queuemetrics.
I can see logs produced by agents action (e.g pause) in queue_log:
1263074798|1263074798.1778|8|Local/206@from-internal|ADDMEMBER|
1263075727|NONE|NONE|Agent/206|PAUSEALL|
1263075727|1263075727.1784|NONE|Agent/206|PAUSEREASON|13
1263075771|NONE|NONE|Agent/206|UNPAUSEALL|

but Real Time Monitoring screen shows 0 Agents in queue!

QueueMetrics:
You should enable rewriteLocal so that the Local/206@... is read as Agent/206.
For the rest I would advise against mixing Agents and channels (not because this is a problem for QM but because they are different things).

witekprytek:
Sorry for my late answer.
rewriteLocal did the trick. I can now see logged in agetns...but.

When I log in using queumetrics I can see on agent console "Agent/206: Agent is currently logged on queues: 8 "
(I have put 888 as the extension number)

I can see agent in real time monitoring and in asterisk console (Agent/206 with ext 888):
Members:
      Local/206@from-internal (dynamic) (Not in use) has taken no calls yet
   No Callers

but no calls are forwarded to the agent - do I need to configure something else?
Asterisk try to call Local/206 not Local/888
- Executing [206@from-internal:4] Macro("Local/206@from-internal-7d3b,2", "dialout-trunk|2|206||") in new stack
    -- Executing [s@macro-dialout-trunk:1] Set("Local/206@from-internal-7d3b,2", "DIAL_TRUNK=2") in new stack

QueueMetrics:
It looks like it's calling a trunk..... how is that?

witekprytek:
yeap It try to calling the trunk, because QM is not able to login correctly.

I have added new agent using qm and then login using agent webpage:

-- Executing [20@queuemetrics:1] Answer("Local/20@queuemetrics-fd56,2", "") in new stack
    -- Executing [20@queuemetrics:2] NoOp("Local/20@queuemetrics-fd56,2", " "QM: Logging on Agent/7889 to extension 888@from-internal made by Agent/7889" ") in new stack
    -- Executing [10@queuemetrics:1] Answer("Local/20@queuemetrics-fd56,1", "") in new stack
    -- Executing [10@queuemetrics:2] Wait("Local/20@queuemetrics-fd56,1", "10") in new stack
    -- Executing [20@queuemetrics:3] AgentCallbackLogin("Local/20@queuemetrics-fd56,2", "7889||888@from-internal") in new stack
    -- <Local/20@queuemetrics-fd56,2> Playing 'agent-incorrect' (language 'en')
  == Manager 'queuemetricsmgr' logged off from 127.0.0.1

so ...the agent is not able to login.
When I  manually modify agents.conf file and add prevoiusly configured agent (via qm - eg aGENT/206) to the agent.conf file  i have a little different message:
Executing [20@queuemetrics:3] AgentCallbackLogin("Local/20@queuemetrics-5fb4,2", "206||888@from-internal") in new stack
    -- <Local/20@queuemetrics-5fb4,2> Playing 'invalid' (language 'en')

..but finally effect is the same

Navigation

[0] Message Index

[#] Next page

[*] Previous page