Hi Ian,
that's good enough, but why does it ringa agent/101 two times in a row
when agent/103 is logged on but unavailable? I thought it would just skip
agent/103, retry 101 (once) then 102 and so on....
Thank you
l.
In data Mon, 13 Mar 2006 02:12:36 +0100, Kevin P. Fleming
<[EMAIL PROTECTED]> ha scritto:
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.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Assum est, versa et manduca.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
