Dynamic Routes Future plans: Difference between revisions

Latest revision as of 19: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.

@@ Line 1: / Line 1: @@
+'''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.
-* 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 stop regardless of whether the user has pressed #. This allows for capturing simple yes/no responses with single digit 1 or 2.
+* 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.
-* 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, for example