Guest

Cisco Unity Connection

System Requirements for Cisco Unity Connection Release 8.x

  • Viewing Options

  • PDF (434.6 KB)
  • Feedback

Table of Contents

System Requirements for Cisco Unity Connection Release8.x

Hardware Requirements

Supported Optional Hardware

Software Requirements

Software Requirements—Cisco Unity Connection Server

Software Requirements—Administrator Workstations

Software Requirements—User Workstations

Requirements for the Phone System Integration

Licensing Requirements

Requirements for Using Unified Messaging Features (Unity Connection 8.5 and Later Only)

Unified Messaging Requirements: Synchronizing Unity Connection and Exchange Mailboxes (Single Inbox) (Unity Connection 8.5 and Later Only)

Unified Messaging Requirements: SpeechView Transcriptions (Unity Connection 8.5 and Later Only)

Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.5 and Later Only)

Unified Messaging Requirements: Accessing Calendar Information for Meetings (Connection 8.5 and Later Only)

Unified Messaging Requirements: Accessing Exchange Contact Information (Connection 8.5 and Later Only)

Requirements for Using Voice-Recognition Features

Requirements for Using SpeechView Transcriptions (Unity Connection 8.0 Only)

Requirements for Accessing the Unity Connection Web Tools Through the Cisco PCA

Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Web Inbox (Unity Connection 8.5 and Later)

Requirements for Accessing Voice Messages by Using Cisco Unity Connection ViewMail for IBM Lotus Notes

Requirements for Accessing Voice Messages by Using Cisco Unity Connection ViewMail for Microsoft Outlook 8.0(1)

Requirements for Accessing Voice Messages by Using Cisco ViewMail for Microsoft Outlook 8.5 and Later

Requirements for Accessing Unity Connection Voice Messages by Using an IMAP Email Client

Requirements for Accessing Unity Connection Voice Messages by Using Cisco Unified Personal Communicator

Requirements for Accessing Unity Connection Voice Messages by Using Cisco Mobile and Cisco Unified Mobile Communicator

Requirements for Accessing Unity Connection Voice Messages by Using Cisco Unified Messaging with IBM Lotus Sametime

Requirements for Accessing Unity Connection Voice Messages by Using Visual Voicemail

Requirements for Accessing Unity Connection Voice Messages by Using RSS Readers

Requirements for Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.0 Only)

Requirements for Accessing Calendar Information for Meetings (Unity Connection 8.0 Only)

Requirements for Accessing Exchange Contact Information (Unity Connection 8.0 Only)

Requirements for Cisco Unity Connection Phone View

Requirements for a Cisco Fax Server Integration

Requirements for an LDAP Directory Integration

Requirements for a Cisco Unity Connection 8.x Cluster

Unity Connection Cluster Requirements When the Servers Are Installed in the Same Building or Site

Unity Connection Cluster Requirements When the Servers Are in Separate Buildings or Sites

Requirements for Cisco Unity Connection Networking

Requirements for Intrasite Networking

Requirements for Intersite Networking

Requirements for Using Single Sign-On Feature (Unity Connection 8.6 and later Only)

Requirements for VPIM Networking

Requirements for Using a Provisioning Application

Requirements for Migrating from Cisco Unity Connection1.x to Version8.x

Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity Connection Version8.x By Using a Flash Cutover

Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version8.x By Using a Gradual Migration

Requirements for Installing Cisco Unity Connection on a Virtual Machine

Directory Object Limits for Cisco Unity Connection 8.x

Available Languages for Cisco Unity Connection 8.x Components

Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection 8.x

Survivable Remote Site Voicemail

System Requirements for Cisco Unity Connection Release 8.x

Revised August 28, 2014 (Originally published February 11, 2010)

This document lists requirements for a Cisco Unity Connection version 8.x system. It contains the following sections:

Hardware Requirements

Revised November 16, 2010


Caution If you try to install version 8.x on an unsupported platform, Cisco Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program. See the server-specific table in the “Cisco Unity Connection Supported Servers” section of the Cisco Unity Connection 8.x Supported Platforms List to verify platform specifications, particularly regarding memory and processor speed.

  • If you are upgrading from an earlier version of Unity Connection or migrating from Cisco Unity to Unity Connection 8.x, you may need replace the existing server, or add memory and/or replace hard disks for the installation to complete successfully and for Unity Connection to function properly. For information on whether your current server is supported for Unity Connection 8.x and, if so, whether you need to upgrade the hardware, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List .
  • If you are adding features, for example, Cisco Unity Connection Networking, a Unity Connection cluster, or single inbox, you may need to replace hard disks or add memory to the Unity Connection server for the feature to be supported. For more information, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List :

Supported Optional Hardware

The following optional hardware is supported for use with Cisco Unity Connection 8.x:

  • HP StorageWorks DAT 72 USB Tape Drive, for backup
  • HP StorageWorks Ultrium 448 Tape Drive, for backup

Software Requirements

This section contains the following information:

Software Requirements—Cisco Unity Connection Server

Cisco Unity Connection software and any required third-party software are installed by Cisco Unity Connection Setup.

Software Requirements—Administrator Workstations

Revised May 14, 2014

 

  • To access web applications on the Cisco Unity Connection server, the operating system and web browser must be compatible with the version of Unity Connection that you are installing. Table 1 lists supported operating-system and browser combinations.

 

Table 1 Supported Operating Systems and Browsers on Administrator Workstations for Cisco Unity Connection 8.x

Operating System
on Administrator Workstation
Browser on Administrator Workstation

Microsoft Windows Vista

  • Microsoft Internet Explorer 8.0 and 7.0
  • Mozilla Firefox 3.0 and 2.0
  • Microsoft Windows Server 2003
  • Microsoft Windows XP
  • Microsoft Internet Explorer 8.0
  • Microsoft Internet Explorer 7.0 and 6.0 (plus SP1)
  • Mozilla Firefox 3.0 and 2.0

Mac OS X 10.4 and later

Mozilla Firefox 3.0 and 2.0

Red Hat Enterprise Linux

Mozilla Firefox 3.0 and 2.0

Microsoft Windows 7

(32 and 64 bit)

  • Microsoft Internet Explorer 8.0, 9.0(1) and 10.0
  • Mozilla Firefox 3.6, 10

Microsoft Windows 81
(32-bit and 64-bit)

  • Standard
  • Professional
  • Enterprise
  • Microsoft Internet Explorer 10.0
  • Mozilla Firefox 17

1.Windows 8 in the Desktop Mode.


NoteCisco Unity Connection Web Interface drop down menus: Cisco Unity Connection Administration(CUCA) and Cisco Personal Communications Assistant(CPCA) are not supported for Google Chrome.


  • Table 2 lists software required for correct browser configuration.
  • Table 2 Software Required for Correct Browser Configuration on Administrator Workstations for Cisco Unity Connection 8.x

     

    Browser
    Required Software

    Firefox

    The following software, depending on the operating system:

    • With Mac OS X:

    Java Runtime Environment 7 update 51.

    • With Linux:

    ALSA driver version 1.0.9 or later

    Java Runtime Environment 7 update 51.

    • With Windows:

    Java Runtime Environment 7 update 51.

    Internet Explorer

    Java Runtime Environment 7 update 51.


