Dynamic Routes FAQ - Revision history

John: /* Q. What does the message > mean? */

2021-01-05T11:37:25Z

Q. What does the message > mean?

← Older revision		Revision as of 13:37, 5 January 2021
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is ~~not part of~~ the ~~FreePBX core release~~ and ~~therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at~~ this ~~time I have not applied for code signing rights~~.		From version 15.0.1 Dynamic Routes is included in the Contributed modules repository ("Unsupported" repository in module admin). So from version 15.0.1 you may access an officially signed module and this warning will no longer be visible.

	~~You~~ may find the following [https://wiki.freepbx.org/display/FOP/Signing+your+own+modules link] helpful if you would like to remove the warning. It explains how to sign your own modules. It is possible to sign the module with a local key.		For previous versions, they were not part of the FreePBX official releases and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, I have not applied for code signing rights and with the inclusion of 15.0.1 in Freepbx this will no longer be necessary. If you are still using an early version, you may find the following [https://wiki.freepbx.org/display/FOP/Signing+your+own+modules link] helpful if you would like to remove the warning. It explains how to sign your own modules. It is possible to sign the module with a local key.

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2019-12-07T10:29:22Z

Q. What does the message > mean?

← Older revision		Revision as of 12:29, 7 December 2019
Line 41:		Line 41:
	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights.

	You may find the following link helpful if you would like to remove the warning. It explains how to sign your own modules. It is possible to sign the module with a local key.		You may find the following [https://wiki.freepbx.org/display/FOP/Signing+your+own+modules link] helpful if you would like to remove the warning. It explains how to sign your own modules. It is possible to sign the module with a local key.
	~~[https://wiki.freepbx.org/display/FOP/Signing+your+own+modules]~~

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2019-12-07T10:28:25Z

Q. What does the message > mean?

← Older revision		Revision as of 12:28, 7 December 2019
Line 40:		Line 40:

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights.

			You may find the following link helpful if you would like to remove the warning. It explains how to sign your own modules. It is possible to sign the module with a local key.
			[https://wiki.freepbx.org/display/FOP/Signing+your+own+modules]

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. Does Dynamic Route create the lookup table I will use in my query? */

2018-01-21T17:36:48Z

Q. Does Dynamic Route create the lookup table I will use in my query?

← Older revision		Revision as of 19:36, 21 January 2018
Line 57:		Line 57:
	===Q. Does Dynamic Route create the lookup table I will use in my query?===		===Q. Does Dynamic Route create the lookup table I will use in my query?===

	A. No. Dynamic Route creates the internal tables needed to store the configurations of the Dynamic Routes that you define. Specific Dynamic Routes may be configured to access a database table containing data that will be used in the routing decision. This data is external to Dynamic Routes and Dynamic Routes will only query this data as directed to do so by your configuration. Dynamic Routes will not create your external data tables or data. If you need an example of how to set up data tables to be queried by Dynamic Route, then please see this [[~~Creating a table for use with Dynamic Routes~~\|link]] for information.		A. No. Dynamic Route creates the internal tables needed to store the configurations of the Dynamic Routes that you define. Specific Dynamic Routes may be configured to access a database table containing data that will be used in the routing decision. This data is external to Dynamic Routes and Dynamic Routes will only query this data as directed to do so by your configuration. Dynamic Routes will not create your external data tables or data. If you need an example of how to set up data tables to be queried by Dynamic Route, then please see this [[Creating_a_MySQL_table_for_use_with_Dynamic_Routes\|link]] for information.

	===Q. Why don't my inbound calls get routed through Dynamic Routes?===		===Q. Why don't my inbound calls get routed through Dynamic Routes?===

John: /* Q. What does the message > mean? */

2018-01-21T17:34:39Z

Q. What does the message > mean?

← Older revision		Revision as of 19:34, 21 January 2018
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sangoma key signing agreement requires that the developer indemnify Sangoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge. I don't see any easy solution to this, but if you have a suggestion you are welcome to contact me.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights.

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2016-07-28T09:43:44Z

Q. What does the message > mean?

← Older revision		Revision as of 11:43, 28 July 2016
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The ~~Sagoma~~ key signing agreement requires that the developer indemnify ~~Sagoma~~ for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge. I don't see any easy solution to this, but if you have a suggestion you are welcome to contact me.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sangoma key signing agreement requires that the developer indemnify Sangoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge. I don't see any easy solution to this, but if you have a suggestion you are welcome to contact me.

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2016-07-28T09:33:51Z

Q. What does the message > mean?

← Older revision		Revision as of 11:33, 28 July 2016
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sagoma key signing agreement requires that the developer indemnify Sagoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sagoma key signing agreement requires that the developer indemnify Sagoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge. I don't see any easy solution to this, but if you have a suggestion you are welcome to contact me.

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2016-07-28T09:32:45Z

Q. What does the message > mean?

← Older revision		Revision as of 11:32, 28 July 2016
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sagoma key signing agreement requires that the developer indemnify Sagoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. ~~While a~~ commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is ~~given away~~ free of charge.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sagoma key signing agreement requires that the developer indemnify Sagoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. A commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is provided free of charge.

	==Configuration FAQ==		==Configuration FAQ==

John: /* Q. What does the message > mean? */

2016-07-28T09:31:43Z

Q. What does the message > mean?

← Older revision		Revision as of 11:31, 28 July 2016
Line 39:		Line 39:
	* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning		* Locally modified modules (for example to add a bug fix or new feature while waiting for that to be included in the official version) produce a tampered module warning

	Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. ~~If you feel~~ that it is a ~~problem to live~~ with ~~the warning message~~, ~~you are welcome~~ to ~~contact me~~.		Dynamic Routes is not part of the FreePBX core release and therefore the code is not signed by Sangoma. Although Sangoma provides for third party code signing after execution of a contract, at this time I have not applied for code signing rights. The Sagoma key signing agreement requires that the developer indemnify Sagoma for legal fees for any claims arising from the signed module. While that seems quite reasonable, signing this condition would open the developer up to the risk of unlimited legal fees. While the probability of that happening may be low, there is the potential to have to spend money fighting off even unfounded claims. While a commercial operation might mitigate those risks with income from software licences, I cannot afford to do that as the Dynamic Route software is given away free of charge.

	==Configuration FAQ==		==Configuration FAQ==

John: /* When reporting a problem what information should I provide? */

2016-06-13T14:03:14Z

When reporting a problem what information should I provide?

← Older revision		Revision as of 16:03, 13 June 2016
Line 67:		Line 67:
	===When reporting a problem what information should I provide?===		===When reporting a problem what information should I provide?===

	Please see [[Support\|here]]		Please see [[Dynamic Routes Support\|here]]

	===Q. Why do I get strange errors when using asterisk MYSQL module?===		===Q. Why do I get strange errors when using asterisk MYSQL module?===