The Backup Server for Cisco Unified Communications Manager (CUCM), formerly known as Cisco CallManager (CCM), has the ability to back up files to a server using the SFTP protocol. VShell provides secure file transfer capabilities, rock solid, reliable performance. This makes VShell for Windows a popular choice as the destination server for CUCM.
Please note: If using CUCM v9.x or later, VShell Workgroup or Enterprise editions may be required to accommodate the number of concurrent connections made by CUCM. It is also recommended that Disconnect idle sessions after ## minutes be enabled in the Common category of VShell's control panel.
The following table provides the information that will be used within CUCM and VShell as the example scenario is created.
|Server Hostname or IP Address||vshellserver.mydomain.com
(TCP/IP hostname or IP address of the Windows machine running VShell)
|Microsoft Windows Machine Name||VSHELLSERVER
This is the name of the machine as it appears in a Microsoft network (a Workgroup or Domain). This name may be different than the TCP/IP hostname.
This is the username that will be used to log into VShell. This is a username (a user) that is created in Microsoft Windows.
This is the file path on the server where files will be stored.
This is the name of the folder that CUCM will see, rather than the full name and path of the destination folder on the server.
In VShell versions 4.5 and later, the VShell Windows installer includes a wizard that makes configuration of VShell for CUCM even easier.
While running the installer, simply choose the CUCM option on the VShell Usage Scenario page.After installation is complete, the VShell CUCM Configuration Wizard will guide you through the configuration process.
You will be prompted for the username and password of the account that will upload files from CUCM to VShell. You will also be prompted for the location on the VShell server for CUCM files to be uploaded. During configuration, the wizard logs all changes it makes to a log file, for which you can specify the name and location.
If needed, the VShell CUCM Configuration Wizard can also be run from the command line after VShell is installed. From the VShell installation directory, run:
Alternatively, the configuration can be done manually using the VShell Control Panel, by following the instructions provided in the section on Configuring VShell versions 4.4 and earlier.
In VShell versions 4.4 and earlier, the VShell Control Panel is used to configure the VShell SFTP server to receive backups from CUCM. The following steps show how to configure the VShell server so that the CUCM backup software SFTP client will be placed in the intended directory, lock the server down so that the SFTP client will only see its virtual root directory, not other users' virtual root directories, and lock down the Access Control category to provide only Logon and SFTP access:
The following steps are listed on Cisco's website to configure CUCM for SFTP network backup:
The following Cisco Unified Communications Manager Backup Server configuration window shows the client settings that would be used to connect to the VShell server with settings shown above.
The following troubleshooting tips will help discover the cause of any problems encountered when the connection is tested. Before diagnosing problems, always enable Debug messages in the VShell control panel's Logging category.
Cisco's Unified CallManager also provides an interface named Cisco Unified Operating System Administration. Cisco Unified Operating System Administration provides an Install/Upgrade option which may interact with VShell for Windows through SFTP. The Cisco Unified Operating System Administration tool connects to an SFTP server and performs a directory listing. It currently requires that the SFTP server it connects to report the directory listing in a "Unix" format. The Unix format is not the format proposed in the SFTP draft standard, but it is required by the client. In order to accommodate the Cisco Unified Operating System Administration Install/Upgrade client, the VShell administrator must make the following registry change.
Note: The VShell control panel must be closed before registry changes.
Here you can control cookies using the checkboxes below. Some cookies are essential for the use of our website and cannot be disabled. Others provide a convenience to the user and, if disabled, may reduce the ease of use of our site. Finally, some cookies provide anonymous analytic tracking data that help us provide the user with a richer browsing experience. You can elect to disable these cookies as well.