Page 40 - Asterisk™: The Future of Telephony
P. 40

although the underlying causes will be different. As loads increase, the system will have
               increasing difficulty maintaining connections. For a PBX, such a situation is nothing
               short of disastrous, so careful attention to performance requirements is a critical con-
               sideration during the platform selection process.

               Table 2-1 lists some very basic guidelines that you’ll want to keep in mind when plan-
               ning  your  system.  The  next  section  takes  a  close  look  at  the  various  design  and
               implementation issues that will affect its performance.

                           The size of an Asterisk system is actually not dictated by the number of
                           users or sets, but rather by the number of simultaneous calls it will be
                           expected to support. These numbers are very conservative, so feel free
                           to experiment and see what works for you.

               Table 2-1. System requirement guidelines
                 Purpose                   Number of channels  Minimum recommended
                 Hobby system              No more than 5  400 MHz x86, 256 MB RAM
                 SOHO system (small office/home office—  5 to 10  1 GHz x86, 512 MB RAM
                 less than three lines and five sets)
                 Small business system     Up to 25      3 GHz x86, 1 GB RAM
                 Medium to large system    More than 25  Dual CPUs, possibly also multiple servers in a distrib-
                                                         uted architecture

               With large Asterisk installations, it is common to deploy functionality across several
               servers. One or more central units will be dedicated to call processing; these will be
               complemented by one or more ancillary servers handling peripherals (such as a data-
               base system, a voicemail system, a conferencing system, a management system, a web
               interface, a firewall, and so on). As is true in most Linux environments, Asterisk is well
               suited to growing with your needs: a small system that used to be able to handle all
               your call-processing and peripheral tasks can be distributed among several servers when
               increased demands exceed its abilities. Flexibility is a key reason why Asterisk is ex-
               tremely cost-effective for rapidly growing businesses; there is no effective maximum or
               minimum size to consider when budgeting the initial purchase. While some scalability
               is possible with most telephone systems, we have yet to hear of one that can scale as
               flexibly as Asterisk. Having said that, distributed Asterisk systems are not simple to
               design—this is not a task for someone new to Asterisk.












               12 | Chapter 2: Preparing a System for Asterisk
   35   36   37   38   39   40   41   42   43   44   45