Table Of Contents
Release Notes for Cisco Unity ViewMail for Microsoft Outlook Release 8.0(3)
Determining the ViewMail for Outlook Version
New and Changed Requirements and Support—Release 8.0(3)
Available Languages for ViewMail for Outlook
New and Changed Functionality—Release 8.0(3)
Media Master in ViewMail for Outlook Uses HTTPS Protocol to Communicate with Cisco Unity Server
Installation and Upgrade Information
Task List for Installing ViewMail for Outlook for the First Time
Task List for Upgrading to ViewMail for Outlook 8.0(3)
Considerations for Upgrading to ViewMail for Outlook 8.0(3)
Downloading ViewMail for Outlook 8.0(3)
Customizing the ViewMail for Outlook Software Before Installing It on Subscriber Workstations
Customizing ViewMail for Outlook to Use the G.729a Format for Recording Messages
Customizing ViewMail for Outlook for Secure Messaging
Customizing the TCP Port That ViewMail for Outlook Uses for RPC Connections for Secure Messaging
Installing ViewMail for Outlook 8.0(3)
Installing ViewMail for Outlook 8.0(3) from a Cisco Unity Disc or from a Network Drive
Authentium Command AntiVirus for Windows Is Not Supported
Some Software on Subscriber Workstations Can Cause ViewMail for Outlook to Fail
ViewMail for Outlook Form Will Not Load When Subscriber Has a Full Mailbox
Windows Terminal Services Is Not Supported
Yamaha Synthesizer Software Is Not Supported
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unity ViewMail for Microsoft Outlook Release 8.0(3)
Revised April 4, 2012 (Originally published February 2, 2010)These release notes contain information on downloading and installing software, new and changed requirements and support, new and changed functionality, limitations and restrictions, and caveats for Cisco Unity ViewMail for Microsoft Outlook Release 8.0(3).
The ViewMail for Outlook 8.0(3) files for all languages are available from the Cisco Download Software website. (The location is provided in the applicable procedure later in these release notes.)
The English-United States version of ViewMail for Outlook 8.0(3) is also available on Cisco Unity 8.0(3) DVD 1.
Contents
•
New and Changed Requirements and Support—Release 8.0(3)
•
New and Changed Functionality—Release 8.0(3)
•
Installation and Upgrade Information
•
Obtaining Documentation and Submitting a Service Request
Requirements
•
To install ViewMail for Outlook, you must have local administrator rights on the subscriber workstation.
•
The subscriber workstation must have at least 2.5 MB of hard-disk space available for ViewMail for Outlook in each language.
•
Outlook should not be running and virus-scanning services should be disabled on subscriber workstations when ViewMail is installed.
•
The ViewMail version must be supported with the version of Outlook that is installed and of the operating system. (See the applicable section in Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html, depending on the Cisco Unity version.)
Compatibility Information
•
For information on all qualified version combinations of ViewMail for Outlook, Cisco Unity with Exchange, and the software on subscriber workstations—as well as the support policy for software on subscriber workstations—see Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html.
•
For a list of all languages available for ViewMail for Outlook 8.0(3), see the "Available Languages for Cisco Unity Components" section of System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/8xcusysreq.html.
Determining the ViewMail for Outlook Version
There are two ways to determine the version of ViewMail in use on a subscriber workstation. Do either procedure, as applicable.
To Determine the ViewMail for Outlook Version in Use from Outlook
In the Outlook Inbox on the subscriber workstation, on the Help menu, click About ViewMail.
To Determine the ViewMail for Outlook Version in Use from Add/Remove Programs
Step 1
On the Windows Start menu on the subscriber workstation, click Settings > Control Panel > Add/Remove Programs.
Step 2
In the Currently Installed Programs list, find ViewMail for Outlook.
Related Documentation
For descriptions and URLs of Cisco Unity documentation on Cisco.com, see the Documentation Guide for Cisco Unity Release 8.x. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/documentation/guide/8xcudg.html.
New and Changed Requirements and Support—Release 8.0(3)
This section contains information about new and changed requirements and support in the 8.0(3) release time frame only.
(For information on new and changed requirements and support in earlier versions of Cisco Unity ViewMail for Microsoft Outlook, see the applicable release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.)
Microsoft Windows 7
The following versions of Microsoft Windows 7 are qualified for use with ViewMail for Outlook 8.0(3) on subscriber workstations:
•
Windows 7 Professional (32- and 64-bit)
•
Windows 7 Enterprise (32- and 64-bit)
•
Windows 7 Ultimate (32- and 64-bit)
Microsoft Windows 7 is not supported with any earlier versions of ViewMail for Outlook.
Available Languages for ViewMail for Outlook
No new languages were added with this release.
For a complete list of languages, see the "Available Languages for Cisco Unity Components" section of System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/8xcusysreq.html.
New and Changed Functionality—Release 8.0(3)
This section contains information about new and changed functionality in the 8.0(3) release time frame only.
(For information on new and changed requirements and support in earlier versions of Cisco Unity ViewMail for Microsoft Outlook, see the applicable release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.)
Media Master in ViewMail for Outlook Uses HTTPS Protocol to Communicate with Cisco Unity Server
The ViewMail for Outlook Media Master component can use either HTTP/HTTPS or DCOM as the communication protocol to send recordings and audio streams to and from Cisco Unity.
By default, the Media Master inViewMail uses HTTPS as the communication protocol. HTTPS is preferred because it is secure. HTTP/HTTPS is often more reliable when connecting through a firewall because it uses TCP ports that are typically already opened for administration access.
If the Cisco Unity server is not running Cisco Unity version 8.0 or if the server is not configured to use SSL, then the Media Master in ViewMail will automatically switch to using DCOM as the communication protocol.
If the Cisco Unity server is not configured to use SSL and you want to use HTTP as the communication protocol for TRAP connections, see the "Customizing the Communication Protocol That ViewMail for Outlook Uses to Communicate with Cisco Unity" section for information on how to configure the Media Master to use HTTP instead of HTTPS.
In earlier versions of Cisco Unity and ViewMail for Outlook, the Media Master always used DCOM as the communication protocol between ViewMail and the Cisco Unity server.
Installation and Upgrade Information
•
Task List for Installing ViewMail for Outlook for the First Time
•
Task List for Upgrading to ViewMail for Outlook 8.0(3)
•
Considerations for Upgrading to ViewMail for Outlook 8.0(3)
•
Downloading ViewMail for Outlook 8.0(3)
•
Customizing the ViewMail for Outlook Software Before Installing It on Subscriber Workstations
•
Installing ViewMail for Outlook 8.0(3)
Task List for Installing ViewMail for Outlook for the First Time
Do the following tasks in the order listed for a new ViewMail for Outlook installation.
1.
If applicable, download ViewMail from the Cisco Download Software website. See the "Downloading ViewMail for Outlook 8.0(3)" section.
2.
Customize the ViewMail software, as applicable, before installing it. See the "Customizing the ViewMail for Outlook Software Before Installing It on Subscriber Workstations" section.
The section contains information for the following customizations:
•
To use the G.729a format for recording messages.
•
To use ViewMail with the secure messaging feature.
•
To change the TCP port that ViewMail uses for RPC connections to Cisco Unity.
•
To change the communication protocol ViewMail uses to communicate with Cisco Unity.
CautionYou must customize the ViewMail software before you install it on subscriber workstations. Otherwise, you will have to make the changes manually or by using a configuration management tool.
3.
Install ViewMail. See the "Installing ViewMail for Outlook 8.0(3)" section.
Task List for Upgrading to ViewMail for Outlook 8.0(3)
Do the following tasks in the order listed to upgrade an earlier ViewMail for Outlook version to 8.0(3).
1.
Review the "Considerations for Upgrading to ViewMail for Outlook 8.0(3)" section, and do the procedure(s) to uninstall version 3.x, if applicable.
2.
Download ViewMail from the Cisco Download Software website. See the "Downloading ViewMail for Outlook 8.0(3)" section.
3.
Customize the ViewMail software, as applicable, before installing it. See the "Customizing the ViewMail for Outlook Software Before Installing It on Subscriber Workstations" section.
The section contains information for the following customizations:
•
To use the G.729a format for recording messages.
•
To use ViewMail with the secure messaging feature.
•
To change the TCP port that ViewMail uses for RPC connections to Cisco Unity.
•
To change the communication protocol ViewMail uses to communicate with Cisco Unity.
CautionYou must customize the ViewMail software before you install it on subscriber workstations. Otherwise, you will have to make the changes manually or by using a configuration management tool.
4.
Install ViewMail. See the "Installing ViewMail for Outlook 8.0(3)" section.
Considerations for Upgrading to ViewMail for Outlook 8.0(3)
Subscribers are not required to have special class-of-service (COS) privileges or passwords to use ViewMail for Outlook version 8.x. Any Cisco Unity Unified Messaging subscriber who has ViewMail installed can use it.
Note that it is not necessary to uninstall ViewMail for Outlook version 7.x, 5.x, or 4.x before upgrading to version 8.0(3). The ViewMail 8.0(3) installation process automatically removes any ViewMail 7.x, 5.x, or 4.x versions.
If you encounter a problem with the ViewMail 7.x, 5.x, or 4.x removal, see the section on manually uninstalling ViewMail in the tech note Cisco Unity VMO Is Installed But Not Published in Outlook at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html, in the "Troubleshooting Desktop Applications: VMO and VMI" topic. Although the tech note says it applies to ViewMail versions 3.0(1) and 4.0(1), the procedure for uninstalling ViewMail also applies to ViewMail versions 8.x, 7.x, 5.x and 4.x.
Downloading ViewMail for Outlook 8.0(3)
Revised 04 April, 2012Do the following procedure to download the software from the Cisco Download Software website.
To Download ViewMail for Outlook 8.0(3)
Step 1
Confirm that the computer you are using has the required minimum hard-disk space available for the extracted files, in addition to the space required to download the file (the download file size appears on the download page):
For English-United States file only4 MB plus download file size
For file that contains all other languages110 MB plus download file size
Step 2
On a computer with a high-speed Internet connection, go to the Cisco Unified Communications Applications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=280384298.
Note
To access the software download page, you must be logged on to Cisco.com as a registered user.
Step 3
In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity, and click Cisco Unity ViewMail for Microsoft Outlook Version 8.0.
Step 4
Download the file CiscoUnity.VMO8.0.3.exe to the directory of your choice.
Step 5
Double-click CiscoUnity.VMO8.0.3.exe, and follow the on-screen prompts to extract the files to the directory of your choice on a network drive (or to a writeable compact disc, for copying to the network at a later time).
The executable extracts the files to a CiscoUnity.VMO8.0.3 directory that it creates within your chosen directory.
Step 6
Delete the file CiscoUnity.VMO8.0.3.exe to free hard-disk space.
Customizing the ViewMail for Outlook Software Before Installing It on Subscriber Workstations
CautionYou must customize the ViewMail for Outlook software before you install it on subscriber workstations. Otherwise, you will have to make the changes manually or by using a configuration management tool. Note that for some upgrades, the applicable registry setting cannot be changed by running the ViewMail installation program again; you must use a configuration management tool instead.
See the applicable section(s) to customize theViewMail software for your installation:
•
Customizing ViewMail for Outlook to Use the G.729a Format for Recording Messages
•
Customizing ViewMail for Outlook for Secure Messaging
•
Customizing the TCP Port That ViewMail for Outlook Uses for RPC Connections for Secure Messaging
Customizing ViewMail for Outlook to Use the G.729a Format for Recording Messages
Cisco Unity ViewMail for Microsoft Outlook supports either the G.711 or G.729a codec format for recording messages by using a computer microphone or by using the Paste from File command from the Media Master. By default, messages are saved in the G.711 format.
ViewMail installs the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\Default Wave Format. By default, the registry key is set to use the G.711 format for recording messages. To enable use of the G.729 format, administrators must customize the ViewMail.msi file to change the value of the registry key before installing ViewMail on subscriber workstations.
CautionIf ViewMail version 4.2(2) or later is already installed on a subscriber workstation, the registry setting cannot be changed by running the ViewMail installation program again. Administrators must use a configuration management tool (for example, Microsoft Systems Management Server) to change the registry setting, or must uninstall ViewMail, customize the ViewMail.msi file to change the setting, and install the customized software.
To Customize ViewMail for Outlook to Use the G.729a Format for Recording Messages
Step 1
Browse to the ViewMail directory on the network drive to which you copied or downloaded the ViewMail files. If you do not have rights to write to the directory, move the files to a directory that allows you to do so.
Step 2
In the ViewMail directory, browse to the ENU language directory (or to the language applicable to your installation).
Step 3
Open the file VMOInit.vbs in a text editor (for example, Notepad).
Step 4
Delete the rem that begins the Session.Property("DefaultWaveFormat") = "5" line, so that the line looks like the following example:
Function VMOInitFn()rem Session.Property("EXTENSION") = ""rem Session.Property("UNITYSERVER") = ""rem To enable NoTextToVM, set property NOTEXTTOVM to 1rem Session.Property("NOTEXTTOVM") = "1"rem To enable g729a recording, set property DefaultWaveFormat to 5Session.Property("DefaultWaveFormat") = "5"rem To enable secure messaging, set property ForceMessagesSecure to 1 (Always Force Messages Secure) or 2 (Allow User To Choose).rem By default, it is set to 0 (Always Send Messages Unsecure).rem Session.Property("ForceMessagesSecure") = "1"rem To change RPC Port Number for Encryption and Decryption, set property RpcPortNumberForEncryptionAndDecryption to a new port number.rem By default, it is set to 5050.rem Session.Property("RpcPortNumberForEncryptionAndDecryption") = "5050"rem To change TrapConnectionType (0=AUTO, 1=VMWS, 2=DCOM), set property 'TrapConnectionType' to the selection. By default, it is set to Auto.rem Session.Property("TrapConnectionType") = "0"rem To change HTTP Connection Type (0=HTTPS, 1=HTTP) for VMWS, set property 'HTTPConnectionType' to the selection. By default, it is set to HTTPS.rem Session.Property("HTTPConnectionType") = "0"rem To set HTTPS Ignore Cert Error(0=FALSE, 1=TRUE) for VMWS, set property 'HTTPSIgnoreCertErrors' to the selection. By default, it is set to TRUE.rem Session.Property("HTTPSIgnoreCertErrors") = "1"End FunctionStep 5
Save the script file and close the text editor.
Step 6
Open a Command Prompt window. (On the Windows Start menu, click Programs > Accessories > Command Prompt.)
Step 7
Change to the ViewMail > ENU directory (or to the language applicable to your installation).
Step 8
Enter vmaddbin ViewMail.msi VMOInit.vbs, and press Enter. (When the script completes, your cursor returns to the command line.
Step 9
Run the file ViewMail.msi on a test machine to confirm that the installation completes successfully. (If the installation is unsuccessful, verify the changes made to VMOInit.vbs.)
Step 10
Close the Command Prompt window.
Customizing ViewMail for Outlook for Secure Messaging
When the Cisco Unity system is configured to use the secure messaging feature, ViewMail for Outlook can play and send secure messages only when a connection can be made to the Cisco Unity server. ViewMail installs the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\Force Messages Secure on subscriber workstations.
When a subscriber attempts to send a secure message by using ViewMail while using Outlook in offline mode—or if ViewMail cannot communicate with the Cisco Unity server for any other reason—ViewMail takes one of the following actions, depending on the value of the registry key:
•
0—Sends the message without encrypting it and without attempting to connect to the Cisco Unity server.
•
1—Warns the subscriber that a connection with Cisco Unity could not be made. (The subscriber will have to save the message and resend it at a later time.)
•
2—Warns the subscriber that the message will not be encrypted, and offers the option to send it without encryption.
The registry key is set to zero by default. To send encrypted messages from ViewMail, administrators must customize the ViewMail.msi file to change the value of the registry key before installing ViewMail on subscriber workstations.
CautionIf ViewMail version 5.0(1) or later is already installed on a subscriber workstation, the registry setting cannot be changed by running the ViewMail installation program again. Administrators must use a configuration management tool (for example, Microsoft Systems Management Server) to change the registry setting, or must uninstall ViewMail, customize the ViewMail.msi file to change the setting, and install the customized software.
To Customize ViewMail for Outlook for Secure Messaging
Step 1
Browse to the ViewMail directory on the network drive to which you copied or downloaded the ViewMail files. If you do not have permission to write to the directory, move the files to a directory on which you have write privileges.
Step 2
In the ViewMail directory, browse to the ENU language directory (or to the language applicable to your installation).
Step 3
Open VMOInit.vbs in a text editor.
Step 4
Delete the rem that begins the Session.Property("ForceMessagesSecure") = "1" line, so that the line looks like the following example:
Function VMOInitFn()rem Session.Property("EXTENSION") = ""rem Session.Property("UNITYSERVER") = ""rem To enable NoTextToVM, set property NOTEXTTOVM to 1rem Session.Property("NOTEXTTOVM") = "1"rem To enable g729a recording, set property DefaultWaveFormat to 5rem Session.Property("DefaultWaveFormat") = "5"rem To enable secure messaging, set property ForceMessagesSecure to 1 (Always Force Messages Secure) or 2 (Allow User To Choose).rem By default, it is set to 0 (Always Send Messages Unsecure).Session.Property("ForceMessagesSecure") = "1"rem To change RPC Port Number for Encryption and Decryption, set property RpcPortNumberForEncryptionAndDecryption to a new port number.rem By default, it is set to 5050.Session.Property("RpcPortNumberForEncryptionAndDecryption") = "5050"rem To change TrapConnectionType (0=AUTO, 1=VMWS, 2=DCOM), set property 'TrapConnectionType' to the selection. By default, it is set to Auto.rem Session.Property("TrapConnectionType") = "0"rem To change HTTP Connection Type (0=HTTPS, 1=HTTP) for VMWS, set property 'HTTPConnectionType' to the selection. By default, it is set to HTTPS.rem Session.Property("HTTPConnectionType") = "0"rem To set HTTPS Ignore Cert Error(0=FALSE, 1=TRUE) for VMWS, set property 'HTTPSIgnoreCertErrors' to the selection. By default, it is set to TRUE.rem Session.Property("HTTPSIgnoreCertErrors") = "1"End FunctionStep 5
If you want subscribers to be able to choose to send unencrypted messages when Outlook is in offline mode, change the "1" to "2".
Step 6
Save the script file and close the text editor.
Step 7
Open a Command Prompt window. (On the Windows Start menu, click Programs > Accessories > Command Prompt.)
Step 8
Change to the ViewMail > ENU directory (or to the language applicable to your installation).
Step 9
Enter vmaddbin ViewMail.msi VMOInit.vbs, and press Enter. (When the script completes, your cursor returns to the command line.
Step 10
Run the file ViewMail.msi on a test machine to confirm that the installation completes successfully. (If the installation is unsuccessful, verify the changes made to VMOInit.vbs.)
Step 11
Close the Command Prompt window.
Customizing the TCP Port That ViewMail for Outlook Uses for RPC Connections for Secure Messaging
When the Cisco Unity system is configured to use the secure messaging feature, and when ViewMail for Outlook is using DCOM to communicate with Cisco Unity, Cisco Unity uses TCP port number 5050 for incoming RPC connection requests from ViewMail clients to encrypt and decrypt secure messages. In most cases, the default configuration is fine. However, you may want to change the port to configure for a firewall; any available TCP port can be used.
To change the port that is used, you must make the change on the Cisco Unity server first and then in the ViewMail.msi file.
For information on configuring the Cisco Unity server, see the "Customizing the TCP Port That ViewMail for Outlook Uses For Encrypting and Decrypting Messages" section in the "Securing Subscriber Messages in Cisco Unity 8.x" chapter of the Security Guide for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.
ViewMail installs the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\RPC Port Number for Encryption and Decryption on subscriber workstations.
CautionIf ViewMail version 5.0(1) or later is already installed on a subscriber workstation, the registry setting cannot be changed by running the ViewMail installation program again. Administrators must use a configuration management tool (for example, Microsoft Systems Management Server) to change the registry setting, or must uninstall ViewMail, customize the ViewMail.msi file to change the setting, and install the customized software.
To Customize the TCP Port That ViewMail for Outlook Uses for RPC Connections for Secure Messaging
Step 1
Browse to the ViewMail directory on the network drive to which you copied or downloaded the ViewMail files. If you do not have permission to write to the directory, move the files to a directory on which you have write privileges.
Step 2
In the ViewMail directory, browse to the ENU language directory (or to the language applicable to your installation).
Step 3
Open the file VMOInit.vbs in a text editor.
Step 4
Delete the rem that begins the Session.Property ("RpcPortNumberForEncryptionAndDecryption") = "5050" line, so that the line looks like the following example:
Function VMOInitFn()rem Session.Property("EXTENSION") = ""rem Session.Property("UNITYSERVER") = ""rem To enable NoTextToVM, set property NOTEXTTOVM to 1rem Session.Property("NOTEXTTOVM") = "1"rem To enable g729a recording, set property DefaultWaveFormat to 5rem Session.Property("DefaultWaveFormat") = "5"rem To enable secure messaging, set property ForceMessagesSecure to 1 (Always Force Messages Secure) or 2 (Allow User To Choose).rem By default, it is set to 0 (Always Send Messages Unsecure).rem Session.Property("ForceMessagesSecure") = "1"rem To change RPC Port Number for Encryption and Decryption, set property RpcPortNumberForEncryptionAndDecryption to a new port number.rem By default, it is set to 5050.Session.Property("RpcPortNumberForEncryptionAndDecryption") = "5050"rem To change TrapConnectionType (0=AUTO, 1=VMWS, 2=DCOM), set property 'TrapConnectionType' to the selection. By default, it is set to Auto.rem Session.Property("TrapConnectionType") = "0"rem To change HTTP Connection Type (0=HTTPS, 1=HTTP) for VMWS, set property 'HTTPConnectionType' to the selection. By default, it is set to HTTPS.rem Session.Property("HTTPConnectionType") = "0"rem To set HTTPS Ignore Cert Error(0=FALSE, 1=TRUE) for VMWS, set property 'HTTPSIgnoreCertErrors' to the selection. By default, it is set to TRUE.rem Session.Property("HTTPSIgnoreCertErrors") = "1"End FunctionStep 5
Change the "5050" to the TCP port number that you set on the Cisco Unity server.
Step 6
Save the script file and close the text editor.
Step 7
Open a Command Prompt window. (On the Windows Start menu, click Programs > Accessories > Command Prompt.)
Step 8
Change to the ViewMail > ENU directory (or to the language applicable to your installation).
Step 9
Enter vmaddbin ViewMail.msi VMOInit.vbs, and press Enter. When the script completes, your cursor returns to the command line.
Step 10
Run the file ViewMail.msi on a test machine to confirm that the installation completes successfully. (If the installation is unsuccessful, verify the changes made to VMOInit.vbs.)
Step 11
Close the Command Prompt window.
Customizing the Communication Protocol That ViewMail for Outlook Uses to Communicate with Cisco Unity
Cisco Unity ViewMail for Microsoft Outlook version 8.0(3) uses HTTPS as the default communication protocol for the Media Master component to send recordings and audio streams to and from Cisco Unity. If the Cisco Unity server is not running version 8.0.(3) or the server is not configured to use SSL, then the Media Master in ViewMail will automatically switch to using DCOM as the communication protocol.
There are three Windows registry keys available to customize the communication protocol ViewMail uses:
Trap Connection Type
When a subscriber uses the Media Master component to play or record messages, ViewMail uses either HTTP/HTTPS or DCOM to communicate with the Cisco Unity server, depending on the value of the Trap Connection Type registry key:
•
0—ViewMail will automatically determine the communication protocol based on the Cisco Unity server it is connecting to. It attempts HTTP/HTTPS first and will switch to DCOM if necessary. This is the default setting.
•
1—ViewMail will attempt to use only HTTP/HTTPS as the communication protocol, regardless of how the Cisco Unity server is configured.
•
2—ViewMail will attempt to use only DCOM as the communication protocol, regardless of how the Cisco Unity server is configured.
HTTP Connection Type
When ViewMail is using HTTP/HTTPS to communicate with the Cisco Unity server, whether ViewMail uses HTTP or HTTPS depends on the value of the HTTP Connection Type registry key:
•
0—ViewMail will use only HTTPS as the communication protocol, regardless of how the Cisco Unity server is configured. This is the default setting.
•
1—ViewMail will attempt to use only HTTP as the communication protocol, regardless of how the Cisco Unity server is configured.
Ignore Cert Errors
This registry key applies when HTTPS is configured as the communication protocol between ViewMail and the Cisco Unity server. During the installation of the Cisco Unity server, if you use the self-signed certificate to provide an SSL (HTTPS) connection to ViewMail, the Media Master will encounter certificate authenticity warning errors due to the self-signed certificate. How the Media Master handles the certificate errors depends on the value of the Ignore Cert Errors registry key:
•
0—ViewMail will not ignore certificate errors. The user will not be able to play or record secure messages or use the telephone to record and play messages in ViewMail.
•
1—ViewMail will ignore certificate errors, allowing ViewMail to accept self signed certificates. This is the default setting.
CautionIf ViewMail version 8.0(3) or later is already installed on a subscriber workstation, the registry settings cannot be changed by running the ViewMail installation program again. Administrators must use a configuration management tool (for example, Microsoft Systems Management Server) to change the registry setting, or must uninstall ViewMail, customize the ViewMail.msi file to change the setting, and install the customized software.
To Customize the Communication Protocol That ViewMail for Outlook Uses to Communicate with Cisco Unity
Step 1
Browse to the ViewMail directory on the network drive to which you copied or downloaded the ViewMail files. If you do not have permission to write to the directory, move the files to a directory on which you have write privileges.
Step 2
In the ViewMail directory, browse to the ENU language directory (or to the language applicable to your installation).
Step 3
Open VMOInit.vbs in a text editor.
Step 4
If you want to always use DCOM or always use HTTP/HTTPS as the as the communication protocol, do the following:
a.
Delete the rem that begins the Session.Property("TrapConnectionType") = "0" line so that the line looks like the example in Step 6.
b.
To always use HTTP/HTTPS as the as the communication protocol, change the "0" to "1". To always use DCOM as the as the communication protocol, change the "0" to "2".
Step 5
If your Cisco Unity server is not configured to use SSL and you wish to use HTTP as the as the communication protocol, do the following:
a.
Delete the rem that begins the Session.Property("HTTPConnectionType") = "0" line so that the line looks like the example in Step 6.
b.
To use HTTP as the as the communication protocol, change the "0" to "1".
This registry key applies only when the TrapConnectionType is set to 0 or 1.
Step 6
If your Cisco Unity server is configured to use SSL and you do not want to ignore certificate errors, do the following:
a.
Delete the rem that begins the Session.Property("HTTPSIgnoreCertErrors") = "1" line so that the line looks like the example below.
b.
If you do not want to ignore certificate errors, change the "1" to "0".
This registry key applies only when the TrapConnectionType is set to 0 or 1 and the HTTPConnectionType is set to 0.
The following example shows the rem deleted from Session.Property lines for each of these three settings:
Function VMOInitFn()rem Session.Property("EXTENSION") = ""rem Session.Property("UNITYSERVER") = ""rem To enable NoTextToVM, set property NOTEXTTOVM to 1rem Session.Property("NOTEXTTOVM") = "1"rem To enable g729a recording, set property DefaultWaveFormat to 5rem Session.Property("DefaultWaveFormat") = "5"rem To enable secure messaging, set property ForceMessagesSecure to 1 (Always Force Messages Secure) or 2 (Allow User To Choose).rem By default, it is set to 0 (Always Send Messages Unsecure).Session.Property("ForceMessagesSecure") = "1"rem To change RPC Port Number for Encryption and Decryption, set property RpcPortNumberForEncryptionAndDecryption to a new port number.rem By default, it is set to 5050.rem Session.Property("RpcPortNumberForEncryptionAndDecryption") = "5050"rem To change TrapConnectionType (0=AUTO, 1=VMWS, 2=DCOM), set property 'TrapConnectionType' to the selection. By default, it is set to Auto.Session.Property("TrapConnectionType") = "0"rem To change HTTP Connection Type (0=HTTPS, 1=HTTP) for VMWS, set property 'HTTPConnectionType' to the selection. By default, it is set to HTTPS.Session.Property("HTTPConnectionType") = "0"rem To set HTTPS Ignore Cert Error(0=FALSE, 1=TRUE) for VMWS, set property 'HTTPSIgnoreCertErrors' to the selection. By default, it is set to TRUE.Session.Property("HTTPSIgnoreCertErrors") = "1"End FunctionStep 7
Save the script file and close the text editor.
Step 8
Open a Command Prompt window. (On the Windows Start menu, click Programs > Accessories > Command Prompt.)
Step 9
Change to the ViewMail > ENU directory (or to the language applicable to your installation).
Step 10
Enter vmaddbin ViewMail.msi VMOInit.vbs, and press Enter. (When the script completes, your cursor returns to the command line.
Step 11
Run the file ViewMail.msi on a test machine to confirm that the installation completes successfully. (If the installation is unsuccessful, verify the changes made to VMOInit.vbs.)
Step 12
Close the Command Prompt window.
Installing ViewMail for Outlook 8.0(3)
ViewMail for Outlook can be installed on subscriber workstations throughout your organization in a number of ways. Installation and deployment methods include:
•
Installing ViewMail from a disc or a network drive. See the "Installing ViewMail for Outlook 8.0(3) from a Cisco Unity Disc or from a Network Drive" section. Alternatively, consider providing subscribers with network access to the ViewMail setup application and a procedure so that they can install ViewMail themselves.
•
Using a software publishing tool—such as Microsoft IntelliMirror or Microsoft Systems Management Server (SMS)—to deploy ViewMail to multiple subscriber workstations at one time. For information on using either of the tools, refer to the Microsoft website.
If you use IntelliMirror, deploy ViewMail by assigning or publishing it to a computer, rather than to an individual user. You can also use IntelliMirror or SMS for future upgrades of ViewMail.
•
Deploying ViewMail with Microsoft Office, as part of the Office 2003 or Office XP suites.
CautionWhen installing a new version of Microsoft Outlook on subscriber workstations, you must first uninstall ViewMail. After you have installed Outlook, reinstall ViewMail. Otherwise, ViewMail will seem to be installed properly with the new version of Outlook, but it will not work.
By default, ViewMail for Outlook files are installed in the directory C:\Program Files\ViewMail. You can specify a different directory during a first-time installation of ViewMail. If you are upgrading from a 7.x, 5.x or 4.x version of ViewMail, version 8.0(3) installs in the same directory that was used for the earlier version.
ViewMail installs and uses the following files and registry keys:
Files
•
AvResLoaderSvrSL.dll
•
AvResSvr.dll
•
AvTrapConnectionHolderSvr.dll
•
AvTsmSL.dll
•
AvVox.acm
•
AvWavSL.dll
•
SL_g729a.acm
Depending on the Windows version, the files are installed in one of three directories: C:\Windows\System, C:\Winnt\System32, C:\Windows\System32, or C:\Windows\SysWOW64.
Registry Keys
•
HKEY_CURRENT_USER\Software\Cisco Systems\Cisco Unity\Media Master\Profiles
•
HKEY_CURRENT_USER\Software\Cisco Systems\Cisco Unity\Media Master\Profiles\default
•
HKEY_CURRENT_USER\Software\Cisco Systems\Cisco Unity\VMO\Options
•
HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice
•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
Default Wave Format (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\Default Wave Format)•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
Force Messages Secure (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\Force Messages Secure)•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
NoTextToVM (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\NoTextToVM•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
RPC Port Number for Encryption and Decryption (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\RPC Port Number for Encryption and Decryption•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
Trap Connection Type (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\Trap Connection Type)•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
HTTP Connection Type (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\HTTP Connection Type)•
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Unity\VMO\
Ignore Cert Errors (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\
Cisco Unity\VMO\Ignore Cert Errors)•
HKEY_CURRENT_USER\Software\Cisco Systems\Cisco Unity\VMO\
Profiles\<subscriber 1 alias>•
HKEY_CURRENT_USER\Software\Cisco Systems\Cisco Unity\VMO\
Profiles\<subscriber 2 alias>•
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\
Extensions\ViewMail Extensions (on 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\
Exchange\Client\Extensions\ViewMail Extensions)Installing ViewMail for Outlook 8.0(3) from a Cisco Unity Disc or from a Network Drive
Do the procedure in this section to install ViewMail for Outlook on subscriber workstations from a Cisco Unity disc or from a network drive. You can also install ViewMail for multiple subscribers who share a workstation.
To Install ViewMail for Outlook 8.0(3) from a Cisco Unity Disc or from a Network Drive
Step 1
Confirm that ViewMail requirements have been met. See the "Requirements" section.
Step 2
Browse to the ViewMail directory on Cisco Unity 8.0(3) DVD 1 or on the network drive where you copied or downloaded the ViewMail files.
Step 3
In the ViewMail directory, browse to the applicable language folder. (The ViewMail directory contains a separate folder for each supported language of ViewMail.)
Step 4
Double-click the ViewMail.msi file.
Step 5
Follow the on-screen prompts to complete the installation.
Limitations and Restrictions
Authentium Command AntiVirus for Windows Is Not Supported
Authentium Command AntiVirus for Microsoft Windows is not supported on Cisco Unity subscriber workstations.
Some Software on Subscriber Workstations Can Cause ViewMail for Outlook to Fail
Some security and VPN software installed on subscriber workstations can cause ViewMail for Outlook to fail when subscribers use the phone as the playback device for the Media Master. In particular, software that offers personal firewalls is problematic.
Disable or remove security and VPN software from subscriber workstations. Alternatively, you can set up the Media Master so subscribers can play messages in ViewMail with computer speakers.
ViewMail for Outlook Form Will Not Load When Subscriber Has a Full Mailbox
When a subscriber mailbox reaches the Prohibit Send and Receive limit, ViewMail will not load when the subscriber starts Outlook. The ViewMail form cannot be published until the mailbox size is reduced.
Windows Terminal Services Is Not Supported
Windows Terminal Services (WTS) is not supported for use on subscriber workstations with ViewMail.
Yamaha Synthesizer Software Is Not Supported
Yamaha sound synthesizer software is not supported on Cisco Unity subscriber workstations with ViewMail.
Caveats
You can find the latest caveat information for Cisco Unity ViewMail for Microsoft Outlook version 8.0(3) by using Bug Toolkit, an online tool available for customers to query defects according to their own needs.
Bug Toolkit is available at http://www.cisco.com/go/bugs. Fill in your query parameters by using the custom settings in the Advanced Settings option.
Note
To access Bug Toolkit, you must be signed in to Cisco.com as a registered user.
Release notes for all versions of ViewMail for Outlook are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.

