Elliot Otchet <elliot.otc...@callingcircles.com> writes: > That shouldn't be too hard to accomplish. If you've got the addons > (and mysql) installed you could store them in a MySQL table > (timestamp, device) and have a cron job set to run at X frequency that > un-pauses the queue members via AMI. Don't want to go to MySQL? Use > system() to 'touch' files named after devices. Then have your cron > script go through the files by creation date. Either way gets you > there.
This seems like a very heavyweight solution. Having a cron job running every minute isn't particularly attractive, and making a daemon do the job isn't my cup of tea either. Perhaps the problem could be restated in a different way: After a queue member rejects a call (instead of just not answering), the queue should wait X amount of time before sending the next call. Queues.conf has a million settings, but I can't find one which does this. /Benny _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
