Introduction

In many contact center operations, it is necessary to automatically replicate call recordings to a client's own server, whether due to internal policies, auditing, backup, or regulatory compliance.

For this purpose, RSYNC over SSH is one of the most widely used alternatives due to its security, efficiency, and compatibility with Linux environments.

Requirements

• NAS, SAN, or Linux server with Rsync over SSH support
• User with write permissions on the selected path in the NAS or server
• Firewall port enabled for remote access from the server sending the information
• SSH key shared by Wolkvox at the time of service configuration in Wolkvox Manager or by a Wolkvox agent

Configuration in Wolkvox Manager

1. Log in to Wolkvox Manager with an administrator user and go to "Configuration" from the top-right menu.
2. Navigate to the "Integrations" section.
3. Look for the "Rsync" option.
4. Enable the checkbox "Enable audio copy via rsync".
5. In the "ssh port" field, enter the port number through which communication will be made to the client's server.
6. In the "path (user@ip:/folder)" field, enter the destination path in the format:
   • user@(IP/Domain):/remote/path
     • Example: user@203.0.113.10:/mnt/recordings
7. Enable the checkbox "MP3 (Send MP3 copy)" if you also want to receive recordings in MP3 format. Note that this may generate additional costs and higher disk usage on the client's server.
8. Click "Save" to apply the changes.

Client Firewall Configurations

Enable access through the selected port to the server being published, preferably restricting access only to the IP addresses corresponding to the Wolkvox server(s) that will be sending the recordings. Example:

• port 2022 -> to internal IP 192.168.10.10

Client Server Configurations (Linux)

1. Create the desired user (Example: wolkvox).
2. Create/Select the storage directory (Example: /Recordings).
3. Assign write permissions to the directory for the created user (Example: wolkvox) at the owner or group level.
4. In the directory of the user to be synchronized, it is necessary to add the SSH public key shared by Wolkvox by editing the "authorized_keys" file using your preferred text editor (vim or nano) to allow connection between servers at the following path:
   1. Example: vim /home/wolkvox/.ssh/authorized_keys
   2. Example: nano /home/wolkvox/.ssh/authorized_keys

Validation Recommendations in Case of Issues

Important

The following validations are presented as general recommendations. Each client may have specific security configurations, NAS, or internal policies. Wolkvox does not directly manage or modify the client's infrastructure.

User in Chrooted Environment

Some servers use Chrooted environments to restrict SSH users.

What to Check:

• If the rsync user is limited by ChrootDirectory.
• If the path configured in Wolkvox Manager is relative to the chroot, not absolute.

Recommendation:

• Review the file: /etc/ssh/sshd_config
• Validate ChrootDirectory directives applied to the user or group.

Directory Permissions and Ownership

A common error is that the user does not have write permissions.

Recommended Validation:

• ls -ld /storage/path

Suggested Action:

• sudo chown wolkvox:wolkvox /storage/path
• sudo chmod 755 /storage/path

Review of SSH Service Logs

SSH logs usually clearly indicate the cause of the failure.

Common Locations:

• Debian / Ubuntu:
  • /var/log/auth.log
• CentOS / RHEL / Fedora:
  • /var/log/secure

Recommended Command:

• sudo journalctl -u sshd | grep rsync

Typical Messages to Review:

• Permission denied
• Invalid key
• Chrooted path error