Dynamic Routes Reference documentation - Revision history

John: /* Substitutions */

2018-06-08T04:16:41Z

Substitutions

← Older revision		Revision as of 06:16, 8 June 2018
Line 126:		Line 126:
	\|-		\|-
	\| DYNROUTE_name		\| DYNROUTE_name
	\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module. To ~~refer to~~ the variable named name, use ${DYNROUTE_name} in the Asterisk dial plan.		\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module. To obtain the value of the variable named name, use ${DYNROUTE_name} in the Asterisk dial plan.
	\|}		\|}

John: /* Substitutions */

2018-06-08T04:16:16Z

Substitutions

← Older revision		Revision as of 06:16, 8 June 2018
Line 126:		Line 126:
	\|-		\|-
	\| DYNROUTE_name		\| DYNROUTE_name
	\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module. To refer to the variable named ~~xxx~~, use ${~~DYNROUTE_xxx~~} in the Asterisk dial plan.		\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module. To refer to the variable named name, use ${DYNROUTE_name} in the Asterisk dial plan.
	\|}		\|}

John at 04:15, 8 June 2018

2018-06-08T04:15:42Z

← Older revision		Revision as of 06:15, 8 June 2018
Line 91:		Line 91:
	\| Asterisk Variable		\| Asterisk Variable
	\| The lookup value is read from an Asterisk Variable. The parameters used are:		\| The lookup value is read from an Asterisk Variable. The parameters used are:
	* Asterisk Variable: the variable name from which to read the result. Example: ${~~DYNROUTE_dtmf~~}. Complex expressions may also be written provided they use valid Asterisk functions, for example: ${REGEX("^1.3$" ${DYNROUTE_dtmf})} would check that the DTMF input was in the range 1000-1999 (providing that the Saved input variable name was set to "dtmf")		* Asterisk Variable: the variable name from which to read the result. Example: ${xxx}. Complex expressions may also be written provided they use valid Asterisk functions, for example: ${REGEX("^1.3$" ${DYNROUTE_dtmf})} would check that the DTMF input was in the range 1000-1999 (providing that the Saved input variable name was set to "dtmf")
	\|}		\|}

Line 126:		Line 126:
	\|-		\|-
	\| DYNROUTE_name		\| DYNROUTE_name
	\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module.		\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module. To refer to the variable named xxx, use ${DYNROUTE_xxx} in the Asterisk dial plan.
	\|}		\|}

John: /* Substitutions */

2017-08-24T06:25:05Z

Substitutions

← Older revision		Revision as of 08:25, 24 August 2017
Line 115:		Line 115:
	\|-		\|-
	\| [name]		\| [name]
	\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you are using two levels of Dynamic Route so that you can save the DTMF from the previous Dynamic Route in a uniquely named variable and use that variable in the lookup of the second Dynamic Route. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a later Dynamic Route.		\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you are using two levels of Dynamic Route so that you can save the DTMF from the previous Dynamic Route in a uniquely named variable and use that variable in the lookup of the second Dynamic Route. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a later Dynamic Route.<br><br>If you want to use a variable created outside Dynamic Routes in the lookup, then name the variable with a DYNROUTE_ prefix. Then [name] will be substituted by the value of the asterisk variable DYNROUTE_name. There is currently no way of reading an arbitrarily named asterisk variable, except for the lookup type "Asterisk variable".
	\|}		\|}

John: John moved page Reference documentation to Dynamic Routes Reference documentation without leaving a redirect

2016-06-13T13:19:30Z

John moved page Reference documentation to Dynamic Routes Reference documentation without leaving a redirect

← Older revision		Revision as of 15:19, 13 June 2016
(No difference)

John at 08:54, 12 June 2016

2016-06-12T08:54:28Z

← Older revision		Revision as of 10:54, 12 June 2016
Line 48:		Line 48:
	\|-		\|-
	\| Default Destination		\| Default Destination
	\| Destination to send the call to if the lookup ~~results~~ does not match one of the match values in the Dynamic Route Entries section or if the lookup fails. This is optional but is strongly recommended. If there is no default destination defined, then in the case of a lookup failure or if the lookup result does not match one of the defined values, the call will be disconnected. ~~By defining a~~ default destination ~~you get to choose~~ the behaviour.		\| Destination to send the call to if the lookup result does not match one of the match values in the Dynamic Route Entries section or if the lookup fails. This is optional but is strongly recommended. If there is no default destination defined, then in the case of a lookup failure or if the lookup result does not match one of the defined values, the call will be disconnected. If this is not what is required, define the default destination with the desired behaviour.
	\|-		\|-
	\| Dynamic Route Entries		\| Dynamic Route Entries

