https://voipsupport.it/wiki/api.php?action=feedcontributions&feedformat=atom&user=John 2026-04-24T16:11:15Z User contributions MediaWiki 1.43.6 https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=897 2024-05-01T15:16:25Z

<p>John: </p> <hr /> <div><br /> The Dynamic Route module is now available in Freepbx, through the Unsupported Modules repository and can be installed directly from within Freepbx. Please use the version distributed with Freepbx. <br /> The source code can be accessed at https://github.com/FreePBX-ContributedModules/dynroute<br /> <br /> The contents of this site have been left as a reference. The new documentation is available at https://wiki.freepbx.org/display/FPG/Dynamic+Routes+Moduletext<br /> <br /> ==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> For previous history of Dynamic Route source code please see: [https://github.com/johnfawcett/dynroute/ old repository]<br /> <br /> ===FreePBX 15 support===<br /> <br /> The latest stable release 15.0.1 is available directly in Freepbx module admin by enabling the &quot;Unsupported modules&quot; repository. A bug fix and enhancement release is available (15.0.2) by temporarily enabling the &quot;Edge&quot; releases in Advanced Options and then upgrading Dynamic Routes. (Please note, do not upgrade the other modules that show up when in Edge mode unless you want your whole installation to move to the &quot;Edge&quot; version.) After upgrading to version 15.0.2, you may set Edge mode back to No.<br /> <br /> The following links are here for historical reasons, but should no longer be used. The preferred upgrade method is via Freepbx Module Admin.<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=895 2022-05-08T14:02:11Z

<p>John: </p> <hr /> <div><br /> &lt;pre&gt;The Dynamic Route module is now available in Freepbx, through the Unsupported Modules repository and can be installed directly from within Freepbx. Please use the version distributed with Freepbx. The contents of this site have been left as a reference. The new documentation is available at https://wiki.freepbx.org/display/FPG/Dynamic+Routes+Module&lt;/pre&gt;<br /> <br /> ==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> For previous history of Dynamic Route source code please see: [https://github.com/johnfawcett/dynroute/ old repository]<br /> <br /> ===FreePBX 15 support===<br /> <br /> The latest stable release 15.0.1 is available directly in Freepbx module admin by enabling the &quot;Unsupported modules&quot; repository. A bug fix and enhancement release is available (15.0.2) by temporarily enabling the &quot;Edge&quot; releases in Advanced Options and then upgrading Dynamic Routes. (Please note, do not upgrade the other modules that show up when in Edge mode unless you want your whole installation to move to the &quot;Edge&quot; version.) After upgrading to version 15.0.2, you may set Edge mode back to No.<br /> <br /> The following links are here for historical reasons, but should no longer be used. The preferred upgrade method is via Freepbx Module Admin.<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_FAQ&diff=894 2021-01-05T11:37:25Z

