On 12/27/05, Douglas Garstang <[EMAIL PROTECTED]> wrote: > It seems that Asterisk gives priority to extensions in the extensions.conf > file over what's access in the db via the switch statement. For example, if > you have an entry in extensions.conf and realtime for the same extension, > Asterisk won't look in the db. > > Anyone know if there's a way to switch this around, and have Asterisk look in > realtime first and then if it isn't accessible, use what's in > extensions.conf? Reason is for availability. If database is down, still allow > Asterisk to use what's in extensions.conf as a backup. >
If it can't be done via config, it's probably not too hard to change the code to do it. Be careful with switch though as that is the most demanding (query wise) of all the realtime engines at the moment. It will query the database with every call coming through the dial plan. If you know when your DP is changing, you may opt to do static instead and just reload from DB when your DP changes. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ _______________________________________________ --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
