[asterisk-users] Queues: member order vs. defines in queues.conf

[lists.digium.com at tgice.com]

Hi,

I'm still pulling my hair out getting my queues setup in 1.2.13.

I went in to implement my custom "roundrobinreset" strategy (mentioned 
in a post by me here:

http://lists.digium.com/pipermail/asterisk-users/2006-October/170713.html

and a similar issue is addressed by the developers back in May:

http://lists.digium.com/pipermail/asterisk-dev/2006-May/020916.html

and I got it to basically work, that is do what people either claim that 
"roundrobin" will do *or* that some unspecified strategy will do if one 
uses penalties on members (note, I and at least a few other people on 
the list have attempted to make that approach work with no success -- so 
either it never worked, doesn't work in 1.2.13 or requires some extra 
configuration that we all missed).

There also appears to be some minor (very annoying until one discovers 
the workaround) bug w/ making changes to members in a queue and then 
trying to use 'reload' or 'reload app_queue.so' to redefine the queues.

If all you're doing is adding a new member, that new member seems to get 
stuck on the *front* of the queue (as the first avail. member) 
regardless of its actual position in queues.conf.  The only workaround 
I've discovered is to totally restart Asterisk.  I'm pretty sure that 
used to work fine.  Probably has something to do with the new dynamic 
queue member/agent adding features.

On a related note, it looks like the order of the members is reversed 
vs. how it's defined in queues.conf.  I'm pretty sure that was *not* the 
case in earlier versions (at least in 0.9.x anyway).

Anyone else note these (or better yet, care about or have any answers to 
the questions raised in my earlier posts?)

Thanks,

John Lawler