Maintenance Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
Remote Access for Cisco Unity 8.x
Downloads: This chapterpdf (PDF - 73.0KB) The complete bookPDF (PDF - 2.47MB) | Feedback

Remote Access for Cisco Unity 8.x

Table Of Contents

Remote Access for Cisco Unity 8.x

Accessing Cisco Unity 8.x Remotely

Using Remote Desktop with Cisco Unity 8.x

Using Windows Terminal Services with Cisco Unity 8.x

Windows Terminal Services Limitations

Using a Virtual Private Network with Cisco Unity 8.x


Remote Access for Cisco Unity 8.x


Accessing Cisco Unity 8.x Remotely

There are several methods that allow remote access to the Cisco Unity server so that you can do tasks—such as loading updates or patches, and transferring files—that otherwise would have to be done locally. Depending on your site, you can set up remote access to the Cisco Unity server as described in the following sections:

Using Remote Desktop with Cisco Unity 8.x

Using Windows Terminal Services with Cisco Unity 8.x

Using a Virtual Private Network with Cisco Unity 8.x

Using Remote Desktop with Cisco Unity 8.x

By default, Remote Desktop is disabled on the server. Do the following procedure if you will use Remote Desktop to install software on the server or to perform remote administration.


Caution When you configure Remote Desktop on the client computer, do not choose the option to bring sound to the client computer or all incoming calls will be immediately disconnected. Instead, on the Local Resources tab, in the Remote Computer Sound list, click Leave at Remote Computer.


Caution Do not close the Remote Desktop window without logging out of Windows on the Cisco Unity server, or you may encounter a variety of unpredictable behavior. If you just close the Remote Desktop window, the desktop heap memory that is used by Remote Desktop on the Cisco Unity server is not freed. When desktop heap memory is exhausted, system behavior becomes unpredictable. Problems may include, but are not limited to, Cisco Unity Administrator pages failing to display, Cisco Unity failing to start when you attempt to restart using the tray icon, and desktop-heap warnings and DCOM errors in the system event log. Problems are more likely if you have added the /3GB switch to the boot.ini file to configure the server for more than 96 voice-messaging ports because less desktop heap memory is available.


Caution When you use Remote Desktop to log on to the Cisco Unity server remotely, do not use the /console option, or all incoming calls will be immediately disconnected.


Caution Cisco Security Agent for Cisco Unity pop-up notifications only occur at Console 0, so if you are not physically at the Cisco Unity server or using VNC to access the server, you will not see any pop-up notifications. This can cause serious problems when modifying files or when installing any application other than Cisco Unity 8.x or later. (The Cisco Unity System Setup Assistant for Cisco Unity 8.x and later automatically stops and restarts Cisco Security Agent for Cisco Unity as required.) To install other software by using Remote Desktop, stop and disable Cisco Security Agent for Cisco Unity before starting the installation. Re-enable and restart the service after the installation and any required server restarts are complete.

To Enable Remote Desktop


Step 1 On the Windows Start menu, click Settings > Control Panel > System.

Step 2 In the System Properties control panel, click the Remote tab.

Step 3 Under Remote Desktop, click Enable Remote Desktop on This Computer.

Step 4 Click OK to close the message about using remote connections.

Step 5 Click OK to close the System Properties dialog box.


Using Windows Terminal Services with Cisco Unity 8.x


Caution Cisco Security Agent for Cisco Unity pop-up notifications only occur at Console 0, so if you are not physically at the Cisco Unity server or using VNC to access the server, you will not see any pop-up notifications. This can cause serious problems when modifying files or when installing any application other than Cisco Unity 8.x or later. (The Cisco Unity System Setup Assistant for Cisco Unity 8.x and later automatically stops and restarts Cisco Security Agent for Cisco Unity as required.) To install other software by using Windows Terminal Services, stop and disable Cisco Security Agent for Cisco Unity before starting the installation. Re-enable and restart the service after the installation and any required server restarts are complete.

Do the following procedures to set up and use WTS on your remote computer.

To find additional information about WTS, refer to the Help available from either the Terminal Services server program on the Cisco Unity server, or from the Terminal Services Client program that you install on the remote computer. You can also refer to the Microsoft website.

