asterisk users - Mar 2006 - Understanding queue timeouts + possible bug found

Hello list,
I have been researching a bit into the way the queue app works and how  
different timeouts play together, and have prepared a short tutorial on  
understanding queue timeouts - see  
http://www.oinko.net/astrecipes/index.php?n=118 - any suggestion, error  
found or correction is welcome.

While I was at it, I came across a strange bug: imageine you have three  
callback agents defined, but the terminal for one of them is unavailable.  
In my example they are 101, 102 and 103, where 103 is unavailable. The  
strategy is roundrobin. Have a look at what happens:

1142189627|1142189621.27|queue-dps|NONE|ENTERQUEUE||34
1142189627|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|
1142189644|1142189621.27|queue-dps|Agent/102|AGENTATTEMPT|
1142189655|1142189621.27|queue-dps|Agent/103|AGENTATTEMPT|
1142189655|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|
1142189672|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|   *******
1142189683|1142189621.27|queue-dps|Agent/102|AGENTATTEMPT|
1142189700|1142189621.27|queue-dps|Agent/103|AGENTATTEMPT|
1142189700|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|
1142189711|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|  *******
1142189728|1142189621.27|queue-dps|Agent/102|AGENTATTEMPT|
1142189739|1142189621.27|queue-dps|Agent/103|AGENTATTEMPT|
1142189739|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|
1142189756|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|  ********
1142189767|1142189621.27|queue-dps|Agent/102|AGENTATTEMPT|
1142189784|1142189621.27|queue-dps|Agent/103|AGENTATTEMPT|
1142189784|1142189621.27|queue-dps|Agent/101|AGENTATTEMPT|
1142189795|1142189621.27|queue-dps|NONE|EXITWITHTIMEOUT|1

I have added asterisks to denote a behaviour I dont understand; the  
extension 101 is called twice in a row if 103 is unavailable. DO you think  
this is a bug or there is a valid reason why * behaves like this? (I'm  
running 1.2.4)
Yours
l.





-- 
Loway Research - Home of QueueMetrics
http://queuemetrics.loway.it

Lenz wrote:
> I have added asterisks to denote a behaviour I dont understand; the 
> extension 101 is called twice in a row if 103 is unavailable. DO you
> think  this is a bug or there is a valid reason why * behaves like this?
> (I'm  running 1.2.4)
No, there is no bug here.

In 'roundrobin' mode, the queue calls the next agent after the one it
started with last time. This means that when 103 gets called (and is
unavailable), the call goes 101. On the next cycle, 101 gets called,
because it _started_ with 103 last time.

In 'rrmemory' mode, this is different: it will start with the next agent
after the last one it tried to call (not where it started). Use
'rrmemory' mode, it is really what most people are thinking of when they
want 'round robin' delivery of calls.