Perhaps I was being somewhat ambitious by posting five 9's for "Enterprise Class"
using a three tiered approach, five 9's (5.25 min. per year) for "Carrier Class" four 9's (52.56 min. per year) for "Enterprise Class" three 9's (8.76 hrs. per year) for "User/SOHO Class" each Class having specific requirements of hardware, software, network and power redundancy. I presume this is needed to deliver an "Service Level Agreement" (SLA). "Olle E. Johansson" wrote: > Andrew Kohlsmith wrote: > >>I would set the "Enterprise Class" bar at five 9's reliability > >>(about 5.25 minutes per year of down time) the same > >>as a Class 4/5 phone switch. This would require redundant > >>design considerations in both hardware and software. > > > > To turn around, let's discuss what we need to focus on to get > Asterisk there: > > Here's a few bullet points, there's certainly a lot more > * Linux platform stability - how? > ** Special demands when using Zaptel cards > * Redundancy architecture > * Development/stable release scheme > > Then we have some channel demands, like > * Better support for SRV records in the SIP channel > > More? > > /O > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users -- FREE Unlimited Worldwide Voip calling set-up an account and start saving today! http://www.voippages.com ext. 7000 http://www.pulver.com/fwd/ ext. 83740 free IP phone software @ http://www.xten.com/ http://iaxclient.sourceforge.net/iaxcomm/ _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