NoteCisco Unity Connection Web Interface drop down menus: Cisco Unity Connection Administration(CUCA) and Cisco Personal Communications Assistant(CPCA) are not supported with Google Chrome.


Software Requirements—User Workstations

Revised May 14, 2014

  • The operating system and Internet browser(s) on user workstations must be compatible with the version of Unity Connection that you are installing, to allow users to access the Unity Connection web tools through the Cisco Personal Communications Assistant. See the Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .
  • If you are using Cisco Unity Connection ViewMail for Microsoft Outlook, the ViewMail version must be compatible with the version of Unity Connection that you are installing. See the Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations .
  • If you are using Cisco Unity Connection ViewMail for IBM Lotus Notes, the ViewMail version must be compatible with the version of Unity Connection that you are installing. See the Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations .
  • If you are using an IMAP email application to access Unity Connection voice messages, the email application must be compatible with the version of Unity Connection that you are installing. See the Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations .
  • Table 3 lists software required for correct browser configuration, depending on the browser(s) installed on the user workstation.

 

Table 3 Software Required for Correct Browser Configuration on User Workstations for Cisco Unity Connection 8.x

Browser
Required Software

Firefox

The following software, depending on the operating system:

  • With Mac OS X:

Java Runtime Environment 7 update 51.

  • With Linux:

ALSA driver version 1.0.9 or later

Java Runtime Environment 7 update 51.

  • With Windows:
  • Java Runtime Environment 7 update 51.

Internet Explorer

Java Runtime Environment 7 update 51.

Safari

Java Runtime Environment 7 update 51.

Requirements for the Phone System Integration

Cisco Unity Connection can be integrated with Cisco Unified Communications Manager and Cisco Unified Communications Manager Express.

In addition, Cisco Unified CM integrations with Unity Connection support the use at remote sites of Cisco Unified CM Express in Survivable Remote Site Telephony (SRST) mode or of SRST installed on Cisco IOS platforms.

For supported versions of Cisco Unified CM and Cisco Unified CM Express, see the applicable document, depending on the integration type:

Unity Connection can also be integrated with other supported phone systems and with multiple phone systems simultaneously. For information on other supported phone systems, see the applicable Cisco Unity Connection integration guides at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html .

Licensing Requirements

Added November 16, 2010

Table 4 lists Unity Connection features, indicates whether the features require license tags for which there is a fee, and indicates whether the features are enabled in the default license file (for a demonstration system) that is included on the Unity Connection DVD.

 

Table 4 Licensing Requirements

Feature
Paid Unity Connection License Tag Required
Enabled in Default (Demo) License File

Synchronization of Unity Connection and Exchange mailboxes (single inbox)

None

Yes

Calendar information for meetings

None

Yes

Exchange contact information

None

Yes

Text to speech

None

Yes

SpeechView transcriptions

SpeechView User

No

Voice-recognition features

None

Yes

Clusters

None

Yes

Intrasite/intersite networking

None

Yes

VPIM networking

None

Yes

Languages

None

Yes

Personal call transfer rules

None

Yes

Maximum number of users with Unity Connection mailboxes

LicSubscribersMax

10

Maximum number of users with IMAP or Single Inbox access to voice messages

LicIMAPSubscribersMax

10

Ports

None

2

Maximum recording length

None (limited by system configuration)

30 seconds

TTS sessions

None (depends on the server)

2

Voice-recognition sessions

None (depends on the server)

2

User Interfaces Used to Access Unity Connection Voice Messages

Phone interface (TUI)

None

Yes

Cisco Unity Connection Messaging Inbox (in 8.0)

None

Yes

Cisco Unity Connection Web Inbox (in 8.5)

None

Yes

Cisco Unity Connection ViewMail for IBM Lotus Notes

ViewMail for Lotus Notes

No

Cisco Unity Connection ViewMail for Microsoft Outlook 8.0

None

Yes

Cisco ViewMail for Microsoft Outlook 8.5

None

Yes

IMAP email client

None

Yes

Cisco Unified Personal Communicator

None

Yes

Cisco Mobile and Cisco Unified Mobile Communicator

None

Yes

Cisco Unified Messaging with IBM Lotus Sametime

None

Yes

Visual Voicemail

None

Yes

RSS readers

None

Yes

Cisco Unity Connection Phone View

None

Yes

Requirements for Using Unified Messaging Features (Unity Connection 8.5 and Later Only)

Revised December 16, 2010

See the applicable section:

Unified Messaging Requirements: Synchronizing Unity Connection and Exchange Mailboxes (Single Inbox) (Unity Connection 8.5 and Later Only)

Revised August 28, 2014

  • Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:

Exchange Server 2013 with Cumulative Update 5 and earlier.

Exchange Server 2010 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2010 with Service Pack 2 (All editions are supported.)

Exchange Server 2010 with Service Pack 1 Update Rollup 3 or later (All editions are supported.)

Exchange Server 2010 with Service Pack 1 (All editions are supported.)

Exchange Server 2007 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)

To synchronize Unity Connection and Exchange 2007 mailboxes, you must install Unity Connection 8.5(1) Service Update 1 (SU 1) or later.

Exchange Server 2003 with Service Pack 2 (All editions are supported.)

To synchronize Unity Connection and Exchange 2003 mailboxes, you must install Unity Connection 8.5(1) Service Update 1 (SU 1) or later.

Connection single inbox feature with Exchange 2003 requires WebDav interface to work properly. If Form Based Authentication option is enabled, WebDav interface can break the access to Exchange sever, therefore, it is not recommended to use single Inbox.

With Exchange 2003, Connection's Single Inbox feature requires WebDav interface to function properly. Due to a limitation documented by Microsoft, 'Forms Based Authentication' may disrupt WebDav and hence is not recommended to be used with Single Inbox feature.

  • Microsoft Business Productivity Online Suite (BPOS-Dedicated) is now supported in Cisco Unity Connection 8.5(1) SU 1 .You can configure Unity Connection to synchronize voice messages in Unity Connection user's mailbox with the user's Exchange mailbox configured on Microsoft Business Productivity Online Suite (BPOS-Dedicated) environments as well as other third party hosted dedicated Exchange environments. For more information on Unity Connection's integration with Microsoft BPOS Dedicated environments, see the “Cisco Unity Connection 8.x Overview” chapter of the Design Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdgx.html .
  • Microsoft Office 365 is now supported with Cisco Unity Connection 8.6(2) and later. It is a cloud hosted collaboration solution provided by Microsoft. Using Microsoft Office 365, you can access emails and calendars anywhere. For more information on Unity Connection integration with Microsoft Office-365, see the "Configuring Cisco Unity Connection 8.6(2) and Microsoft Office-365 for Unified Messaging" chapter of the Unified Messaging Guide for Cisco Unity Connection at

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx.html .

  • Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
  • The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
  • Exchange clusters are supported.
  • To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Unity Connection supports a maximum of 20 unified messaging services per Unity Connection server.
  • Depending on the number of voice messaging ports on each Unity Connection server, the path of connectivity must have the following guaranteed bandwidth with no steady-state congestion:

