On Tue, Aug 25, 2009 at 3:15 PM, Pascal Bruno <[email protected]> wrote:
> On Tue, Aug 25, 2009 at 2:52 PM, Alex Balashov > <[email protected]>wrote: > >> With enough spiritual commitment, anything can be done; you certainly >> *can* do it this way. You can write a fairly sophisticated dialer in >> Bash, too. >> >> The issue is whether it is methodologically correct and qualitatively >> appropriate. It is much easier to schedule calls and manage outcomes >> dynamically - such as highly granular agent stats informed by >> up-to-the-minute heuristics, or aggressive overdial ratio control - with >> real-time monitoring of both call initiation and call results via AMI. >> >> It's a question of ROI on your time. You can do it however you want, >> especially if you're really motivated to avoid a particular type of >> development chore. > > > What you are saying makes sense, but I haven't used AMI for anything yet, > so I cannot comment on how easy/reliable/stable it is do work with in terms > of developing an autodialer, but I just did not agree when you said it was > definitely the way to go, because there is not one way to go. The one I > did, using call files to dial was pretty reliable, and I you are able to > distribute the calls different servers using the interface. > Agreed, simple cron jobs can count and distribute call files across servers with very little scripting. It is simple, and simple and efficient, and that is good. The AMI has been notorious for bogging down and halting systems when used in an intensive way. -- Thanks, Steve Totaro +12409381212 (Cell) +12024369784 (Skype)
_______________________________________________ -- 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
