[solved] how availability sessions are measured?

[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]

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. 

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]

You should either use AGENTLOGIN or ADDMEMBER, not both.

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.

[qmax]

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

as far as i understand call-center business logic,
adding agent to queue can not mean this agent is available.
it is a matter of asterisk configuration and/or agents organization.

i supposed, that queues/agents are to be configured before they start to work, possible staying configured for days or ever weeks.
and when agent logging in, it signals to system that it is ready to accept calls from previously assigned queues.

what working scenario QueueMetrix is intended to use with?

the only possible solution i see here is then agents logins and joins queue simultaneous.

[qmax]

ok.
another solution came in mind.

we could avoid logging add/remove member completely
but rather somehow setup or patch asterisk to queue_log login/logoff along with queue number.

will QM recognize this weird mode?

[QueueMetrics]

i supposed, that queues/agents are to be configured before they start to work, possible staying configured for days or ever weeks.
and when agent logging in, it signals to system that it is ready to accept calls from previously assigned queues.

what working scenario QueueMetrix is intended to use with?

the only possible solution i see here is then agents logins and joins queue simultaneous.

That is for "thrue" agents - you have an existing confuhiration and they are bootstrapped with the correct queue associations. With AddMember, this is not so.
In any case, as we are speaking of the ACD module, if you want to log on an agent and have him/her NOT receive calls immediately, you should do a Logon + Pauseall.
 

[qmax]

i supposed, that queues/agents are to be configured before they start to work, possible staying configured for days or ever weeks.
and when agent logging in, it signals to system that it is ready to accept calls from previously assigned queues.

what working scenario QueueMetrix is intended to use with?

the only possible solution i see here is then agents logins and joins queue simultaneous.

That is for "thrue" agents - you have an existing confuhiration and they are bootstrapped with the correct queue associations. With AddMember, this is not so.
In any case, as we are speaking of the ACD module, if you want to log on an agent and have him/her NOT receive calls immediately, you should do a Logon + Pauseall.
 

do you mean, that for "true" agents - we should have static configuration in queues.conf?
and then agents need just to login (using AgentLogin) anf logof (using hangup) ?

static queue member configuration is not appropriative for us - for some queues it may change during the day several times, while for others - it may stay unchanged for weeks.

thus we are looking for a way to reconfigure queue member on the fly.
still no good solution.

[QueueMetrics]

To me, the easiest way would be mintaining agent-queue associations in QM and using the AddMember buttons to do an "add all" - this will call Asterisk behind the scenes and log on the agent by adding it separately to each queues.

[qmax]

It's ok to adding and removing agents to queues through web interface.
(btw, there are completely inadequate russian labels).

But If to engage pausing to do not account their time,  when they are in queue, but does not login -
we need make agents unpaused before login and paused back after logoff.
I just cannot figure out how to implement it.

Upd:
Ok. dealed with pauses.

Solution:
joining queue sets pause "prepearing to work"
logging in unpauses agent
logging out (hangup) sets pause "out of air"
leaving queue sets pause "finishing work"

[QueueMetrics]

That's cool.
We're working on an updated Russian translation.