For 50 voice messaging ports on each server—7 Mbps

For 100 voice messaging ports on each server—14 Mbps

For 150 voice messaging ports on each server—21 Mbps

For 200 voice messaging ports on each server—28 Mbps

For 250 voice messaging ports on each server—35 Mbps

The bandwidth numbers above are intended as guidelines to ensure proper operation of mailbox synchronization. For information on bandwidth requirements for Unity Connection clusters, see the “Requirements for a Cisco Unity Connection 8.x Cluster” section. Additional conditions such as network congestion, CPU utilization, and message size may contribute to lower throughput than expected. Call-control and call-quality requirements are in addition to the guidelines above and should be calculated by using the bandwidth recommendations in the applicable Cisco Unified Communications SRND at http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns818/landing_uc_mgr.html .

  • The default Unity Connection configuration is sufficient for a maximum of 2000 users and 80 milliseconds of round-trip latency between Unity Connection and Exchange servers. For more than 2000 users and/or more than 80 milliseconds of latency, you can change the default configuration. For more information, see the “ Latency” section in the “Single Inbox in Cisco Unity Connection 8.5 and Later” chapter of the Design Guide for Cisco Unity Connection Release 8.x . at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdgx.html .
  • Users must be assigned to a class of service that is enabled for using single inbox.
  • For each user configured for single inbox, an email client that is configured to access the user’s Exchange mailbox. For full single-inbox functionality, we recommend that you use Microsoft Outlook and install Cisco ViewMail for Microsoft Outlook. ViewMail for Outlook is required to:

Review secure Unity Connection voice messages by using Outlook.

Compose, reply to, or forward synchronized voice messages by using Outlook.

Other email clients can be used to access Unity Connection voice messages in Exchange, but users will not have the functionality provided by ViewMail for Outlook.

For information on Unity Connection support for Outlook, see the “Requirements for Accessing Voice Messages by Using Cisco ViewMail for Microsoft Outlook 8.5 and Later” section.

  • For users who are configured for single inbox and SpeechView transcriptions, the message in Exchange is not updated with the transcribed text. You can configure Unity Connection to send a notification message that contains the transcription.
  • When message expiration and single inbox are configured, the .wav file is not deleted from the message in Exchange. Voice messages in Unity Connection are still removed from user mailboxes and are replaced with a recording that tells the user “This message is expired.”

Unified Messaging Requirements: SpeechView Transcriptions (Unity Connection 8.5 and Later Only)

The SpeechView feature—which provides transcriptions of voice messages—is supported with Cisco Unity Connection version 8.5 and later.

  • Users must have SpeechView User licenses.
  • Users must be assigned to a class of service enabled for using SpeechView transcriptions of voice messages.

For Unity Connection 8.0 requirements, see the “Requirements for Using SpeechView Transcriptions (Unity Connection 8.0 Only)” section.


Note In Cisco Unity Connection 8.6(2) and later, you need to install different licenses for both standard and professional SpeechView transcription service.


Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.5 and Later Only)

Revised August 28, 2014

  • Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:

Exchange Server 2013 with Cumulative Update 5 and earlier.

Exchange Server 2010 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2010 with Service Pack 2 (All editions are supported.)

Exchange Server 2010 with Service Pack 1 Update Rollup 3 or later (All editions are supported.)

Exchange Server 2010 with Service Pack 1 (All editions are supported.)

Exchange Server 2007 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)

Exchange Server 2003 with Service Pack 2 (All editions are supported.)

Microsoft Business Productivity Online Suite is not supported.

  • Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
  • The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
  • Exchange clusters are supported.
  • To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Unity Connection supports a maximum of 20 unified messaging services per Unity Connection server.
  • Microsoft Office 365 emails configured with Unity Connection are supported.

For Unity Connection 8.0 requirements, see the “Requirements for Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.0 Only)” section.

Unified Messaging Requirements: Accessing Calendar Information for Meetings (Connection 8.5 and Later Only)

Revised August 28, 2014

Cisco Unity Connection integrated with a supported application for calendar information:

  • Cisco Unified MeetingPlace 8.0. Other versions of MeetingPlace are not supported, and Cisco Unified MeetingPlace Express is not supported.

NoteA Connection user configured with Microsoft Exchange calendars cannot configure Cisco Unified MeetingPlace at the same time.


  • When accessing Exchange calendars, Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:

Exchange Server 2013 with Cumulative Update 5 and earlier.

Exchange Server 2010 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2010 with Service Pack 2 (All editions are supported.)

Exchange Server 2010 with Service Pack 1 Update Rollup 3 or later (All editions are supported.)

Exchange Server 2010 with Service Pack 1 (All editions are supported.)

Exchange Server 2007 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)

Exchange Server 2003 with Service Pack 2 (All editions are supported.)

Microsoft Business Productivity Online Suite is not supported.

  • Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
  • The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
  • Exchange clusters are supported.
  • To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Unity Connection supports a maximum of 20 unified messaging services per Unity Connection server.
  • Microsoft Office 365 calendars configured with Unity Connection are supported.

For Unity Connection 8.0 requirements, see the “Requirements for Accessing Calendar Information for Meetings (Unity Connection 8.0 Only)” section.

Unified Messaging Requirements: Accessing Exchange Contact Information (Connection 8.5 and Later Only)

Revised August 28, 2014

Exchange contacts can be imported into Cisco Unity Connection, allowing users to place outgoing calls by using voice commands and to create personal call transfer rules based on the contact information.

  • Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:

Exchange Server 2013 with Cumulative Update 5 and earlier.

Exchange Server 2010 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2010 with Service Pack 2 (All editions are supported.)

Exchange Server 2010 with Service Pack 1 Update Rollup 3 or later (All editions are supported.)

Exchange Server 2010 with Service Pack 1 (All editions are supported.)

Exchange Server 2007 with Service Pack 3 (Unity Connection8.6(2) SU 3 and later only)

Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)

Exchange Server 2003 with Service Pack 2 (All editions are supported.)

Microsoft Business Productivity Online Suite is not supported.

  • Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
  • The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
  • Exchange clusters are supported.
  • To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Unity Connection supports a maximum of 20 unified messaging services per Unity Connection server.
  • Microsoft Office 365 contacts configured with Unity Connection are supported.

For Unity Connection 8.0 requirements, see the “Requirements for Accessing Exchange Contact Information (Unity Connection 8.0 Only)” section.

Requirements for Using Voice-Recognition Features

Revised April 29, 2011

  • Users must be assigned to a class of service enabled for using voice recognition.
  • Phone systems must be configured to send calls to Unity Connection in any of the supported audio codecs except G729a. The G.729a audio codec is not supported with the voice-recognition features.

Note Remote Message Monitor is only supported if all end points (incoming, Unity, and outgoing) are using the same codec.


Requirements for Using SpeechView Transcriptions (Unity Connection 8.0 Only)

