Relocate Audio Files

The "Relocate Audio Files" job can be used to move audio files from one location to another. For example, the files can be moved automatically from local file storage to the external storage by schedule.

Create the Relocate job

Navigate to Administration -> Storage -> Relocate Audio Files and click Add to create the relocate job.

Fill out the required configuration parameters:

• Name - give the job a distinctive name.
• Access Scope - specifiy for which tenants this job is applicable to. This setting is visible only for a multi-tenant environment.
• Test Only - use this option for testing purposes. If selected, the job will be simulated by writing a log file to a test drive.
• Destination storage target - select the previously configured storage target as a destination point.
• Destination filename format - define a format for filenames and, optionally, directories. The job can inject various call metadata attributes into file/directory names. For example, it can create directory for each day in format YYYYMMDD and then include caller-number and called-number into file name.
• Parallel upload. A number of parallel upload workers sending data simultaneously. Depending on network latency, an increase of the parallel workers may improve an upload speed due to better bandwidth utilization. This setting can be helpful when using a remote storage target.
• Mode. Full or incremental import mode.
  • Full - will move all call recordings to the target server everytime the job is started. It will gracefully skip the import process if the target server contains such recordings already.
  • Incremental - remembers which records have been moved to the target server and do not process them on next start. Such mode is useful when job is scheduled for periodic replication (every hour/day etc). It will work a lot faster than the full replication mode because it will skip automatically the previously uploaded recordings.
• If destination file exists - use this option to optimize file relocation jobs when file at the destination already exists. For example, when two MiaRec server instances (primary and secondary) relocate files to the same destination. When application detects that file already exists at the destination (because another server has already relocated file there), MiaRec compares file size only. If file size is the same, then it assumes that file content is the same as well. This is a good enough solution in most of scenarios. Calculation of checksum is recommended only when there is a suspicion that the files are corrupted at the destination target.
• Remove empty directories - use this option to delete empty directories. Usually, recording files are grouped by date on file system, i.e. new directory is created for every day (YYYYMMDD). When directory becomes empty after file relocation, the application can optionally delete such directory (up to one level).

Action after successful processing

Using these options, you can create a chain of post-processing, and mark is with relevant flags. For example, you can transcribe the recordings and mark them with a relevant tag. Then, you can apply filtering criteria to move the recordings with this tag. And once the recordings are relocated, you tell the system to clear the tag from the recordings.

Job advanced settings

Please also check the following advanced settings for the job:

• Log file - select this check box to write a detailed log for diagnostic purposes.
• Keep job history - specify the number of days to keep the the successful job history. Default value: 60.
• Timezone - allows you to change the timezone of a scheduled job. Timezone affects the scheduler, date/time attribute in Filtering Criteria, and Filename Format. Leave this attribute empty to use a system default timezone.
• Execution time limit - a job will be aborted if it executes longer than the specified time limit (in minutes). Leave this attribute empty to use a default value. Default value: <not defined>.
• Keep alive timeout - specify a timeout (in minutes) to terminate the job. Leave this attribute empty to use a default value. Default value: 15.
• Email notification on completion - activates the notification by email about successful job execution. You can trigger the email notification either every time the job completes successfully or for the first of any consecutive completion message.
• Email notification on failure - activates the notification by email about failed job execution. You can trigger the email notification either every time the job failes or for the first of any consecutive failure message.
• Email notification address - specify the email address for notifications. Use a comma to separate multiple email addresses.

Info

Note, it is necessary to configure "Web portal URL" under Administration -> System -> Advanced Settings, otherwise the URL links to job details in the email will be invalid. Also, make sure the email integration is enabled under Administration > System > Email Integration.

Schedule

The job may be started manually or automatically by schedule. The schedule may be configured to run the job every hour/day/week/month. Also, you can set up a custom interval by selecting the Custom (crontab) option.

Please check some examples, on configuring a custom interval:

• Run the job every 5 minutes.

• Run the job on 5-th minute of every hour (i.e. 00:05; 01:05; 02:05 and so on).

• Run the job on 15-th and 45-th minute of every hour (i.e. 00:15; 00:45; 01:15, 01:45 and so on).

• Run the job every hour, on the hour, from 8 AM through 5 PM.