Unified Messaging Guide for Cisco Unity Connection Release 8.5 and Later

Accessing Exchange Email Using Text to Speech in Unity Connection 8.5 and Later

When Unity Connection is configured to allow access to Exchange email using text to speech, users have the option to hear their emails read to them when they sign in to Unity Connection by phone.

Unity Connection uses the IMAP protocol to access emails in Exchange so that the messages can be played using text to speech. By default, Exchange is not configured to allow IMAP access to messages. You must enable IMAP access on each Exchange server that contains emails that you want licensed Unity Connection users to be able to access.

For information on enabling IMAP access to Exchange in Unity Connection 8.0, see the "Enabling IMAP Access to Exchange in Cisco Unity Connection 8.0” section of the “Configuring Text-to-Speech Access to Exchange Emails in Cisco Unity Connection 8.0" chapter of the System Administration Guide for Cisco Unity Connection, available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx/8xcucsag295.html.

Accessing Exchange Calendars and Contacts in Unity Connection 8.5 and Later

When Unity Connection is configured to access Exchange calendars and contacts, Unity Connection users can do the following by phone:

• Hear a list of upcoming meetings (Outlook meetings only).
• Hear a list of the participants for a meeting.
• Send a message to the meeting organizer.
• Send a message to the meeting participants.
• Accept or decline meeting invitations (Outlook meetings only).
• Cancel a meeting (meeting organizers only).

In addition, Unity Connection enables users to import Exchange contacts using the Unity Connection Messaging Assistant web tool. The contact information can then be used in rules that users create in the Cisco Unity Connection Personal Call Transfer Rules web tool and when users place outgoing calls using voice commands.

If you configure a Unity Connection user for access to the Exchange calendar, you cannot also configure the user for access to Cisco Unified MeetingPlace.

Synchronizing Voice Messages in Unity Connection and Exchange Mailboxes for Single Inbox

This section describes how synchronizing voice messages in Unity Connection and Exchange mailboxes works. See the following sections:

• Storing Voice Messages with Single Inbox Configuration
• Single Inbox with ViewMail for Outlook
• Single Inbox without ViewMail for Outlook or with Other Email Clients
• Accessing Secure Voice Messages in the Exchange Mailbox
• Synchronizing Transcription of Voice Messages between Unity Connection 8.6(2) and Later with Exchange Mailboxes
• Synchronization with Outlook Folders
• Message Routing through SMTP Domain Name
• Location of Deleted Messages
• Types of Unity Connection Messages Not Synchronized with Exchange
• Replication of Status Changes
• Disabling and Re-enabling Single Inbox Affecting the Synchronization of Unity Connection and Exchange Mailboxes
• Synchronization of Read/Heard Receipts, Delivery Receipts, and Non-delivery Receipts
• Relating Unified Messaging Accounts and User Accounts for Unity Connection 8.5 and Later
• Creating Unified Messaging Accounts on Unity Connection 8.5 and Later

You may experience delay (in order of hours) in synchronization of voice messages from Exchange server to Unity Connection while Resynchronize All Single-Inbox Messages SysAgent task is running. It is recommended to run Resynchronize All Single-Inbox Messages SysAgent task during off hours.

Storing Voice Messages with Single Inbox Configuration

All Unity Connection voice messages, including those sent from Cisco Unity Connection ViewMail for Microsoft Outlook, are first stored in Unity Connection and are immediately replicated to the Exchange mailbox for the recipient.

Note When Unity Connection is configured for Single Inbox to Exchange, where a Blackberry Enterprise Server is also integrated with the Exchange server to send voice mail out to Blackberry devices, there will be a 10-15 min delay between the time the voice mail hits Exchange and the notification is picked up by the BES.To resolve the above issue you need to consider the following-

• For the Blackberry Enterprise Server - Install BES version 5.0.03 MR5 or later.
• For Unity Connection with Exchange 2007 or Exchange 2010, no Engineering Special is required. For Unity Connection8.5(x), or 8.6(1) with Exchange 2003, install an Engineering Special. You must contact the Cisco Support Group to receive the latest Engineering Special.

Single Inbox with ViewMail for Outlook

Consider the following points if you want to use Outlook for sending, replying, and forwarding voicemails and to synchronize these messages with Unity Connection:

• Install ViewMail for Outlook on user workstations. If ViewMail for Outlook is not installed, the voicemails that are sent by Outlook are treated as.wav file attachments by Unity Connection. For more information on installing ViewMail for Outlook, see the Release Notes for Cisco ViewMail for Microsoft Outlook for the latest release at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
• Make sure to add SMTP proxy addresses for unified messaging users in Unity Connection. The SMTP proxy address of a user specified in Cisco Unity Connection Administration must match the Exchange/ Office 365 email address specified in the unified messaging account in which single inbox is enabled.
• Associate an email account of each user in the organization with a Unity Connection server domain.

The Outlook Inbox folder contains both voicemails and the other messages stored in Exchange/ Office 365. The voicemails also appear in the Web Inbox of a user.

A single inbox user has a Voice Outbox folder added to the Outlook mailbox. Unity Connection voicemails sent from Outlook do not appear in the Sent Items folder

Note Private messages cannot be forwarded.

Single Inbox without ViewMail for Outlook or with Other Email Clients

If you use another email client to access Unity Connection voice messages in Exchange, or if you do not install ViewMail for Outlook:

• The email client treats Unity Connection voice messages like emails with.wav file attachments.
• When a user replies to or forwards a Unity Connection voice message, the reply or forward also is treated like an email, even if the user attaches a.wav file. Message routing is handled by Exchange, not by Unity Connection, so the message is never sent to the Unity Connection mailbox for the recipient.
• Users cannot listen to secure voice messages.
• It may be possible to forward private voice messages. (When users use ViewMail for Outlook, ViewMail for Outlook prevents private messages from being forwarded.)

Note If a voice message is sent to the user of Exchange 2003, it is immediately synchronized between Unity Connection and Exchange. The.wav file attachment is displayed both in Web Inbox and Outlook of Exchange 2003. In Outlook WebMail Access of Exchange 2003, the email shows the attachment symbol but when the email is opened, the.wav file attachment is not displayed. Both in Outlook and OWA of Exchange 2007, 2010 and 2013 (Unity Connection 8.6(2) SU3 and later), the.wav file attachment is displayed in the email.

Accessing Secure Voice Messages in the Exchange Mailbox

To play secure Unity Connection voice messages in the Exchange mailbox, users must use Microsoft Outlook and Cisco Unity Connection ViewMail for Microsoft Outlook. Without ViewMail for Outlook installed, users accessing secure voice messages see only text in the body of a decoy message; the text briefly explains secure messages.

Synchronizing Transcription of Voice Messages between Unity Connection 8.6(2) and Later with Exchange Mailboxes

In Unity Connection 8.6(1) and earlier releases, the transcriptions were only available at Unity Connection server and read using either IMAP client or Web Inbox. With Unity Connection 8.6(2) and later releases, the system administrator can enable the SpeechView transcriptions synchronization to single inbox. To enable transcription of voice messages, Unity Connection users must configure the following services:

• Unified Messaging Service: To configure the Unified Messaging Service, see the "Creating a Unified Messaging Service to Access Exchange from Cisco Unity Connection 8.5 and later" section of "Configuring Cisco Unity Connection 8.5 and Later and Microsoft Exchange for Unified Messaging" chapter in Unified Messaging Guide for Cisco Unity Connection. http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx.html
• SpeechView Transcription Service: To configure the Speech View Transcription Service, see the "Overview of SpeechView in Cisco Unity Connection 8.x" section of "Configuring Transcription (SpeechView) in Cisco Unity Connection 8.x" chapter in the System Administration Guide for Cisco Unity Connection guide. http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagpdf.pdf

Note that the following services are not supported with Unity Connection 8.6(2), if configured with single inbox:

– Synchronization of Multiple Forward Message

– Synchronization of transcription for user's with Exchange 2003

In single inbox, the transcription of Voice Messages is synchronized with Exchange in the following ways:

• When sender sends voice mail to Unity Connection user through Web Inbox or touchtone conversation user interface and the Unity Connection user views voice mail through various email clients, then the transcription of voice messages are synchronized, as shown in the Table 2-1 .

Table 2-1 When Sender Sends Voice Mail Through Web Inbox or Touchtone Conversation User Interface

• When sender sends voice mail to Unity Connection user through ViewMail for Outlook and the Unity Connection user views voice mail through various email clients, then the transcription of voice messages are synchronized, as shown in the Table 2-2 :

Table 2-2 When Sender Sends Voice Maill Through ViewMail for Outlook

Note Voice messages received by Unity Connection, which are composed using ViewMail for Outlook have message body either with text or blank body.

• Synchronizing the transcription of voice messages, when the sender sends voice mail to Unity Connection through third-party email clients and the receiver views the voice mail through various clients.

– The transcription of voice messages can be synchronized in either of the above mentioned scenarios.

When a sender sends a voice message to a Unity Connection user, Unity Connection sends the received voice message to the Nuance server for the transcription of voice messages. However, in case of any failure/error in the transcription of voice messages, Nuance server sends back the error code to Unity Connection.

Transcription of Voice messages in Secure and Private Messages

• Secure Messages: are stored only on the Unity Connection server. Secure messages are transcribed only if the user belongs to a class of service.
• Private Messages: The transcription of private messages is not supported.

Synchronization with Outlook Folders

Unity Connection synchronizes voice messages in the following Outlook folders with the Unity Connection Inbox folder for the user, so the messages are still visible in the Unity Connection Inbox folder:

• Subfolders under the Outlook Inbox folder
• Subfolders under the Outlook Deleted Items folder
• The Outlook Junk Email folder

Messages in the Outlook Deleted Items folder appear in the Unity Connection deleted items folder.