The SpeechView feature—which provides transcriptions of voice messages—is supported with Cisco Unity Connection version 8.0(2) and later.

  • Users must have SpeechView User licenses.
  • Users must be assigned to a class of service enabled for using SpeechView transcriptions of voice messages.

For Unity Connection 8.5 requirements, see the “Unified Messaging Requirements: SpeechView Transcriptions (Unity Connection 8.5 and Later Only)” section.

Requirements for Accessing the Unity Connection Web Tools Through the Cisco PCA

Messaging Assistant web tool

Messaging Inbox web tool (Unity Connection 8.0 Only)

Personal Call Transfer Rules web tool

  • Cisco Unity Connection must be integrated with a supported version of the Cisco Unified Communications Manager phone system. (Cisco Unified Communications Manager Express is not supported.)
  • Users must be assigned to a class of service enabled for using the Personal Call Transfer Rules web tool.
  • A supported operating system and web browser(s) on user workstations. See Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .

Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Web Inbox (Unity Connection 8.5 and Later)

Revised December 20, 2010

  • Users must have Inbox User licenses.
  • Users must be assigned to a class of service enabled for using the Web Inbox and RSS feeds.
  • Adobe Flash Player version 10 or later on user workstations.
  • QuickTime version 7 or later on user workstations.
  • A supported operating system and web browser(s) on user workstations. See Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .

Requirements for Accessing Voice Messages by Using Cisco Unity Connection ViewMail for IBM Lotus Notes

  • A ViewMail for Lotus Notes license installed on the Cisco Unity Connection server. (Without the license on the server, ViewMail for Notes installed on user workstations provides all features and functionality for 30 days in demo mode, and then stops.)
  • Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.
  • Users must have email accounts in Notes configured to access Connection voice messages.
  • A ViewMail for Notes version supported for use with the Notes version and operating system on user workstations. See Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .

For workstation and other software-related requirements, and for installation and upgrade information, see Release Notes for Cisco Unity Connection ViewMail for IBM Lotus Notes at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

Requirements for Accessing Voice Messages by Using Cisco Unity Connection ViewMail for Microsoft Outlook 8.0(1)

Revised November 16, 2010

  • Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.
  • Users must have email accounts in Outlook configured to access Connection voice messages.
  • A ViewMail for Outlook version supported for use with the Outlook version and operating system on user workstations. See Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .

For workstation and other software-related requirements, and for installation and upgrade information, see Release Notes for Cisco Unity Connection ViewMail for Microsoft Outlook Release 8.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/vmo/release/notes/801cucvmorn.html .

Requirements for Accessing Voice Messages by Using Cisco ViewMail for Microsoft Outlook 8.5 and Later

Revised February 10, 2011

  • IMAP users only: Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.
  • IMAP users only: Users must have email accounts in Outlook configured to access Connection voice messages.
  • Single-inbox users only: Users must have Exchange email accounts in Outlook pointing to their Exchange mailboxes.
  • Cisco Unity users only: Users must have email accounts in Outlook configured to access Cisco Unity voice messages.
  • A ViewMail for Outlook version supported for use with the Outlook version and operating system on user workstations. See Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html .

For workstation and other software-related requirements, and for installation and upgrade information, see Release Notes for Cisco ViewMail for Microsoft Outlook at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

Requirements for Accessing Unity Connection Voice Messages by Using an IMAP Email Client

Requirements for Accessing Unity Connection Voice Messages by Using Cisco Unified Personal Communicator

For workstation, system, and other software-related requirements, see the applicable Release Notes for Cisco Unified Personal Communicator at http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html .

Cisco Unified Personal Communicator 8.x and 7.x support secure messaging with Cisco Unity Connection 8.x.

Cisco Unified Personal Communicator versions 8.0 and later support IMAP IDLE.

Requirements for Accessing Unity Connection Voice Messages by Using Cisco Mobile and Cisco Unified Mobile Communicator

  • Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.

For a list of the mobile phones that Cisco Unified Mobile Communicator supports, see the applicable release notes at http://cisco.com/en/US/products/ps7270/prod_release_notes_list.html .


NoteCisco Unified Mobility Advantage does not support IMAP IDLE. As a result, each active instance of Cisco Mobile or Cisco Unified Mobile Communicator that is accessing Connection voice messages counts as four simultaneous connections. For information on the maximum number of connections supported on specific Unity Connection servers, see theCisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html.


Requirements for Accessing Unity Connection Voice Messages by Using Cisco Unified Messaging with IBM Lotus Sametime

For workstation and other software-related requirements, and for installation and upgrade information, see the applicable Release Notes for Cisco Unified Messaging with IBM Lotus Sametime at http://www.cisco.com/en/US/products/ps9830/prod_release_notes_list.html .

Cisco Unified Messaging with Lotus Sametime 8.x and 7.x support secure messaging with Cisco Unity Connection 8.x.


NoteCisco Unified Messaging with Lotus Sametime 8.x and 7.x support IMAP IDLE. However, Cisco Unified Messaging with Lotus Sametime version 1.2(3) does not support IMAP IDLE. As a result, each active instance of Cisco Unified Messaging with Lotus Sametime that is accessing Connection voice messages counts as four simultaneous connections. For information on the maximum number of connections supported on specific Unity Connection servers, see theCisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html.


Requirements for Accessing Unity Connection Voice Messages by Using Visual Voicemail

Revised May 3, 2010

  • A supported Cisco Unified IP Phone model. (See the “Cisco Unified IP Phone Requirements” section under “System Requirements” in the Release Notes for Visual Voicemail .)

For server and phone firmware requirements, and other information about using Visual Voicemail, see the applicable Release Notes for Visual Voicemail at http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html .

Requirements for Accessing Unity Connection Voice Messages by Using RSS Readers

  • Users must be assigned to a class of service enabled for using the Messaging Inbox and RSS feeds.
  • Sound card, speakers, and media player on user workstations.

Requirements for Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.0 Only)

  • Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:

Exchange Server 2007 (All editions are supported.)

Exchange Server 2003 with Service Pack 1 or later (All editions are supported.)

  • Exchange server(s) in a supported Windows domain configuration. Table 5 lists the supported configurations.

 

Table 5 Supported Exchange and Windows Domain Configurations

Exchange Configuration
Supported Windows Domain Configurations

One server running
Exchange Server 2007

  • Exchange server is a Windows Server 2003, 2008, or 2012 domain controller/global catalog server.
  • Exchange server is a Windows Server 2003, 2008, or 2012 member server.

One server running
Exchange Server 2003

  • Exchange server is a Windows Server 2000, 2003, or 2008 domain controller/global catalog server.
  • Exchange server is a Windows Server 2000, 2003, or 2008 member server.
  • The Cisco Unity Connection server and the Exchange server(s) must be located in the same local-area network.

For Unity Connection 8.5 requirements, see the “Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech (Unity Connection 8.5 and Later Only)” section.

Requirements for Accessing Calendar Information for Meetings (Unity Connection 8.0 Only)

Revised July 7, 2010

Cisco Unity Connection integrated with a supported application for calendar information:

  • Cisco Unified MeetingPlace 8.0 and 7.0
  • Cisco Unified MeetingPlace Express 2.0 Microsoft Exchange Server 2003 with Service Pack 1 or later (All editions are supported.)

