[VoiceOps] Centralized management for distributed Asterisk servers

Troy Davis troy at yort.com
Tue Jan 11 12:38:41 EST 2011


I'd echo that.  Your best bet for lots of small on-site installs that don't
depend on a central resource is probably one of these:

1) puppet, chef, or another automated deployment system with file template
support and SCCS-style versioning.  puppet and chef both support erb
templates and deploying from a git repo, which would be ideal for this.

2) Asterisk RealTime on a local Postgres/MySQL server (potentially
co-resident with Asterisk, though security may dictate otherwise).  If you
don't make a lot of config changes, this is probably overkill -- #1 alone is
probably enough.

3) Starting with a Switchvox or at least AsteriskNow ISO.  Both are
fully-baked products, so I wouldn't expect them to be the skeleton you use
for #1 or #2, but they might get you started.


Also, it's worth asking them how independent each of these nodes will really
be.  Some folks are adamant about distributed on-site PBXes, then still use
VoIP over consumer/SMB broadband Internet.  They still can't call out during
IP connectivity outages, have introduced lots more failure cases with a
zillion tiny, under-maintained systems, and often don't put in the effort to
fully automate the deployment/maintenance.

Troy

-- 
http://twitter.com/troyd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110111/5053433a/attachment.html>


More information about the VoiceOps mailing list