On Thu, Apr 23, 2009 at 6:43 PM, Matt Riddell <[email protected]> wrote:
> On 24/04/2009 10:19 a.m., Steve Totaro wrote: > > A much more scalable way to do this is to create and then FTP or move > > .call files to the proper directory. Depends how much you plan on > > banging on the AMI. > > Maybe, but the Asterisk Manager is happy with 10 calls per second and if > your controlling process is spread across Asterisk machines you can do > hundreds of calls per second. If you're doing what it seems he is, I'd > agree that call files may be easier, but I'm not sure it scales better. > How many call files can you put in a directory, is he using a hard > drive or compact flash (max writes). > > I've never actually done any proper tests of the comparison between a > call file and a manager originate. I would have thought they were > pretty much the same, albeit that you're adding an extra layer of > complexity with the call files. > > -- > Kind Regards, > > Matt Riddell > Director > _______________________________________________ > > http://www.venturevoip.com (Great new VoIP end to end solution) > http://www.venturevoip.com/news.php (Daily Asterisk News - html) > http://www.venturevoip.com/newrssfeed.php (Daily Asterisk News - rss) > > I have in VERY intensive AMI usage environments. You can easily drop 100 or more call files in the spool dir and no worries. @ ~100 calls it may take a second or so to ring (all SIP extensions). I have no doubt that it is the more stable and scalable way to go. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell)
_______________________________________________ -- 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