For Unity Connection 8.5 requirements, see the “Unified Messaging Requirements: Accessing Calendar Information for Meetings (Connection 8.5 and Later Only)” section.

Requirements for Accessing Exchange Contact Information (Unity Connection 8.0 Only)

Exchange contacts can be imported into Cisco Unity Connection, allowing users to place outgoing calls by using voice commands and to create personal call transfer rules based on the contact information.

  • Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server is required:

Exchange Server 2007 (All editions are supported.)

Exchange Server 2003 with Service Pack 1 or later (All editions are supported.)

For Unity Connection 8.5 requirements, see the “Unified Messaging Requirements: Accessing Exchange Contact Information (Connection 8.5 and Later Only)” section.

Requirements for Cisco Unity Connection Phone View

  • Cisco Unity Connection integrated with a supported version of the Cisco Unified Communications Manager phone system. For supported versions, see the applicable document, depending on the integration type:

SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html .

SIP Trunk Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucsiptrunkmtx.html .

  • A supported Cisco Unified IP Phone model, with the supported Cisco Unified Communications Manager version firmware installed. The following IP Phone models are supported: 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE.

Requirements for a Cisco Fax Server Integration

Revised June 2, 2011

  • Cisco Fax Server version 9.x (available from Cisco until May 2011)
  • OpenText Fax Server, RightFax Edition, version 9.x and later.
  • Sagemcom Xmedius Fax SP version 6.5.5.

Requirements for an LDAP Directory Integration

Revised June 17, 2013

  • Cisco Unity Connection integrated with a supported LDAP directory. Table 6 lists supported directories and the Unity Connection version(s) with which they are supported.

The last column in the table indicates whether an LDAP directory supports specifying additional LDAP directory servers to act as backup in case the LDAP directory servers that Unity Connection accesses for synchronization and for authentication become unavailable.

 

Table 6 LDAP Directories Supported for Synchronization and Authentication

Supported LDAP Directory
Supports Redundant
Directory Servers

Microsoft Active Directory 2008 and Active Directory 2008 R2

Yes

Microsoft Active Directory 2008 Lightweight Directory Services

Yes

Microsoft Active Directory 2003

Yes

Microsoft Active Directory Application Mode (Windows Server 2003 and Windows XP Professional)

Yes

OpenLDAP 2.3.39 and 2.4

Yes

Sun iPlanet Directory Server 5.1 and later

No

Oracle Directory Server Enterprise Edition 11g (formerly Sun ONE Directory Server)

No

  • When you are using Active Directory, you can integrate a single Unity Connection server with more than one user search base, but all user search bases must be in the same Active Directory forest. To integrate Unity Connection with more than one forest, you must install one digitally networked Unity Connection server per forest.
  • When you are configuring Unity Connection for Microsoft Active Directory 2008 Lightweight Directory Services, choose the “Microsoft Active Directory Application Mode” option in Cisco Unity Connection Administration.
  • When you are using a Sun iPlanet or Oracle Directory Server Enterprise Edition 11g, you can integrate a single Unity Connection server with more than one user search base, but all user search bases must be in the same tree. To integrate Unity Connection with more than one tree, you must install one digitally networked Connection server per tree.

Requirements for a Cisco Unity Connection 8.x Cluster

See the applicable section:

Unity Connection Cluster Requirements When the Servers Are Installed in the Same Building or Site

Revised April 18, 2013

The specifications for the physical server and the virtual machine should match as closely as possible for available hard-disk space/vDisk space and for RAM/vRAM.

When the hard disks in the physical server and the virtual hard disks in the virtual machine are not the same size, the smaller disks determine the amount of disk space available for voice messages.

When the number of users supported for the physical server and the virtual machine do not match, only the smaller number of users is supported for the cluster.

With Platform Overlay 1 servers, you must add 2 GB of RAM to the physical server so the amount of RAM in the physical server matches the 6 GB of vRAM configured for Unity Connection on the virtual machine.


Note In case of performing any troubleshooting steps, the Cisco support personnel may request for the additional RAM as required.


  • Both Unity Connection servers must be collocated.
  • Both Unity Connection servers must be located in the same local-area network.
  • Both Unity Connection servers must have a minimum 100 Mbps connection to the network.
  • The maximum round-trip latency must be no more than 10 ms. A fixed network latency of 5 ms or less is a best practice.
  • The network must use the following load-balancing techniques for connections to the Connection servers:

The Unity Connection servers are assigned a common DNS name with the Unity Connection publisher server first.

All user client and administrator sessions connect to the Unity Connection publisher server. If the Unity Connection publisher server stops functioning, the user client and administrator sessions must connect to the Unity Connection subscriber server.

Phone systems must attempt to route incoming calls to the Unity Connection subscriber server. If no voice messaging ports are available to answer calls on the Unity Connection subscriber server, the phone systems must route calls to the Unity Connection publisher server.

  • The Unity Connection servers must not be separated by a firewall.
  • Both Unity Connection servers must have the same software and engineering-special versions installed.
  • Both Unity Connection servers must have the same enabled features and configurations.
  • Both Unity Connection servers must connect to the same phone system(s).
  • If the Unity Connection servers contain dual NICs, the two NICs on each Unity Connection server must be configured for fault tolerance using a single IP address, or one of the NICs must be disabled. Configuring the two NICs with distinct IP addresses for network load balancing is not supported.
  • For selected servers supported for earlier versions of Unity Connection, a memory upgrade. To determine whether your server requires a memory upgrade, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List.
  • For selected servers supported for earlier versions of Unity Connection, replacement hard disks. To determine whether your server requires hard-disk replacement, see the applicable server-specific table in the Cisco Unity Connection 8. Supported Platforms List.

NoteThe Unity Connection cluster feature is not supported for use with Cisco Unified Communications Manager Business Edition.


Unity Connection Cluster Requirements When the Servers Are in Separate Buildings or Sites

Revised April 18, 2013

The specifications for the physical server and the virtual machine should match as closely as possible for available hard-disk space/vDisk space and for RAM/vRAM.

When the hard disks in the physical server and the virtual hard disks in the virtual machine are not the same size, the smaller disks determine the amount of disk space available for voice messages.

When the number of users supported for the physical server and the virtual machine do not match, only the smaller number of users is supported for the cluster.

With Platform Overlay 1 servers, you must add 2 GB of RAM to the physical server so the amount of RAM in the physical server matches the 6 GB of vRAM configured for Unity Connection on the virtual machine.


Note In case of performing any troubleshooting steps, the Cisco support personnel may request for the additional RAM as required.


  • Depending on the number of voice messaging ports on each Unity Connection server, the path of connectivity must have the following guaranteed bandwidth with no steady-state congestion:

For 50 voice messaging ports on each server—7 Mbps

For 100 voice messaging ports on each server—14 Mbps

For 150 voice messaging ports on each server—21 Mbps

For 200 voice messaging ports on each server—28 Mbps

For 250 voice messaging ports on each server—35 Mbps