If the user moves voice messages (except secure voice messages) into Outlook folders that are not under the Inbox folder, the messages are moved to the deleted items folder in Unity Connection. The messages can still be played using ViewMail for Outlook because a copy still exists in the Outlook folder. If the user moves the messages back into the Outlook Inbox folder or into an Outlook folder that is synchronized with the Unity Connection Inbox folder, and:

• If the message is still in the deleted items folder in Unity Connection, the message is synchronized back into the Unity Connection Inbox for that user.
• If the message is not still in the deleted items folder in Unity Connection, the message is still playable in Outlook, but it is not resynchronized into Unity Connection.

Secure voice messages behave differently. When Unity Connection replicates a secure voice message to Exchange, it replicates only a decoy message that briefly explains secure messages; the only copy of the voice message remains on the Unity Connection server. When a user plays a secure message using ViewMail for Outlook, ViewMail retrieves the message from the Unity Connection server and plays it without ever storing the message in Exchange or on the computer of the user.

If the user moves a secure message to an Outlook folder that is not synchronized with the Unity Connection Inbox folder, the only copy of the voice message is moved to the deleted items folder in Unity Connection, and the message can no longer be played in Outlook. If the user moves the message back into the Outlook Inbox folder or into an Outlook folder that is synchronized with the Unity Connection Inbox folder, and:

• If the message is still in the deleted items folder in Unity Connection, the message is synchronized back into the Unity Connection Inbox for that user, and the message becomes playable again in Outlook.
• If the message is not still in the deleted items folder in Unity Connection, the message is not resynchronized into Unity Connection and can no longer be played in Outlook.

Message Routing through SMTP Domain Name

Unity Connection uses SMTP domain name to route messages between digitally networked Connection servers and to construct the SMTP address of the sender on outgoing SMTP messages. For each user, Unity Connection creates an SMTP address of <Alias>@<SMTP Domain>. This SMTP address is displayed on the Edit User Basics page for the user. Examples of outgoing SMTP messages that use this address format include messages sent by users on this server to recipients on other digitally networked Unity Connection servers and messages that are sent from the Unity Connection phone interface or Messaging Inbox and relayed to an external server based on the Message Actions setting of the recipient.

Unity Connection also uses the SMTP Domain to create sender VPIM addresses on outgoing VPIM messages, and to construct the From address for notifications that are sent to SMTP notification devices.

When Unity Connection is first installed, the SMTP Domain is automatically set to the fully qualified host name of the server.

Make sure that the SMTP domain of Unity Connection is different from the Corporate Email domain to avoid issues in message routing for Unity Connection.

Some scenarios in which you may encounter issues with the same domain are listed below:

• Routing of the voice messages between digitally networked Unity Connection servers
• Relaying of the messages
• Replying and Forwarding of the voice messages using ViewMail for Outlook
• Routing of the SpeechView messages to Unity Connection server
• Sending the SMTP message Notifications
• Routing of the VPIM messages

Note Unity Connection requires a unique SMTP domain for every user, which is different from the corporate email domain. Due to same domain name configuration on Microsoft Exchange and Cisco Unity Connection, the users who are configured for Unified Messaging may face issues in adding recipient while composing, replying and forwarding of messages.For more information on resolving domain name configuration issues, see the Creating Unified Messaging Accounts on Unity Connection 8.5 and Later section.

Location of Deleted Messages

By default, when a user deletes a voice message in Unity Connection, the message is sent to the Unity Connection deleted items folder and synchronized with the Outlook Deleted Items folder. When the message is deleted from the Unity Connection deleted items folder (the user can do this manually, or you can configure message aging to do it automatically), it is also deleted from the Outlook Deleted Items folder.

If you are adding the single-inbox feature to an existing system, and if you have configured Unity Connection to permanently delete messages without saving them in the deleted items folder, messages that users delete using Web Inbox or Unity Connection phone interface are still permanently deleted. However, messages that users delete using Outlook are only moved to the Deleted Items folder in Outlook, not permanently deleted. When Unity Connection synchronizes with Exchange, the message is moved to the Unity Connection deleted items folder; it is not permanently deleted. We recommend that you do one or both of the following:

• Configure message aging to permanently delete messages in the Unity Connection deleted items folder.
• Configure message quotas, so that Unity Connection prompts users to delete messages when their mailboxes approach a specified size.

When a user deletes a voice message from any Outlook folder, including the Outlook Inbox folder, the Deleted Items folder, or any subfolder, the message is moved to the deleted items folder in Unity Connection. No operation in Outlook will cause a message to be permanently deleted in Unity Connection.

Types of Unity Connection Messages Not Synchronized with Exchange

The following types of messages are not synchronized:

• Sent messages
• Draft messages
• Messages configured for future delivery but not yet delivered
• Broadcast messages
• Unaccepted dispatch messages. When a dispatch message has been accepted by a recipient, it becomes a normal message and is synchronized with Exchange for the user who accepted it and deleted for all other recipients. Until someone on the distribution list accepts a dispatch message, the message waiting indicator for everyone on the distribution list will remain on, even when users have no other unread messages.

Replication of Status Changes

Status changes (for example, from unread to read), changes to the subject line, and changes to the priority are replicated from Unity Connection to Exchange and vice versa, as applicable.

Disabling and Re-enabling Single Inbox Affecting the Synchronization of Unity Connection and Exchange Mailboxes

When you configure unified messaging, you create one or more unified messaging services that define, among other things, which unified messaging features are enabled. You also create one or more unified messaging accounts for each user to associate the user with unified messaging services. You can disable single inbox in three ways:

• Entirely disable a unified messaging service in which single inbox is enabled. This disables all enabled unified messaging features (including single inbox) for all users that are associated with the service.
• Disable only the single inbox feature for a unified messaging service, which disables only the single inbox feature for all users that are associated with that service.
• Disable single inbox for a unified messaging account, which disables single inbox only for the associated user.

If you disable and later re-enable single inbox using any of these methods, Unity Connection resynchronizes the Unity Connection and Exchange mailboxes for the affected users. Note the following:

• If users delete messages in Exchange but do not delete the corresponding messages in Unity Connection while single inbox is disabled, the messages will be resynchronized into the Exchange mailbox when single inbox is re-enabled.
• If messages are hard deleted from Exchange (deleted from the Deleted Items folder) before single inbox is disabled, the corresponding messages that are still in the deleted items folder in Unity Connection when single inbox is re-enabled will be resynchronized into the Exchange Deleted Items folder.
• If users hard delete the messages in Unity Connection but do not delete the corresponding messages in Exchange while single inbox is disabled, the messages remain in Exchange when single inbox is re-enabled. Users must delete the messages from Exchange manually.
• If users change the status of messages in Exchange (for example, from unread to read) while single inbox is disabled, the status of Exchange messages will be changed to the current status of the corresponding Unity Connection messages when single inbox is re-enabled.
• When you re-enable single inbox, depending on the number of users associated with the service and the size of their Connection and Exchange mailboxes, resynchronization for existing messages may affect synchronization performance for new messages.

Synchronization of Read/Heard Receipts, Delivery Receipts, and Non-delivery Receipts

Unity Connection can send heard/read receipts, delivery receipts, and non-delivery receipts to Unity Connection users who send voice messages. If the sender of a voice message is configured for single inbox, the applicable receipt is sent to the Unity Connection mailbox for the sender. The receipt is then synchronized into the Exchange mailbox for the sender.

Note the following.

• Read/heard receipts: When sending a voice message, a sender can request a read/heard receipt. If you do not want Unity Connection to respond to requests for read receipts, in Unity Connection Administration, uncheck the Respond to Requests for Read Receipts check box, which appears on the Users > Users > Edit > Mailbox page and on the Templates > User Templates > Edit > Mailbox page.
• Delivery receipts: A sender can request a delivery receipt only when sending a voice message from ViewMail for Outlook. You cannot prevent Unity Connection from responding to a request for a delivery receipt.
• Non-delivery receipts (NDR): A sender receives an NDR when a voice message cannot be delivered. If you do not want Unity Connection to send an NDR when a message cannot be delivered, in Unity Connection Administration, uncheck the Send Non-Delivery Receipts for Message Failed Delivery check box, which appears on the Users > Users > Edit User Basics page and on the Templates > User Templates > Edit User Template Basics page.

Note the following about NDRs:

– When the sender accesses Unity Connection using the TUI, the NDR includes the original voice message, which allows the sender to resend the message at a later time or to a different recipient.

– When the sender accesses Unity Connection using Web Inbox, the NDR includes the original voice message, but the sender cannot resend it.

– When the sender uses ViewMail for Outlook to access Unity Connection voice messages that have been synchronized into Exchange, the NDR is a receipt that contains only an error code, not the original voice message, so the sender cannot resend the voice message.

– When the sender is an outside caller, NDRs are sent to Unity Connection users on the Undeliverable Messages distribution list. Verify that the Undeliverable Messages distribution list includes one or more users who regularly monitors and reroutes undelivered messages.

Exchange Servers Communication with Unity Connection 8.5 and Later

When you add a unified messaging service, which defines the communication between Unity Connection and Exchange, you can choose whether you want Unity Connection to communicate directly with a specific Exchange server or you want Unity Connection to search for Exchange servers. The choice you make determines which Exchange mailboxes Unity Connection can access:

• If you choose a specific Exchange 2003 server, Unity Connection can only access mailboxes on that Exchange server.
• If you choose a specific Exchange 2007 client access server, Unity Connection can access all Exchange 2007 mailboxes in the Exchange organization, but cannot access Exchange 2003, Exchange 2010, or Exchange 2013 (Unity Connection 8.6(2) SU3 and later) mailboxes.
• If you choose a specific Exchange 2010 client access server, Unity Connection can access all Exchange 2010 and Exchange 2007 mailboxes in the Exchange organization, but cannot access Exchange 2013 (Unity Connection 8.6(2) SU3 and later) and Exchange 2003 mailboxes.
• If you choose a specific Exchange 2013 client access server (Unity Connection 8.6(2) SU3 and later), Unity Connection can access all Exchange 2013, Exchange 2010 and Exchange 2007 mailboxes in the Exchange organization, but cannot access Exchange 2003 mailboxes.
• If you choose to allow Unity Connection to search for Exchange servers, then you need to select from the following two options:

