you all - everyone who depends on Asterisk, or deploys it should be creating their own deployment guides for reference. Every Asterisk install is different, and thus you should treat it as such. You should put together a reference manual related to your particular install… Test test and test agian, and when its 100% you then have a reference guide along with a rock solid asterisk install.
There is nothing more important to a business owner than having some reference material with their phone system… and it is piece of mind for you as well
I use the wiki all the time, and anything I implement I promptly update my procedural manual on.
Create your own custom reference manuals and procedural manuals to protect yourselves and your clients![/quote]
I actually do that. Creating a complete reference manual for everything Asterisk is capable of doing and updating it is beyond the abilities of any one person or group of people though[/quote]
Not creating a reference manual for everything Asterisk can do, but creating a procedural manual for your clients on the features you have implemented. Even when you have great documentation for a product you should always create a procedural manual on what and how “your” using it. Everyone does things a little different, and your implementation though similar than maybe mine, will be differnent, and when you get into extensions.conf programming and extending the asterisk APIs then you have a new monster completely – though functionality stays the same.[/quote]
Well after the dual fiasco’s of the voip wiki down and the freepbx wiki still down I won’t be contributing to either of those anymore.
I’ll just stick to making my own little documents for my own use. Too bad as I really do believe in sharing the info. The more people share the better it is for all but until someone comes up with a more reliable way of doing this I’m not going to spend any more time on it.