Note The bandwidth numbers above are intended as guidelines to ensure proper operation of an active-active cluster with respect to synchronization traffic between the two servers. Additional conditions such as network congestion, CPU utilization, and message size may contribute to lower throughput than expected. Call-control and call-quality requirements are in addition to the guidelines above and should be calculated by using the bandwidth recommendations in the applicable Cisco Unified Communications SRND at http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns818/landing_uc_mgr.html.


  • The maximum round-trip latency must be no more than 150 ms.
  • The network must use the following load-balancing techniques for connections to the Connection servers:

The Unity Connection servers are assigned a common DNS name with the Unity Connection publisher server first.

All user client and administrator sessions connect to the Unity Connection publisher server. If the Unity Connection publisher server stops functioning, the user client and administrator sessions must connect to the Unity Connection subscriber server.

Phone systems must attempt to route incoming calls to the Unity Connection subscriber server. If no voice messaging ports are available to answer calls on the Unity Connection subscriber server, the phone systems must route calls to the Unity Connection publisher server.

  • The TCP and UDP ports of the firewall must be open as listed in the “IP Communications Required by Cisco Unity Connection 8.x” chapter of the Security Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/security/guide/8xcucsecx.html .
  • Both Unity Connection servers must have the same software and engineering-special versions installed.
  • Both Unity Connection servers must have the same enabled features and configurations.
  • Both Unity Connection servers must be configured to be in the same time zone.
  • Both Unity Connection servers must connect to the same phone system(s).
  • If the Unity Connection servers contain dual NICs, the two NICs on each Unity Connection server must be configured for fault tolerance using a single IP address, or one of the NICs must be disabled. Configuring the two NICs with distinct IP addresses for network load balancing is not supported.
  • For selected servers supported for earlier versions of Unity Connection, a memory upgrade. To determine whether your server requires a memory upgrade, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List .
  • For selected servers supported for earlier versions of Unity Connection, replacement hard disks. To determine whether your server requires hard-disk replacement, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List .

NoteThe Unity Connection cluster feature is not supported for use with Cisco Unified Communications Manager Business Edition.


Requirements for Cisco Unity Connection Networking

Up to ten Cisco Unity Connection servers can be joined through intrasite networking to form a single site (known as a Digital Network in release 7.x). In addition, two Unity Connection sites can be linked together through intersite networking for a total of up to 20 Cisco Unity Connection servers sharing the same directory information.

Alternatively, you can use intersite networking to link a single Cisco Unity Connection site of up to ten servers with a single Cisco Unity server or Digital Network. (In a Cisco Unity Connection cluster, only the publisher server is joined to the network, so a cluster counts as a single server toward the limit of ten in each site.)

See the applicable section:

Requirements for Intrasite Networking

Revised September 05, 2012

Intrasite networking uses SMTP to provide directory synchronization and message networking among Cisco Unity Connection servers.


NoteUnity Connection version 7.x servers and version 8.x servers can coexist in the same site as long as each 7.x server meets all the applicable requirements in theSystem Requirements for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.


Intrasite networking has the following requirements:

  • Each version 8.x server in the site must meet all applicable requirements listed in this document.
  • Each server in the site must be able to access the other servers in the site directly through TCP/IP port 25 (SMTP), or SMTP messages must be routed among the servers through an SMTP smart host.
  • If your site includes one or more Connection clusters, you must have a smart host available to resolve the SMTP domain of the cluster to both the publisher and subscriber servers in order for message traffic to reach the cluster subscriber server in the event that the publisher server is down.
  • When intrasite networking and voice recognition are configured, and when you are using one or more Cisco MCS-7815 or MCS-7825 servers, an additional 2 GB of memory (for a total of 6 GB) is required in the servers when the sum of users, locations, contacts (user- and administrator-defined), and distribution lists (personal and system) exceeds 2,000. (These are the first six items on the Tools > Grammar Statistics page in Cisco Unity Connection Administration.) For more information on Cisco MCS-7815 and MCS-7825 servers and the specifications on the memory that must be added, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html.
  • The virtual directory created by the networked Unity Connection servers must not exceed the maximum total numbers of objects listed in Table 8 in the “Directory Object Limits for Cisco Unity Connection 8.x” section.

NoteIntrasite networking is not supported for use with Cisco Unified Communications Manager Business Edition.


Requirements for Intersite Networking

Revised September 05, 2012

You can use intersite networking to link one Cisco Unity Connection site to another Unity Connection site. Or you can use it to link a Unity Connection site to a Cisco Unity server or Cisco Unity Digital Network. The linked sites are called a Cisco Voicemail Organization. To create an intersite link, you choose a single location on each site to act as a gateway to the other site. The gateways exchange directory synchronization information by using HTTP or HTTPS; voice messages are exchanged between the sites by using SMTP.

Intersite networking has the following requirements:

  • Each Unity Connection server or cluster in the Cisco Voicemail Organization must be at version 8.x, and must meet all applicable requirements listed in this document.
  • Each Unity Connection site must meet the requirements listed in the “Requirements for Intrasite Networking” section.
  • Each Unity Connection site gateway must be able to route SMTP messages to the remote site gateway (when two Unity Connection sites are linked) or to the Microsoft Exchange organization for delivery to the Interoperability Gateway for Microsoft Exchange (when a Unity Connection site is linked to a Cisco Unity site). This routing can be done either directly through TCP/IP port 25 or through an SMTP smart host.
  • The site gateways must be IP addressable and able to route to each other by using HTTP on port 80 or HTTPS on port 443.
  • If you are using a Cisco MCS-7815 or MCS-7825 server as a Unity Connection site gateway and voice recognition is configured on the server, an additional 2 GB of memory (for a total of 6 GB) is required in the servers when the sum of users, locations, contacts (user- and administrator-defined), and distribution lists (personal and system) exceeds 2,000.(These are the first six items on the Tools > Grammar Statistics page in Cisco Unity Connection Administration.) For more information on Cisco MCS-7815 and MCS-7825 servers and the specifications on the memory that must be added, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .
  • The virtual directory created by the networked sites must not exceed the maximum total numbers of objects listed in Table 8 in the “Directory Object Limits for Cisco Unity Connection 8.x” section.
  • Intersite networking can be used to link a maximum of two sites. (Adding more than one intersite link per site is not supported.)
  • If you are linking to a Cisco Unity server or Digital Network, see the Cisco Unity Networking Options Requirements at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html , for additional requirements.

NoteIntersite networking is not supported for use with Cisco Unified Communications Manager Business Edition.


Requirements for Using Single Sign-On Feature (Unity Connection 8.6 and later Only)

Added June 6, 2011

In case of a cluster, Cisco Unity Connection is required on each cluster of a server.

The single sign-on feature requires the following third-party applications:

  • Microsoft Windows Server 2003 with SP1/SP2 or Microsoft Windows Server 2008 with SP2 for deploying Active Directory.
  • Microsoft Active Directory server (any version).
  • ForgeRock Open Access Manager (OpenAM) version 9.0.
  • Apache Tomcat 7.0.0

