On Mon, 31 Oct 2005, Greg Boehnlein wrote: >As long as you need to do things the way that [EMAIL PROTECTED] has decided is >the >"correct" way to do things. If you need to step outside of the basic >parameters for which it was originally intended and do any minute amount >of customization, the chore becomes ominous. The name of the product is >"Asterisk At Home" not, "Asterisk At A Small Business".
>Just as Digium about the nightmares they have in their support desk >because of [EMAIL PROTECTED] You can really make the best of all worlds if you use [EMAIL PROTECTED] as a quick load ([EMAIL PROTECTED]) then adjust. I use the 1.5 [EMAIL PROTECTED] load, yum update, then pull CVS for zaptel, libpri, asterisk & asterisk-addons. After modifications such as WebMin, TFTP, and the like I pick up the new AMP AMP 1.10.009 writes over the header file in apache and adds the new voice mail interface. Sugar and [EMAIL PROTECTED] interfaces are hidden but available, but you can always delete the web folders. I add the interface to the cisco xml to allow for the interface to the contact portion of sugar, but do the contacts DB upload without sugar. I add an XML interface to the cisco phones so the extensions in AMP are available as a directory at the phone. I add a paging for all / one / or groups of extensions. You do not deal with [EMAIL PROTECTED] limitations, but rather the AMP system. I do not find AMP limiting, and if you look at the configuration files there is a way to override every customization installed by AMP. So when I need to dial another server without using a prefix I can customize the extensions.conf by using the custom file (which takes precedence) rather that the rewritten AMP extensions file. You should take another look at the time saver. Since that is what it really is. Regards, Paul Norris _______________________________________________ Asterisk-Biz mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-biz
