> I'm working on a 500 seats Asterisk project. > I'm wondering whether or not I should consider using Asterisk > Realtime and a database to manage phones registrations.
As far as stability goes, I've had no problem with realtime. In fact I've run a nationwide VoIP provider with asterisk using realtime. The main consideration I would make for using/not using it is how dynamic the system is. If you have 500 seats that aren't likely to change and aren't designing an interface to actually manage those users, then go static. Less complexity, less chance for failure (you don't have to worry about db servers, etc.). On the other hand, if it is for a situation where you are constantly adding phones, changing caller-ids, swapping phones and their extensions, etc. Realtime is the only way to go. And a free hint: if you are going to have to do anything that resembles number porting, swapping extensions, etc.--don't use extensions/phone numbers as SIP usernames. You have to regenerate config files, etc. Make your SIP usernames meaningless and use func_odbc to look up what extension is tied to which device. Terry _______________________________________________ --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