I lurk and comment a little on here and have been playing with * for a short while. I am interested in hearing about the pros and cons for using a database backend to Asterisk. My current setup is simple, out of the box with config files in /etc/asterisk and logs etc going into /var. I notice a great many of the contributors here seem to use a db backend (is this also called Real Time Asterisk?) and I'd like to know why if anyone cares to comment. Thanks Alan -- The way out is open! http://www.theopensourcerer.com
just my $0.02. don't interduce any other point of failure into a phone system. unless the need outweigh the disadvantage. On 11/28/07, Alan Lord <alanslists at gmail.com> wrote:> I lurk and comment a little on here and have been playing with * for a > short while. > > I am interested in hearing about the pros and cons for using a database > backend to Asterisk. My current setup is simple, out of the box with > config files in /etc/asterisk and logs etc going into /var. > > I notice a great many of the contributors here seem to use a db backend > (is this also called Real Time Asterisk?) and I'd like to know why if > anyone cares to comment. > > Thanks > > Alan > > -- > The way out is open! > http://www.theopensourcerer.com > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
Alan Lord wrote:> I notice a great many of the contributors here seem to use a db backend >I use it to add features that that change quite often. Black lists, meetme conferences, caller-id lookups, DID routing, fax2email, etc. I just make sure that nothing that I add, if it were to fail (Say, MySQL were down), would impede the basic function of the phone system. Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
Pros: 1. No need to reload Asterisk when you change settings 2. Changes are applied instantly 3. Easy to manage dialplan/users/settings 4. With properly programmed GUI you can give users some self-help services 5. No noticable overhead - dual xeon + 2gb ram does 400 simm. calls 6. You can have your DB on other server, that let's you connect several Asterisk servers to one DB - unified configuration Cons: 1. None Regards/Pagarbiai, Mindaugas Kezys Advanced Billing for Asterisk PBX -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Alan Lord Sent: Wednesday, November 28, 2007 6:22 PM To: asterisk-users at lists.digium.com Subject: [asterisk-users] To DB or not to DB? I lurk and comment a little on here and have been playing with * for a short while. I am interested in hearing about the pros and cons for using a database backend to Asterisk. My current setup is simple, out of the box with config files in /etc/asterisk and logs etc going into /var. I notice a great many of the contributors here seem to use a db backend (is this also called Real Time Asterisk?) and I'd like to know why if anyone cares to comment. Thanks Alan -- The way out is open! http://www.theopensourcerer.com _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
I think the answer to this really depends on how regularly you make changes to your config. Adding a database connection increases the complexity (although it is not rocket science) and adds moving parts and therefore has more things to go wrong. If you are using Dynamic realtime, then you are relying 100% on your database being up for your phone system to work. With static realtime, you gain some benefit of the config being cached inside asterisk and reloaded when necessary. For a simple setup, which does not change regularly (as is common with most small office systems) - I do not see the need in using a database to store configs - obviously in a big network with hundreds of users, the advantages of using a database increases with size. Robert McNaught -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071128/e885f9ce/attachment.htm
On Nov 28, 2007 8:48 AM, Mindaugas Kezys <mkezys at gmail.com> wrote:> Pros: > > 1. No need to reload Asterisk when you change settings >Is reloading the text based config that dangerous? Is there a memory leak or something? How many times can you reload before you should restart Asterisk? -Thermal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071128/5acce2e8/attachment.htm