Dynamic Routes Future plans - Revision history

John at 17:58, 29 October 2017

2017-10-29T17:58:42Z

← Older revision		Revision as of 19:58, 29 October 2017
Line 3:		Line 3:
	* 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.
	* 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, {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 #.

John at 22:49, 10 September 2017

2017-09-10T22:49:25Z

← Older revision		Revision as of 00:49, 11 September 2017
Line 1:		Line 1:
	'''Changes that may be ~~address~~ in a future release'''		'''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.

John at 22:49, 10 September 2017

2017-09-10T22:49:15Z

← Older revision		Revision as of 00:49, 11 September 2017
Line 1:		Line 1:
			'''Changes that may be address 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.
	* 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, {name} would be replaced with the value of variable name.

	'''Changes committed to master but not yet ~~release~~'''		'''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 #.		* 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 #.

John at 22:48, 10 September 2017

2017-09-10T22:48:35Z

← Older revision		Revision as of 00:48, 11 September 2017
Line 2:		Line 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, {name} would be replaced with the value of variable name.

	Changes committed to master but not yet release		'''Changes committed to master but not yet release'''
	* 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 #.		* 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 #.

John at 22:48, 10 September 2017

2017-09-10T22:48:22Z

← Older revision		Revision as of 00:48, 11 September 2017
Line 1:		Line 1:
	* 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.
			* 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 release
	* 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 #.		* 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 #.
	* 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.

John at 06:44, 24 August 2017

2017-08-24T06:44:34Z

← Older revision		Revision as of 08:44, 24 August 2017
Line 1:		Line 1:
	* 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.
	* 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.		* 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 #.
	* 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~~ {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, {name} would be replaced with the value of variable name.

John at 06:39, 24 August 2017

2017-08-24T06:39:26Z

← Older revision		Revision as of 08:39, 24 August 2017
Line 1:		Line 1:
	* 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.
	* 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.		* 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, for example		* 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 {name} would be replaced with the value of variable name.

John at 06:36, 24 August 2017

2017-08-24T06:36:38Z

← Older revision		Revision as of 08:36, 24 August 2017
Line 1:		Line 1:
	* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)		* 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.		* 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, for example

John at 06:27, 24 August 2017

2017-08-24T06:27:58Z

← Older revision		Revision as of 08:27, 24 August 2017
Line 1:		Line 1:
	* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)		* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)
			* 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.

John: Created page with "* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)"

2016-06-18T08:00:16Z

Created page with "* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)"

New page

* Optimize the dial plan results checking syntax (can be useful if there are a lot of matches)