John at 08:53, 12 June 2016

2016-06-12T08:53:17Z

← Older revision		Revision as of 10:53, 12 June 2016
Line 39:		Line 39:
	\|-		\|-
	\| Saved input varibale name		\| Saved input varibale name
	\| Name of variable in which to save DTMF input for future use in the ~~dialplan~~ or further dynamic routes. This is available as [name] in the query/lookup where name is the name of the variable you specify here. To use the variable in the ~~dialplan~~ (e.g. custom ~~applicaitons~~) it is necessary to prefix it with DYNROUTE_ e.g. DYNROUTE_name		\| Name of variable in which to save DTMF input for future use in the dial plan or further dynamic routes. This is available as [name] in the query/lookup where name is the name of the variable you specify here. To use the variable in the dial plan (e.g. custom applications) it is necessary to prefix it with DYNROUTE_ e.g. DYNROUTE_name
	\|-		\|-
	\| Saved result variable name		\| Saved result variable name
	\| Name of variable in which to save lookup result for future use in the ~~dialplan~~ or further dynamic routes. This is available as [name] in the query/lookup where name is the name of the variable you specify here. To use the variable in the ~~dialplan~~ (e.g. custom ~~applicaitons~~) it is necessary to prefix it with DYNROUTE_ e.g. DYNROUTE_name		\| Name of variable in which to save lookup result for future use in the dial plan or further dynamic routes. This is available as [name] in the query/lookup where name is the name of the variable you specify here. To use the variable in the dial plan (e.g. custom applications) it is necessary to prefix it with DYNROUTE_ e.g. DYNROUTE_name
	\|-		\|-
	\| Source Type		\| Source Type
Line 48:		Line 48:
	\|-		\|-
	\| Default Destination		\| Default Destination
	\| Destination to send the call to if the lookup results does not match one of the match values in the Dynamic Route Entries section or if the lookup fails.		\| Destination to send the call to if the lookup results does not match one of the match values in the Dynamic Route Entries section or if the lookup fails. This is optional but is strongly recommended. If there is no default destination defined, then in the case of a lookup failure or if the lookup result does not match one of the defined values, the call will be disconnected. By defining a default destination you get to choose the behaviour.

	\|-		\|-
	\| Dynamic Route Entries		\| Dynamic Route Entries

John at 23:25, 11 June 2016

2016-06-11T23:25:10Z

← Older revision		Revision as of 01:25, 12 June 2016
Line 78:		Line 78:
	\| A lookup is done to an Asterisk ODBC data source. The parameters used are:		\| A lookup is done to an Asterisk ODBC data source. The parameters used are:
	* ODBC function: the Asterisk ODBC function name that has been configured		* ODBC function: the Asterisk ODBC function name that has been configured
	* ODBC query: the query		* ODBC query: the query. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]'
	For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux \|article]]		For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux \|article]]
	\|-		\|-

John at 23:23, 11 June 2016

2016-06-11T23:23:46Z

← Older revision		Revision as of 01:23, 12 June 2016
Line 119:		Line 119:
	\|}		\|}

	<strong>In custom dial plan or other ~~Freepbx~~ modules</strong>		<strong>In custom dial plan or other FreePBX modules</strong>

	{\| class="wikitable"		{\| class="wikitable"
Line 127:		Line 127:
	\|-		\|-
	\| DYNROUTE_name		\| DYNROUTE_name
	\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another ~~Freepbx~~ module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another ~~Freepbx~~ module.		\| Where "name" is the value of one of these two fields: Saved input varibale name or Saved result varibale name. In the case of Saved input variable name, the DTMF input is saved under this name. This is useful if you need to use the value in a custom dial plan application or another FreePBX module. In the case of Saved result variable name, the result returned from the lookup is saved to the variable name and can be used in a custom dial plan application or another FreePBX module.
	\|}		\|}

John: /* Source Type */

2016-06-11T17:47:39Z

Source Type

← Older revision		Revision as of 19:47, 11 June 2016
Line 79:		Line 79:
	* ODBC function: the Asterisk ODBC function name that has been configured		* ODBC function: the Asterisk ODBC function name that has been configured
	* ODBC query: the query		* ODBC query: the query
	For information about setting up ODBC see this [[How to set up an ODBC on Linux \|article]]		For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux \|article]]
	\|-		\|-
	\| URL		\| URL