<p>John: /* Q. What does the message &gt; mean? */</p> <hr /> <div>==General FAQ==<br /> <br /> ===Q. What are the prerequisites for Dynamic Routes?===<br /> <br /> A. The Dynamic Route module itself does not introduce additional prerequisites, so if your system is set up for Asterisk and FreePBX this module can be installed without adding any additional software. However, the lookup method you choose can introduce additional prerequisites.<br /> <br /> If you are using Dynamic Routes to connect to a MySQL database directly (without ODBC) then an additional Asterisk module is required (app_mysql). Please note that the app_mysql is not built by default. Please see this [[How to install Asterisk app_mysql|link]] for information. Although app_mysql is still widely used, it is no longer the recommended way to connect to the MySQL database from Asterisk.<br /> <br /> If you are using Dynamic Routes with ODBC you will need to install the ODBC software and driver for your database and configure it. Please see this [[How to set up an Asterisk ODBC data source on Linux|link]] for information.<br /> <br /> ===Q. Does Dynamic Routes effect performance?===<br /> <br /> A. For most installations that are not under heavy load, there will not be performance concerns. However in high traffic installations, the performance aspect should be considered. Of course if the mysql query is not correctly tuned, then even low traffic sites will have issues. So first of all, the query to be used should be checked on a database with similar volumes as the production environment to ensure that it completes quickly. Any tuning of the query or needed indexes should be added.<br /> <br /> Instead of running the query against an online database, you may also consider a batch procedure which periodically extracts the needed information, reorganized in the optimum way and then load into a table where asterisk will specifically query it.<br /> <br /> Performance will be enhanced by using a local database instead of a remote database. Performance is also enhanced by using a non-SSL connection to the database, but this is not advisable for a remote database due to security concerns - see below. Even for a local database there may be security concerns of using a non-SSL connection, depending on who may access the server.<br /> <br /> When connecting to a database Dynamic Routes can use MySQL directly (using Asterisk app_mysql) or ODBC. ODBC is now the recommended way of accessing a database from Asterisk. It is reported that the level of indirection does not introduce any noticeable performance issue.<br /> <br /> ===Q. Does Dynamic Routes effect system availability?===<br /> <br /> A. With Dynamic Routes a database or a web service can be used for lookups during incoming calls. Therefore the database or web server become a necessary component for call processing. If the server is unavailable, dynamic routing will not take place. You may however define a default destination. When a lookup fails it will follow the default destination. The default destination is also used when the lookup succeeds but no match is found. Using a local database or web server reduces availability dependencies but does not remove them entirely. <br /> <br /> ===Q. What are the security implications of using Dynamic Routes?===<br /> <br /> A. The asterisk mysql add-on does not support SSL encrypted connections, so information (including credentials) passed between asterisk and the database may be intercepted. That is one reason why a local database is recommended. If your installation must use a remote server, consider whether a better option, also from performance and availability perspectives, would be to periodically copy the data needed into the mysql database running on the asterisk server.<br /> <br /> If you must use a remote server, then it is recommended (unless you can setup a local LAN between the two servers without risk of interception) to use ODBC with SSL enabled. An alternative is to setup an encrypted tunnel using a VPN or a software like stunnel.<br /> <br /> In any case it is recommended that the database be separate to the ones used for FreePBX configurations and CDRs. It is also recommended that a specific user is setup in order to access the database and that it has only select permissions on the tables that are used in the query. You should avoid using tables in the query that contain sensitive data, such as passwords. Consider defining a view if you have this case, which only gives access to the relevant columns needed. On MySQL for performance reasons that impact the whole server avoid using grant statements that contain column level access.<br /> <br /> ===Q. What does the message &lt;&lt;Module &quot;Dynamic Routes&quot; is unsigned and should be re-downloaded&gt;&gt; mean?===<br /> <br /> A. FreePBX now has a system whereby a hash of the source code is computed and signed by Sangoma. See [http://wiki.freepbx.org/display/FPG/Module+Signing this link] for more information. This functionality is extremely useful because users know that the modules are the official versions and (unless the verification code itself is tampered with) they know that the code has not been modified.<br /> <br /> While very useful, there are a couple of implications:<br /> * Third party modules will show an unsigned module warning<br /> * 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<br /> <br /> From version 15.0.1 Dynamic Routes is included in the Contributed modules repository (&quot;Unsupported&quot; 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. <br /> <br /> 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.<br /> <br /> ==Configuration FAQ==<br /> <br /> ===Q. How can I avoid matching short caller ids?===<br /> <br /> A. You can use a condition in the WHERE clause to ensure that only caller ids of sufficient length are matched. This is useful if your database contains company phone numbers with similar prefixes, but when receiving calls the caller id is set to the shorter main phone number of the company.<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like '%[NUMBER]' and length('[NUMBER]') &gt; 4&lt;/pre&gt;<br /> <br /> ===Q. How can I match data in my database when sometimes the caller id arrives with an international prefix of + country codes, other times 00 country code and other times just as a national number?===<br /> <br /> A. You may use the MySQL TRIM function to adjust the presented caller id to match the type of data in your database. For example:<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like concat('%',TRIM(LEADING '+' FROM TRIM(LEADING '0' FROM '[NUMBER]')))&lt;/pre&gt;<br /> <br /> ===Q. Does Dynamic Route create the lookup table I will use in my query?===<br /> <br /> 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.<br /> <br /> ===Q. Why don't my inbound calls get routed through Dynamic Routes?===<br /> <br /> A. Dynamic Routes does not automatically intervene in the call processing of your system. If you want calls to pass through Dynamic Routes you will need to configure your system to hand the calls to a specific Dynamic Route. Typically you can do this from the FreePBX &quot;Connectivity&quot; menu by choosing &quot;Inbound Routes&quot;. Choose the inbound route you want to pass through Dynamic Route and in that route put the Dynamic Route as the destination. Call flow will then pass through the specified Dynamic Route.<br /> <br /> ==Trouble shooting FAQ==<br /> <br /> ===When reporting a problem what information should I provide?===<br /> <br /> Please see [[Dynamic Routes Support|here]]<br /> <br /> ===Q. Why do I get strange errors when using asterisk MYSQL module?===<br /> <br /> &lt;pre&gt;[2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Error in extension logic (missing '}')<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Can't find trailing parenthesis for function 'CALLERID(nu'?<br /> [2015-04-24 21:52:59] ERROR[14294][C-000020b6] func_callerid.c: Unknown callerid data type 'nu'.<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:4] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Query resultid 1 select callerid_firstname from calleridlookup where owner='john' and '&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_query: mysql_query failed. Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:5] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Fetch fetchid dynroute&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_fetch: missing some arguments<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:6] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Clear &quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Identifier 0, identifier_type 2 not found in identifier list<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Invalid result identifier 0 passed in aMYSQL_clear<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:7] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Disconnect 1&quot;) in new stack<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:8] Set(&quot;SIP/215-00000087&quot;, &quot;__DYNROUTE_TEST=&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected '=', expecting $end; Input:&gt;&lt;/pre&gt;<br /> <br /> A. Do not use a semicolon at the end of the query. This syntax is not supported by asterisk MYSQL module.</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=893 2021-01-05T11:33:41Z

<p>John: /* FreePBX 15 support */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> For previous history of Dynamic Route source code please see: [https://github.com/johnfawcett/dynroute/ old repository]<br /> <br /> ===FreePBX 15 support===<br /> <br /> The latest stable release 15.0.1 is available directly in Freepbx module admin by enabling the &quot;Unsupported modules&quot; repository. A bug fix and enhancement release is available (15.0.2) by temporarily enabling the &quot;Edge&quot; releases in Advanced Options and then upgrading Dynamic Routes. (Please note, do not upgrade the other modules that show up when in Edge mode unless you want your whole installation to move to the &quot;Edge&quot; version.) After upgrading to version 15.0.2, you may set Edge mode back to No.<br /> <br /> The following links are here for historical reasons, but should no longer be used. The preferred upgrade method is via Freepbx Module Admin.<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=892 2021-01-05T11:32:43Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> For previous history of Dynamic Route source code please see: [https://github.com/johnfawcett/dynroute/ old repository]<br /> <br /> ===FreePBX 15 support===<br /> <br /> The latest stable release 15.0.1 is available directly in Freepbx module admin by enabling the &quot;Unsupported modules&quot; repository. A bug fix and enhancement release is available (15.0.2) by temporarily enabling the &quot;Edge&quot; releases in Advanced Options and then upgrading Dynamic Routes. (Please note, do not upgrade the other modules that show up when in Edge mode unless you want your whole installation to move to the &quot;Edge&quot; version.) After upgrading to version 15.0.2, you may set Edge mode back to No.<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=891 2021-01-05T11:29:06Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> For previous history of Dynamic Route source code please see: [https://github.com/johnfawcett/dynroute/ old repository]<br /> <br /> ===FreePBX 15 support===<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=890 2021-01-05T11:28:27Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. For the last version please see: [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> Please see: [https://github.com/johnfawcett/dynroute/ for previous history of Dynamic Route source code]<br /> <br /> <br /> ===FreePBX 15 support===<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=889 2021-01-05T11:27:52Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project was previously hosted on github but has now been included in Freepbx contributed modules repository. for the last version. The code is now hosted in the Freepbx contributed modules repository [https://git.freepbx.org/projects/FPBXCN/repos/dynroute/browse Dynamic Route current version source code repository]<br /> <br /> Please see: [https://github.com/johnfawcett/dynroute/ for previous history of Dynamic Route source code]<br /> <br /> <br /> ===FreePBX 15 support===<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=File:Dynroute-15.0.0.tgz.sig&diff=888 2020-08-31T17:37:20Z

<p>John: </p> <hr /> <div></div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_gpg_signatures&diff=887 2020-08-31T17:35:58Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 2.11.3.2&lt;/strong&gt;<br /> <br /> [[File:dynroute-2.11.3.2.zip.sig]]<br /> <br /> &lt;strong&gt;Signature for 13.0.5&lt;/strong&gt;<br /> <br /> [[File:dynroute-13.0.5.zip.sig]]<br /> <br /> &lt;strong&gt;Signature for 14.0.0&lt;/strong&gt;<br /> <br /> [[File:dynroute-14.0.0.tgz.sig]]<br /> <br /> &lt;strong&gt;Signature for 14.0.1&lt;/strong&gt;<br /> <br /> [[File:dynroute-14.0.1.tgz.sig]]<br /> <br /> &lt;strong&gt;Signature for 15.0.0&lt;/strong&gt;<br /> <br /> [[File:dynroute-15.0.0.tgz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=886 2020-08-31T17:34:57Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project is hosted on github. Please see: [https://github.com/johnfawcett/dynroute/ Dynamic Route source code repository]<br /> <br /> [https://github.com/johnfawcett/dynroute/blob/master/CHANGES.txt Dynamic Routes Change Log]<br /> <br /> ===FreePBX 15 support===<br /> <br /> [https://updates.voipsupport.it/dynroute-15.0.0.tgz Dynamic Routes 15.0.0]<br /> <br /> Updated for the Freepbx 15 release. Any new features will be added to this version.<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Voipsupport:Privacy_policy&diff=883 2019-12-07T10:42:50Z

<p>John: /* Data processing location */</p> <hr /> <div>===Information that is recorded===<br /> <br /> When you visit this site certain information about your visit is logged: the date and time, your ip address, the pages served, the referring page, browser name and operating system and result or error code. No personally identifying information is logged.<br /> <br /> For more information please see [https://httpd.apache.org/docs/2.4/logs.html#accesslog combined log format].<br /> <br /> ===Use of the information===<br /> <br /> The purpose of the logging is two fold:<br /> * to provide the service, for example by enabling checking of logs in case of errors or problems <br /> * to evaluate the use of the site by compiling statistics about number of visitors and the pages visited.<br /> <br /> No information is ever sold or provided externally.<br /> <br /> ===Duration of the storage===<br /> <br /> Any information recorded is automatically cancelled on a rotating basis after 4 weeks.<br /> <br /> ===Cookies===<br /> <br /> Cookies are used to a limited extent:<br /> * for the sole purpose of providing the the web site service and<br /> * are strictly necessary in order to provide the service.<br /> <br /> Cookies are not used to track user behaviour.<br /> <br /> The cookies used are:<br /> * __cfduid: this is stictly necessary for the CloudFlare service, see [https://support.cloudflare.com/hc/en-us/articles/200170156-What-does-the-CloudFlare-cfduid-cookie-do- this page]. The cookie has a duration of 1 year, but you may cancel it at any time.<br /> * voipsupport_session: used for the correct functioning of the Mediawiki software. The cookie has a duration limited to the length of the browsing session.<br /> <br /> ===Data processing location===<br /> <br /> The web server is located within the EU. No information is stored outside the EU. The site uses the [https://www.cloudflare.com/ CloudFlare] service in order to improve performance and security. That means that some or all the data will transit through an external server, usually nearer to your location.<br /> <br /> For more information about the CloudFlare policy, please see [https://blog.cloudflare.com/what-cloudflare-logs/ this link]</div>

John https://voipsupport.it/wiki/index.php?title=Voipsupport:Privacy_policy&diff=882 2019-12-07T10:42:09Z

<p>John: /* Information that is recorded */</p> <hr /> <div>===Information that is recorded===<br /> <br /> When you visit this site certain information about your visit is logged: the date and time, your ip address, the pages served, the referring page, browser name and operating system and result or error code. No personally identifying information is logged.<br /> <br /> For more information please see [https://httpd.apache.org/docs/2.4/logs.html#accesslog combined log format].<br /> <br /> ===Use of the information===<br /> <br /> The purpose of the logging is two fold:<br /> * to provide the service, for example by enabling checking of logs in case of errors or problems <br /> * to evaluate the use of the site by compiling statistics about number of visitors and the pages visited.<br /> <br /> No information is ever sold or provided externally.<br /> <br /> ===Duration of the storage===<br /> <br /> Any information recorded is automatically cancelled on a rotating basis after 4 weeks.<br /> <br /> ===Cookies===<br /> <br /> Cookies are used to a limited extent:<br /> * for the sole purpose of providing the the web site service and<br /> * are strictly necessary in order to provide the service.<br /> <br /> Cookies are not used to track user behaviour.<br /> <br /> The cookies used are:<br /> * __cfduid: this is stictly necessary for the CloudFlare service, see [https://support.cloudflare.com/hc/en-us/articles/200170156-What-does-the-CloudFlare-cfduid-cookie-do- this page]. The cookie has a duration of 1 year, but you may cancel it at any time.<br /> * voipsupport_session: used for the correct functioning of the Mediawiki software. The cookie has a duration limited to the length of the browsing session.<br /> <br /> ===Data processing location===<br /> <br /> The web server is located within the EU. No information is stored outside the EU. The site uses the [https://www.cloudflare.com/ CloudFlare] service in order to improve performance and security. That means that some data will transit through an external server, usually nearer to your location.<br /> <br /> For more information about the CloudFlare policy, please see [https://blog.cloudflare.com/what-cloudflare-logs/ this link]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_FAQ&diff=881 2019-12-07T10:29:22Z

<p>John: /* Q. What does the message &gt; mean? */</p> <hr /> <div>==General FAQ==<br /> <br /> ===Q. What are the prerequisites for Dynamic Routes?===<br /> <br /> A. The Dynamic Route module itself does not introduce additional prerequisites, so if your system is set up for Asterisk and FreePBX this module can be installed without adding any additional software. However, the lookup method you choose can introduce additional prerequisites.<br /> <br /> If you are using Dynamic Routes to connect to a MySQL database directly (without ODBC) then an additional Asterisk module is required (app_mysql). Please note that the app_mysql is not built by default. Please see this [[How to install Asterisk app_mysql|link]] for information. Although app_mysql is still widely used, it is no longer the recommended way to connect to the MySQL database from Asterisk.<br /> <br /> If you are using Dynamic Routes with ODBC you will need to install the ODBC software and driver for your database and configure it. Please see this [[How to set up an Asterisk ODBC data source on Linux|link]] for information.<br /> <br /> ===Q. Does Dynamic Routes effect performance?===<br /> <br /> A. For most installations that are not under heavy load, there will not be performance concerns. However in high traffic installations, the performance aspect should be considered. Of course if the mysql query is not correctly tuned, then even low traffic sites will have issues. So first of all, the query to be used should be checked on a database with similar volumes as the production environment to ensure that it completes quickly. Any tuning of the query or needed indexes should be added.<br /> <br /> Instead of running the query against an online database, you may also consider a batch procedure which periodically extracts the needed information, reorganized in the optimum way and then load into a table where asterisk will specifically query it.<br /> <br /> Performance will be enhanced by using a local database instead of a remote database. Performance is also enhanced by using a non-SSL connection to the database, but this is not advisable for a remote database due to security concerns - see below. Even for a local database there may be security concerns of using a non-SSL connection, depending on who may access the server.<br /> <br /> When connecting to a database Dynamic Routes can use MySQL directly (using Asterisk app_mysql) or ODBC. ODBC is now the recommended way of accessing a database from Asterisk. It is reported that the level of indirection does not introduce any noticeable performance issue.<br /> <br /> ===Q. Does Dynamic Routes effect system availability?===<br /> <br /> A. With Dynamic Routes a database or a web service can be used for lookups during incoming calls. Therefore the database or web server become a necessary component for call processing. If the server is unavailable, dynamic routing will not take place. You may however define a default destination. When a lookup fails it will follow the default destination. The default destination is also used when the lookup succeeds but no match is found. Using a local database or web server reduces availability dependencies but does not remove them entirely. <br /> <br /> ===Q. What are the security implications of using Dynamic Routes?===<br /> <br /> A. The asterisk mysql add-on does not support SSL encrypted connections, so information (including credentials) passed between asterisk and the database may be intercepted. That is one reason why a local database is recommended. If your installation must use a remote server, consider whether a better option, also from performance and availability perspectives, would be to periodically copy the data needed into the mysql database running on the asterisk server.<br /> <br /> If you must use a remote server, then it is recommended (unless you can setup a local LAN between the two servers without risk of interception) to use ODBC with SSL enabled. An alternative is to setup an encrypted tunnel using a VPN or a software like stunnel.<br /> <br /> In any case it is recommended that the database be separate to the ones used for FreePBX configurations and CDRs. It is also recommended that a specific user is setup in order to access the database and that it has only select permissions on the tables that are used in the query. You should avoid using tables in the query that contain sensitive data, such as passwords. Consider defining a view if you have this case, which only gives access to the relevant columns needed. On MySQL for performance reasons that impact the whole server avoid using grant statements that contain column level access.<br /> <br /> ===Q. What does the message &lt;&lt;Module &quot;Dynamic Routes&quot; is unsigned and should be re-downloaded&gt;&gt; mean?===<br /> <br /> A. FreePBX now has a system whereby a hash of the source code is computed and signed by Sangoma. See [http://wiki.freepbx.org/display/FPG/Module+Signing this link] for more information. This functionality is extremely useful because users know that the modules are the official versions and (unless the verification code itself is tampered with) they know that the code has not been modified.<br /> <br /> While very useful, there are a couple of implications:<br /> * Third party modules will show an unsigned module warning<br /> * 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<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==Configuration FAQ==<br /> <br /> ===Q. How can I avoid matching short caller ids?===<br /> <br /> A. You can use a condition in the WHERE clause to ensure that only caller ids of sufficient length are matched. This is useful if your database contains company phone numbers with similar prefixes, but when receiving calls the caller id is set to the shorter main phone number of the company.<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like '%[NUMBER]' and length('[NUMBER]') &gt; 4&lt;/pre&gt;<br /> <br /> ===Q. How can I match data in my database when sometimes the caller id arrives with an international prefix of + country codes, other times 00 country code and other times just as a national number?===<br /> <br /> A. You may use the MySQL TRIM function to adjust the presented caller id to match the type of data in your database. For example:<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like concat('%',TRIM(LEADING '+' FROM TRIM(LEADING '0' FROM '[NUMBER]')))&lt;/pre&gt;<br /> <br /> ===Q. Does Dynamic Route create the lookup table I will use in my query?===<br /> <br /> 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.<br /> <br /> ===Q. Why don't my inbound calls get routed through Dynamic Routes?===<br /> <br /> A. Dynamic Routes does not automatically intervene in the call processing of your system. If you want calls to pass through Dynamic Routes you will need to configure your system to hand the calls to a specific Dynamic Route. Typically you can do this from the FreePBX &quot;Connectivity&quot; menu by choosing &quot;Inbound Routes&quot;. Choose the inbound route you want to pass through Dynamic Route and in that route put the Dynamic Route as the destination. Call flow will then pass through the specified Dynamic Route.<br /> <br /> ==Trouble shooting FAQ==<br /> <br /> ===When reporting a problem what information should I provide?===<br /> <br /> Please see [[Dynamic Routes Support|here]]<br /> <br /> ===Q. Why do I get strange errors when using asterisk MYSQL module?===<br /> <br /> &lt;pre&gt;[2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Error in extension logic (missing '}')<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Can't find trailing parenthesis for function 'CALLERID(nu'?<br /> [2015-04-24 21:52:59] ERROR[14294][C-000020b6] func_callerid.c: Unknown callerid data type 'nu'.<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:4] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Query resultid 1 select callerid_firstname from calleridlookup where owner='john' and '&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_query: mysql_query failed. Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:5] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Fetch fetchid dynroute&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_fetch: missing some arguments<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:6] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Clear &quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Identifier 0, identifier_type 2 not found in identifier list<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Invalid result identifier 0 passed in aMYSQL_clear<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:7] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Disconnect 1&quot;) in new stack<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:8] Set(&quot;SIP/215-00000087&quot;, &quot;__DYNROUTE_TEST=&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected '=', expecting $end; Input:&gt;&lt;/pre&gt;<br /> <br /> A. Do not use a semicolon at the end of the query. This syntax is not supported by asterisk MYSQL module.</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_FAQ&diff=880 2019-12-07T10:28:25Z

<p>John: /* Q. What does the message &gt; mean? */</p> <hr /> <div>==General FAQ==<br /> <br /> ===Q. What are the prerequisites for Dynamic Routes?===<br /> <br /> A. The Dynamic Route module itself does not introduce additional prerequisites, so if your system is set up for Asterisk and FreePBX this module can be installed without adding any additional software. However, the lookup method you choose can introduce additional prerequisites.<br /> <br /> If you are using Dynamic Routes to connect to a MySQL database directly (without ODBC) then an additional Asterisk module is required (app_mysql). Please note that the app_mysql is not built by default. Please see this [[How to install Asterisk app_mysql|link]] for information. Although app_mysql is still widely used, it is no longer the recommended way to connect to the MySQL database from Asterisk.<br /> <br /> If you are using Dynamic Routes with ODBC you will need to install the ODBC software and driver for your database and configure it. Please see this [[How to set up an Asterisk ODBC data source on Linux|link]] for information.<br /> <br /> ===Q. Does Dynamic Routes effect performance?===<br /> <br /> A. For most installations that are not under heavy load, there will not be performance concerns. However in high traffic installations, the performance aspect should be considered. Of course if the mysql query is not correctly tuned, then even low traffic sites will have issues. So first of all, the query to be used should be checked on a database with similar volumes as the production environment to ensure that it completes quickly. Any tuning of the query or needed indexes should be added.<br /> <br /> Instead of running the query against an online database, you may also consider a batch procedure which periodically extracts the needed information, reorganized in the optimum way and then load into a table where asterisk will specifically query it.<br /> <br /> Performance will be enhanced by using a local database instead of a remote database. Performance is also enhanced by using a non-SSL connection to the database, but this is not advisable for a remote database due to security concerns - see below. Even for a local database there may be security concerns of using a non-SSL connection, depending on who may access the server.<br /> <br /> When connecting to a database Dynamic Routes can use MySQL directly (using Asterisk app_mysql) or ODBC. ODBC is now the recommended way of accessing a database from Asterisk. It is reported that the level of indirection does not introduce any noticeable performance issue.<br /> <br /> ===Q. Does Dynamic Routes effect system availability?===<br /> <br /> A. With Dynamic Routes a database or a web service can be used for lookups during incoming calls. Therefore the database or web server become a necessary component for call processing. If the server is unavailable, dynamic routing will not take place. You may however define a default destination. When a lookup fails it will follow the default destination. The default destination is also used when the lookup succeeds but no match is found. Using a local database or web server reduces availability dependencies but does not remove them entirely. <br /> <br /> ===Q. What are the security implications of using Dynamic Routes?===<br /> <br /> A. The asterisk mysql add-on does not support SSL encrypted connections, so information (including credentials) passed between asterisk and the database may be intercepted. That is one reason why a local database is recommended. If your installation must use a remote server, consider whether a better option, also from performance and availability perspectives, would be to periodically copy the data needed into the mysql database running on the asterisk server.<br /> <br /> If you must use a remote server, then it is recommended (unless you can setup a local LAN between the two servers without risk of interception) to use ODBC with SSL enabled. An alternative is to setup an encrypted tunnel using a VPN or a software like stunnel.<br /> <br /> In any case it is recommended that the database be separate to the ones used for FreePBX configurations and CDRs. It is also recommended that a specific user is setup in order to access the database and that it has only select permissions on the tables that are used in the query. You should avoid using tables in the query that contain sensitive data, such as passwords. Consider defining a view if you have this case, which only gives access to the relevant columns needed. On MySQL for performance reasons that impact the whole server avoid using grant statements that contain column level access.<br /> <br /> ===Q. What does the message &lt;&lt;Module &quot;Dynamic Routes&quot; is unsigned and should be re-downloaded&gt;&gt; mean?===<br /> <br /> A. FreePBX now has a system whereby a hash of the source code is computed and signed by Sangoma. See [http://wiki.freepbx.org/display/FPG/Module+Signing this link] for more information. This functionality is extremely useful because users know that the modules are the official versions and (unless the verification code itself is tampered with) they know that the code has not been modified.<br /> <br /> While very useful, there are a couple of implications:<br /> * Third party modules will show an unsigned module warning<br /> * 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<br /> <br /> 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.<br /> <br /> 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.<br /> [https://wiki.freepbx.org/display/FOP/Signing+your+own+modules]<br /> <br /> ==Configuration FAQ==<br /> <br /> ===Q. How can I avoid matching short caller ids?===<br /> <br /> A. You can use a condition in the WHERE clause to ensure that only caller ids of sufficient length are matched. This is useful if your database contains company phone numbers with similar prefixes, but when receiving calls the caller id is set to the shorter main phone number of the company.<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like '%[NUMBER]' and length('[NUMBER]') &gt; 4&lt;/pre&gt;<br /> <br /> ===Q. How can I match data in my database when sometimes the caller id arrives with an international prefix of + country codes, other times 00 country code and other times just as a national number?===<br /> <br /> A. You may use the MySQL TRIM function to adjust the presented caller id to match the type of data in your database. For example:<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like concat('%',TRIM(LEADING '+' FROM TRIM(LEADING '0' FROM '[NUMBER]')))&lt;/pre&gt;<br /> <br /> ===Q. Does Dynamic Route create the lookup table I will use in my query?===<br /> <br /> 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.<br /> <br /> ===Q. Why don't my inbound calls get routed through Dynamic Routes?===<br /> <br /> A. Dynamic Routes does not automatically intervene in the call processing of your system. If you want calls to pass through Dynamic Routes you will need to configure your system to hand the calls to a specific Dynamic Route. Typically you can do this from the FreePBX &quot;Connectivity&quot; menu by choosing &quot;Inbound Routes&quot;. Choose the inbound route you want to pass through Dynamic Route and in that route put the Dynamic Route as the destination. Call flow will then pass through the specified Dynamic Route.<br /> <br /> ==Trouble shooting FAQ==<br /> <br /> ===When reporting a problem what information should I provide?===<br /> <br /> Please see [[Dynamic Routes Support|here]]<br /> <br /> ===Q. Why do I get strange errors when using asterisk MYSQL module?===<br /> <br /> &lt;pre&gt;[2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Error in extension logic (missing '}')<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Can't find trailing parenthesis for function 'CALLERID(nu'?<br /> [2015-04-24 21:52:59] ERROR[14294][C-000020b6] func_callerid.c: Unknown callerid data type 'nu'.<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:4] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Query resultid 1 select callerid_firstname from calleridlookup where owner='john' and '&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_query: mysql_query failed. Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:5] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Fetch fetchid dynroute&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_fetch: missing some arguments<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:6] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Clear &quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Identifier 0, identifier_type 2 not found in identifier list<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Invalid result identifier 0 passed in aMYSQL_clear<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:7] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Disconnect 1&quot;) in new stack<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:8] Set(&quot;SIP/215-00000087&quot;, &quot;__DYNROUTE_TEST=&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected '=', expecting $end; Input:&gt;&lt;/pre&gt;<br /> <br /> A. Do not use a semicolon at the end of the query. This syntax is not supported by asterisk MYSQL module.</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=879 2019-05-11T15:25:37Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]<br /> * [[Linux/Solr reindex dovecot]]<br /> * [[Linux/Solr command line search]]<br /> * [[Linux/VLAN on bridged network]]<br /> * [[Linux/VLAN]] on main network<br /> * [[Linux/Multihomed network routing]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/VLAN&diff=878 2019-05-07T23:13:29Z

<p>John: Created page with &quot;nmcli con add type vlan con-name VLAN15 ifname VLAN15 id 15 dev enp0s25 ip4 192.168.15.30/24 gw4 192.168.15.1&quot;</p> <hr /> <div>nmcli con add type vlan con-name VLAN15 ifname VLAN15 id 15 dev enp0s25 ip4 192.168.15.30/24 gw4 192.168.15.1</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=877 2019-05-07T23:13:12Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]<br /> * [[Linux/Solr reindex dovecot]]<br /> * [[Linux/Solr command line search]]<br /> * [[Linux/VLAN on bridged network]]<br /> * [[Linux/VLAN]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/VLAN_on_bridged_network&diff=876 2019-05-07T23:11:59Z

<p>John: Created page with &quot;nmcli con add type vlan con-name enp0s25.11 dev enp0s25 id 11 master virbr1 connection.autoconnect yes&quot;</p> <hr /> <div>nmcli con add type vlan con-name enp0s25.11 dev enp0s25 id 11 master virbr1 connection.autoconnect yes</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=875 2019-05-07T23:11:12Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]<br /> * [[Linux/Solr reindex dovecot]]<br /> * [[Linux/Solr command line search]]<br /> * [[Linux/VLAN on bridged network]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/Solr_command_line_search&diff=874 2019-04-14T19:20:47Z

<p>John: Created page with &quot;Testing from doveadm doveadm search -u user@example.com mailbox inbox body text_to_search_for&quot;</p> <hr /> <div>Testing from doveadm<br /> <br /> doveadm search -u user@example.com mailbox inbox body text_to_search_for</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=873 2019-04-14T19:20:00Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]<br /> * [[Linux/Solr reindex dovecot]]<br /> * [[Linux/Solr command line search]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/Solr_reindex_dovecot&diff=872 2019-04-14T16:54:08Z

<p>John: Created page with &quot;Rescan index for all users doveadm fts rescan -A Rescan index for specific user: doveadm fts rescan -u user@example.com Reindex dovecot all users doveadm index -A &quot;*&quot;...&quot;</p> <hr /> <div>Rescan index for all users<br /> <br /> doveadm fts rescan -A<br /> <br /> Rescan index for specific user:<br /> <br /> doveadm fts rescan -u user@example.com<br /> <br /> <br /> <br /> Reindex dovecot all users<br /> <br /> doveadm index -A &quot;*&quot;<br /> <br /> Reindex specific user<br /> <br /> doveadm index -u user@example.com</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=871 2019-04-14T16:52:09Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]<br /> * [[Linux/Solr reindex dovecot]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/Solr_delete_dovecot_index&diff=870 2019-04-14T16:51:38Z

<p>John: </p> <hr /> <div>Delete a dovecot index<br /> <br /> curl https://user:passwordQ@solr.example.com:443/solr/dovecot/update --data '&lt;delete&gt;&lt;query&gt;*:*&lt;/query&gt;&lt;/delete&gt;' -H 'Content-type:text/xml; charset=utf-8'<br /> <br /> Soft Commit<br /> <br /> curl https://user:password@solr.example.com:443/solr/dovecot/update?softCommit=true</div>

John https://voipsupport.it/wiki/index.php?title=Linux/Solr_delete_dovecot_index&diff=869 2019-04-14T16:48:50Z

<p>John: Created page with &quot;Delete a dovecot index curl https://user:passwordQ@solr.site24.it:443/solr/dovecot/update --data &#039;&lt;delete&gt;&lt;query&gt;*:*&lt;/query&gt;&lt;/delete&gt;&#039; -H &#039;Content-type:text/xml; charset=utf-8&#039;&quot;</p> <hr /> <div>Delete a dovecot index<br /> <br /> curl https://user:passwordQ@solr.site24.it:443/solr/dovecot/update --data '&lt;delete&gt;&lt;query&gt;*:*&lt;/query&gt;&lt;/delete&gt;' -H 'Content-type:text/xml; charset=utf-8'</div>

John https://voipsupport.it/wiki/index.php?title=Knowledge_base&diff=868 2019-04-14T16:48:20Z

<p>John: </p> <hr /> <div>* [[Linux/scp missing on centos install]]<br /> * [[Linux/Network does not activate on cloned centos server]]<br /> * [[Linux/LVM how to increase file system size by adding physical volume]]<br /> * [[Linux/LVM how to decrease file system size]]<br /> * [[Linux/LVM adding a NAS partition for backups]]<br /> * [[Linux/Enable EPEL for Centos]]<br /> * [[Linux/Enable rpmforge repository for Centos]]<br /> * [[Linux/Allow yajhfc to connect to hylafax port in passive mode - Centos - Iptables]]<br /> * [[Linux/Code Signing]]<br /> * [[Linux/Setup MySQL to use SSL]]<br /> * [[Linux/Solr delete dovecot index]]</div>

John https://voipsupport.it/wiki/index.php?title=MediaWiki:Sidebar&diff=867 2019-03-16T10:11:18Z

<p>John: </p> <hr /> <div><br /> * navigation<br /> ** mainpage|mainpage-description<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> ** helppage|help<br /> * SEARCH<br /> * TOOLBOX<br /> * LANGUAGES</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_gpg_signatures&diff=866 2019-03-16T10:04:39Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 3.2.1&lt;/strong&gt;<br /> <br /> [[:File:Checkauthlog-3.2.1.tar.gz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[:File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_gpg_signatures&diff=865 2019-03-16T10:03:36Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 3.2.1&lt;/strong&gt;<br /> <br /> [[:File:check auth log-3.2.1.tar.gz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[:File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=File:Checkauthlog-3.2.1.tar.gz.sig&diff=864 2019-03-16T10:03:05Z

<p>John: </p> <hr /> <div></div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_gpg_signatures&diff=863 2019-03-16T10:02:49Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 3.2.1&lt;/strong&gt;<br /> <br /> [[:File:check_auth_log-3.2.1.tar.gz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[:File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_gpg_signatures&diff=862 2019-03-16T10:01:00Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 3.2.1&lt;/strong&gt;<br /> <br /> [[:File:check_auth_log-3.2.1.tgz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[:File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_gpg_signatures&diff=861 2019-03-16T09:49:29Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 3.2.1&lt;/strong&gt;<br /> <br /> [[:File:check auth log-3.2.1.tgz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[:File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog&diff=860 2019-03-16T09:48:47Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> CheckAuthLog is a security feature for email servers. It can check the log files for suspicious email sending behaviour which may be indicative of a compromised email account and block that account.<br /> <br /> ==What could I use it for?==<br /> <br /> If you are running a [http://www.postfix.org Postfix] or [http://www.exim.org Exim] email server, you can use this script to enhance security of your server. Stolen email credentials are now often used to send spam. A spam outflow from your email server could cause reputation problems particularly with large email providers and RBL users. While there are many other things you can do as a first line of defence, if you have a large or variegated group of users, you may not be able to avoid the risk of email credentials being stolen.<br /> <br /> CheckAuthLog is not designed to completely stop spam sending or avoid all fraudulent use of an email account. However it can help stop things before they go too far out of control.<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project is hosted on github. Please see [https://github.com/johnfawcett/checkauthlog CheckAuthLog source code repository]<br /> <br /> [https://github.com/johnfawcett/checkauthlog/archive/V3.2.1.tar.gz CheckAuthLog 3.2.1]<br /> <br /> [[CheckAuthLog Change Log]]<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[CheckAuthLog previous versions]]<br /> <br /> GPG signatures for the latest version is available here [[CheckAuthLog gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[CheckAuthLog Installation instructions| Installation Instructions]]<br /> * [[CheckAuthLog Licence|Licence]]<br /> * [[CheckAuthLog Reference documentation|Reference documentation]]<br /> * [[CheckAuthLog Future plans|Future plans]]<br /> * [[CheckAuthLog FAQ|FAQ]]<br /> * [[CheckAuthLog Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_Change_Log&diff=859 2019-03-16T09:47:52Z

<p>John: </p> <hr /> <div><br /> <br /> 2010-Oct-27 check_auth_log-1.0.1.tgz<br /> <br /> 2010-Sep-19 check_auth_log-1.0.0.tgz<br /> <br /> Version 2.0.0 includes performance improvements for the log file parsing and a mechanism to avoid more than one instance running at a time. Also support is included for Exim. As I do not run Exim that code has only been lightly tested. Feedback is welcome.<br /> Version 3.0.0 released 11 April 2015 contains the following main changes:<br /> * Support for syslog (enabled by default)<br /> * Support for log level (for syslog and for standard output)<br /> * New configuration variable ignored_users to avoid listed users being subject to checks. Comma separated list of logins<br /> * New configuration variable ignored_ips to avoid logging listed ips or ranges. Comma separated list of ips or cidr ranges.<br /> * Ability to notify users their account has been blocked (only useful if the block does not prevent them receiving and reading email)<br /> * Self checking: the script notifies you if it fails to find new log lines after a certain interval (default 1 hour) or new logins after a certain interval (default 1 day - but should be customized to what you expect)<br /> * Self checking is enabled by default but can be turned off if not needed.<br /> * Support for sending self check notifications to the admin via email (not really needed if you run from crontab since you receive the standard output anyway) but for some might be useful<br /> * A new variable that can be used in mysql queries %l (lower case L) which matches the local part of the user name before the @<br /> New command line options:<br /> * -z will run the self check routines only<br /> * -e xxxx@domain.com will simulate the email notification to user specified in the parameter. This can be useful for testing the email setup, without having to trigger a hit on the user or ip limits.<br /> <br /> A bug was found and corrected during testing of version 3 (present in previous versions). If the log file contains multiple login lines that cause the ip or message limits to be exceeded, then each single login line processed would trigger the blocking action. This can logically occur only in the same or next log file, since following the successful blocking action, no new login lines will be generated until the account is unblocked. This did not create any particular negative consequences (reblocking a blocked user), but with the email notification feature, it would have created multiple notifications. Now the script will suppress blocking action if the user was already blocked in the current or previous run.<br /> <br /> Some of the development in version 3 was funded by a donation.<br /> <br /> Versione 3.2.1 released on 16 March 2019 contains code cleanup, bug fix for an issue where the timezone of php is different to the timezone of the server logging, and improved logging which will help in the case of further issues.</div>

John https://voipsupport.it/wiki/index.php?title=CheckAuthLog_previous_versions&diff=858 2019-03-16T09:44:33Z

<p>John: /* Signed with current GPG key */</p> <hr /> <div>==Signed with current GPG key==<br /> <br /> Version 3.0.0: [[File:check_auth_log-3.0.0.tgz]] GPG Signature: [[File:check_auth_log-3.0.0.tgz.sig]]<br /> <br /> Version 2.0.0: [[File:check_auth_log-2.0.0.tgz]] GPG Signature: [[File:check_auth_log-2.0.0.tgz.sig]]<br /> <br /> Version 1.0.1: [[File:check_auth_log-1.0.1.tgz]] GPG Signature: [[File:check_auth_log-1.0.1.tgz.sig]]<br /> <br /> GPG public key for above releases [[File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_Reference_documentation&diff=857 2018-06-08T04:16:41Z

<p>John: /* Substitutions */</p> <hr /> <div>==Dynamic Route==<br /> <br /> The following information documents how to fill in the fields of a Dynamic Route. This documentation refers to the V13 functionality. Not all options are available in previous versions.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Field name<br /> ! Comment<br /> |-<br /> | Dynamic Route Name<br /> | The name of the dynamic route. This can be chosen at will. It is used to identify the route when selecting it as a destination from other applications or inbound routes. <br /> |-<br /> | Dynamic Route Description<br /> | Optional description text for the Dynamic Route. This is for documentation purposes only<br /> |-<br /> | Enable DTMF Input<br /> | Setting: Yes or No. Default: No. If set to yes the call waits for input on the touch tone keypad. This can be used to capture caller input (for example a customer number).<br /> |-<br /> | Announcement<br /> | The system recording to be played back. If Enable DTMF input is set to Yes then playback takes palce before waiting for DTMF input.<br /> |-<br /> | Timeout<br /> | Timeout in seconds to wait for DTMF input. This value is only used if Enable DTMF Input is set to Yes. If no value is given for timeout, the default for the channel is used. It is best to set an explicit value to avoid doubts. <br /> |-<br /> | Validation<br /> | Validation rules using a Asterisk regular expression (see Asterisk [https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Function_REGEX REGEX]). For example to ensure the input is between 3 and 4 digits long you could use ^[0-9]\{3,4\}$<br /> |-<br /> | Invalid Retries<br /> | Number of times to retry if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Retry Recording <br /> | Recording to play if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Recording<br /> | Recording to play if DTMF input does not match validation rules and Invalid Retries have been exhausted.<br /> |-<br /> | Invalid Destination<br /> | The destination to send the call to if DTMF input does not match the validation rules and Invalid Retries ahve been exhausted. The call is sent to this destination after playing the Invalid Recording if it is defined.<br /> |-<br /> | Saved input varibale name<br /> | 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<br /> |-<br /> | Saved result variable name<br /> | 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<br /> |-<br /> | Source Type<br /> | The type of lookup (see under Source types below for further information<br /> |-<br /> | Default Destination<br /> | 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.<br /> |-<br /> | Dynamic Route Entries<br /> | Zero or more entries to be matched by the lookup result. If the lookup matches, then the call is routed to the chosen destination. Each match is tried in the order given until one matches. If no match is found then the call is sent to the Default Destination. Additional rows may be added by clicking the + symbol. Entries may be deleted by cancelling the value in the Match field.<br /> |}<br /> <br /> ==Source Type==<br /> <br /> The following are the currently available source types for lookups. Each source type has its own specific fields for defining the lookup parameters.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Source Type<br /> ! Comment<br /> |-<br /> | none<br /> | No lookup is carried out. The call is sent to the default destination<br /> |-<br /> | MySQL<br /> | A lookup is done to a MySQL database. The parameters used are:<br /> * MySQL hostname: hostname of server<br /> * MySQL database: database name<br /> * MySQL username: username<br /> * MySQL password: password<br /> * MySQL query: the SQL to be used. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> |-<br /> | ODBC<br /> | A lookup is done to an Asterisk ODBC data source. The parameters used are:<br /> * ODBC function: the Asterisk ODBC function name that has been configured<br /> * ODBC query: the query. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux |article]]<br /> |- <br /> | URL<br /> | A lookup is done to a URL. The parameters used are:<br /> * URL Looup: the URL to be used for the lookup. The results must be text only. HTML, XML and JSON is not supported. The URL may contains parameters and the parameter values may include the substitutions indicated in the following table. Example: &lt;nowiki&gt;http://localhost/test.php?param1=4&amp;param2=[NUMBER]&lt;/nowiki&gt;<br /> |-<br /> | AGI<br /> | A lookup is done by launching an Asterisk AGI script. The parameters used are:<br /> * AGI Lookup: the name of the Asterisk AGI script to be launched.<br /> * AGI Result Variable: the name of the variable that the script uses to communicate the result. The script should execute a SET VARIABLE command using this variable name at the end of execution in order to pass back the lookup result. An example script is given in the installation directory (test.agi).<br /> |-<br /> | Asterisk Variable<br /> | The lookup value is read from an Asterisk Variable. The parameters used are:<br /> * 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(&quot;^1.3$&quot; ${DYNROUTE_dtmf})} would check that the DTMF input was in the range 1000-1999 (providing that the Saved input variable name was set to &quot;dtmf&quot;)<br /> |}<br /> <br /> ==Substitutions==<br /> <br /> &lt;strong&gt;In the lookup&lt;/strong&gt;<br /> <br /> When defining the query field for the lookup, the following Variable Names will be substituted by the corresponding value at the time of the call routing.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | [INPUT]<br /> | The DTMF input by the caller on the touchtone keypad<br /> |-<br /> | [NUMBER]<br /> | The callerid of the incoming call<br /> |-<br /> | [DID]<br /> | The called number<br /> |-<br /> | [name]<br /> | Where &quot;name&quot; 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.&lt;br&gt;&lt;br&gt;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 &quot;Asterisk variable&quot;. <br /> |}<br /> <br /> &lt;strong&gt;In custom dial plan or other FreePBX modules&lt;/strong&gt;<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | DYNROUTE_name<br /> | Where &quot;name&quot; 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.<br /> |}<br /> <br /> ==Screenshot of adding a Dynamic Route==<br /> <br /> [[File:dynamic_route_add.png]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_Reference_documentation&diff=856 2018-06-08T04:16:16Z

<p>John: /* Substitutions */</p> <hr /> <div>==Dynamic Route==<br /> <br /> The following information documents how to fill in the fields of a Dynamic Route. This documentation refers to the V13 functionality. Not all options are available in previous versions.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Field name<br /> ! Comment<br /> |-<br /> | Dynamic Route Name<br /> | The name of the dynamic route. This can be chosen at will. It is used to identify the route when selecting it as a destination from other applications or inbound routes. <br /> |-<br /> | Dynamic Route Description<br /> | Optional description text for the Dynamic Route. This is for documentation purposes only<br /> |-<br /> | Enable DTMF Input<br /> | Setting: Yes or No. Default: No. If set to yes the call waits for input on the touch tone keypad. This can be used to capture caller input (for example a customer number).<br /> |-<br /> | Announcement<br /> | The system recording to be played back. If Enable DTMF input is set to Yes then playback takes palce before waiting for DTMF input.<br /> |-<br /> | Timeout<br /> | Timeout in seconds to wait for DTMF input. This value is only used if Enable DTMF Input is set to Yes. If no value is given for timeout, the default for the channel is used. It is best to set an explicit value to avoid doubts. <br /> |-<br /> | Validation<br /> | Validation rules using a Asterisk regular expression (see Asterisk [https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Function_REGEX REGEX]). For example to ensure the input is between 3 and 4 digits long you could use ^[0-9]\{3,4\}$<br /> |-<br /> | Invalid Retries<br /> | Number of times to retry if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Retry Recording <br /> | Recording to play if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Recording<br /> | Recording to play if DTMF input does not match validation rules and Invalid Retries have been exhausted.<br /> |-<br /> | Invalid Destination<br /> | The destination to send the call to if DTMF input does not match the validation rules and Invalid Retries ahve been exhausted. The call is sent to this destination after playing the Invalid Recording if it is defined.<br /> |-<br /> | Saved input varibale name<br /> | 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<br /> |-<br /> | Saved result variable name<br /> | 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<br /> |-<br /> | Source Type<br /> | The type of lookup (see under Source types below for further information<br /> |-<br /> | Default Destination<br /> | 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.<br /> |-<br /> | Dynamic Route Entries<br /> | Zero or more entries to be matched by the lookup result. If the lookup matches, then the call is routed to the chosen destination. Each match is tried in the order given until one matches. If no match is found then the call is sent to the Default Destination. Additional rows may be added by clicking the + symbol. Entries may be deleted by cancelling the value in the Match field.<br /> |}<br /> <br /> ==Source Type==<br /> <br /> The following are the currently available source types for lookups. Each source type has its own specific fields for defining the lookup parameters.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Source Type<br /> ! Comment<br /> |-<br /> | none<br /> | No lookup is carried out. The call is sent to the default destination<br /> |-<br /> | MySQL<br /> | A lookup is done to a MySQL database. The parameters used are:<br /> * MySQL hostname: hostname of server<br /> * MySQL database: database name<br /> * MySQL username: username<br /> * MySQL password: password<br /> * MySQL query: the SQL to be used. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> |-<br /> | ODBC<br /> | A lookup is done to an Asterisk ODBC data source. The parameters used are:<br /> * ODBC function: the Asterisk ODBC function name that has been configured<br /> * ODBC query: the query. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux |article]]<br /> |- <br /> | URL<br /> | A lookup is done to a URL. The parameters used are:<br /> * URL Looup: the URL to be used for the lookup. The results must be text only. HTML, XML and JSON is not supported. The URL may contains parameters and the parameter values may include the substitutions indicated in the following table. Example: &lt;nowiki&gt;http://localhost/test.php?param1=4&amp;param2=[NUMBER]&lt;/nowiki&gt;<br /> |-<br /> | AGI<br /> | A lookup is done by launching an Asterisk AGI script. The parameters used are:<br /> * AGI Lookup: the name of the Asterisk AGI script to be launched.<br /> * AGI Result Variable: the name of the variable that the script uses to communicate the result. The script should execute a SET VARIABLE command using this variable name at the end of execution in order to pass back the lookup result. An example script is given in the installation directory (test.agi).<br /> |-<br /> | Asterisk Variable<br /> | The lookup value is read from an Asterisk Variable. The parameters used are:<br /> * 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(&quot;^1.3$&quot; ${DYNROUTE_dtmf})} would check that the DTMF input was in the range 1000-1999 (providing that the Saved input variable name was set to &quot;dtmf&quot;)<br /> |}<br /> <br /> ==Substitutions==<br /> <br /> &lt;strong&gt;In the lookup&lt;/strong&gt;<br /> <br /> When defining the query field for the lookup, the following Variable Names will be substituted by the corresponding value at the time of the call routing.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | [INPUT]<br /> | The DTMF input by the caller on the touchtone keypad<br /> |-<br /> | [NUMBER]<br /> | The callerid of the incoming call<br /> |-<br /> | [DID]<br /> | The called number<br /> |-<br /> | [name]<br /> | Where &quot;name&quot; 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.&lt;br&gt;&lt;br&gt;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 &quot;Asterisk variable&quot;. <br /> |}<br /> <br /> &lt;strong&gt;In custom dial plan or other FreePBX modules&lt;/strong&gt;<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | DYNROUTE_name<br /> | Where &quot;name&quot; 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.<br /> |}<br /> <br /> ==Screenshot of adding a Dynamic Route==<br /> <br /> [[File:dynamic_route_add.png]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_Reference_documentation&diff=855 2018-06-08T04:15:42Z

<p>John: </p> <hr /> <div>==Dynamic Route==<br /> <br /> The following information documents how to fill in the fields of a Dynamic Route. This documentation refers to the V13 functionality. Not all options are available in previous versions.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Field name<br /> ! Comment<br /> |-<br /> | Dynamic Route Name<br /> | The name of the dynamic route. This can be chosen at will. It is used to identify the route when selecting it as a destination from other applications or inbound routes. <br /> |-<br /> | Dynamic Route Description<br /> | Optional description text for the Dynamic Route. This is for documentation purposes only<br /> |-<br /> | Enable DTMF Input<br /> | Setting: Yes or No. Default: No. If set to yes the call waits for input on the touch tone keypad. This can be used to capture caller input (for example a customer number).<br /> |-<br /> | Announcement<br /> | The system recording to be played back. If Enable DTMF input is set to Yes then playback takes palce before waiting for DTMF input.<br /> |-<br /> | Timeout<br /> | Timeout in seconds to wait for DTMF input. This value is only used if Enable DTMF Input is set to Yes. If no value is given for timeout, the default for the channel is used. It is best to set an explicit value to avoid doubts. <br /> |-<br /> | Validation<br /> | Validation rules using a Asterisk regular expression (see Asterisk [https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Function_REGEX REGEX]). For example to ensure the input is between 3 and 4 digits long you could use ^[0-9]\{3,4\}$<br /> |-<br /> | Invalid Retries<br /> | Number of times to retry if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Retry Recording <br /> | Recording to play if DTMF input does not match validation rules.<br /> |-<br /> | Invalid Recording<br /> | Recording to play if DTMF input does not match validation rules and Invalid Retries have been exhausted.<br /> |-<br /> | Invalid Destination<br /> | The destination to send the call to if DTMF input does not match the validation rules and Invalid Retries ahve been exhausted. The call is sent to this destination after playing the Invalid Recording if it is defined.<br /> |-<br /> | Saved input varibale name<br /> | 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<br /> |-<br /> | Saved result variable name<br /> | 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<br /> |-<br /> | Source Type<br /> | The type of lookup (see under Source types below for further information<br /> |-<br /> | Default Destination<br /> | 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.<br /> |-<br /> | Dynamic Route Entries<br /> | Zero or more entries to be matched by the lookup result. If the lookup matches, then the call is routed to the chosen destination. Each match is tried in the order given until one matches. If no match is found then the call is sent to the Default Destination. Additional rows may be added by clicking the + symbol. Entries may be deleted by cancelling the value in the Match field.<br /> |}<br /> <br /> ==Source Type==<br /> <br /> The following are the currently available source types for lookups. Each source type has its own specific fields for defining the lookup parameters.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Source Type<br /> ! Comment<br /> |-<br /> | none<br /> | No lookup is carried out. The call is sent to the default destination<br /> |-<br /> | MySQL<br /> | A lookup is done to a MySQL database. The parameters used are:<br /> * MySQL hostname: hostname of server<br /> * MySQL database: database name<br /> * MySQL username: username<br /> * MySQL password: password<br /> * MySQL query: the SQL to be used. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> |-<br /> | ODBC<br /> | A lookup is done to an Asterisk ODBC data source. The parameters used are:<br /> * ODBC function: the Asterisk ODBC function name that has been configured<br /> * ODBC query: the query. It can contain substitutions as indicated in the table below. Example: select destination from callerid_table where calleridnum like '%[NUMBER]' <br /> For information about setting up ODBC see this [[How to set up an Asterisk ODBC data source on Linux |article]]<br /> |- <br /> | URL<br /> | A lookup is done to a URL. The parameters used are:<br /> * URL Looup: the URL to be used for the lookup. The results must be text only. HTML, XML and JSON is not supported. The URL may contains parameters and the parameter values may include the substitutions indicated in the following table. Example: &lt;nowiki&gt;http://localhost/test.php?param1=4&amp;param2=[NUMBER]&lt;/nowiki&gt;<br /> |-<br /> | AGI<br /> | A lookup is done by launching an Asterisk AGI script. The parameters used are:<br /> * AGI Lookup: the name of the Asterisk AGI script to be launched.<br /> * AGI Result Variable: the name of the variable that the script uses to communicate the result. The script should execute a SET VARIABLE command using this variable name at the end of execution in order to pass back the lookup result. An example script is given in the installation directory (test.agi).<br /> |-<br /> | Asterisk Variable<br /> | The lookup value is read from an Asterisk Variable. The parameters used are:<br /> * 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(&quot;^1.3$&quot; ${DYNROUTE_dtmf})} would check that the DTMF input was in the range 1000-1999 (providing that the Saved input variable name was set to &quot;dtmf&quot;)<br /> |}<br /> <br /> ==Substitutions==<br /> <br /> &lt;strong&gt;In the lookup&lt;/strong&gt;<br /> <br /> When defining the query field for the lookup, the following Variable Names will be substituted by the corresponding value at the time of the call routing.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | [INPUT]<br /> | The DTMF input by the caller on the touchtone keypad<br /> |-<br /> | [NUMBER]<br /> | The callerid of the incoming call<br /> |-<br /> | [DID]<br /> | The called number<br /> |-<br /> | [name]<br /> | Where &quot;name&quot; 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.&lt;br&gt;&lt;br&gt;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 &quot;Asterisk variable&quot;. <br /> |}<br /> <br /> &lt;strong&gt;In custom dial plan or other FreePBX modules&lt;/strong&gt;<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Variable Name<br /> ! Substituted by <br /> |-<br /> | DYNROUTE_name<br /> | Where &quot;name&quot; 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.<br /> |}<br /> <br /> ==Screenshot of adding a Dynamic Route==<br /> <br /> [[File:dynamic_route_add.png]]</div>

John https://voipsupport.it/wiki/index.php?title=Linux/LVM_how_to_increase_file_system_size_by_adding_physical_volume&diff=854 2018-04-21T23:29:36Z

<p>John: </p> <hr /> <div>1. Scan for devices that can be used as physical volumes<br /> <br /> &lt;pre&gt;lvmdiskscan&lt;/pre&gt;<br /> <br /> 2. Create physical volume<br /> <br /> &lt;pre&gt;pvcreate /dev/sdd1&lt;/pre&gt;<br /> <br /> 3. Display physical volume<br /> <br /> &lt;pre&gt;pvdisplay&lt;/pre&gt;<br /> <br /> 4. Display logical volume group<br /> <br /> &lt;pre&gt;vgdisplay&lt;/pre&gt;<br /> <br /> 5. Add a physical volume to a logical volume group<br /> &lt;pre&gt;vgextend vg1 /dev/sdf1&lt;/pre&gt;<br /> <br /> 6. Display all logical volumes<br /> <br /> &lt;pre&gt;lvdisplay&lt;/pre&gt;<br /> <br /> 7. Display a specific logical volume<br /> <br /> &lt;pre&gt;lvdisplay -v /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 8. Extend logical volume by a set amount (e.g. 1GB)<br /> <br /> &lt;pre&gt;lvextend -L+1G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 9. Extend logical volume to a set amount (e.g. 12GB)<br /> <br /> &lt;pre&gt;lvextend -L12G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 10. Extend logical volume to fill all free space on logical volume group<br /> <br /> &lt;pre&gt;lvextend -l +100%FREE /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 11. Resize the underlying ext4 file system to the maximum of the new logical volume<br /> &lt;pre&gt;resize2fs /dev/myvg/homevol&lt;/pre&gt;</div>

John https://voipsupport.it/wiki/index.php?title=Linux/LVM_how_to_increase_file_system_size_by_adding_physical_volume&diff=853 2018-04-21T23:28:36Z

<p>John: </p> <hr /> <div>1. Scan for devices that can be used as physical volumes<br /> <br /> &lt;pre&gt;lvmdiskscan&lt;/pre&gt;<br /> <br /> 2. Create physical volume<br /> <br /> &lt;pre&gt;pvcreate /dev/sdd1&lt;/pre&gt;<br /> <br /> 3. Display physical volume<br /> <br /> &lt;pre&gt;pvdisplay&lt;/pre&gt;<br /> <br /> 4. Display logical volume group<br /> <br /> &lt;pre&gt;vgdisplay&lt;/pre&gt;<br /> <br /> 5. Add a physical volume to a logical volume group<br /> &lt;pre&gt;vgextend vg1 /dev/sdf1&lt;/pre&gt;<br /> <br /> 6. Display all logical volumes<br /> <br /> &lt;pre&gt;lvdisplay&lt;/pre&gt;<br /> <br /> 7. Display a specific logical volume<br /> <br /> &lt;pre&gt;lvdisplay -v /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 8. Extend logical volume by a set amount (e.g. 1GB)<br /> <br /> &lt;pre&gt;lvextend -L+1G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 9. Extend logical volume to a set amount (e.g. 12GB)<br /> <br /> &lt;pre&gt;lvextend -L12G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 10. Extend logical volume to fill all free space on logical volume group<br /> <br /> &lt;pre&gt;lvextend -l +100%FREE /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 11. Resize the underlying ext4 file system to the maximum of the new logical volume. Get the device name from df command<br /> <br /> &lt;pre&gt;resize2fs /dev/myvg/homevol&lt;/pre&gt;</div>

John https://voipsupport.it/wiki/index.php?title=Linux/LVM_how_to_increase_file_system_size_by_adding_physical_volume&diff=852 2018-04-21T23:26:51Z

<p>John: </p> <hr /> <div>1. Scan for devices that can be used as physical volumes<br /> <br /> &lt;pre&gt;lvmdiskscan&lt;/pre&gt;<br /> <br /> 2. Create physical volume<br /> <br /> &lt;pre&gt;pvcreate /dev/sdd1&lt;/pre&gt;<br /> <br /> 3. Display physical volume<br /> <br /> &lt;pre&gt;pvdisplay&lt;/pre&gt;<br /> <br /> 4. Display logical volume group<br /> <br /> &lt;pre&gt;vgdisplay&lt;/pre&gt;<br /> <br /> 5. Add a physical volume to a logical volume group<br /> &lt;pre&gt;vgextend vg1 /dev/sdf1&lt;/pre&gt;<br /> <br /> 6. Display all logical volumes<br /> <br /> &lt;pre&gt;lvdisplay&lt;/pre&gt;<br /> <br /> 7. Display a specific logical volum<br /> <br /> &lt;pre&gt;lvdisplay -v /dev/myvg/homevol&lt;pre&gt;<br /> <br /> 8. Extend logical volume by a set amount (e.g. 1GB)<br /> <br /> &lt;pre&gt;lvextend -L+1G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 9. Extend logical volume to a set amount (e.g. 12GB)<br /> <br /> &lt;pre&gt;lvextend -L12G /dev/myvg/homevol&lt;/pre&gt;<br /> <br /> 10. Extend logical volume to fill all free space on logical volume group<br /> <br /> &lt;pre&gt;lvextend -l +100%FREE /dev/myvg/testlv&lt;/pre&gt;<br /> <br /> 11. Resize the underlying ext4 file system to the maximum of the new logical volume. Get the device name from df command<br /> <br /> &lt;pre&gt;resize2fs /dev/mapper/VolGroup-lv_root&lt;/pre&gt;</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_FAQ&diff=851 2018-01-21T17:36:48Z

<p>John: /* Q. Does Dynamic Route create the lookup table I will use in my query? */</p> <hr /> <div>==General FAQ==<br /> <br /> ===Q. What are the prerequisites for Dynamic Routes?===<br /> <br /> A. The Dynamic Route module itself does not introduce additional prerequisites, so if your system is set up for Asterisk and FreePBX this module can be installed without adding any additional software. However, the lookup method you choose can introduce additional prerequisites.<br /> <br /> If you are using Dynamic Routes to connect to a MySQL database directly (without ODBC) then an additional Asterisk module is required (app_mysql). Please note that the app_mysql is not built by default. Please see this [[How to install Asterisk app_mysql|link]] for information. Although app_mysql is still widely used, it is no longer the recommended way to connect to the MySQL database from Asterisk.<br /> <br /> If you are using Dynamic Routes with ODBC you will need to install the ODBC software and driver for your database and configure it. Please see this [[How to set up an Asterisk ODBC data source on Linux|link]] for information.<br /> <br /> ===Q. Does Dynamic Routes effect performance?===<br /> <br /> A. For most installations that are not under heavy load, there will not be performance concerns. However in high traffic installations, the performance aspect should be considered. Of course if the mysql query is not correctly tuned, then even low traffic sites will have issues. So first of all, the query to be used should be checked on a database with similar volumes as the production environment to ensure that it completes quickly. Any tuning of the query or needed indexes should be added.<br /> <br /> Instead of running the query against an online database, you may also consider a batch procedure which periodically extracts the needed information, reorganized in the optimum way and then load into a table where asterisk will specifically query it.<br /> <br /> Performance will be enhanced by using a local database instead of a remote database. Performance is also enhanced by using a non-SSL connection to the database, but this is not advisable for a remote database due to security concerns - see below. Even for a local database there may be security concerns of using a non-SSL connection, depending on who may access the server.<br /> <br /> When connecting to a database Dynamic Routes can use MySQL directly (using Asterisk app_mysql) or ODBC. ODBC is now the recommended way of accessing a database from Asterisk. It is reported that the level of indirection does not introduce any noticeable performance issue.<br /> <br /> ===Q. Does Dynamic Routes effect system availability?===<br /> <br /> A. With Dynamic Routes a database or a web service can be used for lookups during incoming calls. Therefore the database or web server become a necessary component for call processing. If the server is unavailable, dynamic routing will not take place. You may however define a default destination. When a lookup fails it will follow the default destination. The default destination is also used when the lookup succeeds but no match is found. Using a local database or web server reduces availability dependencies but does not remove them entirely. <br /> <br /> ===Q. What are the security implications of using Dynamic Routes?===<br /> <br /> A. The asterisk mysql add-on does not support SSL encrypted connections, so information (including credentials) passed between asterisk and the database may be intercepted. That is one reason why a local database is recommended. If your installation must use a remote server, consider whether a better option, also from performance and availability perspectives, would be to periodically copy the data needed into the mysql database running on the asterisk server.<br /> <br /> If you must use a remote server, then it is recommended (unless you can setup a local LAN between the two servers without risk of interception) to use ODBC with SSL enabled. An alternative is to setup an encrypted tunnel using a VPN or a software like stunnel.<br /> <br /> In any case it is recommended that the database be separate to the ones used for FreePBX configurations and CDRs. It is also recommended that a specific user is setup in order to access the database and that it has only select permissions on the tables that are used in the query. You should avoid using tables in the query that contain sensitive data, such as passwords. Consider defining a view if you have this case, which only gives access to the relevant columns needed. On MySQL for performance reasons that impact the whole server avoid using grant statements that contain column level access.<br /> <br /> ===Q. What does the message &lt;&lt;Module &quot;Dynamic Routes&quot; is unsigned and should be re-downloaded&gt;&gt; mean?===<br /> <br /> A. FreePBX now has a system whereby a hash of the source code is computed and signed by Sangoma. See [http://wiki.freepbx.org/display/FPG/Module+Signing this link] for more information. This functionality is extremely useful because users know that the modules are the official versions and (unless the verification code itself is tampered with) they know that the code has not been modified.<br /> <br /> While very useful, there are a couple of implications:<br /> * Third party modules will show an unsigned module warning<br /> * 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<br /> <br /> 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.<br /> <br /> ==Configuration FAQ==<br /> <br /> ===Q. How can I avoid matching short caller ids?===<br /> <br /> A. You can use a condition in the WHERE clause to ensure that only caller ids of sufficient length are matched. This is useful if your database contains company phone numbers with similar prefixes, but when receiving calls the caller id is set to the shorter main phone number of the company.<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like '%[NUMBER]' and length('[NUMBER]') &gt; 4&lt;/pre&gt;<br /> <br /> ===Q. How can I match data in my database when sometimes the caller id arrives with an international prefix of + country codes, other times 00 country code and other times just as a national number?===<br /> <br /> A. You may use the MySQL TRIM function to adjust the presented caller id to match the type of data in your database. For example:<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like concat('%',TRIM(LEADING '+' FROM TRIM(LEADING '0' FROM '[NUMBER]')))&lt;/pre&gt;<br /> <br /> ===Q. Does Dynamic Route create the lookup table I will use in my query?===<br /> <br /> 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.<br /> <br /> ===Q. Why don't my inbound calls get routed through Dynamic Routes?===<br /> <br /> A. Dynamic Routes does not automatically intervene in the call processing of your system. If you want calls to pass through Dynamic Routes you will need to configure your system to hand the calls to a specific Dynamic Route. Typically you can do this from the FreePBX &quot;Connectivity&quot; menu by choosing &quot;Inbound Routes&quot;. Choose the inbound route you want to pass through Dynamic Route and in that route put the Dynamic Route as the destination. Call flow will then pass through the specified Dynamic Route.<br /> <br /> ==Trouble shooting FAQ==<br /> <br /> ===When reporting a problem what information should I provide?===<br /> <br /> Please see [[Dynamic Routes Support|here]]<br /> <br /> ===Q. Why do I get strange errors when using asterisk MYSQL module?===<br /> <br /> &lt;pre&gt;[2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Error in extension logic (missing '}')<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Can't find trailing parenthesis for function 'CALLERID(nu'?<br /> [2015-04-24 21:52:59] ERROR[14294][C-000020b6] func_callerid.c: Unknown callerid data type 'nu'.<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:4] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Query resultid 1 select callerid_firstname from calleridlookup where owner='john' and '&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_query: mysql_query failed. Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:5] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Fetch fetchid dynroute&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_fetch: missing some arguments<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:6] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Clear &quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Identifier 0, identifier_type 2 not found in identifier list<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Invalid result identifier 0 passed in aMYSQL_clear<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:7] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Disconnect 1&quot;) in new stack<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:8] Set(&quot;SIP/215-00000087&quot;, &quot;__DYNROUTE_TEST=&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected '=', expecting $end; Input:&gt;&lt;/pre&gt;<br /> <br /> A. Do not use a semicolon at the end of the query. This syntax is not supported by asterisk MYSQL module.</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_FAQ&diff=850 2018-01-21T17:34:39Z

<p>John: /* Q. What does the message &gt; mean? */</p> <hr /> <div>==General FAQ==<br /> <br /> ===Q. What are the prerequisites for Dynamic Routes?===<br /> <br /> A. The Dynamic Route module itself does not introduce additional prerequisites, so if your system is set up for Asterisk and FreePBX this module can be installed without adding any additional software. However, the lookup method you choose can introduce additional prerequisites.<br /> <br /> If you are using Dynamic Routes to connect to a MySQL database directly (without ODBC) then an additional Asterisk module is required (app_mysql). Please note that the app_mysql is not built by default. Please see this [[How to install Asterisk app_mysql|link]] for information. Although app_mysql is still widely used, it is no longer the recommended way to connect to the MySQL database from Asterisk.<br /> <br /> If you are using Dynamic Routes with ODBC you will need to install the ODBC software and driver for your database and configure it. Please see this [[How to set up an Asterisk ODBC data source on Linux|link]] for information.<br /> <br /> ===Q. Does Dynamic Routes effect performance?===<br /> <br /> A. For most installations that are not under heavy load, there will not be performance concerns. However in high traffic installations, the performance aspect should be considered. Of course if the mysql query is not correctly tuned, then even low traffic sites will have issues. So first of all, the query to be used should be checked on a database with similar volumes as the production environment to ensure that it completes quickly. Any tuning of the query or needed indexes should be added.<br /> <br /> Instead of running the query against an online database, you may also consider a batch procedure which periodically extracts the needed information, reorganized in the optimum way and then load into a table where asterisk will specifically query it.<br /> <br /> Performance will be enhanced by using a local database instead of a remote database. Performance is also enhanced by using a non-SSL connection to the database, but this is not advisable for a remote database due to security concerns - see below. Even for a local database there may be security concerns of using a non-SSL connection, depending on who may access the server.<br /> <br /> When connecting to a database Dynamic Routes can use MySQL directly (using Asterisk app_mysql) or ODBC. ODBC is now the recommended way of accessing a database from Asterisk. It is reported that the level of indirection does not introduce any noticeable performance issue.<br /> <br /> ===Q. Does Dynamic Routes effect system availability?===<br /> <br /> A. With Dynamic Routes a database or a web service can be used for lookups during incoming calls. Therefore the database or web server become a necessary component for call processing. If the server is unavailable, dynamic routing will not take place. You may however define a default destination. When a lookup fails it will follow the default destination. The default destination is also used when the lookup succeeds but no match is found. Using a local database or web server reduces availability dependencies but does not remove them entirely. <br /> <br /> ===Q. What are the security implications of using Dynamic Routes?===<br /> <br /> A. The asterisk mysql add-on does not support SSL encrypted connections, so information (including credentials) passed between asterisk and the database may be intercepted. That is one reason why a local database is recommended. If your installation must use a remote server, consider whether a better option, also from performance and availability perspectives, would be to periodically copy the data needed into the mysql database running on the asterisk server.<br /> <br /> If you must use a remote server, then it is recommended (unless you can setup a local LAN between the two servers without risk of interception) to use ODBC with SSL enabled. An alternative is to setup an encrypted tunnel using a VPN or a software like stunnel.<br /> <br /> In any case it is recommended that the database be separate to the ones used for FreePBX configurations and CDRs. It is also recommended that a specific user is setup in order to access the database and that it has only select permissions on the tables that are used in the query. You should avoid using tables in the query that contain sensitive data, such as passwords. Consider defining a view if you have this case, which only gives access to the relevant columns needed. On MySQL for performance reasons that impact the whole server avoid using grant statements that contain column level access.<br /> <br /> ===Q. What does the message &lt;&lt;Module &quot;Dynamic Routes&quot; is unsigned and should be re-downloaded&gt;&gt; mean?===<br /> <br /> A. FreePBX now has a system whereby a hash of the source code is computed and signed by Sangoma. See [http://wiki.freepbx.org/display/FPG/Module+Signing this link] for more information. This functionality is extremely useful because users know that the modules are the official versions and (unless the verification code itself is tampered with) they know that the code has not been modified.<br /> <br /> While very useful, there are a couple of implications:<br /> * Third party modules will show an unsigned module warning<br /> * 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<br /> <br /> 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.<br /> <br /> ==Configuration FAQ==<br /> <br /> ===Q. How can I avoid matching short caller ids?===<br /> <br /> A. You can use a condition in the WHERE clause to ensure that only caller ids of sufficient length are matched. This is useful if your database contains company phone numbers with similar prefixes, but when receiving calls the caller id is set to the shorter main phone number of the company.<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like '%[NUMBER]' and length('[NUMBER]') &gt; 4&lt;/pre&gt;<br /> <br /> ===Q. How can I match data in my database when sometimes the caller id arrives with an international prefix of + country codes, other times 00 country code and other times just as a national number?===<br /> <br /> A. You may use the MySQL TRIM function to adjust the presented caller id to match the type of data in your database. For example:<br /> <br /> &lt;pre&gt;select destination from callerid_table where calleridnum like concat('%',TRIM(LEADING '+' FROM TRIM(LEADING '0' FROM '[NUMBER]')))&lt;/pre&gt;<br /> <br /> ===Q. Does Dynamic Route create the lookup table I will use in my query?===<br /> <br /> 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.<br /> <br /> ===Q. Why don't my inbound calls get routed through Dynamic Routes?===<br /> <br /> A. Dynamic Routes does not automatically intervene in the call processing of your system. If you want calls to pass through Dynamic Routes you will need to configure your system to hand the calls to a specific Dynamic Route. Typically you can do this from the FreePBX &quot;Connectivity&quot; menu by choosing &quot;Inbound Routes&quot;. Choose the inbound route you want to pass through Dynamic Route and in that route put the Dynamic Route as the destination. Call flow will then pass through the specified Dynamic Route.<br /> <br /> ==Trouble shooting FAQ==<br /> <br /> ===When reporting a problem what information should I provide?===<br /> <br /> Please see [[Dynamic Routes Support|here]]<br /> <br /> ===Q. Why do I get strange errors when using asterisk MYSQL module?===<br /> <br /> &lt;pre&gt;[2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Error in extension logic (missing '}')<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] pbx.c: Can't find trailing parenthesis for function 'CALLERID(nu'?<br /> [2015-04-24 21:52:59] ERROR[14294][C-000020b6] func_callerid.c: Unknown callerid data type 'nu'.<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:4] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Query resultid 1 select callerid_firstname from calleridlookup where owner='john' and '&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_query: mysql_query failed. Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:5] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Fetch fetchid dynroute&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: aMYSQL_fetch: missing some arguments<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:6] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Clear &quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Identifier 0, identifier_type 2 not found in identifier list<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] app_mysql.c: Invalid result identifier 0 passed in aMYSQL_clear<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:7] MYSQL(&quot;SIP/215-00000087&quot;, &quot;Disconnect 1&quot;) in new stack<br /> [2015-04-24 21:52:59] VERBOSE[14294][C-000020b6] pbx.c: -- Executing [s@dynroute-21:8] Set(&quot;SIP/215-00000087&quot;, &quot;__DYNROUTE_TEST=&quot;) in new stack<br /> [2015-04-24 21:52:59] WARNING[14294][C-000020b6] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected '=', expecting $end; Input:&gt;&lt;/pre&gt;<br /> <br /> A. Do not use a semicolon at the end of the query. This syntax is not supported by asterisk MYSQL module.</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=849 2018-01-10T21:17:07Z

<p>John: /* FreePBX 14 support */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project is hosted on github. Please see: [https://github.com/johnfawcett/dynroute/ Dynamic Route source code repository]<br /> <br /> [https://github.com/johnfawcett/dynroute/blob/master/CHANGES.txt Dynamic Routes Change Log]<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.1/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release. Any new features are added to this version.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_Future_plans&diff=848 2017-10-29T17:58:42Z

<p>John: </p> <hr /> <div>'''Changes that may be addressed in a future release'''<br /> <br /> * 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.<br /> * 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.</div>

John https://voipsupport.it/wiki/index.php?title=File:Dynroute-14.0.1.tgz.sig&diff=847 2017-10-21T12:01:26Z

<p>John: </p> <hr /> <div></div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes_gpg_signatures&diff=846 2017-10-21T12:00:04Z

<p>John: </p> <hr /> <div><br /> &lt;strong&gt;Signature for 2.11.3.2&lt;/strong&gt;<br /> <br /> [[File:dynroute-2.11.3.2.zip.sig]]<br /> <br /> &lt;strong&gt;Signature for 13.0.5&lt;/strong&gt;<br /> <br /> [[File:dynroute-13.0.5.zip.sig]]<br /> <br /> &lt;strong&gt;Signature for 14.0.0&lt;/strong&gt;<br /> <br /> [[File:dynroute-14.0.0.tgz.sig]]<br /> <br /> &lt;strong&gt;Signature for 14.0.1&lt;/strong&gt;<br /> <br /> [[File:dynroute-14.0.1.tgz.sig]]<br /> <br /> &lt;strong&gt;GPG Public Key used to sign the release packages&lt;/strong&gt;<br /> <br /> [[File:johnfawcett.gpg]]</div>

John https://voipsupport.it/wiki/index.php?title=Dynamic_Routes&diff=845 2017-10-21T11:59:16Z

<p>John: /* How do I get it? */</p> <hr /> <div>==What is it?==<br /> <br /> Dynamic Routes is a FreePBX module. [[http://www.freepbx.org FreePBX]] is a GUI which allows administrators to configure the [http://www.asterisk.org Asterisk] communications platform without writing Asterisk dial plan code or configuration files. Dynamic Routes adds to the FreePBX functionality, by configuration of call routing based on the result of a lookup.<br /> <br /> Originally Dynamic Routes allowed lookups only to a MySQL database. In the latest version there are many more lookup methods. However the principle is still the same: to allow data dependent call routing.<br /> <br /> ==What could I use it for?==<br /> <br /> The potential uses are many. Here are some examples:<br /> * screen calls to a support hotline according to agreed support methods and service levels<br /> * route calls to a dedicated agent or queue by customer category or importance<br /> * play different announcements to different callers<br /> * basically anything where you want the call to go to a different destination depending on some known data (like the Caller id) or data input by the customer using DTMF keypad (like contract id)<br /> <br /> ==How do I get it?==<br /> <br /> The code for the project is hosted on github. Please see: [https://github.com/johnfawcett/dynroute/ Dynamic Route source code repository]<br /> <br /> [https://github.com/johnfawcett/dynroute/blob/master/CHANGES.txt Dynamic Routes Change Log]<br /> <br /> ===FreePBX 14 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/releases/download/14.0.0/dynroute-14.0.1.tgz Dynamic Routes 14.0.1]<br /> <br /> Updated for the Freepbx 14 release. Any new features are added to this version.<br /> <br /> ===FreePBX 13 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/13.0.5.zip Dynamic Routes 13.0.5]<br /> <br /> This version has been rewritten to comply with the FreePBX 13 framework. You may use this version to upgrade from a previous 13.x version or 2.11 version. This version may not be used on previous versions of FreePBX.<br /> <br /> ===FreePBX 11 and 12 support===<br /> <br /> [https://github.com/johnfawcett/dynroute/archive/2.11.3.2.zip Dynamic Routes 2.11.3.2]<br /> <br /> As of 20/03/2017 this version is no longer supported. Please use a later version if possible.<br /> <br /> Previous versions are archived for historical reference but are no longer maintained and should not be used: [[Dynamic Routes previous versions]]<br /> <br /> GPG signatures for the latest versions are available here [[Dynamic Routes gpg signatures]]<br /> <br /> ==Where can I get more information?==<br /> <br /> * [[Dynamic Routes Installation instructions|Installation instructions]]<br /> * [[Dynamic Routes Example configuration|Example configuration]]<br /> * [[Dynamic Routes Reference documentation|Reference documentation]]<br /> * [[Dynamic Routes Future plans|Future plans]]<br /> * [[Dynamic Routes Licence|Licence]]<br /> * [[Dynamic Routes FAQ|FAQ]]<br /> * [[Dynamic Routes Support|Support]]</div>

John