– Exchange 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2007, Exchange 2010, and Exchange 2013 (Unity Connection 8.6(2) SU3 and later).

– Exchange 2003, 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2003, Exchange 2007, and Exchange 2010. When the Exchange organization includes Exchange 2003 servers, Unity Connection always communicates directly with the Exchange back-end servers, it never communicates with Exchange front-end servers.

Note the following:

• If you want to choose a specific Exchange server when you add a unified messaging service, you may need to add more than one unified messaging service to allow Unity Connection to access all of the mailboxes in the Exchange organization. Table 2-3 explains when you need to add more than one unified messaging service.

Table 2-3 Adding Unified Messaging Services Based on Versions of Exchange

• If you choose to allow Unity Connection to search for Exchange servers, Unity Connection can automatically detect when you move mailboxes from one version of Exchange to another and can automatically update Unity Connection user settings.
• If you choose a specific Exchange server, Unity Connection can sometimes detect when you move mailboxes from one Exchange server to another, and can automatically access the Exchange mailbox in the new location. When Unity Connection cannot detect mailbox moves, you must manually update unified messaging services or unified messaging accounts:

– If you moved all of the Exchange mailboxes accessed by a unified messaging service: Update the unified messaging service to access a different Exchange server.

– If you moved only some of the Exchange mailboxes accessed by a unified messaging service: Update unified messaging account settings to use a unified messaging service that accesses mailboxes in the new location.

Table 2-4 identifies when Unity Connection can and cannot automatically detect mailbox moves between Exchange servers. For information on updating Unity Connection user settings when Unity Connection cannot detect mailbox moves, see the “Configuring Cisco Unity Connection 8.5 and Later and Microsoft Exchange for Unified Messaging” chapter.

• If Unity Connection is not configured to use DNS, you must choose a specific Exchange server. If this does not allow you to access all of the Exchange mailboxes in the organization as described earlier in this section, you must create more than one unified messaging service.
• If you choose a specific Exchange server and that server stops functioning, Unity Connection cannot access any Exchange mailboxes. If you choose to allow Unity Connection to search for Exchange servers and if the Exchange server that Unity Connection is currently communicating with stops functioning, Unity Connection searches for another Exchange server and begins accessing mailboxes through that server.

Confirming Exchange Authentication and SSL Settings for Unity Connection 8.5 and Later

Confirm that the Exchange servers that Unity Connection will access are configured to use the desired authentication mode (basic, digest, or NTLM) and web-based protocol (HTTPS or HTTP). For information on which Exchange servers Unity Connection will access, see the “Exchange Servers Communication with Unity Connection 8.5 and Later” section.

Later in the task list, you will create one or more Unity Connection unified messaging services, and select the same authentication mode and web-based protocol that you specify in Exchange when you do the applicable procedures in this section.

Do the procedure in the applicable section:

• Confirming Exchange 2013 Authentication and SSL Settings for Unity Connection
• Confirming Exchange 2013 Authentication and SSL Settings for Unity Connection
• Confirming Exchange 2007 Authentication and SSL Settings for Unity Connection 8.5 and Later
• Confirming Exchange 2003 Authentication and SSL Settings for Unity Connection 8.5 and Later

Confirming Exchange 2013 Authentication and SSL Settings for Unity Connection

To Confirm Exchange 2013 Authentication and SSL Settings for Unity Connection

Step 1 Decide which type of authentication (basic or NTLM) you want Unity Connection to use to sign in to Exchange 2013 client access servers (Unity Connection 8.6(2) SU3 and later). You must configure the following servers to use the same type of authentication:

• All Exchange 2013 client access servers (Unity Connection 8.6(2) SU3 and later).

Step 2 Decide whether you want the communication between Unity Connection and Exchange 2013 client access servers (Unity Connection8.6(2) SU3 and later) to be SSL encrypted. If so, you must specify the same SSL setting on the following servers:

• All Exchange 2013 client access servers (Unity Connection 8.6(2) SU3 and later).

Step 3 Sign in to a server that has access to the same Exchange 2013 client access servers (Unity Connection 8.6(2) SU3 and later) that Unity Connection has. Use an account that is a member of the local Administrators group.

Step 4 On the Windows Start menu, select Programs > Administrative Tools > Internet Information Services (IIS) Manager.

Step 5 For the first Exchange 2013 client access server (Unity Connection 8.6(2) SU3 and later) for which you want to confirm settings, in the left pane, expand <servername> > Sites > Default Website > EWS.

Step 6 Under Default Website, select Autodiscover.

Step 7 In the middle pane, in the IIS section, double-click Authentication.

Step 8 Confirm that the Status column says Enabled for the type of authentication that you want the unified messaging services account to use to sign in to Exchange client access servers. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• NTLM

Step 9 If you changed any settings, in the right pane, select Apply.

Step 10 In the left pane, select Autodiscover again.

Step 11 In the middle pane, double-click SSL Settings.

Step 12 If the Require SSL check box is checked:

• When you create a unified messaging service in Unity Connection, you must choose HTTPS for the web-based protocol.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 13 If you changed any settings, in the right pane, select Apply.

Step 14 In the left pane, under Default Website, select EWS.

Step 15 In the middle pane, in the IIS section, double-click Authentication.

Step 16 Confirm that the Status column says Enabled for the type of authentication that you want the unified messaging services account to use to sign in to Exchange mailboxes. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• NTLM

Step 17 If you changed any settings, in the right pane, select Apply.

Step 18 In the left pane, select EWS again.

Step 19 In the middle pane, double-click SSL Settings.

Step 20 If the Require SSL check box is checked:

• You must choose HTTPS for the web-based protocol when you create a unified messaging service in Unity Connection.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 21 If you changed any settings, in the right pane, select Apply.

Step 22 Repeat Step 5 through Step 22 for the other Exchange 2013 client access servers (Unity Connection 8.6(2) SU3 and later) that Unity Connection can access.

Step 23 Close IIS Manager.

Confirming Exchange 2010 Authentication and SSL Settings for Unity Connection 8.5 and Later

To Confirm Exchange 2010 Authentication and SSL Settings for Unity Connection 8.5 and Later

Step 1 Decide which type of authentication (basic, digest, or NTLM) you want Unity Connection to use to sign in to Exchange 2010 client access servers. You must configure the following servers to use the same type of authentication:

• All Exchange 2010 client access servers.
• All Exchange 2007 client access servers, if there are Exchange 2007 mailboxes that you want Unity Connection to be able to access.
• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.

Step 2 Decide whether you want the communication between Unity Connection and Exchange 2010 client access servers to be SSL encrypted. If so, you must specify the same SSL setting on the following servers:

• All Exchange 2010 client access servers.
• All Exchange 2007 client access servers, if there are Exchange 2007 mailboxes that you want Unity Connection to be able to access.
• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.

Step 3 Sign in to a server that has access to the same Exchange 2010 client access servers that Unity Connection has. Use an account that is a member of the local Administrators group.

Step 4 On the Windows Start menu, select Programs > Administrative Tools > Internet Information Services (IIS) Manager.

Step 5 For the first Exchange 2010 client access server for which you want to confirm settings, in the left pane, expand <servername> > Sites > Default Website.

Step 6 Under Default Website, select Autodiscover.

Step 7 In the middle pane, in the IIS section, double-click Authentication.

Step 8 Confirm that the Status column says Enabled for the type of authentication that you want the unified messaging services account to use to sign in to Exchange client access servers. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• Digest
• NTLM

Note NTLM v1 is supported with Single Inbox Feature

Step 9 If you changed any settings, in the right pane, select Apply.

Step 10 In the left pane, select Autodiscover again.

Step 11 In the middle pane, double-click SSL Settings.

Step 12 If the Require SSL check box is checked:

• When you create a unified messaging service in Unity Connection, you must choose HTTPS for the web-based protocol.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 13 If you changed any settings, in the right pane, select Apply.

Step 14 In the left pane, under Default Website, select EWS.

Step 15 In the middle pane, in the IIS section, double-click Authentication.

Step 16 Confirm that the Status column says Enabled for the type of authentication that you want the unified messaging services account to use to sign in to Exchange mailboxes. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• Digest
• NTLM

Step 17 If you changed any settings, in the right pane, select Apply.

Step 18 In the left pane, select EWS again.

Step 19 In the middle pane, double-click SSL Settings.

Step 20 If the Require SSL check box is checked:

• You must choose HTTPS for the web-based protocol when you create a unified messaging service in Unity Connection.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 21 If you changed any settings, in the right pane, select Apply.

Step 22 If you have installed Exchange 2010 Service Pack 1 or later, skip to Step 23.

If you have not installed Exchange 2010 Service Pack 1 or later, edit the Exchange web.config files for EWS and for autodiscovery to match the settings in IIS Manager:

• For EWS, see “Enable or Disable SSL on Exchange Web Services Virtual Directories” on the Microsoft Technet website. Search on the document title.
• No comparable document exists for autodiscovery, but you can use the applicable procedure in the EWS document to edit the web.config file in the \Exchange Server\V14\ClientAccess\Autodiscover directory.

Step 23 Repeat Step 5 through Step 22 for the other Exchange 2010 client access servers that Unity Connection can access.

Step 24 Close IIS Manager.

Confirming Exchange 2007 Authentication and SSL Settings for Unity Connection 8.5 and Later

