Hey, I just found out today that it doesn't work on Asterisk 1.4.19 (at least for realtime queues) if you have autofill=yes in queues.conf. However it works if you add it in queue settings for each queue, for realtime that would be ALTER TABLE queue_table ADD COLUMN autofill TINYINT(1) UNSIGNED DEFAULT 1;
For following this issue, see http://bugs.digium.com/view.php?id=12445 Regards, Atis On Sat, Apr 12, 2008 at 4:42 AM, Rilawich Ango <[EMAIL PROTECTED]> wrote: > Do you mean autofill works in 1.4.x? But it doesn't work even I set it. > > > > On Fri, Apr 11, 2008 at 11:07 AM, BJ Weschke <[EMAIL PROTECTED]> wrote: > > Rilawich Ango wrote: > > > Thanks. I have checked that the queue.conf. I keep the default > > > setting as autofill=yes in my tests. That's mean even autofill=yes, > > > the 1st caller will still stick the whole queue. > > > asterisk version : 1.4.18 > > > > > > --queue.conf-- > > > ; AutoFill Behavior > > > ; The old/current behavior of the queue has a serial type behavior > > > ; in that the queue will make all waiting callers wait in the queue > > > ; even if there is more than one available member ready to take > > > ; calls until the head caller is connected with the member they > > > ; were trying to get to. The next waiting caller in line then > > > ; becomes the head caller, and they are then connected with the > > > ; next available member and all available members and waiting callers > > > ; waits while this happens. The new behavior, enabled by setting > > > ; autofill=yes makes sure that when the waiting callers are > connecting > > > ; with available members in a parallel fashion until there are > > > ; no more available members or no more waiting callers. This is > > > ; probably more along the lines of how a queue should work and > > > ; in most cases, you will want to enable this behavior. If you > > > ; do not specify or comment out this option, it will default to no > > > ; to keep backward compatibility with the old behavior. > > > ; > > > autofill = yes > > > > > > > > This was something I put in a long while back on 1.2 branch because we > really needed it for 1.2 to "bug fix" the behavior, but also needed to > prevent the change in behavior for those that didn't want it to change. > > > > That being the case and we're in the day and age of 1.6 branches now, > it'd be interesting to think of what people would think of deprecating this > option completely now in /trunk in favor of the "autofill=yes" behavior being > the only behavior available. I cannot think of any use cases where the > autofill=no behavior might be desirable. That being said, I also might have > blinders on so would be curious to here what the rest of the community has to > say about it. > > > > BJ > > > > -- > > Bird's The Word Technologies, Inc. > > http://www.btwtech.com/ > > > > > > > > > > > > > > _______________________________________________ > > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > > > asterisk-users mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Atis Lezdins, VoIP Project Manager / Developer, [EMAIL PROTECTED] Skype: atis.lezdins Cell Phone: +371 28806004 Cell Phone: +1 800 7300689 Work phone: +1 800 7502835 _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
