[asterisk-users] Static extensions.conf|ael, best practice, hints (was: Re: What do you use? .conf or AEL?)
Philipp Kempgen
philipp.kempgen at amooma.de
Mon Feb 23 04:49:15 CST 2009
Tilghman Lesher schrieb:
> On Wednesday 11 February 2009 13:39:58 Philipp Kempgen wrote:
>> Tilghman Lesher schrieb:
>> >> 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).
>> > 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.)?
>
> As of 1.6, you can have pattern-match hints that query a database for the
> actual set of channels.
Two additional questions:
What about permissions that could be expressed by contexts without
actually using contexts (static dialplan, not to be modified by
a web interface)?
What about permissions that are more complicated than what can be
expressed by contexts?
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
--
More information about the asterisk-users
mailing list