A template generator is
quite doable, In fact, someone has already done it. I still use it
regularly but work on it was discontinued maybe about a year ago
It works even better than
you might think. Creates maybe 90% and in some cases 100% deployment ready
conf files. It can even link in to remote Asterisk servers via SSH and
automatically transfer, update, and reload Asterisk configs.
You should still be able
to download it from their website but I don't see a link anywhere
obvious.
From: Gary G. Hendershot [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 10:08 AM
To: [EMAIL PROTECTED]; 'Discussion of AstLinux - Asterisk on Compact Flash'
Subject: [Astlinux-users] Sample Configs
I agree in principal with your goal but think reality may fall
short of your expectation ... I think you could probably get your "template" to
about 50% of deployment ready if you make some basic assumptions up front
.. assumptions like the type of phones you will use for example .. I
have found that even something as trivial as the sip.conf definition for each
phone model presents unique requirements ...
On the extensions.conf side of things, I think my own template is
about 60% ... all I need to do to get it ready to deploy is add the internal
extensions, assign the external peers to variables in the global section and
implement the IVR menu to provide the choices the client needs ... the
rudiments of the inbound/outbound call handling and the set of PBX features I
normally provide are ready to go ... but then my own requirements are very
modest and I purposely keep the extensions.conf simple ... suspect others would
want a lot more features than what I try to implement ..
The IVR system is usually the most complex item and is the
area where systems like TrixBox tend to really hold you back ... you could
template a basic tree with a main level and maybe a couple sub levels as an
outline, but actually tailoring it to the client need will still require some
effort ... and frankly, that is where you are earning your money when you set
one of these things up ...
Where you can use a template scenario is PBX feature
implementation ... stuff like the number to dial to retrieve voicemail and such
.. a template for these works well as basically what you are doing is writing
macros, functions or sub-routines that act on the same set of parameters each
time ... what changes is the parameters being passed ... so this chunk of
extensions.conf is pretty much a cut and paste type of thing ... the more code
you write in this manner, the more you can template ..
I think that when it comes to the sip.conf, iax.conf and
zapata.conf, things are bit more difficult to template ... I don't think I have
ever had 2 that were close enough that a template made sense ... I suspect that
if I were to limit myself to a single phone model and a single sip or iax
service provider this might be do-able ... but so far every one I have setup has
required very unique configs in these ... however, I have heavily
commented versions of each of these files that include the settings I used
previously for a variety of phones and services so I don't have to totally
reinvent the wheel each time ...
in any case, I am very interested in seeing where this leads you
.. I would love to see you prove me wrong and come up with a template that is
90% ready to go out of the box ... I am not the sharpest tool in the shed, so
please make me look like an idiot and do it ... I could benefit greatly from
your success in this area ...
my stuff is generally antiquated as I started writing it back
before version 1 of Asterisk and still use techniques that are out of date by
today's standards ... but if providing my stuff helps you figure out how
NOT to do it, I may actually be helping you .. let me know off list if
this would help you ...
G.Hendershot
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Caldwell
Sent: Wednesday, October 18, 2006 7:55 AM
To: Gene Cooper; Discussion of AstLinux - Asteriskon Compact Flash
Subject: Re: [Astlinux-users] Sample Configs
______________________
David Caldwell
Access IT Limited
t: +44(0)1227 750555
f: +44(0)1227 750070
w: www.accessit.co.uk
______________________
From: Gene Cooper [mailto:[EMAIL PROTECTED]
To: [EMAIL PROTECTED], Discussion of AstLinux - Asterisk on Compact Flash [mailto:[EMAIL PROTECTED]
Sent: Wed, 18 Oct 2006 04:14:43 +0100
Subject: Re: [Astlinux-users] Sample Configs
Welllll,
I hate to sound even more ignorant than usual, but I'm not happy with
_any_ of the configs I've come up with on my own.
I configured an Asterisk system from scratch a couple of years ago that
always had 'issues'. Then I found [EMAIL PROTECTED] and, though a bit
unwieldy, it worked great. I only had to do minor tweaks...which is a
lot easier than coming up with the entire configuration. I started
testing Astlinux using the default config files. I was able to make
things work, but I decided the default config files were meant more as
documentation than a practical application.
When I started evaluating Astlinux, I gave thought (and a small bit of
effort) to just copying the working Trixbox configs to Astlinux. I
decided that was just not a good idea...too messy.
I really would like to do this project justice. I really like the
'clean lines' of Astlinux and I'd really like my base config(s) to be
just as clean...then extend as necessary per client (as I'm sure many of
you already do).
I'd like to start with a small business scenario for 3-30 phones.
If given approval, I'll post the sample configs on a new support section
of my web site. I have a Docman file library I could use too. I can
also easily give other folks the ability to post wiki-style, if desired.
Thanks again,
G
David Caldwell wrote:
> Hi Gene,
>
> Yes, a page dedicated to configs would be useful IMO. What gaps have you
> got that need filling in your configs?
>
> David.
>
>
> ------------------------------------------------------------------------
>
> **********************************************************************************************************
> Disclaimer: This message may only be read in context and with common sense. If concerned by it or in doubt, please destroy it. If this message is not meant for you, we have made a mistake and would appreciate your help. We promise that we mean no offence and will endeavour to rectify our mistake. Our full contact details can be found on www.accessit.co.uk
> **********************************************************************************************************
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED].
--
=============================
Gene Cooper
Sonora Communications, Inc.
5531 N. Oracle Road
Tucson, AZ 85704
(520) 293-8461 x101
(520) 888-4060 fax
[EMAIL PROTECTED]
**********************************************************************************************************
Disclaimer: This message may only be read in context and with common sense. If concerned by it or in doubt, please destroy it. If this message is not meant for you, we have made a mistake and would appreciate your help. We promise that we mean no offence and will endeavour to rectify our mistake. Our full contact details can be found on www.accessit.co.uk
**********************************************************************************************************
_______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
