Tilghman Lesher wrote: > > > I *STRONGLY* recommend that you do NOT use realtime extensions. If you > want a dynamic dialplan, the correct way to do it is to segregate your logic > and your data (via something like func_odbc), not to stick all of your logic > into a database. >
Should this be taken as a warning to us happy realtime users that it is deprecated, and/or likely to go away? If that's where it's headed (once upon a time a discussion to "do it the right way" was scheduled for the Atlanta confab last spring, but the topic never emerged there AFAIK) then it ought to be officially deprecated so those of us who use it extensively can begin to plan our migration to other ways of solving the problems that realtime seems (at least to me) to solve nicely. I can deploy large numbers of servers with complex and coherent dialplans with pretty much zero effort on a given new client, and I can also effect system-wide changes across my servers with a single database update. I find it to be a powerful and useful feature. But if there's a better way to do it I'm willing to learn. To my knowledge there are no Postgres ports of ODBC running yet under openWRT, and so I am using the PG module to access my information. At the moment func_odbc wouldn't seem to get the job done for me as per your suggestion above. B. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ --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
