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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Lord Sent: Wednesday, November 28, 2007 6:22 PM To: [email protected] 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 _______________________________________________ --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
