On Tue, 2 Aug 2005, Andrew Kohlsmith wrote:
> On Tuesday 02 August 2005 09:55, Adam Dobrin wrote: > > And as much as you dislike these kinds of questions; its unfortunate > > that the community doesn't have any good answers to them available--they > > should be. It would be great if we could get some independent > > verification of digium's claims/figures. > > Unfortunately it's NOT that simple. The motherboard and chipset play a big > part in this, as does the network card, the types of codecs you're > transcoding between, the SIP UAs if you're using it, what esle the box is > doing... > > Honestly if you're unsure you grab a box you think will work (use some margin > here) and try. Report back. It's the only way you'll figure it out. I (and > most others) can't be arsed to try and cut every corner so you just don't see > the figures, and Digium's figures are for a specific system and setup. YMMV. So, I know that a 3GHz P4 box with 1GB ram, Intel 815 chipset can handle 120 concurrent calls on Zaptel PRI trunks - these are looped, with one side of the call playing musiconhold, the other side playing various gsm prompts. About 70% CPU used, no slips or anything, subjective voice quality perfect. I was able to add 5000 SIP and 5000 IAX2 peers registering - that's about 100 registrations per second - that pretty much fills the CPU up but still things sound fine. These were using realtime but with rtcachefriends I think. But, on top of that add a Monitor() into gsm format on one side of each call - that's 60 Monitors - and cpu starts becoming a problem. Of course, I can't answer the question as to minimum CPU - I only have the CPU that I have. Hope that is some help, Steve _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
