ViewMail for Microsoft Outlook Functionality Additions Through Releases

Introduction

This document describes feature changes that were implemented in previous versions of ViewMail for Microsoft Outlook (VMO) but are still possible in the latest releases of VMO. New and changed functionality for VMO is described in the release notes whent it is first introduced. However, these changes do not propagate to the new versions of VMO release note documentation. It is sometime difficult to find information on previous feature changes. The goal of this document is to provide a summary of changes in one location.

VMO Release 8.6(4) New Functionality

Support For Reply With Text Only with VMO

In VMO Release 8.5(7) and earlier, the Reply With Text Only feature for voice messages is not supported. With VMO Release 8.6(4) and later, the Reply With Text Only feature for voice messages is supported. VMO considers the Reply With Text Only as a normal email and sends it to the respective recipient.

Note: The Reply With Text Only feature with VMO does not work with secure messages.

In order to enable a text-only reply for VMO, you must complete these steps:

1. Configure the System Registry value of type DWORD as:
   
   

   [HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for Outlook\ VoiceMailReplywithText]
   "VoiceMailReplywithText" = "1"

   
   
   
2. Configure the Microsoft Exchange environment routing rules so that all mails sent to the Connection Simple Mail Transfer Protocol (SMTP) domain are routed to the proper Connection server.
   
   
3. Configure Connection in order to relay emails to the user's corporate email within Exchange. For more information, refer to the Message Actions in Cisco Unity Connection 8.x section in the User Moves, Adds, and Changes Guide for Cisco Unity Connection Release 8.x document.
   
   
4. Configure the SMTP proxy address for the non-Single Inbox (SIB) user. For more information, refer to the SMTP Proxy Addresses in Cisco Unity Connection 8.x section in the User Moves, Adds, and Changes Guide for Cisco Unity Connection Release 8.x document.

Support For Group Exchange Mailbox Access Play Messages

If you have delegate rights to access another user's mailbox in VMO Release 8.5(7) and earlier, you cannot play voice messages of that user. If you have delegate rights to access another user's mailbox with VMO Release 8.6(4) and Cisco Unity Connection Release 8.5(1) with Engineering Special 49 and later, you can play voice messages of that user from the user's inbox.

Note: Group Exchange Mailbox Access Play Messages do not work with secure messages.

In order to enable the Group Exchange Mailbox Access Play Messages functionality, complete these steps:

