M4 CDR Management

From Kolmisoft Wiki
(Redirected from M2 CDR Management)
Jump to navigationJump to search

Description

When there are many old calls that are no longer useful, they can be archived and moved to another place.

Such housekeeping increases system stability, reliability, and speed.

Usage

Configuration

Archiving options can be set in MAINTENANCE -> Settings in Archived Calls section:

  • Delete not-Archived not-Answered Calls older than: - this is the number of days (default is 45 days in fresh installations). When a not-Archived not-Answered call is older than the number you set, it will be deleted. Linux cron job /etc/cron.d/m2_delete_old_calls

is executed every 30 minutes which checks if there are any matching calls and delete them if it finds any.

  • Archive to - choose where to store Archived Calls. By default Archived Calls are stored in another MySQL table mor.calls_old. You can also choose to store Archived Calls in compressed CSV files by selecting File (TGZ) option.
    • It is also possible to choose to store Archived Calls to FTP (TGZ). In this case, Archived Calls will be stored on an FTP server. Please enter FTPserver details if you would like to use this option.
  • Archive Calls older than – this is the number of days. When a Call is older than the number you set, it will be archived and moved to Archived Calls.
  • Archive only ANSWERED calls – check to archive only answered Calls. Failed, Busy and No Answer Calls will be deleted.
  • Archive Calls every day at – when archiving process should be started? Call archiving requires a lot of system resources therefore it is advisable to start archiving when call traffic is low.
  • Stop Archiving Calls at – when archiving process should be stopped? It is advisable to stop archiving before call traffic is increased. If time is not specified, Call archiving will be stopped when all Calls are archived.
  • Do not delete Archived Calls from calls table - do not delete calls from the calls table after copying them to the calls_old table.
  • Delete Calls instead of Archiving - if you don't need Calls older than X days, you can delete them instead of archiving them.
  • Delete Archived Calls older than - this is the number of days. When archived Call is older than the number you set, it will be deleted.
  • SQL Max Execution Time - max time in seconds for SQL query. The default time is 300 seconds (5 minutes). Used in Statistics pages (Calls List export and similar).

NOTE: you can check the completion of the call archiving process and other information in Background Tasks.

Archived Calls

If calls are stored in another MySQL table mor.calls_old it can be found at Reports –> Call list –> Archived Calls.
Here you can see a similar table to Last Calls, so you can check call information at any time you want. You can find more information about each field in Last Calls

NOTE Simple Users cannot see the Archived Calls page.

Archived Calls in Files

If Archive to File (TGZ) option is enabled, Calls will be archived to CSV files (max 50000 lines per file), then compressed to TGZ and stored in your Backup storage directory (http://wiki.kolmisoft.com/index.php/Backup_system#Configuration).
Calls archiving into file allows avoiding growing database and lets to use archived calls data more flexible.

Files with calls can be found at REPORTS –> Call list –> Archived Calls -> Files

M4 old calls in file.png

NOTE Files can be reached and managed by admin only.

Bulk management

Files can be deleted one by one with click on DELETE in the files list or a few at a time by selecting the period in Bulk management



See also