To Confirm Exchange 2007 Authentication and SSL Settings for Unity Connection 8.5 and Later

Step 1 Decide which type of authentication (basic, digest, or NTLM) you want Unity Connection to use to sign in to Exchange 2007 client access servers. You must configure the following servers to use the same type of authentication:

• All Exchange 2007 client access servers.
• All Exchange 2010 client access servers, if there are Exchange 2010 mailboxes that you want Unity Connection to be able to access.
• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.

Step 2 Decide whether you want the communication between Unity Connection and Exchange 2007 client access servers to be SSL encrypted. If so, you must specify the same SSL setting on the following servers:

• All Exchange 2007 client access servers.
• All Exchange 2010 client access servers, if there are Exchange 2010 mailboxes that you want Unity Connection to be able to access.
• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.

Step 3 Sign in to a server that has access to the same Exchange 2007 client access servers as Unity Connection has. Use an account that is a member of the local Administrators group.

Step 4 On the Windows Start menu, select Programs > Administrative Tools > Internet Information Services (IIS) Manager.

Step 5 For the first Exchange 2007 server for which you want to confirm settings, in the left pane, expand <servername> > Sites > Default Website.

Step 6 Under Default Website, right-click Autodiscover, and select Properties.

Step 7 In the Autodiscover Properties dialog box, select the Directory Security tab.

Step 8 In the Authentication and Access Control section, select Edit.

Step 9 In the Authentication Methods dialog box, confirm that the check box is checked for the type of authentication that you want the unified messaging services account to use to find Exchange servers. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• Digest
• NTLM

Step 10 Select OK.

Step 11 In the Secure Communications section, select Edit.

Step 12 In the Secure Communications dialog box, if the Require Secure Channel (SSL) check box is checked:

• You must choose HTTPS for the web-based protocol when you create a unified messaging service in Unity Connection.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 13 Select OK twice.

Step 14 In the left pane, under Default Website, right-click EWS, and select Properties.

Step 15 In the EWS Properties dialog box, select the Directory Security tab.

Step 16 In the Authentication and Access Control section, select Edit.

Step 17 In the Authentication Methods dialog box, confirm that the check box is checked for the type of authentication that you want the unified messaging services account to use to find Exchange servers. When you create a unified messaging services account, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• Digest
• NTLM

Step 18 Select OK.

Step 19 In the Secure Communications section, select Edit.

Step 20 In the Secure Communications dialog box, if the Require Secure Channel (SSL) check box is checked:

• You must choose HTTPS for the web-based protocol when you create a unified messaging service in Unity Connection.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 21 Select OK twice.

Step 22 Repeat Step 5 through Step 21 for the other Exchange 2007 client access servers that Unity Connection can access.

Step 23 Close IIS Manager.

Confirming Exchange 2003 Authentication and SSL Settings for Unity Connection 8.5 and Later

To Confirm Exchange 2003 Authentication and SSL Settings for Unity Connection 8.5 and Later

Step 1 Decide which type of authentication (basic, digest, or NTLM) you want Unity Connection to use to sign in to Exchange 2003 servers.

If you are configuring Unity Connection to search for Exchange servers, you must configure the following servers to use the same type of authentication:

• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.
• All Exchange 2007 client access servers.
• All Exchange 2010 client access servers, if there are Exchange 2010 mailboxes that you want Unity Connection to be able to access.

If you are choosing specific Exchange servers, you do not need to configure all Exchange servers to use the same type of authentication. Each Exchange server is associated with a separate unified messaging service, so the Exchange authentication mode only needs to match the authentication mode for the corresponding unified messaging service.

Note If you are choosing a specific Exchange 2003 front-end server, you may need to use basic authentication. For more information, on the Microsoft website, see the “Authentication Mechanisms for HTTP” in the Exchange Server 2003 section of the TechNet Library.

Step 2 Decide whether you want the communication between Unity Connection and Exchange 2007 client access servers to be SSL encrypted. If so, you must specify the same SSL setting on the following servers:

• All Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.
• All Exchange 2007 client access servers.
• All Exchange 2010 client access servers, if there are Exchange 2010 mailboxes that you want Unity Connection to be able to access.

Step 3 Sign in to a server that has access to the same Exchange 2003 servers as Unity Connection has. Use an account that is a member of the local Administrators group.

Step 4 On the Windows Start menu, select Programs > Administrative Tools > Internet Information Services (IIS) Manager.

Step 5 For the first Exchange 2003 server for which you want to confirm settings, in the left pane, expand <servername> > Web Sites > Default Website.

Step 6 Under Default Website, right-click Exchange, and select Properties.

Step 7 In the Exchange Properties dialog box, select the Directory Security tab.

Step 8 In the Authentication and Access Control section, select Edit.

Step 9 In the Authentication Methods dialog box, confirm that the check box is checked for the type of authentication that you want the unified messaging services account to use to sign in to Exchange servers. When you create a unified messaging service, you will configure Unity Connection to use the same type of authentication.

Unity Connection supports only the following types of authentication:

• Basic
• Digest
• NTLM

Step 10 Select OK.

Step 11 In the Secure Communications section, select Edit.

Step 12 In the Secure Communications dialog box, if the Require Secure Channel (SSL) check box is checked:

• You must choose HTTPS for the web-based protocol when you create a unified messaging service in Unity Connection.
• You must download SSL certificates from the Exchange server and install them on the Unity Connection server.

Step 13 Select OK twice.

Step 14 Repeat Step 5 through Step 13 for the other Exchange 2003 servers that you want Unity Connection to be able to access.

Step 15 Close IIS Manager.

Creating the Unified Messaging Services Account in Active Directory and Granting Permissions for Unity Connection 8.5 and Later

Unity Connection accesses Exchange mailboxes using an Active Directory account called the unified messaging services account. After you create the account, you grant it the rights necessary for Unity Connection to perform operations on behalf of the user. For Exchange 2010 and 2007, operations are performed through Exchange Web Services (EWS). For Exchange 2003, operations are performed through WebDav. These operations include uploading messages into Exchange mailboxes, tracking changes to the messages in Exchange, updating the messages with changes made in Unity Connection, deleting messages in Exchange when the messages are deleted in Unity Connection, tracking when messages are deleted in Exchange so they can be moved to the deleted items folder in Unity Connection, and so on.

See the following sections:

• Task list for Creating the Unified Messaging Services Account and Granting Permissions for Unity Connection 8.5 and Later
• Confirming that Local Computer Account is a Member of the Windows Authorization Access Group on Client Access Servers (Exchange 2007 Only)
• Assigning the Application Impersonation Management Role to Unified Messaging Services Accounts (Exchange 2013 and Exchange 2010 Only)
• Granting Rights to the Unified Messaging Services Account (Exchange 2007 Only)
• Granting Permissions to the Unified Messaging Services Account (Exchange 2003 Only)

Task list for Creating the Unified Messaging Services Account and Granting Permissions for Unity Connection 8.5 and Later

1. Create one or more domain user accounts in the Active Directory forest that includes the Exchange servers with which you want Unity Connection to communicate. Note the following:

– Give the account a name that identifies it as the unified messaging services account for Unity Connection.

– Do not create an Exchange mailbox for the account.

– Do not add the account to any administrator group.

– Do not disable the account, or Unity Connection cannot use it to access Exchange mailboxes.

– Specify a password that satisfies the password-security requirements of your company.

The password is encrypted with AES 128-bit encryption and stored in the Unity Connection database. The key that is used to encrypt the password is accessible only with root access, and root access is available only with assistance from Cisco TAC.

– When you are configuring unified messaging for a Unity Connection cluster, Unity Connection automatically uses the same unified messaging services account for both Unity Connection servers.

– When you are configuring unified messaging for intersite networking or for intrasite networking, you can use the same unified messaging services account for more than one Unity Connection server. However, this is not a requirement and does not affect functionality or performance.

2. If you are using Exchange 2007: For all client access servers, confirm that the local computer account is a member of the Windows Authorization Access group. See the “Confirming that Local Computer Account is a Member of the Windows Authorization Access Group on Client Access Servers (Exchange 2007 Only)” section.

3. For each version of Exchange that you want Unity Connection to be able to access, do the procedure in the corresponding section:

– Assigning the Application Impersonation Management Role to Unified Messaging Services Accounts (Exchange 2013 and Exchange 2010 Only)

– Granting Rights to the Unified Messaging Services Account (Exchange 2007 Only)

– Granting Permissions to the Unified Messaging Services Account (Exchange 2003 Only)

Confirming that Local Computer Account is a Member of the Windows Authorization Access Group on Client Access Servers (Exchange 2007 Only)

If you are configuring unified messaging for Unity Connection users whose Exchange mailboxes are homed on Exchange 2007 servers, do the following procedure to confirm that the local computer accounts for those servers are members of the Windows Authorization Access group, as they are by default. Do the procedure for all Exchange 2007 client access servers that Unity Connection can access.

To Confirm that the Local Computer Account is a Member of the Windows Authorization Access Group on Client Access Servers (Exchange 2007 Only)

Step 1 Sign in to a server on which Active Directory Users and Computers is installed. Use an account that is a member of the Domain Admins group.

Step 2 On the Windows Start menu, select Administrative Tools > Active Directory Users and Computers.

Step 3 In the left pane, expand the name of a domain that contains Exchange 2007 client access servers that Unity Connection can access, and select Builtin.

Step 4 In the right pane, right-click Windows Authorization Access Group, and select Properties.

Step 5 In the Windows Authorization Access Group Properties dialog box, select the Members tab.

Step 6 Select Add.

Step 7 In the Select Users, Contacts, Computers, or Groups dialog box, select Object Types.

Step 8 Check the Computers check box.

Step 9 Select OK to close the Object Types dialog box.