The single sign-on feature uses Active Directory and OpenAM in combination to provide single sign-on access to client applications.

These third party products must meet the following configuration requirements:

  • Active Directory must be deployed in a Windows domain-based network configuration, not only as an LDAP server.
  • The OpenAM server must be accessible by name on the network to all client systems, Unity Connection server, and the Active Directory server.
  • The OpenAM server can be installed on Microsoft Windows 2003 server or RedHat Enterprise Linux (RHEL) server.
  • The Active Directory (Domain Controller) server, Windows clients, Cisco Unity Connection, and
  • OpenAM must be in the same domain.
  • DNS must be enabled in the domain.
  • The clocks of all the entities participating in single sign-on must be synchronized

See the third-party product documentation for more information about those products.

Single sign-on allows the end users to log in once and gain access to use the following Cisco Unity Connection applications without signing on again:

  • Cisco Personal Communications Assistant
  • Web Inbox
  • Cisco Unity Connection Administration
  • Cisco Unity Connection Serviceability

To use single sign on for a browser-based client application, you must configure the web browser. The following web browsers are supported:

  • Internet Explorer 6.x and later versions
  • Mozilla Firefox 3.x and later versions

Requirements for VPIM Networking

Cisco Unity Connection 8.x supports Voice Profile for Internet Mail (VPIM) version 2, which allows the exchange of voice and text messages with other messaging systems.

VPIM Networking can be used to provide message networking between Unity Connection 8.x and the following messaging systems:

  • Cisco Unity Connection 8.x, 7.x, and 2.x.
  • Cisco Unity Connection in Cisco Unified Communications Manager Business Edition 8.x, 7.x, and 6.x.
  • Cisco Unity 8.x, 7.x, 5.x, and 4.x.
  • Cisco Unity Express 3.2(1) and later.
  • Cisco Unified Messaging Gateway 1.0(2) and later.
  • Third-party voice messaging systems that support the VPIM version 2 protocol, as defined in Internet RFC 3801.

For information on using VPIM in Cisco Unity Connection, see the “VPIM Networking in Cisco Unity Connection 8.x” chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html .

Requirements for Using a Provisioning Application

A supported provisioning application:

  • Unimax Second Nature version 6.8 B0 and later.

Any technical support or troubleshooting required on the provisioning software must be obtained from the manufacturer. Cisco is responsible for providing technical support only on the Unity Connection application.

Requirements for Migrating from Cisco Unity Connection 1.x to Version 8.x

During the migration, only user data and, optionally, voice messages are preserved. System-level configuration data (for example, templates and classes of service) must be manually configured.


Caution Requirements for Cisco Unity Connection 8.x are different from requirements for Unity Connection 1.x. The system must meet Unity Connection 8.x requirements to receive support from Cisco TAC.

A migration from Unity Connection version 1.x to 8.x has the following requirements:

  • All applicable requirements listed in this document.
  • Unity Connection 1.2. If the Unity Connection server is running version 1.1, you must upgrade to version 1.2 before you can migrate to version 8.x.
  • A server that is supported for use with Unity Connection and that meets Unity Connection 8.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Unity Connection 1.x are supported for use with Unity Connection 8.x.) For information on supported Unity Connection servers, including specifications on individual servers, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .

Caution If you try to install version 8.x on an unsupported platform, Cisco Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program.

  • For selected servers supported for earlier versions of Unity Connection, replacement hard disks or a memory upgrade. To determine whether your server requires replacement hard disks or a memory upgrade, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List.

Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity Connection Version 8.x By Using a Flash Cutover


Caution Requirements for Cisco Unity Connection are different from requirements for Cisco Unity. The system must meet Unity Connection 8.x requirements to receive support from Cisco TAC.

A migration from Cisco Unity version 4.0(3) or later to Unity Connection 8.x by using a flash cutover has the following requirements:

  • All applicable requirements listed in this document.
  • A Cisco Unity system at version 4.0(3) or later. Upgrades from other versions are not supported. (If your Cisco Unity system is at an earlier version, you must upgrade to version 4.0(3) or later before exporting data because that is the minimum version supported by the Cisco Objected Backup and Restore Application Suite (COBRAS) migration tool.)
  • A server that is supported for use with Unity Connection and that meets Unity Connection 8.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Cisco Unity are supported for use with Unity Connection.) For information on supported Unity Connection servers, including specifications on individual servers, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .

Caution If you try to install version 8.x on an unsupported platform, Cisco Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program.

Note that voice cards are not supported for integrations with circuit-switched phone systems.

  • For selected servers supported for earlier versions of Cisco Unity and Cisco Unity Connection, and for selected Unity Connection 8.x configurations, a memory upgrade and/or replacement hard disks. To determine whether your server requires a memory upgrade and/or replacement hard disks, see the applicable server-specific table in the Cisco Unity Connection 8.x Supported Platforms List.

Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version 8.x By Using a Gradual Migration

Revised December 8, 2010


Caution Requirements for Cisco Unity Connection are different from requirements for Cisco Unity. The system must meet Unity Connection 8.x requirements to receive support from Cisco TAC.

A migration from Cisco Unity to Unity Connection 8.x by gradually moving data has the following requirements:

  • All applicable requirements listed in this document.
  • A Cisco Unity Digital Network in which at least one server is running version 8.0(3) to act as a gateway to Unity Connection. Other servers in the Cisco Unity Digital Network must be running version 8.0(3) or later, or version 7.0(2) with Engineering Special (ES) 36 or later.
  • A server that is supported for use with Unity Connection and that meets Unity Connection 8.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Cisco Unity are supported for use with Unity Connection.) For information on supported Unity Connection servers, including specifications on individual servers, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .

Caution If you try to install version 8.x on an unsupported platform, Cisco Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program.

Note that voice cards are not supported for integrations with circuit-switched phone systems.

Requirements for Installing Cisco Unity Connection on a Virtual Machine

Revised June 9, 2011

For information on installing other Cisco Unified Communications applications on the same physical server on which Unity Connection is installed, see the Unified Communications Virtualization wiki at http://cisco.com/go/uc-virtualized .

  • Unity Connection version 8.0(2) or later.

Unity Connection 7.1(3) is required to migrate from a physical server running Unity Connection 7.1(2) or earlier to a virtual server when the physical Unity Connection server is not supported for use with Unity Connection 8.x. However, after you complete the migration, you must upgrade the Unity Connection virtual machine to version 8.0(2) or later. Running an earlier version in a production virtual environment is not supported.

For VMware configurations supporting up to 10,000 users: Any edition.

For VMware configurations supporting up to 20,000 users: Enterprise Plus edition.


Note Updates to ESXi Version 4.0 Update 1 and ESXi Version 4.1 are supported.


Directory Object Limits for Cisco Unity Connection 8.x

Revised December 19, 2012

This section contains two tables that list directory object limits.

Table 7 lists the maximum numbers of certain objects that can be created on a Cisco Unity Connection server. For these objects, the limits apply regardless of the platform overlay in use by the server.

If you are using intrasite or intersite networking to link Unity Connection servers, the limits in Table 7 apply to each Unity Connection server in the site or organization.

