Recording Library Setup - SFTP Setup on Recording Library (Linux to CentOS 7)

Use the following setup instructions to install vsftpd on a Linux machine running Recording Library.  Utilizing vsftpd will allow you to push recordings from a Voicemail Pro UCM module or Avaya Application server using SFTP in lue of NFS or Samba shares.  Do all below steps as a root user.

If you are offloading recordings from a Voicemail Pro on Linux to another Windows server with Recording Library, follow our article that reviews the Linux to Windows setup.

Step 1) Install FTP server

On the Recording Library server, install the vsftpd package.

# yum install vsftpd

After the service is installed, it must be started and enabled as it will be disabled by default.

# systemctl start vsftpd

# systemctl enable vsftpd

The firewall then must be told to allow traffic through in order for the VM Pro to send recordings to the server.

# firewall-cmd --zone=public --permanent --add-port=21/tcp

# firewall-cmd --zone=public --permanent --add-service=ftp

# firewall-cmd --reload

Step 2) Configure FTP

First we need to make a backup of the configuration file.

# cp /etc/vsftpd/vsftpd.conf /etc/vsftpd/vsftpd.conf.orig

Then the configuration file needs to be edited.

# nano /etc/vsftpd/vsftpd.conf

Change the below values to match.  If the values do not exist, add at the bottom of the file.















local_root=/var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp



Write out the configuration file and exit Nano.  We know need to create the folder for the VM Pro to send the recordings to and secure the connection.  

# mkdir /var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp

# semanage boolean -m ftpd_full_access --on

# systemctl restart vsftpd

Step 3) Create FTP User and Path

The FTP protocol needs to have a user assigned to it and that user needs to have a home path.  This will be the user and path that the VM Pro will send the recordings to using SFTP.

# useradd -m -c "VRL User" -s /bin/bash vrl

# passwd vrl

Then enter a password and record it for future reference

# echo "vrl" | tee -a /etc/vsftpd.userlist

# usermod -d /var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp vrl

# chown vrl:vrl /var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp

# chmod 777 /var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp

# systemctl restart vsftpd

Step 4) Configure VM Pro

Launch Avaya's Voicemail Pro application. Expand the Application drop down menu, hover over Preferences, and select General. 


Go to the Voicemail Recording tab within the System Preferences window that appears. Here you will need to enter in the created user account (vrl), it's password, the VRL directory that we created (/var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp), and the IP address of the Linux server running the Recording Library. The Test Connection button should be successful as we've already tested the connection from the Linux terminal. An example of these settings is below.

Again, if you experience trouble connecting, review the previous steps on this guide. Ensure the vsftpd service is started, ensure that the user password is correct, etc.

Now that the settings are entered, press OK. The go to the File drop down and press Save and Make Live. You should start to see recordings moving from the VM Pro Linux VRL storage location to the new Recording Library Linux vrlftp directory.

Step 3) Configure the Recording Library Settings

The last step is the simplest. Open Chronicall, go to System Settings, expand the Recording Libraries section, and go to the Recording Library settings. Update the Monitored Recording Directory field to the file path of where the recordings are being stored. In the example used within this article, that would be /var/lib/Xima\ Software/Chronicall/recording\ library/vrlftp. The press OK and save the Chronicall settings.  Then go back to the Recording Library terminal and restart the Recording Library service (# systemctl restart recording_library)

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request
Powered by Zendesk