Douglas Garstang 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.
This is true in general for Asterisk dialplans, it has nothing to do with Realtime.
Extensions defined in the context itself are always searched before any included contexts or switches. If you want to control the search order, you must put _all_ your extensions into separate contexts (by type or whatever other grouping you wish) and then use a 'master' context with include/switch statements in the order you wish them to be processed.
_______________________________________________ --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