Table 8 applies to the virtual directory created by the networked Unity Connection servers. When Unity Connection servers are networked together by using intrasite networking, replication between locations creates the virtual directory consisting of the users, administrator-defined contacts, system distribution lists, partitions, search spaces, and VPIM locations that are homed on each location, along with data about the locations themselves. When servers are networked together by using intersite networking, the virtual directory for an individual server consists of all users from both sites plus the administrator-defined contacts local to the site to which the server belongs, along with the system distribution lists, partitions, and search spaces on both sites, plus the VPIM locations on the local site.

Limits for other objects that depend on the platform overlay are listed in the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .

 

Table 7 Directory Object Limits for a Unity Connection 8.x Server

Directory Object
Unity Connection
Version 8.0 Limit
Unity Connection Version 8.5 Limit
Unity Connection Version 8.6 Limit

Classes of service

3,000

3,000

3,000

Call handlers

2,500

2,500

2,500

Call routing rules

1,200

1,200

1,200

Mailbox stores

5

5

5

Search spaces

200

200

2000

Partitions

200

200

2000

User-defined contacts

100,000

100,000

100,000

VPIM locations

10

100

100

The limits in Table 8 apply to the entire site or Cisco Voicemail Organization, regardless of whether the network comprises only two locations or the maximum number of supported locations. (For example, in Unity Connection version 8.x, if the individual server platforms support the limits, you can have 10 locations in one site with 10,000 Unity Connection users each, or 20 locations in two sites with 5,000 Unity Connection users each.)

 

Table 8 Directory Object Limits for a Unity Connection 8.x Site or Cisco Voicemail Organization

Directory Object
Unity Connection
Version 8.0 Limit
Unity Connection
Version 8.5 Limit
Unity Connection
Version 8.6 Limit

Connection locations

10 per site

10 per site

10 per site

VPIM locations

10 per site

100 per site

100 per site

Intersite links

1 per site

1 per site

1 per site

Total number of Unity Connection users and administrator-defined contacts

100,000

100,000

100,000

System distribution lists

100,000

100,000

100,000

Members per system distribution list

25,000

25,000

25,000

Total number of distribution list members across all system distribution lists

1.5 million

1.5 million

1.5 million

Nested lists within a distribution list

20

20

20

Search spaces

2,000 per site

2,000 per site

10,000*

Partitions

2,000 per site

2,000 per site

10,000*


Note When using more than 2000 search spaces and partitions in a single site, the following activities slow down:

  • Searching for Search Spaces in the System Administration slows down
  • Modifying and saving search spaces can take over 6 minutes.
  • Changing/ Saving/ Reordering Search spaces can take unto 20 mins to replicate across the site.

Available Languages for Cisco Unity Connection 8.x Components

Revised February 13, 2013


NoteLanguages are not licensed, and Unity Connection 8.x does not enforce a limit on the number of languages you can install and use. However, the more languages you install, the less hard-disk space is available for storing voice messages. In theCisco Unity Connection 8.x Supported Platforms List (http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html), information on the number of minutes of storage available on each server assumes that you have installed no more than five languages.


This section lists the languages in which Unity Connection components are available.

Cisco Personal Communications Assistant (PCA)

Arabic-Saudi Arabia, Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, Finnish, French-Canada, French-France, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Personal Communications Assistant (PCA) Help

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection Administration

English-United States, Japanese

Cisco Unity Connection Administration Help

English-United States

Cisco Unity Connection ViewMail for IBM Lotus Notes

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection ViewMail for IBM Lotus Notes Help

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco ViewMail for Microsoft Outlook 8.5

Arabic-Saudi Arabia, Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, Finnish, French-Canada, French-France, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection ViewMail for Microsoft Outlook 8.0

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection ViewMail for Microsoft Outlook 8.0 Help

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection Web Inbox (in Unity Connection 8.5)

Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, Finnish, French-Canada, French-France, German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

System prompts

Arabic-Saudi Arabia, Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-Australia, English-United Kingdom, English-United States, English TTY/TDD-United States, Finnish, French-Canada, French-France, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Text-to-speech engine

Arabic-Saudi Arabia, Chinese-PRC, Catalan, Chinese-Hong Kong, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-Australia, English-United States, English-United Kingdom, Finnish, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Transcription service for Cisco SpeechView

English-Australia, English-United States, English-Canada, Spanish-Mexico, Spanish-Colombia, Spanish-Ecuadorian, Spanish-Argentinean, Spanish-Spanish, Spanish-United States, Spanish-Uruguay, Catalan-Spain, French-Canadian

Voice-recognition engine

English-United States

Product documentation for administrators/installers

English-United States, Japanese

Product documentation for end users

Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Netherlands, English-United States, French-France, German, Italian, Japanese, Korean, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish

Translated versions of the five Cisco Unity Connection user guides are available at http://www.cisco.com/en/US/products/ps6509/tsd_products_support_translated_end_user_guides_list.html .

Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection 8.x

Revised November 16, 2010

Use the numeric codes in Table 9 when you are using the Bulk Administration Tool and a CSV file to create or update users. Enter the applicable four- or five-digit numeric code in the Language column for each user. For more information, see the “Using the Cisco Unity Connection 8.x Bulk Administration Tool” appendix of the User Moves, Adds, and Changes Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmacx.html .

Use the alphabetic codes to interpret language-related log entries and error codes.

 

Table 9 Codes for Languages Supported in Cisco Unity Connection

Language
Numeric Code
Alphabetic Code

Arabic-Saudi Arabia

1025

ARA

Catalan

1027

CAT

Chinese-Hong Kong

3076

ZHH

Chinese-PRC

2052

CHS

Chinese-Taiwan

1028

CHT

Czech

1029

CSY

Danish

1030

DAN

Dutch-Netherlands

1043

NLD

English-Australia

3081

ENA

English-United Kingdom

2057

ENG

English-United States

1033

ENU

English TTY/TDD-United States

33801

ENX

Finnish

1035

FIN

French-Canada

3084

FRC

French-France

1036

FRA

German

1031

DEU

Greek

1032

ELL

Hebrew

1037

HEB

Hungarian

1038

HUN

Italian

1040

ITA

Japanese

1041

JPN

Korean

1042

KOR

Norwegian

1044

NOR

Polish

1045

PLK

Portuguese-Brazil

1046

PTB

Portuguese-Europe

2070

PTG

Russian

1049

RUS

Spanish-Latin America

9226

ESO

Spanish-Spain

1034

ESP

Swedish

1053

SVE

Turkish

1055

TRK

Survivable Remote Site Voicemail

Added May 20, 2010

Survivable Remote Site Voicemail (SRSV) provides backup voicemail service in a centralized messaging and centralized call processing deployment. SRSV uses Cisco Unity Express servers in branch locations to provide backup voicemail service for Unity Connection servers located in the headquarters when the network connection between sites is unavailable.

For additional information about SRSV, see Release Notes for Cisco Unified SRSV-CUE Release 8.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/umg/rel8_0/release_notes/rn_srsv_cue_80.html .