1. Configure the System Registry value of type DWORD as:
   
   

   [HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for Outlook\ VoiceMailTUI
   "VoiceMailTUI" = "1"

   
   
   
2. Configure the user in Exchange in order to delegate mail access to another user.

VMO Release 8.6(5) New Functionaility

Support For Cisco Unity Voice Mail Attachment with VMO

In Cisco VMO Release 8.6(4) and earlier, when Cisco Unity users migrate to Cisco Unity Connection, they cannot play voice mails in Connection. Therefore, Cisco Unity voice mails and .wav files are only visible as attachments in Microsoft Outlook without VMO control over them.

With Cisco VMO Release 8.6(5) and later, migrated Cisco Unity users can play non-secure voice mails and .wav file attachments with the VMO Play Attachment feature. For more information on migration from Cisco Unity to Cisco Unity Connection, refer to the Migrating from Cisco Unity to Cisco Unity Connection 8.x by Gradually Moving Data chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Connection.

Note: You might experience a delay if the size of the attachment is large.

Migrated Cisco Unity users can play these types of voice mails and .wav file attachments:

• Cisco Unity Connection voice mails
• Cisco Unity voice mails
• Any .wav file attachment

When you migrate from Cisco Unity to Cisco Unity Connection Release 8.6(1) Engineering Special 14 and later or Cisco Unity Connection Release 8.6(2) Engineering Special 18 and later, you can play Cisco Unity non-secure voice messages with the VMO Play Attachment feature. This includes the voice messages that are not migrated from Cisco Unity to Unity Connection.

Note: The Play Attachment feature is only available for Connection voice messages that already exist, Cisco Unity voice messages, and .wav attachments. However, users are not able to reply and forward the Cisco Unity voice messages and .wav file attachments respectively.

Cisco Unity secure messages cannot be played with VMO or media player. When you attempt to play them, this encrypted message is played:

"This voice message is secure and can be played only by using a Cisco Unity supported client. If you received this message in error, delete it immediately and notify the sender."

In order to play Cisco Unity voice mail attachment with VMO, you must configure the System Registry value of type DWORD as:

[HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for Outlook\ VoiceMailUpload_Play]
"VoiceMailUpload_Play" = "1"

Note: The default value of System Registry key VoiceMailUpload_PLay is 0. If the registry value is set to 0, then only Cisco Unity Connection voice mails are played and not Cisco Unity voice mails.

Support For Single Sign-On in VMO

When you try to get connected with Cisco Unity Connection in Cisco VMO Release 8.6(4) and earlier, you must enter the login credentials.

Cisco VMO Release 8.6(5) and later, when integrated with single sign-on, allows you to gain access to use VMO without the need to enter login credentials. If you are authenticated to Active Directory, you are automatically connected to Cisco Unity Connection as well.

Here are some important points to note:

• The single sign-on feature is only enabled if you have VMO Release 8.6(5) and later and Connection Release 8.6(1) Engineering Special 17 and later or Connection Release 8.6(2) Engineering Special 18 and later.
  
  
• Cisco VMO Release 8.6(5) and later with single sign-on is only applicable for SIB users.

In order to disable the single sign-on feature in the registry editor, complete these steps:

1. Configure the System Registry value of type DWORD in Windows XP as:
   
   

   [HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for
   Outlook\Profiles\User Name\Server\VoiceMailRequiresUserNameAndPassword]
   "VoiceMailRequiresUserNameAndPassword" = "1"

   
   
   

   Note: In order to configure the System Registry value of type DWORD in Windows 7, use this path: [HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for Outlook\Profiles\Outlook\Servers\User Name\].

   
   
   
2. Restart Outlook, and manually enter the User Name and Password fields on the Cisco VMO page.

Note: The default value of System Registry key VoiceMailRequiresUserNameAndPassword is 0. If the registry value is set to 1, then the single sign-on feature with VMO is disabled.

Synchronization of Voice Messages in Sent Items Folder

With VMO Release 8.6(5) and later, Cisco Unity Connection Release 8.6(1) Engineering Special 17 and later, and Connection Release 8.6(2) Engineering Special 18 and later maintain a copy of voice messages sent by the user in the Exchange Sent Items folder. The voice messages are also visible in the Connection Sent Items folder. The voice messages in the Exchange Sent Items folder and the Unity Connection Sent folder are synchronized on an hourly basis. Moreover, the voice messages in the Exchange Sent Items folder can only be played with a computer. When you send the voice message to your voice mailbox, the voice message becomes visible in the Connection Sent Items folder. However, it does not get synchronized with the Exchange Sent Items folder.

By default, the synchronization of the voice messages in the Exchange Sent Items folder with Connection Sent Items folder is not enabled. In order to enable the feature, navigate to System Settings > Advanced > Messaging page in Cisco Unity Connection Administration and change the Sent Messages: Retention Period (in Days) setting to a value greater than zero.

For more information, refer to the Messaging Configuration section of Cisco Unity Connection 8.x Advanced Settings document.

Note: In order to play the voice messages in Exchange Sent Items folder with a phone, you must enable Group Exchange Mailbox Access Play Messages functionality. For detailed information, refer to the section Support For Group Exchange Mailbox Access Play Messages.

Support For Group Exchange Mailbox Access Play Messages

If you have delegate rights to access another user's mailbox in VMO Release 8.5(7) and earlier, you cannot play the voice message of that user. If you have delegate rights to access another user's mailbox in VMO Release 8.6(5) and Cisco Unity Connection Release 8.6(1) with Engineering Special 17 and later or Connection Release 8.6(2) Engineering Special 18 and later, you can play the voice message of that user from the user's inbox.

Note: Group Exchange Mailbox Access Play Messages do not work with secure messages.

In order to enable the Group Exchange Mailbox Access Play Messages functionality, complete these steps:

1. Configure the System Registry value of type DWORD as:
   
   

   [HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for Outlook\ VoiceMailTUI
   "VoiceMailTUI" = "1"

   
   
   
2. Configure the user in Exchange in order to delegate mail access to another user.

VMO Release 8.6(7) New Functionaility

Support For IPv6 with Cisco VMO

In Cisco VMO Release 8.6(6) and earlier, network communications over IPv4 are supported between Outlook and Cisco Unity Connection Release 8.6(x) and earlier. In Cisco VMO Release 8.6(7) and later, network communications over both the IPv4 and IPv6 are supported between Outlook and Cisco Unity Connection Release 9.0 and later. You can enter either of these in the Voicemail Server Name field:

• IPv4 address/Hostname
• IPv6address/Hostname

As a best practice, Cisco recommends that you enter the IPv6 address between the & brackets in the Voicemail Server Name field.

For more information on the IPv6 support with VMO, refer to Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations.

Support For Failover Feature in Cisco VMO

In Cisco VMO Release 8.6(6) and earlier, the Voice Mail Server is updated with the user-defined Voice Mail Server value regardless of the Cisco Unity Connection cluster status.

With Cisco VMO Release 8.6(7) and later, the Voice Mail Server is updated automatically with the current primary Cisco Unity Connection server on the basis of the Cisco Unity Connection cluster status.

Before you use Cisco Unity Connection Failover feature, note that:

• The Cisco Unity Connection Failover feature is only enabled if you have VMO Release 8.6(7) and later and Connection Release 8.6(2) Engineering Special 27 and later.
  
  
• The Cisco Unity Connection Failover feature is only applicable for SIB users with Cisco VMO Release 8.6(7) and later.
  
  
• If you want to use the Cisco Unity Connection Failover feature, single sign-on must be enabled. For more information, refer to the Single Sign-On in ViewMail for Outlook(VMO) section of the Release Notes for Cisco ViewMail for Microsoft Outlook Release 8.6(5) document.
  
  
• If the Cisco Unity Connection Failover feature is enabled, the VoiceMail Server Name field of VMO is read-only.

In order to enable the Unity Connection Failover feature in the registry editor, you must configure the System Registry value of type DWORD as:

[HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for
Outlook\Profiles\User Name\Server\VoiceMailSSOCxnFailOverMode]
"VoiceMailSSOCxnFailOverMode" = "1"

Note: The default value of System Registry key VoiceMailSSOCxnFailOverMode is 0. If the registry value is set to 1, then the Cisco Unity Connection Failover feature with VMO is enabled.

Support For Strict Single Sign-On in VMO

If the user authentication fails in Cisco VMO Releases 8.6(5) and 8.6(6) with single sign-on enabled, VMO allows you to update the username and password fields.

If the user authentication fails in Cisco VMO Release 8.6(7) and later with strict single sign-on enabled, VMO does not allow you to update the username and password fields.

Before you use strict single sign-on, you must ensure:

• The strict single sign-on feature is only enabled with VMO Release 8.6(7) and later.
  
  
• If you want to use the strict single sign-on functionality, the single sign-on must be enabled. For more information, see the Support for Single Sign-on in ViewMail for Outlook(VMO) section in the Release Notes for Cisco ViewMail for Microsoft Outlook Release 8.6(5) document.

In order to enable the strict single sign-on feature in the registry editor, you must configure the System Registry value of type DWORD as:

[HKEY_CURRENT_USER\Software\Cisco Systems\ViewMail for
Outlook\Profiles\User Name\Server\VoiceMailSSOStrictMode]
"VoiceMailSSOStrictMode" = "1"

Note: The default value of System Registry key VoiceMailSSOStrictMode is 0. If the registry value is set to 1, then the strict single sign-on feature with VMO is enabled.

Related Information

• Release Notes Viewmail for Outlook 8.6(4)
• Release Notes Viewmail for Outlook 8.6(5)
• Release Notes Viewmail for Outlook 8.6(6)
• Release Notes Viewmail for Outlook 8.6(7)