Dynamic Routes Future plans: Difference between revisions
Jump to navigation
Jump to search
(Created page with "* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)") |
No edit summary |
||
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches) | '''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. |
Latest revision as of 18:58, 29 October 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.