[asterisk-users] WAS: 64 analog phones NOW: Selection criteria
and recipie for a good Asterisk install [long]
jromero at eusnetworks.com
Thu Sep 28 12:17:15 MST 2006
Has anyone tried RedFone?? It is supposed to offload a lot of that bus
overhead to the external unit doing TDMoE.
Email: jromero at euscorp.com
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-
> bounces at lists.digium.com] On Behalf Of John covici
> Sent: Thursday, September 28, 2006 12:14 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] WAS: 64 analog phones NOW: Selection
> criteria and recipie for a good Asterisk install [long]
> OK, pardon my ignorance -- but what can you tune on such a system?
> How does Linux handle separate buses?
> on Thursday 09/28/2006 Colin
Anderson(ColinA at landmarkmasterbuilder.com)
> > >I concur with your approach, but "Tier 1" means as little here as
> > >does when evaluating Internet backbone carriers. could you expand
> > >what evaluation criteria you use? I'm going to be pre-speccing
> > >stuff myself this month...
> > Sorry I should have been more clear. A good Asterisk install needs
> > holistic approach to use a hippy dippy phrase. A Tier 1 server,
> is a
> > midrange to high end name brand server from the Big 3 (Dell,
> > am I missing someone?) is usually highly optimized for bus
> > although that design was intended for a different use - usually
> > I/O. As well, a Tier 1 server will have two seperate, independent
> > and this to me is a critical feature - it allows you to completely
> > your TDM traffic from network, disk I/O etc. On my big production
> > I took great care to ensure the Digium cards were all on their
> on a
> > single bus, and everything else on the other bus. This is how I can
> > TE110's in a single box with no problems. zttest does not give me
> > the time, but on the other hand it *never* drops below 99.9987%,
> > load. I selected this Netfinity because of the obvious care put
> > design, but the specs are unimpressive: quad Xeon 700's. CPU is
> > for Asterisk, IMO unless you are doing tons of transcoding and if
> > doing that, then your design is flawed.
> > Anyway, the holistic approach (to go on a small rant for the newbie
> > be summed up as follows:
> > 1. Good box, see above
> > 2. Good LAN - this is so critical and so often overlooked in the
> and age
> > of guys crimping their own cables and running $150 switches. You
> > that, and if you do, you do so at your own peril. Managed swiches,
> > professional cable installation. This is not a problem for me since
> *am* a
> > professional cable installer but I have actually witnessed people
> > patch cables with a flat blade screwdriver and a hammer!
> > 3. Tuning of the LAN - VLAN's are good. QoS packets are good.
> > honor the QoS packets are good.
> > 4. Handset selection - this is another biggie. I've selected Snom
> 360's, and
> > yes they have warts, but they are feature rich for the price and
> > really good about revising firmware. When you select handsets, GET
> > USERS INVOLVED.
> > 5. Tuning of Asterisk box itself - this cannot be under emphasized.
> This is
> > a very important step and tuning methodologies vary according to
> > skill of the admin, and particular circumstances. I've learned
> > than I ever wanted to about processor affinity sinc I started using
> > Asterisk.
> > 6. Termination of PSTN. Basically I would never do an Asterisk
> > I was forced to do something stupid like aggregate a dozen Centrex
> lines or
> > some mickey mouse deal with FXO ATA's or whatever except for a
> > prototype install. PRI, BRI, IAX or SIP, don't mess around with
> > else.
> > 7. Relationship with provider. What is their SLA? Is it the
> or the
> > clec? An incumbent will be more expensive and more difficult to
> > but they will tend to be more reliable. A clec will be cheaper and
> > be way more accomodating but you will most likely not get five 9's
> > them. A VoIP provider should never be trusted, period. You will not
> > nines from them, ever. Plan failover situations accordingly.
> > 8. Plan plan plan plan. A good install of ANYTHING is 80% planning
> > it. What is your plan when your primary PSTN provider fails? What
> > plan if your Asterisk box goes pear shaped? My dialplan can survive
> > PSTN, WAN or LAN failure (albeit with reduced functionality). I
> keep a
> > cold spare, an identically configured box that I can literally
> > the rack, turn it on, plug in the PRI's and no problem.
> > 9. Internet bandwidth and latency. I am fortunate enough to have a
> great IP
> > provider. Ask for demos - most guys will install a 90 day trial or
> > like that. Do not believe the brochure, get the product installed
> put it
> > under load.
> > 10. Traffic prioritization at the IP demarc - total no brainer.
> > 11. Constant, constant user feedback and remediation. If you are
> > to your users, your install will ultimately fail even if you have
> > of everything. Underpromise and overdeliver. Never loose sight of
> > - they have to pick up the phone, and it has to work. Always.
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> > asterisk-users mailing list
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
> John Covici
> covici at ccs.covici.com
> --Bandwidth and Colocation provided by Easynews.com --
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
More information about the asterisk-users