PBX Nodes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[File:PBXNodes.png|thumb|400px]] | [[File:PBXNodes.png|thumb|400px]] | ||
The MiRTA PBX system can be composed of several pbx nodes. License is enforced only for the number of pbx nodes. In the main screen, the number of connected peers for each node is shown. A peer can be connected to multiple nodes. A series of extra actions are available and a check for ODBC connectivity is performed as well process status. | The MiRTA PBX system can be composed of several pbx nodes. License is enforced only for the number of pbx nodes. In the main screen, the number of connected peers for each node is shown. A peer can be connected to multiple nodes. A series of extra actions are available and a check for ODBC connectivity is performed as well process status. | ||
Asterisk may have some problem when it is started and MySQL database is not yet ready. There are a total of 4 ODBC datasource used, two for configuration (asterisk1 and asterisk2) and two for CDR (asteriskcdrdb1 and asteriskcdrdb2). While the datasource for the configuration is automatically restarted if disconnected, the CDR datasource will not. That happens only at start. If any of the datasource is not connected, a red DB icon is shown. | |||
Starting with Asterisk 13.8.2, asterisk doesn't use pooled ODBC connection, so checking ODBC connection is harder. | |||
In case a CDR datasource is not connected, it is possible to reconnect using the following command: | |||
asterisk -rx 'module reload cdr_adaptive_odbc.so' | |||
In case an ODBC datasource is not connected, it is possible to reconnect using the following command: | |||
asterisk -rx 'module reload res_odbc.so' | |||
The following icon status are available: | |||
[[File:fa-database|16px]] ODBC database connection | |||
Revision as of 13:07, 22 April 2016
The MiRTA PBX system can be composed of several pbx nodes. License is enforced only for the number of pbx nodes. In the main screen, the number of connected peers for each node is shown. A peer can be connected to multiple nodes. A series of extra actions are available and a check for ODBC connectivity is performed as well process status.
Asterisk may have some problem when it is started and MySQL database is not yet ready. There are a total of 4 ODBC datasource used, two for configuration (asterisk1 and asterisk2) and two for CDR (asteriskcdrdb1 and asteriskcdrdb2). While the datasource for the configuration is automatically restarted if disconnected, the CDR datasource will not. That happens only at start. If any of the datasource is not connected, a red DB icon is shown.
Starting with Asterisk 13.8.2, asterisk doesn't use pooled ODBC connection, so checking ODBC connection is harder.
In case a CDR datasource is not connected, it is possible to reconnect using the following command:
asterisk -rx 'module reload cdr_adaptive_odbc.so'
In case an ODBC datasource is not connected, it is possible to reconnect using the following command:
asterisk -rx 'module reload res_odbc.so'
The following icon status are available:
File:Fa-database ODBC database connection