<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mike wrote:
<blockquote cite="mid:023501c9a8cb$3a4fb720$aeef2560$@ca" type="cite">
<blockquote type="cite">
<pre wrap="">You can reliably run asterisk on just about any x86 hardware. You don't
mention what kind of stresses you are going to put on it, so your sizing
questions are impossible to answer. How many extensions? How many
simultaneous calls? Will you be transcoding? Routing to/from the PSTN?
What cards will you be putting in the box? Some cards don't play nicely
together if forced to share interrupts, for example.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
Sizing is important. Take your company's projected growth rate, double
it, and work it out for 3-5 years. I recommend 5 years for the<br>
sizing. As much as its fun to tinker, once it goes into production you
want to have it as stable as possible.<br>
<br>
Look at all the apps you want to use and figure out how much they are
going to cost you in terms of resources. In the company<br>
I work for, we put in Asterisk to replace our Nortel system which
reached the limits. So we expected standard usage rates<br>
and growth etc.<br>
<br>
However, once we introduced meetme application our Asterisk usage
spiked. We figured on average 2-3<br>
meetme meetings a week (based on the usage of a third party conference
bridge we had before), and now<br>
its at 2-3 a day. We had it setup so that every person has their own
conference bridge.<br>
<br>
Other features are also taking up more resources. I'm currently
modigying meetime and writing an AGI so that<br>
once the meetme conference ends, it will take the recording and conver
it to an mp3 and then emails it to <br>
the leader. <br>
<br>
<br>
<br>
<blockquote cite="mid:023501c9a8cb$3a4fb720$aeef2560$@ca" type="cite">
<pre wrap="">
I wasn't worried about sizing (let's imagine that this is more than enough
for now and less than I'll need later). More about whether this was the
right BRAND more than the right hardware. Does HP make Asterisk friendly
hardware? I know Dells was problems a few years back.
As for CPU, the question is mostly one about more GHz or more cores? Dual
cores are cheaper by GHz. What`s best for Asterisk?
I am doing only SIP to SIP calls. Some transcoding (half calls are G711 to
G729, the other half are G729 both ways).
[snip]
</pre>
<blockquote type="cite">
<pre wrap="">I'm shooting from the hip here, but I don't think dual CPU gives you
</pre>
</blockquote>
<pre wrap=""><!---->redundancy. If one chip fries I am pretty sure the machine will crash.
This was sort of a question disguised as a statement. Can a CPUs function
when it's neighbour is fried?
Mike
</pre>
</blockquote>
<blockquote cite="mid:023501c9a8cb$3a4fb720$aeef2560$@ca" type="cite">
<pre wrap="">
_______________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a>
</pre>
</blockquote>
<br>
</body>
</html>