QueueMetrics > Running QueueMetrics

[solved] how availability sessions are measured?

(1/3) > >>

qmax:
How is availability of agent measured in reports?
When a session considered started and ended?

We have dynamic queues configuration via QueueAddMember/QueueRemoveMember.
queue_log:
...|...|queue|agent|REMOVEMEMBER|
...|...|queue|agent|ADDMEMBER|

Agents log on/off using AgentLogin.
queue_log:
...|NONE|sgent|AGENTLOGIN|extension
...|NONE|agent|AGENTLOGOFF|extension|...

Upd.
After agent added to queue, QM starts to show this agent as "logged in" in realtime monitor.
In spite of whether he actually logged or not.
Is it configurable in QM,
or we rather have to disable logging add/remove member commands ?

QueueMetrics:
You should either use AGENTLOGIN or ADDMEMBER, not both.

I suggest that you just use ADDMEMBER; when you do an ADDMEMBER, for QM it's just like the agent did an AGENTLOGON as well.

If you use both, QM will terminate the session when agent is removed from ALL queues and does an AGENTLOGOFF as well. 

qmax:

--- Quote from: QueueMetrics on June 05, 2009, 11:08:30 ---You should either use AGENTLOGIN or ADDMEMBER, not both.

I suggest that you just use ADDMEMBER; when you do an ADDMEMBER, for QM it's just like the agent did an AGENTLOGON as well.

If you use both, QM will terminate the session when agent is removed from ALL queues and does an AGENTLOGOFF as well. 

--- End quote ---

Thus, it is impossible to manage queue membership and logging in separately?

We would like, that agents are distributed to queues by managers,
and agents themselves then logon/logoff/pause/unpause as they are ready to work...

qmax:

--- Quote from: QueueMetrics on June 05, 2009, 11:08:30 ---You should either use AGENTLOGIN or ADDMEMBER, not both.

--- End quote ---

How?
ast cmd AddQueueMember assigns agent to queue, but does not logs agent.
ast cmd AgentLogin logs agent, but do not assign it to queue.

QueueMetrics:
In QM, an Addmember will log on the agent as well.

Navigation

[0] Message Index

[#] Next page