According to Avaya the correct way to get Voicemail Pro wav files into Chronicall is with the built-in SFTP mechanism. With the release of IP Office 11 the Samba solution no longer works as a means to transfer the .wav files to the Chronicall Recording Library. The correct way to get recordings from Voicemail Pro into Chronicall is by setting up an SFTP server on the Recording Library machine and configuring Voicemail Pro to transfer the files over that connection.
Every major Linux distribution by default comes with OpenSSH which provides the needed SFTP functionality. This article explains how to configure OpenSSH and Voicemail Pro so that Chronicall Recording Library can access and process the recording files.
- Firstly, make a directory that outside sources can access. This folder can be anywhere! In our example, we made /home/xmadmin/VmProVRL and shared that folder by using chmod 777
- Then, ensure that the server has OpenSSH
- In our example below, the command we used was service sshd status to check and ensure it was running as intended.
- This service is commonly how PuTTY and other SSH/SFTP clients are able to connect. That being said - please don't stop this service)
- To ensure we can connect, run the sftp (target server user name)@(target server ip address). Reference the Screenshot below
- Here, we were connected to the Voicemail Pro Server and are connecting to the Chronicall server via SFTP. This is essential as we won't be able to perform the next step.
- Finally, we proceed to the Voicemail Pro Application. Here we will access the Administration option, Preferences, then General
- After that is done, we will configure the FTP to resemble the screenshot below. Here, we may need to input the full directory so that it resembles /home/xmadmin/VmProVRL
- Save your configuration and then test your connection! Note: you may need to restart the Voicemail Pro service for this configuration change to take effect.
- After this is done, make sure your monitored directory is looking at the previously mentioned location on the Chronicall server. If recordings are not processing, restarting the service ought to resolve that outright!