for each context in realtime you must have an pointer to it in the extensions.conf or included file... heaving a flat config automade on a cronjob still leaves your with the need to execute and extension reload.
There will be changes in 1.6 that will allow you to have your entire extensions.conf in realtime so you can create pointable, immediatly accessable realtime entries with no need for the flat file point anymore. However keep in mind the current limitation and memory/performance issues you can run into when using real time on large systems. Rob Morris wrote: > HI There, > > > I am running Asterisk RealTIme using MYSql and have found the same limitation. > > > AS far as I can tell you must have the Realtime switch inside a flat > file (extensions.conf) for each context which is in MYSql. > > and of course every time you add a new context you must do a reload. > > One way to get around this is to create a new flat file say > 'mysql_context.conf' and include it in your extensions.conf. > > > this 'mysql_contexts.conf' can be generate from the Mysql database, > with a little programming. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
