I second the "Real" database idea. AFAIK, the Asterisk database is still a Berkley DB. I'm accessing Postgres using an AGI and returning dialplan variables with what I want to process. The Asterisk database is best for small, non-critical information, though there are good procedures documented for backup and reload of it.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Benny Amorsen Sent: Tuesday, April 21, 2009 11:39 AM To: Sriram Cc: [email protected] Subject: Re: [asterisk-users] Asterisk Database "Sriram" <[email protected]> writes: > 1. I need to store the CallerId of the PSTN caller with his language > preference so that next time he is played the prompt in his language that > he chose the first time.What would be better - storing his number in the > Asterisk DB and using Dbput and DBget ? or storing it in MySQL from the > dial plan and quering it everytime to see the callers record ? how many > records can AstDB handle safely ? In my case the total records wont exceed > 20,000 since there are many repeat callers ? Asterisk DB is either an SQLite database or a Berkeley database, I forget which (did it change?). Either way, 20,000 should be a problem for the underlying database. I'd still go for the "real" database (using Postgres, but I guess you can use MySQL if you feel like it), probably using func_ODBC. With Asterisk DB you have to go through Asterisk to view or change contents of the database; a real database makes management easier. /Benny _______________________________________________ -- 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
