Hi Douglas Garstang,
Check out the functionality of AMP (Asterisk Management Portal). It
does what you want. It stores the configuration in the DB, then runs
some perl scripts to generate configuration files from the DN and then
reloads asterisk.
HTH.
Regards,
Jithu
Peter Bowyer wrote:
On 22/12/05, Douglas Garstang <[EMAIL PROTECTED]> wrote:
Just wondering if anyone here has tried the approach, where all config files
are stored in a database, maybe using the ast_static table structure. Rather
than using realtime to access the database live, you have scripts that read
the contents of the db, and generate the .conf files from that., and then do
a 'reload'.
Anyone tried that? How'd it work for you?
http://www.voip-info.org/wiki/view/Asterisk+configuration+from+database
Specifically, option 4b. You have scripts to do the bulk of this in
your /contrib directory.
--
Peter Bowyer
Email: [EMAIL PROTECTED]
Tel: +44 1296 768003
VoIP: sip:[EMAIL PROTECTED]
VoIP: [EMAIL PROTECTED]
FWD: **275*5048707000
VoipTalk: **473*5048707000
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
