On Feb 22, 2006, at 6:33 PM, Bartek Kania wrote:
As I recall anthm made a pluggable pbx patch to allow different
dialplans, maybe we should look into that first.
That can easily be accommodated with the property list system. All we
need is a key/value pair in the master config file that says which
language the dialplan is in and what module is required to understand
it.
I have now played with the master config plist to see how this can be
incorporated and I came up with two different flavours ...
One way would be to add a new section for the dialplan, like so ...
Dialplan = {
Engine = "asterisk_v1.0";
MethodOfConfiguration = ini;
};
Alternatively, an entry called "_dialplan" could be added to the
"Modules" section. The underscore would be to indicate that this is
not a real module but an internal one.
This would then look like so ...
Modules = {
_dialplan = {
Engine = "asterisk_v1.0";
MethodOfConfiguration = ini;
};
I am leaning towards the first method. However, if the goal is to
eventually make the dialplan engine a plug-in module, then the second
method may be prefereable as all we'd need to do to accommodate the
architectural change would be to remove the preceding underscore.
Another question that comes up is whether or not to remove the
"dialplan" parameter from the "Filenames" section and move it into
the dialplan entry/section.
Let me know what you think.
regards
benjk
___________________________________________________________
Yahoo! Photos NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
