I've made several test using the 'queue-state' branches (now integrated on SVN trunk) and I can confirm that this solve all our problems using Queue and Local channels, we can now specify an alternate device to monitor the state. I have also "backport" the change to Asterisk 1.4.17 and already using it on multiple call center since last week.
>> Once the call was answered the status changed to In Use, and then >> everything worked as expected. I had a patch made that caused Queue() to >> not deliver calls to members with a status of Unknown -or- In Use, and >> that solved my problem for now, but not entirely sure what issues I'll >> run into in the future because of it :) >> > > The proper fix for this is in SVN trunk Asterisk now, which is to allow > app_queue to check a *different* device for state than it does for > dialing. This will allow you to create a custom set of 'devices' that > you control the state of via whatever logic you choose and then let > app_queue monitor those to determine the availability of queue members. > -- Joel Vandal ScopServ International, Inc. http://www.scopserv.com/ _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
