Asterisk Up-to-Speed
PBX - New Features, Upgrades, and Changes
Asterisk 1.4 -> Asterisk 1.6.0 -> Asterisk 1.6.1 -> Asterisk 1.6.2 -> Asterisk 1.8
PBX - New Features, Upgrades, and Changes
Asterisk 1.6.0 -> Asterisk 1.6.1- It is now possible to specify a pattern match as a hint. Once a phone subscribes to something that matches the pattern a hint will be created using the contents and variables evaluated.
- Dialplan matching has been extended to allow an extension to return to the PBX core to wait for more digits. This is done by using the new dialplan application called "Incomplete". This will permit a whole new level of extension control, by giving the administrator more control over early matches employing one of the short-circuit pattern match operators. Note that custom applications can trigger this same behavior by returning the special value AST_PBX_INCOMPLETE.
- In the dialplan expression parser, the logical value of spaces immediately preceding a standalone 0 previously evaluated to true. It now evaluates to false. This has confused a good many people in the past (typically because they failed to realize the space had any significance). Since this violates the Principle of Least Surprise, it has been changed.
- extensions.conf now allows you to use keyword "same" to define an extension
without actually specifying an extension. It uses exactly the same pattern
as previously used on the last "exten" line. For example:
exten => 123,1,NoOp(something)
same => n,SomethingElse()
LUA SUPPORT:
- Added support for writing and running your dialplan in lua using the pbx_lua module. See configs/extensions.lua.sample for examples of how to do this.
DUNDI:
- pbx_dundi.c: tos parameter changed to use new values. Old values like lowdelay, lowcost and other is not acceptable now. Look into qos.tex for description of this parameter.
- Added the ability to specify arguments to the Dial application when using the DUNDi switch in the dialplan.
- Added the ability to set weights for responses dynamically. This can be done using a global variable or a dialplan function. Using the SHELL() function would allow you to have an external script set the weight for each response.
- Added two new dialplan functions, DUNDIQUERY and DUNDIRESULT. These
functions will allow you to initiate a DUNDi query from the dialplan,
find out how many results there are, and access each one.