Tilghman Lesher schrieb: > On Wednesday 11 February 2009 13:07:16 Gordon Henderson wrote: >> On Wed, 11 Feb 2009, Tilghman Lesher wrote:
>> > My viewpoint is that you should work on separation of your application >> > code versus data, so that other than new development, your dialplan >> > should be completely static and never need changing (other than, like I >> > said, new development). >> But what would you call "new development"? Say I have a site who has many >> extensions and they then wanted to create a call-group - ie. one new >> extension, ring multiple phones? >> >> In my world, they go to the web interface, create the extension, tick a >> selection of existing extensions and the code then writes out a new >> segment of dialplan to create the new extension, issues an extensions >> reload command to asterisk and off it goes... > I'd have a range of extensions, when dialled, it goes to the database, > retrieves the list of channels, and dials those channels. The web frontend > would look exactly the same, but the data would go directly into a database, > not taking an extra step to go into a dialplan, then reload the text file. How do you define the hints (for BLF, directed pickup, group pickup etc.)? Philipp Kempgen -- AMOOCON 2009, May 4-5, Rostock / Germany -> http://www.amoocon.de Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -> http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998 -- _______________________________________________ -- 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
