Dynamic Routes Future plans: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Changes that may be | '''Changes that may be addressed in a future release''' | ||
* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches). Currently each match is managed by a sequential IF statement. This could be done differently by going directly to the mached entry. | * Optimize the dial plan results checking syntax (can be useful if there are a lot of matches). Currently each match is managed by a sequential IF statement. This could be done differently by going directly to the mached entry. | ||
Revision as of 23:49, 10 September 2017
Changes that may be addressed in a future release
- Optimize the dial plan results checking syntax (can be useful if there are a lot of matches). Currently each match is managed by a sequential IF statement. This could be done differently by going directly to the mached entry.
- Allow for the lookup string to contain asterisk variable substitutions. Currently [name] is substituted by the value of variable DYNROUTE_name, so it is not possible to use arbitrary asterisk variables. By introducing a new lookup type, {name} would be replaced with the value of variable name.
Changes committed to master but not yet released
- Introduce a new field which contains the maximum length of DTMF input. Default is 0 which means no limit. When the limit is reached DTMF input stops regardless of whether the user has pressed #. This allows for example the capturing of simple yes/no responses with single digit 1 or 2 without needing to press #.