This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
configuration:telephony:history [2014/01/16 15:06] – admin | configuration:telephony:history [2014/01/16 15:20] – admin | ||
---|---|---|---|
Line 3: | Line 3: | ||
:!: | :!: | ||
- | In Comms Mundi there is a limitation on the number of calls store internally, to avoid this limit, you can export the telephony call logs to an external database or to an CSV file. | + | In Comms Mundi there is a limitation on the number of rows store internally, to avoid this limit, you can export the telephony call logs to an external database or to an CSV file. |
Line 19: | Line 19: | ||
===== Automatic exporting history to external database ===== | ===== Automatic exporting history to external database ===== | ||
- | To be able to export call log automatically to a remote database using a ODBC connector. | + | In the page **Telephony-> |
+ | To configure the export do: | ||
+ | |||
+ | * check //Enable CDR backend // | ||
+ | * Set the // | ||
+ | * to add a new column, click on the //add// button. Set the **column** name and **variable** field to export. | ||
+ | * to delete a column, click on the //delete// button | ||
+ | * set the //ODBC// connector | ||
+ | * set the //table// | ||
+ | * by pressing //create table// will create the table on the remote database | ||
+ | * click //update// | ||
:!: | :!: | ||
The export is done at the same time as the CDR. If there is a problem connecting to the ODBC (connection lost, table doesn' | The export is done at the same time as the CDR. If there is a problem connecting to the ODBC (connection lost, table doesn' | ||