> > Bartek Kania wrote: > > There has been talk of replacing the dialplan with > something good and > > beautiful. > > > > What features do we want/need in the dialplan and how should they > > work? And, do we have anyone who wants to code it? > > Take a look at how FreeSwitch have incorporated JavaScript in the > dialplan. I think it's possible to build some fairly powerful > behaviour, > with only a small handful of primitive functions (such as > opening an RTP > stream, recording a file, playing a file, detecting DTMF etc). > > A lot of what is implemented as dialplan apps or functions in > Asterisk/OpenPBX will be native features of most languages (such as > string handling, conditional branching, date/time functions). >
Benjk and I were excited about the io language (http://www.iolanguage.com/about/). It's very small, embeddable and extensible. We need to move away from the status quo and find something powerful that is also intuitive. "like legos" I believe there is a need for a two-layer plan, at least conceptually two layers. The top layer is simple and works like legos or a GUI, very intuitive. The bottom layer is more involved and is used to create the building blocks for the simple layer. Maybe it would be like macros in current dialplan terminology. There would probably be a standard library of functions. Both layers can be changed however anyone who can do current dial-plans would easily pick up the syntax for the lego-like dial plan layer. Also, we can get rid of silly repetition like "exten 220 => " over and over again. Hopefully use labels instead of "priorities" if something like that is still needed. Whatever we choose should also lend itself easily to some kind of GUI adaptation. -Nate _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