Note that in order to use the paste function in the Medial Master when you use WTS to access either the Cisco Unity Administrator or Cisco Personal Communications Assistant on a Cisco Unity server using Windows 2000, the WAV file that you paste must be in G.711 format.

To Create the Windows Terminal Client Install Disks

To use WTS on a remote computer, you must first create a set of install disks by using the WTS host program on the Cisco Unity server. You will need two blank disks—labeled "Disk 1" and "Disk 2"—to do this procedure.


Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Administrative Tools > Terminal Services Client Creator.

Step 2 In the Create Installation Disk(s) dialog box, do the following sub-steps:

a. Click Terminal Services for 32-bit x86 Windows.

b. Check the Format Disk(s) check box to erase any existing data on the disks, and then click OK.

Step 3 Follow the on-screen instructions to create the two install disks.

Step 4 Close the Create Installation Disk(s) dialog box.


To Set Up the WTS Client on a Remote Computer


Step 1 On the remote computer, insert Disk 1 in the A drive, and run Setup.exe.

Step 2 Follow the on-screen instructions to complete the installation.

Step 3 On the Windows Start menu, click Programs > Terminal Services Client > Client Connection Manager.

Step 4 In the Client Connection Manager window, click File > New Connection.

Step 5 Follow the on-screen instructions to complete the Connection wizard.


To Start a Remote Session with WTS

When you connect to the Cisco Unity server from a remote computer by using WTS, your computer controls the server. The Cisco Unity server screen appears within a window on your remote computer and, in general, you can access any of the server files and applications. We recommend that the Cisco Unity server host only one WTS connection at a time.


Step 1 On the remote computer, do one of the following:

In the Client Connection Manager window, double-click the new connection icon that was created in the "To Set Up the WTS Client on a Remote Computer" procedure.

On the Windows Start menu, click Programs > Terminal Services Client > <New connection icon>. If you changed the default location for the new connection icon, go to the location that you specified in the "To Set Up the WTS Client on a Remote Computer" procedure.

Step 2 Log on to the Cisco Unity Administrator with the applicable name and password.


To Do File Transfers


Step 1 On the remote computer, run \\<IP Address for Cisco Unity Server>\c$.

Step 2 Log on to the Cisco Unity Administrator with the applicable name and password.

Step 3 Transfer files by using either copy-and-paste or drag-and-drop Windows commands.


To End a Remote Session with Windows Terminal Services


Step 1 On the remote computer, exit the Cisco Unity Administrator.

Step 2 On the remote computer, log off of Windows.


Caution Do not close the WTS window without logging off of Windows, or you may encounter a variety of unpredictable behavior. If you just close the WTS window, the desktop heap memory that is used by WTS on the Cisco Unity server is not freed. When desktop heap memory is exhausted, system behavior becomes unpredictable. Problems may include, but are not limited to, Cisco Unity Administrator pages failing to display, Cisco Unity failing to start when you attempt to restart using the tray icon, and desktop-heap warnings and DCOM errors in the system event log. Problems are more likely if you have added the /3GB switch to the boot.ini file to configure the server for more than 96 voice-messaging ports because less desktop heap memory is available.

Windows Terminal Services Limitations

WTS is supported for accessing the Cisco Unity server remotely, with the limitations listed in the applicable version of Release Notes for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html. In the "Limitations and Restrictions" section, see "Windows Terminal Services." When accessing subscriber workstations remotely, WTS is not supported for use with Cisco Unity ViewMail for Microsoft Outlook.

Using a Virtual Private Network with Cisco Unity 8.x

A Virtual Private Network (VPN) is a private network that uses public phone lines (or in some cases a cable modem). Privacy is maintained through encryption and the use of secure protocols. When you use a VPN to access Cisco Unity through a firewall, you will be able to use Cisco Unity as if you were inside the network.

VPN is required in the following circumstances:

You need access to the Cisco Unity Administrator website (http://<Cisco Unity server name>/web/sa) from a remote computer outside your network firewall.

You need to use the Media Master control bar to record voice names and greetings by using Distributed Component Object Model (DCOM) to connect your remote computer to the Cisco Unity server through a firewall.


Note If you are not using VPN for remote access, refer to the Microsoft website for information on configuring DCOM through a firewall.


Discuss setting up a VPN with your LAN administrator.