<br><br><div class="gmail_quote">2009/5/9 Steve Edwards <span dir="ltr"><<a href="http://asterisk.org">asterisk.org</a>@<a href="http://sedwards.com">sedwards.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, 8 May 2009, Dave Walker wrote:<br>
<br>
> I have a question for those who have done a few professional installs of<br>
> Asterisk. Is it taboo to use something like AsteriskNow/FreePBX/Trixbox<br>
> to get a base installation of Asterisk installed and functional for a<br>
> small office? If not then do you always compile from scratch or use<br>
> CentOS and the yum repositories?<br>
<br>
</div>I used Asterisk At Home (predecessor of Trixbox) for my first couple of<br>
installs. I didn't need most of the cruft included and never took the time<br>
to understand all the funny little things that were done behind my back to<br>
make life easy for someone with little to no Linux skills.<br>
<br>
Fortunately, I was able to replace those systems before they were hacked<br>
by default passwords and buggy code.<br>
<br>
Now, I install a minimal CentOS (de-selecting every single package) and<br>
yum in just what I need. Then I install Zaptel, Libpri, and Asterisk from<br>
source. (I'm a 1.2 Luddite.)<br>
<br>
"Parts left out don't get broke."<br>
<br>
Thanks in advance,<br>
</blockquote></div><br>Building everything from scrach each time is good when you have time, but when you want a nice web interface for cdr stats, end point management and good auto provisioning, it is not an option. Security issues are standing on good knowledge of the system and experience, to do not encounter "default passwords and buggy code" issues.<br>
Have fun.<br>