Step 10 On the Select Users, Contacts, Computers, or Groups dialog box, enter the names of all of the Exchange 2007 client access servers in the domain that you expanded in Step 3.

Step 11 Select Check Names.

Step 12 Select OK to close the Select Users, Contacts, Computers, or Groups dialog box.

Step 13 Select OK to close the Windows Authorization Access Group Properties dialog box.

Step 14 Repeat Step 3 through Step 13 for the other domains that contain Exchange 2007 client access servers that Unity Connection can access.

Assigning the Application Impersonation Management Role to Unified Messaging Services Accounts (Exchange 2013 and Exchange 2010 Only)

To Assign the ApplicationImpersonation Management Role to Unified Messaging Services Accounts (Exchange 2013 and Exchange 2010 Only)

Step 1 Sign in to a server on which Exchange Management Shell is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant permissions on Exchange objects in the configuration container.

Step 2 Run the following command in Exchange Management Shell to assign the ApplicationImpersonation management role to the unified messaging services account for Exchange 2013 (Unity Connection 8.6(2) SU3 and later) or 2010.

new-ManagementRoleAssignment -Name: RoleName -Role:ApplicationImpersonation -User:' Account '

where:

• RoleName is the name that you want to give the assignment, for example, Unity ConnectionUMServicesAcct. The name that you enter for RoleName appears when you run get-ManagementRoleAssignment.
• Account is the name of the unified messaging services account in domain\alias format.

Step 3 If you created more than one unified messaging services account, repeat Step 2 for the remaining accounts. Specify a different value for RoleName for each unified messaging services account.

Granting Rights to the Unified Messaging Services Account (Exchange 2007 Only)

Do the following procedures for all unified messaging services accounts.

To Grant Rights to the Unified Messaging Services Account for Cisco Unity Connection 8.5 (Exchange 2007 Only)

Step 1 Sign in to a server on which Exchange Management Shell is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant rights on Exchange objects in the configuration container.

Step 2 Run the following commands in Exchange Management Shell to grant the required rights to the unified messaging services account for Exchange 2007:

Add-ADPermission -Identity ( PermissionLevel ).DistinguishedName -User (Get-User -Identity Account | select-object).identity -ExtendedRight ms-Exch-EPI-Impersonation

Add-ADPermission -Identity ( PermissionLevel ).DistinguishedName -User (Get-User -Identity Account | select-object).identity -ExtendedRight ms-Exch-EPI-May-Impersonate

Add-ADPermission -Identity ( PermissionLevel ).DistinguishedName -User (Get-User -Identity Account | select-object).identity -ExtendedRights Receive-As

where:

• PermissionLevel is determined by whether you want to grant the unified messaging services account rights to access individual servers or rights to access all Exchange 2007 servers in the organization:

– To grant the unified messaging services account rights to access individual Exchange servers, replace PermissionLevel with:

Get-ExchangeServer -Identity ServerName

where ServerName is the name of the Exchange 2007 server to which you want the unified messaging services account to have access.

– To grant the unified messaging services account rights to access all Exchange 2007 servers in the Exchange organization, replace PermissionLevel with:

Get-OrganizationConfig

For more information on the Add-ADPermission commandlet and the Identity parameter, see Exchange 2007 Help.

• Account is the name of the unified messaging services account in domain\alias format.

Step 3 If you created more than one unified messaging services account, repeat Step 2 for the remaining accounts.

Step 4 If you set permissions on individual Exchange server in Step 2 and you have more than one Exchange 2007 server, repeat Step 1 through Step 3 on the following servers:

• All other Exchange 2007 client access servers that Unity Connection can access.
• All Exchange 2007 mailbox servers that home mailboxes that you want Unity Connection to be able to access.

To Grant Unified Messaging Services Accounts the Permission to Sign In Locally for Cisco Unity Connection 8.5 (Exchange 2007 Only)

Step 1 On an Exchange 2007 client access server that Unity Connection can access, sign in using an account that is a member of the local Administrators group.

Step 2 On the Windows Start menu, select Administrative Tools > Local Security Policy.

Step 3 In the left pane, expand Local Policies, and select User Rights Assignment.

Step 4 In the right pane, right-click Allow Log on Locally, and select Properties.

Step 5 In the Allow Log on Locally Properties dialog box, on the Local Security Setting tab, select Add User or Group.

Step 6 On the Select Users, Computers, or Groups dialog box, enter the name of the unified messaging services account that you created in Task 1. of the “Task list for Creating the Unified Messaging Services Account and Granting Permissions for Unity Connection 8.5 and Later” section.

If intrasite networking or intersite networking is configured, and if you created more than one unified messaging services account, enter the names of the unified messaging services accounts for the Unity Connection servers that will access this Exchange 2007 client access server.

Step 7 Select Check Names.

Step 8 Select OK to close the Select Users, Computers, or Groups dialog box.

Step 9 Select OK to close the Allow Log on Locally Properties dialog box.

Step 10 Close Local Security Settings.

Step 11 Repeat Step 1 through Step 10 on the following servers:

• All other Exchange 2007 client access servers that Unity Connection can access.
• All Exchange 2007 mailbox servers that home mailboxes that you want Unity Connection to be able to access.

Granting Permissions to the Unified Messaging Services Account (Exchange 2003 Only)

To grant permissions to the unified messaging services account so Unity Connection can access Exchange 2003, do the following procedure.

To Grant Permissions to the Unified Messaging Services Account for Cisco Unity Connection 8.5 (Exchange 2003 Only)

Step 1 Sign in to a server on which Exchange System Manager is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant permissions on Exchange objects in the configuration container.

Step 2 On the Windows Start menu, select Programs > Microsoft Exchange > System Manager.

Step 3 In the left pane, expand Servers.

Step 4 Right-click the name of the Exchange server that contains mailboxes that will be accessed by Cisco Unity Connection, and select Properties.

Step 5 In the <Server name> Properties dialog box, select the Security tab.

Step 6 Select Add.

Step 7 In the Select Users, Computers, or Groups dialog box, in the Enter the Object Names to Select field, enter the name of the unified messaging services account.

Step 8 Select Check Names.

Step 9 Select OK to close the dialog box.

Step 10 In the <Server name> Properties dialog box, in the Group or User Names list, select the name of the unified messaging services account.

Step 11 In the Permissions For <Account name> list, check the Allow check box for the following permissions:

• Send As
• Receive As
• Administer Information Store

Step 12 Select OK to close the <Server name> Properties dialog box.

Step 13 Repeat Step 4 through Step 12 for each additional Exchange server that you want to access.

Removing EWS Limits from Exchange 2013 and Later

