BJ Weschke 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. > >
Is this option active in 1.2.24? I thought it was only in 1.4 It's not mentioned in the queues.conf.sample. regards, Drew -- Drew Gibson Systems Administrator OANDA Corporation www.oanda.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
