Summary:ASTERISK-00144: Agent Groups and Strategy leastrecent
Reporter:outtolunc (outtolunc)Labels:
Date Opened:2003-08-21 15:46:27Date Closed:2011-06-07 14:10:46
Versions:Frequency of
musiconhold => op
agent => 123,123,Sip Op - 123
agent => 300,300,TBS Op - 300
music = op
;announce = queue-markq
context = qout_op
timeout = 20
strategy = leastrecent
retry = 1
maxlen = 0
member => Agent/300
member => Agent/301
member => Agent/@1
if Agent/300 and 301 are removed, (Agent/@1 (or :1) only) strategy = leastrecent doesn't work (it bridges with the lowest agent # ready to take a call)

also, if Agent/@1 (or :1) is above member => Agent/300 and 301, it doesn't do leastrecent (must be below)
Comments:By: outtolunc (outtolunc) 2003-08-21 16:16:35

op_ready     has 0 calls (max unlimited) in 'leastrecent' strategy
     Agent/300 has taken no calls yet
     Agent/301 has taken no calls yet
     Agent/@1 has taken 1 calls (last was 96 secs ago)
  No Callers
the only 2 agents that have been loggin in are 300 and 301, yet neither show a call being taken..  (meaning the 'agent group' is getting the credit, not the actual agent)

By: Mark Spencer (markster) 2003-08-21 18:03:24

Strategy is not enforced on @1 / :1 because as far as the queue is concerned that's a single channel.  You *must* explicitly list both if you want to have the behavior you want.

By: Mark Spencer (markster) 2003-08-21 18:31:11

It's not a bug.  THe strategy applies to how the agent rings its channels.  As far as it's concerned Agent/@1 or Agent/:1 is just one channel, and of course chan_agent knows nothing of strategies.

To clarify, if you want it to use that strategy, you must list each agent individually in queues.conf and if you want the ability to pick up still, add :1 (perhaps with a penalty).

By: outtolunc (outtolunc) 2003-08-21 18:31:29

Grr, my bad.

you can close this bug.