asterisk users - Feb 2005 - Round Robin Strategy doesn't seem to work

Hi,

I have configured a call queue as follows:
[sales]
music = default
strategy = roundrobin
timeout = 20
retry = 5
reportholdtime = yes
announce = queue-sales
member => Agent/9021
member => Agent/5901
member => Agent/9020
member => Agent/1114

Now, I would expect all calls to this queue to be delivered first to 9021,
then to 5901, then to 9020, then to 1114 (all agents are logged in and
available).  However, what actually happens is that the first call to the
queue is delivered first to 9021 (and on through the queue order from
there), but then the next call is delivered first to 5901 (and on through
the queue order from there).  The third call to the queue is delivered first
to 9020, the fourth call to 1114.

What I want is for all calls to the queue to be delivered to available
agents in the order that they are listed in the member configuration each
and every time.  Am I missing the point here?  Has anyone else run into this
problem?

Thanks for any insight.

Regards,
Todd

Todd Gunsolley
Spry Hosting
todd.gunsolley@spry.com

You could use penalties to enforce the order like so:
member => Agent/9021
member => Agent/5901,1	; the number after the comma is a penalty
member => Agent/9020,2  ; those with the highest penalty should
member => Agent/1114,3  ; receive calls last

Hope this helps,
~Senyo

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Todd Gunsolley
Sent: Thursday, February 10, 2005 1:32 PM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] Round Robin Strategy doesn't seem to work

Hi,

I have configured a call queue as follows:
[sales]
music = default
strategy = roundrobin
timeout = 20
retry = 5
reportholdtime = yes
announce = queue-sales
member => Agent/9021
member => Agent/5901
member => Agent/9020
member => Agent/1114

Now, I would expect all calls to this queue to be delivered first to 9021,
then to 5901, then to 9020, then to 1114 (all agents are logged in and
available).  However, what actually happens is that the first call to the
queue is delivered first to 9021 (and on through the queue order from
there), but then the next call is delivered first to 5901 (and on through
the queue order from there).  The third call to the queue is delivered first
to 9020, the fourth call to 1114.

What I want is for all calls to the queue to be delivered to available
agents in the order that they are listed in the member configuration each
and every time.  Am I missing the point here?  Has anyone else run into this
problem?

Thanks for any insight.

Regards,
Todd

Todd Gunsolley
Spry Hosting
todd.gunsolley@spry.com

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

----- Original Message ----- 
From: "Todd Gunsolley" <todd.gunsolley@spry.com>
To: <asterisk-users@lists.digium.com>
Sent: Thursday, February 10, 2005 9:31 PM
Subject: [Asterisk-Users] Round Robin Strategy doesn't seem to work

> Hi,
>
> I have configured a call queue as follows:
> [sales]
> music = default
> strategy = roundrobin
> timeout = 20
> retry = 5
> reportholdtime = yes
> announce = queue-sales
> member => Agent/9021
> member => Agent/5901
> member => Agent/9020
> member => Agent/1114
>
> Now, I would expect all calls to this queue to be delivered first to 9021,
> then to 5901, then to 9020, then to 1114 (all agents are logged in and
> available).  However, what actually happens is that the first call to the
> queue is delivered first to 9021 (and on through the queue order from
> there), but then the next call is delivered first to 5901 (and on through
> the queue order from there).  The third call to the queue is delivered 
> first
> to 9020, the fourth call to 1114.
>
> What I want is for all calls to the queue to be delivered to available
> agents in the order that they are listed in the member configuration each
> and every time.  Am I missing the point here?  Has anyone else run into 
> this
> problem?
>
> Thanks for any insight.
>
> Regards,
> Todd
>
Excuse my Asterisk ignorance but in telephony terms your queue (or hunt 
group) is doing what would be expected from a round-robin group, to do what 
you want would be referred to as a linear group, maybe some * expert can 
confirm.

Steve

Todd Gunsolley wrote:
>What I want is for all calls to the queue to be delivered to available
agents in the order that they are listed in the member configuration each and
every time.  Am I missing the point here?  Has anyone else run into this
problem?
>
>  
>
Not sure it is a "problem". More of a feature.

You have set up a ACD or UCD, which is what most people want, so that 
calls get distributed more or less equally across a group .
Especially in a sales environment, commissioned sales people would raise 
the roof on what you want. They want equal shots at incoming calls.
Can one person be taken out of the list on demand, in case they go to 
lunch or have to take a leak?

What you really want is a circular hunt group ( of stations ) , but in a 
circular hunt, if all stations are busy, the caller will still hear ring 
until one ( station ) is free.
A terminal hunt will ring up the list until all are busy, then you 
either need to return busy or  perhaps go to a VM box?
Sorry I don't have an answer for you.
Are there different types of "queues" or hunt groups that you can
define?


John Novack
>  
>

On Thu, 2005-02-10 at 13:31 -0800, Todd Gunsolley wrote:
> Hi,
> 
> I have configured a call queue as follows:
> [sales]
> music = default
> strategy = roundrobin
> timeout = 20
> retry = 5
> reportholdtime = yes
> announce = queue-sales
> member => Agent/9021
> member => Agent/5901
> member => Agent/9020
> member => Agent/1114
> 
> Now, I would expect all calls to this queue to be delivered first to 9021,
> then to 5901, then to 9020, then to 1114 (all agents are logged in and
> available).  However, what actually happens is that the first call to the
> queue is delivered first to 9021 (and on through the queue order from
> there), but then the next call is delivered first to 5901 (and on through
> the queue order from there).  The third call to the queue is delivered
first
> to 9020, the fourth call to 1114.
> 
> What I want is for all calls to the queue to be delivered to available
> agents in the order that they are listed in the member configuration each
> and every time.  Am I missing the point here?  Has anyone else run into
this
> problem?
IMHO, this sounds like a bug.
The events you are describing are acting as though you had used
"strategy = rrmemory" which is round robin + memory. Either your
config
file is wrong, or you haven't reload'ed the config file, or there be a
bug. Please check the output of "show queues" and then post a bug to
mantis if required. Also you haven't told us the version of asterisk
that you are using this on, so make sure you include that in your bug
report.

Regards,
Adam


-- 
 -- 
Adam Goryachev
Website Managers
Ph:  +61 2 8304 0000                        adam@websitemanagers.com.au
Fax: +61 2 9345 4396                        www.websitemanagers.com.au