If any Unity Connection users who are configured for unified messaging have mailboxes in Exchange 2013(8.6(2), remove the Exchange 2013 EWS limits for the unified messaging service account by creating and applying a new mailbox policy to the target mailbox account. If you do not remove EWS limits, messages may not be synchronized, and status changes (for example, from unread to read), changes to the subject line, and changes to the priority may not be replicated. In addition, attempts to access Exchange calendars and contacts may fail.

Note Prior to Exchange 2013, the throttling limit was calculated against the calling account (in our case service account). Starting with Exchange 2013(Unity Connection 8.6(2) SU3 and later), this limit has been changed. Now the charges are counted against the target mailbox rather than the calling account.

To Remove EWS Limits from Exchange 2013 and later

Step 1 Sign in to a server on which Exchange Management Shell is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant permissions on Exchange objects in the configuration container.

Step 2 Create a new policy with unlimited EWS connections:

New-ThrottlingPolicy -Name " <ConnectionUnifiedMessagingServicesPolicy> " -EWSMaxConcurrency unlimited -EWSMaxBurst unlimited -EWSRechargeRate unlimited -EWSCutOffBalance unlimited -EWSMaxSubscriptions unlimited

where ConnectionUnifiedMessagingServicesPolicy is the name that you want to assign to the policy.

Step 3 Apply the new policy to the unified messaging services user mailbox. For each user mailbox, run the following command:

Set-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingusermailbox > " -ThrottlingPolicy " < ConnectionUnifiedMessagingServicesPolicy > "

where:

• ConnectionUnifiedMessagingusermailbox is the name of the user mailbox.
• ConnectionUnifiedMessagingServicesPolicy is the name of the policy that you created in Step 2.

Note The Set-ThrottlingPolicyAssociation command is not supported with Exchange 2010 version 14.00.0639.021. The users having Exchange 2010 with version 14.00.0639.021 are not allowed to modify an existing throttling policy settings, hence the default policy gets applied here.

Step 4 Confirm that the mailbox is using the new policy:

Get-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingusermailbox >" | findstr "ThrottlingPolicy"

Step 5 On each Exchange 2013 (Unity Connection 8.6(2) SU3 and later) server that has the CAS role, restart the Microsoft Exchange RPC Client Access service.

Removing EWS Limits from Exchange 2010 SP2 RU4 and Later

Microsoft has enabled the client throttling policy feature by default. If there is no throttling policy already configured, Microsoft Exchange applies a default policy to all users. The default throttling policy is tailored for end user's load and not for an enterprise application like, Cisco Unity Connection using impersonation. If any Cisco Unity Connection users who are configured for unified messaging have mailboxes in Exchange 2010, configure the Exchange 2010 EWS limits for the unified messaging users mailbox by creating and applying a new mailbox policy to the unified messaging user mailbox account. If you do not configure EWS limits, messages may not be synchronized, and status changes (for example, from unread to read), changes to the subject line, and changes to the priority may not be replicated. In addition, attempts to access Exchange calendars and contacts may fail.

Note After Exchange 2010 SP2 RU4, when Exchange impersonation is used, the budgets for all the throttling thresholds calculated against the account that is impersonated (target mailbox) and not the impersonating account (Unified Messaging Service Account).

Enabling the Paged View Functionality for Unity Connection Versions 8.5.1 SU6 and Later or Unity Connection Versions 8.6(2) SU4 and Later

Make sure to enable the paged view search functionality. To enable the paged view functionality for messages, you must set the value of the 'System.Messaging.MbxSynch.MbxSynchUsePaging' parameter to 1.

To Enable the Paged View Functionality, Perform the Following Steps

Step 1 Run the following CLI command:

Note When a Unity Connection cluster is configured, you can run the command on publisher or subscriber server.

Step 2 To set the maximum limit of voice messages items that can be managed by Unity Connection with the Paged view search functionality, run the following CLI command:

where, new value specifies the value of the voicemails count limit that you can view after the paging parameter is enabled. Unity Connection by default manages the first 25000 voice messages per mailbox that avoid any delay in message synchronization between Unity Connection and Exchange server. This voicemail count limit can be increased maximum up to 75000.

Removing EWS Limits from Exchange 2010 Service Pack 2 RU4 and Later

For the Unity Connection versions previous to 8.5.1 SU6 or Connection versions previous to 8.6(2) SU4, configure the EWS limits for affected unified users by following the below given steps.

Note These steps are also applicable if the paged view search functionality is disabled.

To Configure EWS Limits from Exchange 2010 Service Pack 2 RU4 and Later

Step 1 Sign in to a server on which Exchange Management Shell is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant permissions on Exchange objects in the configuration container.

Step 2 Create a new policy with the following EWS connections where Exchange mailboxes have more than 1000 messages, which includes voice messages and receipts. For Exchange mailboxes having 10000 messages, then the new throttling policy will be:

New-ThrottlingPolicy -Name " <ConnectionUnifiedMessagingServicesPolicy> " -EWSPercentTimeInCAS 300 -EWSPercentTimeInMailboxRPC 200 -EWSFindCountLimit 10000 -EWSPercentTimeinAD 100

where ConnectionUnifiedMessagingServicesPolicy is the name that you want to assign to the policy. Refer to the Table 2-5 to have detailed description on the throttling policy parameters.

Step 3 Apply the new policy to all the unified messaging user mailbox. For each user mailbox, run the following command:

Set-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingusermailbox > " -ThrottlingPolicy " < ConnectionUnifiedMessagingServicesPolicy > "

where:

• ConnectionUnifiedMessagingusermailbox is the name of the user mailbox.
• ConnectionUnifiedMessagingServicesPolicy is the name of the policy that you created in Step 2.

Step 4 Confirm that the mailbox is using the new policy:

Get-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingusermailbox >" | findstr "ThrottlingPolicy"

Step 5 On each Exchange 2010 server that has the CAS role, restart the Microsoft Exchange RPC Client Access service.

Table 2-5 Recommended Throttle Policy Parameter Values With 10000 Items in User’s Mailbox

Removing EWS Limits from Exchange 2010 SP2 RU3 and Earlier Releases

If any Unity Connection users who are configured for unified messaging have mailboxes in Exchange 2010, configure the Exchange 2010 EWS limits for the unified messaging service account by creating and applying a new mailbox policy to the unified messaging services account. If you do not configure EWS limits, messages may not be synchronized, and status changes (for example, from unread to read), changes to the subject line, and changes to the priority may not be replicated. In addition, attempts to access Exchange calendars and contacts may fail.

Note Prior to Exchange 2010 Service Pack 1, EWS limits were off by default. If you have not yet installed Service Pack 1, which turns limits on by default, we still recommend that you do the following procedure. Otherwise, when you install Service Pack 1, Unity Connection functionality will be affected.

To Configure EWS Limits from Exchange 2010 SP2 RU3 and Earlier Releases

Step 1 Sign in to a server on which Exchange Management Shell is installed. Sign in using either an account that is a member of the Enterprise Admins group or an account that has permission to grant permissions on Exchange objects in the configuration container.

Step 2 Create a new policy with unlimited EWS connections:

New-ThrottlingPolicy -Name " <ConnectionUnifiedMessagingServicesPolicy> " -EWSMaxConcurrency $null -EWSMaxSubscriptions $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSFindCountLimit $null -EWSPercentTimeinAD $null

where ConnectionUnifiedMessagingServicesPolicy is the name that you want to assign to the policy.

Step 3 Apply the new policy to the unified messaging services account and the user mailbox:

Set-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingServicesAccount > " -ThrottlingPolicy " < ConnectionUnifiedMessagingServicesPolicy > "

where:

• ConnectionUnifiedMessagingServicesAccount is the name of the account that you created in the “Creating the Unified Messaging Services Account in Active Directory and Granting Permissions for Unity Connection 8.5 and Later” section.
• ConnectionUnifiedMessagingServicesPolicy is the name of the policy that you created in Step 2.

Note The Set-ThrottlingPolicyAssociation command is not supported with Exchange 2010 version 14.00.0639.021. The users having Exchange 2010 with version 14.00.0639.021 are not allowed to modify an existing throttling policy settings, hence the default policy gets applied here.

Step 4 Confirm that the mailbox is using the new policy:

Get-ThrottlingPolicyAssociation -Identity " < ConnectionUnifiedMessagingServicesAccount >" | findstr "ThrottlingPolicy"

Step 5 If you created more than one unified messaging services account, repeat Step 3 and Step 4 for the remaining accounts.

Step 6 On each Exchange 2010 server that has the CAS role, restart the Microsoft Exchange RPC Client Access service.

Enabling the WebDav Service on Exchange 2003 Servers for Unity Connection 8.5 and Later

If you want Unity Connection to access mailboxes on Exchange 2003 servers, you need to configure Internet Information Services to allow the WebDav service. Do the following procedure.

To Enable the WebDav Service on Exchange 2003 for Cisco Unity Connection 8.5

Step 1 Sign in to a server that has access to the same Exchange 2003 servers that the Unity Connection server has access to. Use an account that is a member of the local Administrators group.

Step 2 On the Windows Start menu, select Programs > Administrative Tools > Internet Information Services (IIS) Manager.

Step 3 For the first Exchange 2003 server for which you want to confirm settings, in the left pane, expand <servername> and select Web Service Extensions.

Step 4 In the right pane, for WebDAV, check the value of the Status column:

• If the value is Allowed, skip to Step 5.
• If the value is Prohibited, select Allow.

Step 5 Repeat Step 3 and Step 4 for the other Exchange 2003 servers that you want Unity Connection to be able to access.

Step 6 Close IIS Manager.

Creating a Unified Messaging Service on Unity Connection 8.5 and Later to Access Exchange

Do the following procedure to create one or more unified messaging services.

Creating a Unified Messaging Service to Access Exchange from Unity Connection 8.5 and Later

Step 1 In Cisco Unity Connection Administration, expand Unified Messaging, then select Unified Messaging Services.

Step 2 On the Search Unified Messaging Services page, select Add New.

Step 3 Decide which options to select for the Message Action for Email and Message Action for Fax lists at the bottom of the page. (For field information, on the Help menu, select This Page.)

If you want to select Relay the Message or Accept and Relay the Message for either list, you must first configure an SMTP Smart Host on the System Settings > SMTP Configuration > Smart Host page. Unity Connection Administration will not let you save a new unified messaging configuration with those settings when no SMTP Smart Host is configured.

Step 4 On the New Unified Messaging Service page, in the Type list, select Exchange/BPOS -D.

Step 5 Check the Enabled check box to enable the service.

For information on synchronization behavior if you later disable a unified messaging service for which single inbox is enabled, see the “Disabling and Re-enabling Single Inbox Affecting the Synchronization of Unity Connection and Exchange Mailboxes” section.

Step 6 In the Display Name field, enter a descriptive name.

If you are creating more than one unified messaging service for Exchange, note that this is the name that will appear on the Users > Unified Messaging Accounts page when you configure users for unified messaging. Enter a display name that will simplify choosing the correct unified messaging service for each user.

Step 7 In the Web-Based Authentication Mode list, select the same authentication mode that you confirmed when you did the applicable procedures in the “Confirming Exchange Authentication and SSL Settings for Unity Connection 8.5 and Later” section.

Step 8 In the Web-Based Protocol list, select the same web-based protocol that you confirmed when you did the applicable procedures in the “Confirming Exchange Authentication and SSL Settings for Unity Connection 8.5 and Later” section.

Step 9 If you want Unity Connection to validate the SSL certificate from the Exchange server, check the Validate Certificates for Exchange Servers check box.

Self-signed certificates cannot be validated. If you selected HTTPS from the Web-Based Protocol list, and if you are using self-signed certificates, do not check the Validate Certificates for Exchange Servers check box. If you do check the check box, Unity Connection will not be able to access Exchange.

Step 10 In the Exchange servers section, if you want Unity Connection to access a specific Exchange server, skip to Step 11.

If you want Unity Connection to automatically find Exchange 2010 or Exchange 2007 client access servers, or Exchange 2003 servers, do the following:

a. Select Search for Exchange Servers.

b. In the Active Directory DNS Domain Name field, enter the DNS domain name of the Active Directory domain in which you want Unity Connection to begin searching for Exchange servers.

c. If you have Exchange servers in more than one Active Directory site, you can improve performance if you specify the site that contains the domain controllers that you want Unity Connection to use to find Exchange servers. In the Active Directory Site Name field, enter the name of the site.

d. Under Exchange Versions, select the versions of Exchange in which you have mailboxes that you want Unity Connection to be able to access.

e. In the Protocol Used to Communicate with Domain Controllers list, select whether Unity Connection should use LDAP or secure LDAP (LDAPS) when communicating with Active Directory to find Exchange servers.

f. If you want Unity Connection to validate the SSL certificate from Active Directory domain controllers, check the Validate Certificates for Active Directory Domain Controllers check box.

Self-signed certificates cannot be validated. If you selected LDAPS from the Protocol Used to Communicate with Domain Controllers list, and if you are using self-signed certificates, do not check the Validate Certificates for Active Directory Domain Controllers check box. If you do check the check box, Unity Connection will not be able to access domain controllers to search for Exchange servers.

g. Skip to Step 12.

Step 11 To configure Unity Connection to access a specific Exchange server, do the following:

a. Select Specify an Exchange Server.

b. In the Exchange Server field, enter the fully qualified domain name or the IP address of the Exchange server that you want Unity Connection to access. If you are entering the name of an Exchange 2013 (Unity Connection 8.6(2) SU3 and later), Exchange 2010, or Exchange 2007 CAS server, you must enter the name of a client access server.

c. In the Exchange Server Type list, select the version of Exchange installed on the server that you specified in Step b.

Step 12 In the Username and Password fields, enter the Active Directory username and password for the account that you created in the “Creating the Unified Messaging Services Account in Active Directory and Granting Permissions for Unity Connection 8.5 and Later” section.

If you specify the username in domain\username format, do not use FQDN format for the domain name.

Step 13 Under Service Capabilities, select the features that you want this unified messaging service to allow.

Note When you configure unified messaging for Unity Connection users, you can disable for an individual user any feature that you enable here. However, you cannot enable for an individual user any feature that you disable here.

For information on synchronization behavior if you later disable a unified messaging service for which single inbox is enabled, see the “Exchange Servers Communication with Unity Connection 8.5 and Later” section.

Step 14 Under Synchronize Connection and Exchange Mailboxes (Single Inbox), choose message actions for email and for fax. (For field information, on the Help menu, select This Page.)

Step 15 Select Save.

Note If you selected HTTPS in the Web-Based Protocol list, or if you selected Secure LDAP (LDAPS) in the Protocol Used to Communicate with Domain Controllers list, you cannot test the configuration until after you have uploaded SSL certificates in Task 17. of the “Task List for Configuring Unity Connection 8.5 and Later and Exchange for Unified Messaging” section because the security-related tests will fail.

Step 16 If you are configuring Unity Connection to communicate with individual Exchange servers, repeat Step 2 through Step 15 to create additional unified messaging services as explained in the Exchange Servers Communication with Unity Connection 8.5 and Later.

Uploading CA Public Certificates for Exchange and Active Directory Servers to Unity Connection 8.5 and Later

When you created unified messaging services, if you selected the option to validate certificates for Exchange servers or for Active Directory domain controllers (DCs), you must upload the public certificates from the certification authority (CA) that signed the certificates on the Exchange servers and DCs. Otherwise, Unity Connection cannot communicate with Exchange servers or with DCs to find Exchange servers, and unified messaging functionality will not work. Do the following tasks:

1. If you selected the option to validate certificates for Exchange servers, and if SSL certificates are not already installed on all of the following servers: Get and install certificates:

– Exchange 2013 (Unity Connection 8.6(2) SU3 and later) or Exchange 2010 client access servers.

– Exchange 2007 client access servers, if there are Exchange 2007 mailboxes that you want Unity Connection to be able to access.

– Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.

In addition, if you selected the option to validate certificates for Active Directory domain controllers, and if SSL certificates are not already installed on your DCs, get and install certificates.

2. If you used an external CA (for example, Verisign) to issue the SSL certificates installed on the servers listed in Task 1., and if you have the public certificates for the CA in.pem format: Save the files to a network location accessible to the Unity Connection server. Then skip to Task 6.

3. If you used Microsoft Certificate Services or Active Directory Certificate Services to issue the SSL certificates, or if you used an external CA and you do not have the public certificate for the CA in.pem format: Download and install OpenSSL or another application that can convert public certificates to.pem format. Unity Connection cannot upload public certificates in other formats.

4. If you used Microsoft Certificate Services to issue the SSL certificates: Do the “To Save the Public Certificate for Microsoft Certificate Services or Active Directory Certificate Services to a File” section.

5. If you used Microsoft Certificate Services, Active Directory Certificate Services, or an external CA, and if you do not have public certificates in.pem format: Use the application that you downloaded in Task 3. to convert the public certificate to.pem format, and save the file to a network location accessible to the Unity Connection server.

6. Upload the public certificates to the Unity Connection server. See the To Upload the Public Certificates on Unity Connection 8.5 or Later.

To Save the Public Certificate for Microsoft Certificate Services or Active Directory Certificate Services to a File

Step 1 Sign in to the server on which you installed Microsoft Certificate Services and issued SSL certificates for the following servers:

• Exchange 2013 (Unity Connection 8.6(2) SU3 and later) or Exchange 2010 client access servers.
• Exchange 2007 client access servers, if there are Exchange 2007 mailboxes that you want Unity Connection to be able to access.
• Exchange 2003 servers, if any, on which there are mailboxes that you want Unity Connection to be able to access.
• Active Directory domain controllers that the Unity Connection server might access.

Step 2 On the Windows Start menu, select Programs > Administrative Tools > Certification Authority.

Step 3 In the left pane of the Certification Authority MMC, right-click the server name, and select Properties.

Step 4 In the <servername> Properties dialog box, on the General tab, select View Certificate.

Step 5 In the Certificate dialog box, select the Details tab.

Step 6 On the Details tab, select Copy to File.

Step 7 On the Welcome to the Certificate Export Wizard page, select Next.

Step 8 On the Export File Format page, select Next to accept the default value of DER Encoded Binary X.509 (.CER).

Step 9 On the File to Export page, specify the full path of the public certificate, including a location that is accessible to the Unity Connection server, and a file name.

Step 10 Select Next.

Step 11 On the Completing the Certificate Export Wizard page, select Finish.

Step 12 Select OK three times to close a message box and two dialog boxes.

Step 13 Close the Certification Authority MMC.

Step 14 If you issued SSL certificates for all of the servers listed in Step 1 using the same installation of Microsoft Certificate Services, you are finished with this procedure. Return to the task list for this section.

If you issued SSL certificates for all of the servers listed in Step 1 using different installations of Microsoft Certificate Services, repeat Step 1 through Step 13 to get one public certificate for each instance of Microsoft Certificate Services. Then return to the task list for this section.

To Upload the Public Certificates on Unity Connection 8.5 or Later

Step 1 On the Unity Connection server, sign in to Cisco Unified Operating System Administration.

Step 2 On the Security menu, select Certificate Management.

Step 3 Select Upload Certificate.

Step 4 In the Certificate Name list, select tomcat-trust.

Step 5 Optional: Enter a description (for example, the name of the certification authority) in the Description field.

Step 6 Select Browse.

Step 7 Browse to the location where you saved the public certificates in.pem format, and select one of the converted certificates.

Step 8 Select Upload File.

Step 9 Repeat Step 3 through Step 8, but select Unity Connection-trust in the Certificate Name list.

Step 10 If you have public certificates from more than one certification authority, repeat Step 3 through Step 9 for the remaining certificates.

Testing Unified Messaging Services on Unity Connection 8.5 and Later

Do the following procedure to test one or more unified messaging services.

To Test Unified Messaging Services on Unity Connection 8.5 and Later

Step 1 In Cisco Unity Connection Administration, expand Unified Messaging, then select Unified Messaging Services.

Step 2 On the Search Unified Messaging Services page, select the service that you want to test.

Step 3 On the Edit Unified Messaging Service page, select Test.

Step 4 If the test results showed configuration problems, resolve the problems, then repeat the test.

Step 5 If you configured two or more unified messaging services, repeat Step 1 through Step 4 to test the remaining services.

Creating Unified Messaging Accounts to Link Unity Connection 8.5 and Later Users to Exchange Mailboxes

This section contains the following sections:

• Relating Unified Messaging Accounts and User Accounts for Unity Connection 8.5 and Later
• Creating Unified Messaging Accounts on Unity Connection 8.5 and Later

Relating Unified Messaging Accounts and User Accounts for Unity Connection 8.5 and Later

Unified messaging accounts tie Unity Connection users to unified messaging services. Unified messaging accounts are separate objects from user accounts:

• When you create a user account, Unity Connection does not automatically create a unified messaging account for that user.
• You can create more than one unified messaging account for a user, but a user’s unified messaging accounts cannot have overlapping features. For example, you cannot create two unified messaging accounts for the same user that both enable single inbox.

Creating multiple unified messaging accounts for a user is one way to control access to unified messaging features. For example, if you want all users to have single inbox but only a few users to have text-to-speech access to Exchange email, you can create two unified messaging services. One activates single inbox and the other activates TTS. You then create unified messaging accounts for all users to give them access to single inbox, and you create a second unified messaging account for the users who you want to have TTS.

• When you add a unified messaging account, the associated user account is updated with a reference to the unified messaging account. The user account does not contain the information on the unified messaging account.
• When you delete a user account, all unified messaging accounts for that user are also deleted. However, when you delete a unified messaging account, the corresponding user account is not deleted. The user account is updated only to remove the reference to the unified messaging account.

Creating Unified Messaging Accounts on Unity Connection 8.5 and Later

Do the following procedure to create one or more unified messaging accounts for Unity Connection users using Unity Connection Administration. You can also create large numbers of unified messaging accounts using the Bulk Administration Tool. For more information, see the “Using the Cisco Unity Connection 8.x Bulk Administration Tool” appendix in the User Moves, Adds, and Changes Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmacx/8xcucmacappa.html.

Note Each unified messaging account is associated with a user, but a unified messaging account is a separate object in the Unity Connection database. If you delete a unified messaging account, the associated user account is not deleted.

To Create Unified Messaging Accounts to Link Cisco Unity Connection 8.5 Users to Exchange Mailboxes

Step 1 In Cisco Unity Connection Administration, expand Users, then select Users.

Step 2 On the Search Users page, select the alias of a user.

Note If the user alias does not appear in the search results table, set the applicable parameters in the search fields at the top of the page, and select Search.

Step 3 On the Edit User Basics page, on the Edit menu, select Unified Messaging Accounts.

Step 4 On the Unified Messaging Accounts page, select Add New.

Step 5 On the New Unified Messaging Account page, in the Unified Messaging Service list, select the name of the service that you want to use for this user. You entered the name when you created the service in the Creating a Unified Messaging Service on Unity Connection 8.5 and Later to Access Exchange.

The display-only Service Type field should display “Exchange.” If it displays another value, choose a different unified messaging service.

Step 6 In the Account Information section, select the applicable option for the Exchange mailbox that you want to access:

• Use This Email Address —If you want to specify an Exchange mailbox different from the one associated with the corporate email address, select this option, and enter the email address (the Active Directory primary SMTP address).
• Use Corporate Email Address —If you want to use the corporate email address, select this option. (You can edit the value in the Corporate Email Address field on the Edit User Basics page.)

Note If the unified messaging service that you selected in Step 5 specifies an Exchange server (instead of automatically searching for Exchange servers), and if users are using TTS to access email in Exchange 2003, you must also select an option in the Account Information (Used Only for Exchange 2003 TTS) section and, if applicable, specify a value for the User ID field.

Step 7 The Account Information (Used Only for Exchange 2003 TTS) section is applicable only when both of the following are true:

• Users are using TTS to access email in Exchange 2003.
• The unified messaging service that you selected in Step 5 specifies an Exchange server (instead of automatically searching for Exchange servers)

Select the applicable option:

• Use Unity Connection Alias —This option is useful when the Active Directory domain alias for the user is the same as the Unity Connection user alias. Unity Connection signs into Exchange as the user using the Unity Connection user alias.
• Use User ID Provided Below —Enter the Active Directory domain alias for the user. This option is useful when the User ID setting is different from the Unity Connection user alias. Unity Connection signs into Exchange as the user using the setting in this field.

Step 8 Verify that the user has an SMTP proxy address that matches the email address that you specified in Step 6, either by entering a value for the Use This Email Address option or by choosing to use the corporate email address:

a. On the Edit menu, select SMTP Proxy Address.

b. If the SMTP Proxy Addresses page includes an entry for the email address that you specified in Step 6, skip to Step 9. Otherwise, continue with Step 8 c .

c. Select Add New.

d. Add the email address that you specified in Step 6.

e. Select Save.

Step 9 The Service Capabilities section displays the options that are enabled in the unified messaging service that you selected in Step 5. If you want to disable any of the services for this user, uncheck the corresponding check box.

You can add more than one unified messaging service for a user, but the same service capability cannot be enabled in more than one unified messaging service for the same user. This also applies to Exchange calendars and MeetingPlace: you cannot configure a user to access Exchange calendars and MeetingPlace scheduling and joining.

For information on synchronization behavior if you later disable single inbox in a unified messaging account, see the “Disabling and Re-enabling Single Inbox Affecting the Synchronization of Unity Connection and Exchange Mailboxes” section.

Step 10 Select Save.

Step 11 To check the configuration for the user, select Test. The Task Execution Results window appears with the test results.

If any part of the test fails, verify the configuration for Exchange, Active Directory, Unity Connection, and the Unity Connection user.

Step 12 Repeat Step 2 through Step 11 for all remaining users.

Testing Unified Messaging Accounts for Unity Connection 8.5 and Later

Do the following procedure to test one or more of the unified messaging accounts that you created in the “Creating Unified Messaging Accounts to Link Unity Connection 8.5 and Later Users to Exchange Mailboxes” section.

To Test User Access to Exchange for Individual Cisco Unity Connection 8.5 Users

Step 1 In Cisco Unity Connection Administration, expand Users, then select Users.

Step 2 On the Search Users page, select the alias of a user who is configured for one or more unified messaging features for Exchange.

Note If the user alias does not appear in the search results table, set the applicable parameters in the search fields at the top of the page, and select Search.

Step 3 On the Edit User Basics page, on the Edit menu, select Unified Messaging Accounts.

Step 4 Select a unified messaging account for Exchange.

Step 5 On the Edit Unified Messaging Account page, select Test.

Step 6 Review the results, resolve problems, if any, and re-run the test until no more problems are found.

Summary of the Configuration of Unified Messaging Accounts for Unity Connection 8.5 and Later

You can view a summary of the configuration for all of the unified messaging accounts on a Unity Connection server, including:

• Current status of Unity Connection configuration settings for each unified messaging account, which indicates whether consistency problems with Unity Connection settings prevent unified messaging from functioning correctly. When you select the status icon for a unified messaging account, the Unified Messaging Account page appears, and the status area of the page lists both problems and possible problems, if any.

You can also test whether a unified messaging account has connectivity with other servers using the Test Connectivity button on the Unified Messaging Account page.

• The alias of the user associated with the account. When you select the alias for a unified messaging account, the Edit Unified Messaging Account page appears, and the status area of the page lists problems and possible problems, if any.
• The display name of the user associated with the unified messaging account.
• The name of the unified messaging service that is associated with the unified messaging account. When you select the service name, the Unified Messaging Services page appears with the settings for the service.
• The current unified messaging settings for each unified messaging account.

To View a Summary of the Configuration of Unified Messaging Accounts for Cisco Unity Connection 8.5

Step 1 In Cisco Unity Connection Administration, expand Unified Messaging, then select Unified Messaging Account Status.

Step 2 To sort by the values in a column in ascending order, select the heading for the column. To sort in descending order, select the heading again.

Step 3 To display the Unified Messaging Accounts page for an account, select the icon or the value of the Alias column in the applicable row.

Step 4 To display the Unified Messaging Services page for an account, select the value of the UM Services column in the applicable row.

Testing System Configuration for Unified Messaging with Exchange on Unity Connection 8.5 and Later

You can run a Unity Connection system test that includes tests of the unified messaging configuration and that provides summary data on configuration problems, if any, for example, the number of accounts assigned to a specified unified messaging service that has configuration problems.

To Check System Configuration and Unified Messaging Configuration on Unity Connection 8.5 and Later

Step 1 In Cisco Unity Connection Administration, expand Tools, then select Task Management.

Step 2 On the Task Definitions page, select Check System Configuration.

Step 3 Select Run Now.

Step 4 Select Refresh to display links to the latest results.

Step 5 Review the results, resolve problems, if any, and re-run the Check System Configuration task until no more problems are found.

Testing Access to Exchange Calendars on Outlook

If you configured Unity Connection access to Exchange calendars, do the following procedure.

To Test Access to Exchange Calendars for Cisco Unity Connection 8.6 (2) and Later for Unified Messaging

Step 1 Sign in to Outlook.

Step 2 On the Go menu, select Calendar.

Step 3 On the File menu, select New > Meeting Request.

Step 4 Enter values in the required fields to schedule a new meeting for the current time, and invite a user who has an account on Cisco Unity Connection.

Step 5 Select Send.

Step 6 Sign in to the Cisco Unity Connection mailbox of the user that you invited to the Outlook meeting in Step 4.

Step 7 If the user account is configured for speech access, say Play Meetings.

If the user account is not configured for speech access, press 6, and then follow the prompts to list meetings.

Unity Connection reads the information about the Exchange meeting.

Resolving SMTP Domain Name Configuration Issues

When a single inbox user receives a voice message, it is synchronized from Unity Connection to Microsoft Exchange. The email address of sender/recipient has Unity Connection domain name, for example, userid@CUC-hostname. Due to this, email clients like Microsoft Outlook or IBM Lotus Notes adds the Unity Connection address as "recent contacts" in the address book. When a user replies to an email or adds recipient while composing an email, the user can enter/select the Unity Connection address, which may lead to NDR. In case you desire when the voice message is synchronized for single inbox users from Unity Connection to Exchange, the email address of sender/recipient is displayed as the corporate email address, for example, userid@corp-hostname, you must perform the following steps:

Step 1 In Cisco Unity Connection Administration, expand System Settings > SMTP Configuration, then select Smart Host.

Step 2 On the Smart Host page, in the Smart Host field, enter the IP address or fully qualified domain name of the SMTP smart host server. (Enter the fully qualified domain name of the server only if DNS is configured).

Note Microsoft Exchange server can be used as a smart host.

Step 3 Select Save.

Step 4 Configure corporate email (For example, userid@corp-hostname) address as SMTP Proxy addresses for connection users. For more information see the “SMTP Proxy Addresses in Cisco Unity Connection 8.x” section in the Setting Up Features and Functionality That Are Controlled by User Account Settings in Cisco Unity Connection 8.x chapter of User Moves, Adds, and Changes Guide for Cisco Unity Connection, available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmacx/8xcucmac040.html.

Step 5 In Cisco Unity Connection Administration, expand System Settings, then select General Configuration.

Step 6 On the General Configuration page, in the When a recipient cannot be found list, select Relay message to smart host so that if the Recipient is not found, the message will be sent to the smart host.

Step 7 Select Save.

Step 8 In Cisco Unity Connection Administration, expand Users > Edit > Message Actions. Select the Accept the message option from the Voicemail drop- down list. Make sure to select the Relay the message option from the Email, Fax, and receipt drop -down lists.

Step 9 Setup a recipient policy on Exchange Server such that the Unity Connection alias resolves to the corporate email Id.

– For Exchange 2013 (Unity Connection 8.6(2) SU3 and later) or Exchange 2010, see the following link:

http://technet.microsoft.com/en-us/library/bb232171.aspx

– For Exchange 2007, see the following link: http://technet.microsoft.com/en-us/library/bb232171(v=exchg.80).aspx.

– For Exchange 2003, see the following link:
http://support.microsoft.com/kb/822447.

– For Configuring Exchange Email Policies with Unity Connection, please see the following white paper link:
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/ps12506/ps6509/guide_c07-728014.html.