Guest

Cisco Unity

System Requirements for Cisco Unity Release 8.x

  • Viewing Options

  • PDF (322.2 KB)
  • Feedback
System Requirements for Cisco Unity Release 8.x

Table Of Contents

System Requirements for Cisco Unity Release 8.x

Hardware Requirements

Hardware Requirement—Cisco Unity Server

Hardware Requirement—Cisco Unity Voice-Recognition Server

Software Requirements

Software Requirements—Cisco Unity Server

Minimum Service Packs Required—Cisco Unity Server

Software Requirements—Cisco Unity Voice-Recognition Server

Software Requirements—Message Store

Supported Exchange Configurations—Message Store

Required Exchange Software and Licenses—Message Store

Minimum Exchange Service Packs Required—Message Store

Recommended Exchange Service Packs—Message Store

Exchange-Related Considerations—Message Store

Software Requirements—Subscriber Workstations

Language Requirements for Third-Party Software

List of Third-Party Software

Active Directory Requirements

Active Directory Requirements—Cisco Unity Unified Messaging

Active Directory Requirements—Cisco Unity Voice Messaging

Network Requirements

Requirements for Configuring a Cisco ASA Firewall for Cisco Unity

Requirements for Using Message Store Clusters

Requirements for Cisco Unity Failover

Failover Requirements When the Message Store Is Installed on a Separate Platform

Failover Requirements When the Message Store Is Installed on the Secondary Cisco Unity Server

Failover Requirements When the Message Store Is Installed on the Primary Cisco Unity Server

Failover Requirements for Separating Cisco Unity Servers by a Firewall

Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites

Requirements for Standby Redundancy

Standby Redundancy Requirements When the Message Store Is Installed on a Separate Platform

Standby Redundancy Requirements When Exchange Server 2003 Is Installed on the Primary Cisco Unity Server

Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall

Requirements for Cisco Unity Phone View

Requirements for More Than 96 Voice Messaging Ports or More Than 7,500 Subscribers on a Cisco Unity Server

Available Languages for Cisco Unity Components

Numeric and Alphabetic Codes for Supported Languages in Cisco Unity

Characteristics of Cisco Unity Configurations

Cisco Unity Unified Messaging Configuration

Cisco Unity Voice Messaging Configuration


System Requirements for Cisco Unity Release 8.x


Revised February 07, 2012 (Originally published February 2, 2010)

This document lists requirements for installing a Cisco Unity system running version 8.x, as well as information on available languages and the characteristics of the Unified Messaging and Voice Messaging configurations. It contains the following sections:

Hardware Requirements

Software Requirements

Language Requirements for Third-Party Software

Active Directory Requirements

Network Requirements

Requirements for Using Message Store Clusters

Requirements for Cisco Unity Failover

Requirements for Standby Redundancy

Requirements for Cisco Unity Phone View

Requirements for More Than 96 Voice Messaging Ports or More Than 7,500 Subscribers on a Cisco Unity Server

Available Languages for Cisco Unity Components

Numeric and Alphabetic Codes for Supported Languages in Cisco Unity

Characteristics of Cisco Unity Configurations

Hardware Requirements

Hardware Requirement—Cisco Unity Server

Hardware Requirement—Cisco Unity Voice-Recognition Server

Hardware Requirement—Cisco Unity Server

A server that meets Cisco Unity specifications. See the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.


Caution Cisco TAC does not provide any assistance for installing, customizing, or troubleshooting Cisco Unity on a platform that is not on the Cisco Unity Supported Platforms List.

Hardware Requirement—Cisco Unity Voice-Recognition Server

A server that meets Cisco Unity voice-recognition server specifications. See the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.


Caution Cisco TAC does not provide any assistance for installing, customizing, or troubleshooting Cisco Unity voice-recognition software on a platform that is not listed on the Cisco Unity Supported Platforms List as supported for voice recognition.

Software Requirements

Software Requirements—Cisco Unity Server

Software Requirements—Cisco Unity Voice-Recognition Server

Software Requirements—Message Store

Software Requirements—Subscriber Workstations


Note If you plan to run Cisco Security Agent for Cisco Unity on the Cisco Unity server, some versions of required software are not supported. See the "Software Requirements" section of the applicable Release Notes for Cisco Security Agent for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.


Software Requirements—Cisco Unity Server

Revised February 14, 2011

A supported 32-bit version of Microsoft Windows Server 2003:

Windows Server 2003 R2 Enterprise Edition

Windows Server 2003 R2 Standard Edition

Windows Server 2003 Enterprise Edition

Windows Server 2003 Standard Edition

The preceding Windows Server 2003 editions are supported for all Microsoft Exchange 2007 and Exchange 2003 configurations. When Exchange 2000 is the message store, they are supported only when an Exchange Server 2007 or Exchange Server 2003 server is available to be the partner Exchange server.

The editions are supported in English, French, German, and Japanese.


Caution To use the Cisco Unity Server Updates wizard to install Microsoft updates for Windows, Exchange, Microsoft SQL Server, and Microsoft Internet Explorer, you must install the English-language version of those applications. If you install them in another language, you must download Microsoft updates from the Microsoft website.

The Cisco Unity Platform Configuration discs install Windows Server 2003 in English. The discs that install Windows Server 2003 also install the Microsoft Multilingual User Interface, so you can localize the Windows user interface into the languages supported for use with Cisco Unity.


Caution The Cisco Unified Communications operating system, which installs Windows for Cisco Unified Communications Manager and other applications, is not supported for use with Cisco Unity.

The applicable version of Microsoft SQL Server:

On a system with more than 32 voice ports, SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition

On a system with 32 or fewer voice ports, SQL Server 2005 Express or SQL Server 2000 Desktop Engine (MSDE 2000)

Other editions of SQL Server and MSDE are not supported.


Note A system that is using Cisco Unity failover requires SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition regardless of the number of voice ports. (See also "Requirements for Cisco Unity Failover" section.)


A supported version of Microsoft Internet Explorer:

8.0

7.0

6.0

Microsoft .NET Framework 1.1 and 2.0

Microsoft Visual C++ 2005 Redistributable DLLs

Microsoft Windows Installer 3.1

Business Objects Crystal Reports XI

Cisco Unity-CM TSP version 8.4(3), if you are integrating Cisco Unity with Cisco Unified Communications Manager or Cisco Unified Communications Manager Express by using Skinny Call Control Protocol (SCCP).

Cisco Unity 8.x

The service packs listed in the following section, "Minimum Service Packs Required—Cisco Unity Server."

Minimum Service Packs Required—Cisco Unity Server

Windows Server 2003 Service Pack 2

The applicable SQL Server service pack:

SQL Server 2005 Service Pack 3—with SQL Server 2005 on the Cisco Unity server

SQL Server 2005 Express Service Pack 3—with SQL Server 2005 Express on the Cisco Unity server

SQL Server 2000 Service Pack 4—with SQL Server 2000 on the Cisco Unity server

MSDE 2000 Service Pack 4—with MSDE 2000 on the Cisco Unity server

We recommend that you also update the Cisco Unity server with the security updates that Microsoft releases monthly. See Software Installed by the Cisco Unity Server Updates Wizard at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/updates/wizard/cuupwz.html.

For support information, see the "Support Policy for Microsoft Service Packs and Updates" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/support/8xcusupp.html.

Software Requirements—Cisco Unity Voice-Recognition Server

Cisco Unity version 8.x voice-recognition software.

Cisco Unity voice-recognition software earlier than version 8.0 is not supported with Cisco Unity 8.x.

Software Requirements—Message Store

Supported Exchange Configurations—Message Store

Required Exchange Software and Licenses—Message Store

Minimum Exchange Service Packs Required—Message Store

Recommended Exchange Service Packs—Message Store

Exchange-Related Considerations—Message Store

Supported Exchange Configurations—Message Store

Revised July 2, 2010

Caution Configuring Cisco Unity to access mailboxes for Cisco Unity subscribers in a hosted Exchange environment or choosing a partner Exchange server in a hosted Exchange environment is not supported.

Table 1 shows the supported configurations when Exchange is used to home mailboxes for subscribers on a Cisco Unity 8.x system.

Table 1 Using Exchange to Home Mailboxes for Cisco Unity Subscribers 

Cisco Unity
Configuration
Supported Exchange Configurations

Unified Messaging

Exchange 2010 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

To use Exchange 2010 with Cisco Unity, you must install Cisco Unity Engineering Special (ES) 2 or later. For information on downloading the ES and procedures for configuring Cisco Unity to use Exchange 2010, see Using Microsoft Exchange 2010 with Cisco Unity 8.0, 7.0, and 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

Exchange 2007 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2003 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2000 on a separate server, supported only for storing mailboxes for Cisco Unity subscribers.

Voice Messaging

Exchange 2007 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2003 on the Cisco Unity server or on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Mixed
Unified Messaging
and Voice Messaging

Mailboxes for Unified Messaging Subscribers

Exchange 2010 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

To use Exchange 2010 with Cisco Unity, you must install Cisco Unity Engineering Special (ES) 2 or later. For information on downloading the ES and procedures for configuring Cisco Unity to use Exchange 2010, see Using Microsoft Exchange 2010 with Cisco Unity 8.0, 7.0, and 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

Exchange 2007 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2003 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2000 on a separate server, supported only for storing mailboxes for Cisco Unity subscribers.

Mailboxes for Voice Messaging Subscribers

Exchange 2007 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

Exchange 2003 on a separate server, supported for the partner Exchange server and for storing mailboxes for Cisco Unity subscribers.

An Exchange mailbox store that homes mailboxes for Unified Messaging subscribers must not be on the same Exchange server as a mailbox store that homes mailboxes for Voice Messaging subscribers.


Required Exchange Software and Licenses—Message Store

Revised July 2, 2010

Caution Do not install any Exchange software, including Exchange System Management Tools, on a Cisco Unity 8.x server on which the Microsoft Messaging API and Collaboration Data Objects (MAPI and CDO) are installed. During Cisco Unity installation, if no Exchange software is installed, the Cisco Unity System Setup Assistant automatically installs MAPI and CDO. If you later install Exchange software, portions of MAPI and CDO are overwritten, and Cisco Unity stops functioning. To determine whether MAPI and CDO are installed on the Cisco Unity server, in the Add or Remove Programs control panel, look for Messaging API and Collaboration Data Objects.

A supported version of Microsoft Exchange Server for use on the partner Exchange server:

Exchange Server 2010 Enterprise Edition OR Standard Edition

To use Exchange 2010 with Cisco Unity, you must install Cisco Unity Engineering Special (ES) 2 or later. For information on downloading the ES and procedures for configuring Cisco Unity to use Exchange 2010, see Using Microsoft Exchange 2010 with Cisco Unity 8.0, 7.0, and 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

Exchange Server 2007 Enterprise Edition OR Standard Edition

Exchange Server 2003 Enterprise Edition OR Standard Edition

Voice Mail Run-Time Edition of Microsoft Exchange Server 2003 Enterprise Edition

Cisco Unity ships with this version, which is for use only in the Cisco Unity Voice Messaging configuration.

The following editions of Exchange 2000 may be used for storing mailboxes for Cisco Unity 8.x Unified Messaging subscribers (see Table 1), but the editions cannot be installed on the partner Exchange server:

Exchange 2000 Server Enterprise Edition

Exchange 2000 Server Standard Edition

The applicable server licenses:

Customers using the Voice Mail Run-Time Edition of Exchange 2003 are responsible for providing only the Windows Server license for each operating system environment.

Customers using a supported edition of Exchange other than the Voice Mail Run-Time Edition are responsible for providing the Windows Server license for each operating system environment and for providing the Exchange Server server license.

Client Access Licenses (CALs) must be purchased for all configurations except Cisco Unity Voice Messaging with:

Exchange Server 2007 software provided by the customer.

The Voice Mail Run-Time Edition of Exchange 2003.

CALs provided by Cisco can be used only for a Voice Messaging configuration. The Cisco-provided CALs cannot be used on systems that are used for email messages.

The service packs listed in the following section, "Minimum Exchange Service Packs Required—Message Store." For information on installing Exchange service packs on servers other than the Cisco Unity server, see the Microsoft website.

Minimum Exchange Service Packs Required—Message Store

Exchange 2007 Service Pack 1 Update Rollup 4:

On Exchange 2007 servers that are running Windows Server 2008. Without the update rollup, message indicators will not function properly. See Microsoft KB article 952580.

Exchange 2003 Service Pack 2:

On the Cisco Unity server when Exchange 2003 software is installed on the server.

In a Cisco Unity Voice Messaging configuration, on any separate Exchange 2003 servers.

We also recommend that you update the Cisco Unity server and/or message store servers, as applicable, with the Exchange service packs listed in the "Recommended Exchange Service Packs—Message Store" section below. Some of the service packs may be more recent than the minimum required service packs listed in this section.

In addition, we recommend that you update the Cisco Unity server with the security updates that Microsoft releases monthly. See Software Installed by the Cisco Unity Server Updates Wizard at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Recommended Exchange Service Packs—Message Store

Revised February, 2012

Exchange 2010 Service Pack 1

Exchange 2010 Service Pack 2

Exchange 2007 Service Pack 3

For support information, see the "Support Policy for Microsoft Service Packs and Updates" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/support/8xcusupp.html.

Exchange-Related Considerations—Message Store

Revised July 2, 2010

To use Exchange 2010 with Cisco Unity, you must install Cisco Unity Engineering Special (ES) 2 or later. For information on downloading the ES and procedures for configuring Cisco Unity to use Exchange 2010, see Using Microsoft Exchange 2010 with Cisco Unity 8.0, 7.0, and 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

If subscribers will be homed in Exchange 2007 and you will be using AMIS or the Cisco Unity Bridge to integrate Cisco Unity with another voice-messaging system, you must retain an Exchange 2003 or an Exchange 2000 server in the forest for the Cisco Unity Voice Connector for Microsoft Exchange. A version of the Voice Connector that supports AMIS and Bridge Networking is not available for Exchange 2007.

When Cisco Unity failover is configured on a system in the Unified Messaging configuration, Exchange must be installed on a separate server from the primary and secondary servers. You can use any supported edition of Exchange (except the Voice Mail Run-Time Edition) for the message store.

When Cisco Unity failover is configured on a system in the Voice Messaging configuration, you can install Exchange either on a separate server from the primary and secondary servers or on the secondary server. Note the following:

If you install Exchange on a separate server, you can install any supported edition of Exchange.

If you install Exchange on the secondary server, you must install Exchange Server 2003. In addition, there is a lower limit on the number of Cisco Unity subscribers. For information on the maximum number of subscribers supported in this configuration, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

See also the "Requirements for Cisco Unity Failover" section.


Note For Cisco Unity configurations with Exchange installed on a separate server, Cisco assumes that the message store environment is already set up and working before the Cisco Unity system is installed.


For additional Exchange-related requirements, see:

Active Directory Requirements

Network Requirements

Requirements for Using Message Store Clusters

Software Requirements—Subscriber Workstations

An operating system that is compatible with the version of Cisco Unity that you are installing.

An Internet browser that is compatible with the version of Cisco Unity that you are installing, for subscribers to access the Cisco PCA.

A messaging client that is compatible with the version of Cisco Unity that you are installing, for subscribers to access voice messages by using Cisco Unity ViewMail for Microsoft Outlook.


Note Accessing Cisco Unity voice messages by using a client that is running on a virtualized workstation is not supported.


For compatible versions of the required software, see Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html.

Language Requirements for Third-Party Software

Required languages for the applications listed in the "List of Third-Party Software" section depend on the Windows locale on the Cisco Unity server.


Caution To use the Cisco Unity Server Updates wizard to install Microsoft updates for Windows, SQL Server, Internet Explorer, and Exchange, you must install the English-language version of those applications. If you install them in another language, you must download Microsoft updates from the Microsoft website.

Table 2 lists the required languages for French, German, Japanese, and U.S. English locales. For locales not listed in the table, U.S. English versions are required for all software.

Note that the locale on the Cisco Unity server must match one of the installed Cisco Unity languages (for example, if you choose French as the locale, then the French Cisco Unity system-prompt set must also be installed).

Table 2 Required Languages for Third-Party Software 

Windows Locale
on Cisco Unity Server
Required Language for Third-Party Software

French

French versions are required for all software (see the "List of Third-Party Software" section) except MDAC, for which U.S. English is required.

German

German versions are required for all software (see the "List of Third-Party Software" section) except MDAC, for which U.S. English is required.

Japanese

Japanese versions are required for all software (see the "List of Third-Party Software" section) except MDAC, for which U.S. English is required.

U.S. English

U.S. English versions are required for all software (see the "List of Third-Party Software" section).

Locales not listed
in this table

U.S. English versions are required for all software (see the "List of Third-Party Software" section).


List of Third-Party Software

Depending on the Windows locale on the Cisco Unity server, the following software must be installed in the languages listed in Table 2:

Cisco Unity ViewMail for Microsoft Outlook

Microsoft Exchange

Microsoft Internet Explorer

Microsoft MDAC

Microsoft Outlook

Microsoft SQL Server or MSDE

Microsoft Windows

Active Directory Requirements

Active Directory Requirements—Cisco Unity Unified Messaging

Active Directory Requirements—Cisco Unity Voice Messaging

(For information on the characteristics of the Unified Messaging and Voice Messaging configurations, see the "Characteristics of Cisco Unity Configurations" section.)

Active Directory Requirements—Cisco Unity Unified Messaging

Revised June 9, 2010

The Cisco Unity server is a member server in an Active Directory 2008 R2, Active Directory 2008, Active Directory 2003, or Active Directory 2000 domain. All domain and forest functional levels are supported, including the levels formerly known as mixed mode and native mode, except when you are using the Interoperability Gateway for Microsoft Exchange to network Cisco Unity with another voice-messaging system. In that configuration, all domain and forest functional levels are supported except Windows 2000 mixed mode and Windows Server 2003 interim mode.


Caution In a Unified Messaging configuration, installing Cisco Unity on a domain controller or global catalog server is not supported.

Each Cisco Unity server requires access to one or more global catalog servers. Each Cisco Unity server also requires access to one or more read/write Active Directory domain controllers in the following domains:

In the domain that contains that Cisco Unity server.

In every domain that contains Active Directory objects for subscribers, contacts, distribution lists, or locations that are homed on that Cisco Unity server.

The domain controller and the global catalog server can be the same server. More than one Cisco Unity server can access the same read/write Active Directory domain controller and global catalog server.

Mailboxes for Cisco Unity subscribers can be homed on Exchange servers in any domain in the forest.

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 8.0 server is accessing an Active Directory 2008 (including R2) global catalog server (GC), a change to the registry on the GC may be required. For information on determining whether the change is required and, if so, how to make the change, see the "Subscribers Logging On to Cisco Unity 8.x Hear `Your Messages Are Not Available Now'" section in the "Troubleshooting Subscriber and Administrator Access in Cisco Unity 8.x" chapter of the Troubleshooting Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/troubleshooting/guide/8xcutsgx.html.

Before you make the Cisco Unity server a member server in an Active Directory 2008 R2 domain, you must install a Microsoft patch on all Active Directory 2008 R2 domain controllers in the forest. The patch, which is available from Microsoft, is associated with Microsoft Knowledge Base article 977180, "Error message when an application or a service tries to query for any deleted objects by using a well-known GUID in a Windows Server 2008 R2-based domain if paged search is used: `0x8007202c Critical extension is unavailable.'"

If you use the new Active Directory 2008 R2 recycle bin feature to restore the Active Directory account for a Cisco Unity subscriber, additional steps are required to reassociate the account and the subscriber. Use the Remove Subscriber Properties tool from CiscoUnityTools.com to remove all Cisco Unity properties from the Active Directory account, reimport the Active Directory account into Cisco Unity, and restart the Cisco Unity server. Messages for the subscriber are retained, but Cisco Unity properties for the user must be reset.

If you want to install the Cisco Unity server in a forest other than the corporate forest and still have users log on to the Cisco Unity Assistant and/or the Cisco Unity Inbox web tools by using user credentials in the corporate forest, you must use the GrantUnityAccess utility to associate Cisco Unity subscribers with Active Directory accounts. For more information, see the "Using Logon Credentials from Active Directory Accounts in a Different Forest" section in the "Managing Subscriber Accounts" chapter of the System Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.html.

Active Directory Requirements—Cisco Unity Voice Messaging

Revised June 9, 2010

The Cisco Unity server is a domain controller/global catalog server (DC/GC) in its own Active Directory 2003 domain, or is a member server in an existing Active Directory 2008 R2, Active Directory 2008, Active Directory 2003, or Active Directory 2000 domain. All domain and forest functional levels are supported, including the levels formerly known as mixed mode and native mode, except when you are using the Interoperability Gateway for Microsoft Exchange to network Cisco Unity with another voice-messaging system. In that configuration, all domain and forest functional levels are supported except Windows 2000 mixed mode and Windows Server 2003 interim mode.

Each Cisco Unity server requires access to one or more global catalog servers. Each Cisco Unity server also requires access to one or more read/write Active Directory domain controllers in the following domains:

In the domain that contains that Cisco Unity server.

In every domain that contains Active Directory objects for subscribers, contacts, distribution lists, or locations that are homed on that Cisco Unity server.

The domain controller and the global catalog server can be the same server. More than one Cisco Unity server can access the same read/write Active Directory domain controller and global catalog server.

Mailboxes for Cisco Unity subscribers can be homed on Exchange servers in any domain in the forest.

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 8.0 server is accessing an Active Directory 2008 (including R2) global catalog server (GC), a change to the registry on the GC may be required. For information on determining whether the change is required and, if so, how to make the change, see the "Subscribers Logging On to Cisco Unity 8.x Hear `Your Messages Are Not Available Now'" section in the "Troubleshooting Subscriber and Administrator Access in Cisco Unity 8.x" chapter of the Troubleshooting Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/troubleshooting/guide/8xcutsgx.html.

Before you make the Cisco Unity server a member server in an Active Directory 2008 R2 domain, you must install a Microsoft patch on all Active Directory 2008 R2 domain controllers in the forest. The patch, which is available from Microsoft, is associated with Microsoft Knowledge Base article 977180, "Error message when an application or a service tries to query for any deleted objects by using a well-known GUID in a Windows Server 2008 R2-based domain if paged search is used: `0x8007202c Critical extension is unavailable.'"

If you use the new Active Directory 2008 R2 recycle bin feature to restore the Active Directory account for a Cisco Unity subscriber, additional steps are required to reassociate the account and the subscriber. Use the Remove Subscriber Properties tool from CiscoUnityTools.com to remove all Cisco Unity properties from the Active Directory account, reimport the Active Directory account into Cisco Unity, and restart the Cisco Unity server. Messages for the subscriber are retained, but Cisco Unity properties for the user must be reset.

If you want to install the Cisco Unity server in a forest other than the corporate forest and still have users log on to the Cisco Unity Assistant and/or the Cisco Unity Inbox web tools by using user credentials in the corporate forest, you must use the GrantUnityAccess utility to associate Cisco Unity subscribers with Active Directory accounts. For more information, see the "Using Logon Credentials from Active Directory Accounts in a Different Forest" section in the "Managing Subscriber Accounts" chapter of the System Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.html.

Network Requirements

Revised May 3, 2010

For new installations, a minimum network bandwidth of 100 Mbps between the Cisco Unity server and the following servers:

The partner Exchange server.

Any Exchange server on which Cisco Unity subscriber mailboxes are homed.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.


Note Existing Cisco Unity Voice Messaging configurations that were installed under the previous 10-Mbps requirement are not required to upgrade unless insufficient bandwidth begins to affect Cisco Unity performance.


When assessing network bandwidth, note the following considerations:

Other traffic on the network between the Cisco Unity server and the listed servers, and how that affects available bandwidth.

The number of voice messages per hour.

The codec being used for recording voice messages. (For example, G.711 is about 480 KB/minute, and G.729a is about 60 KB/minute.)

For a list of supported codecs and the size of voice messages for each codec, see the table in the "Managing the Size of Subscriber Mailboxes for Cisco Unity 8.x" section in the "Best Practices for Managing Exchange for Cisco Unity 8.x" chapter of the Maintenance Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/maintenance/guide/8xcumgx.html.

The Cisco Unity server can be separated by a Cisco ASA firewall from the following servers only in a specific configuration:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

For information on configuring the ASA firewall, see the "Requirements for Configuring a Cisco ASA Firewall for Cisco Unity" section. Other firewalls are not supported.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter of the Security Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.)

For firewall requirements for failover and standby redundancy, see the applicable sections:

Failover Requirements for Separating Cisco Unity Servers by a Firewall

Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites

Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall

The partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server with which the partner server communicates.

If the Cisco Unity system includes a voice-recognition server, the Cisco Unity server cannot be separated from the voice-recognition server by a firewall. In a failover configuration, neither Cisco Unity server can be separated from the voice-recognition server by a firewall.

If the Cisco Unity server contains a dual NIC, the two NICs 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.

If Cisco Unity connects to Media Gateway units (PIMG or TIMG) over a WAN, the requirements for the WAN network connection are:

For G.729a codec formatting, a minimum of 32.76 Kbps guaranteed bandwidth for each voice messaging port.

For G.711 codec formatting, a minimum of 91.56 Kbps guaranteed bandwidth for each voice messaging port.

No network devices that implement network address translation (NAT).

Requirements for Configuring a Cisco ASA Firewall for Cisco Unity

Added May 3, 2010

When separating Cisco Unity by a firewall from Exchange servers, and Active Directory domain controllers and global catalog servers, the firewall configuration must meet the following requirements:

A Cisco ASA 5510 or later Adaptive Security Appliance running ASA 8 or later software.

Dead-connection detection (DCD) enabled and using default values for all timeout periods, for retry interval, and for maximum retries.

For additional requirements, see the following sections:

Network Requirements

Failover Requirements for Separating Cisco Unity Servers by a Firewall

Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites

Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall

Requirements for Using Message Store Clusters

Homing Exchange mailboxes for Cisco Unity subscribers in an Exchange cluster is supported with the following editions:

Exchange 2007 clusters—all four cluster types are supported: cluster continuous replication (CCR), local continuous replication (LCR), single copy cluster (SCC), and standby continuous replication (SCR)

Exchange 2003 clusters

Exchange 2000 clusters (in a Cisco Unity Unified Messaging configuration only)

Do not install the following software on a server in an Exchange cluster:

Cisco Unity software

Cisco Unity Voice Connector for Microsoft Exchange software

Clustered Exchange servers require special hardware that Cisco does not provide and advanced knowledge of Windows and of Exchange clusters. Cisco will not help with configuration or support of the Exchange cluster. It is the responsibility of the customer to obtain support for the Exchange cluster.

Requirements for Cisco Unity Failover

Failover Requirements When the Message Store Is Installed on a Separate Platform

Failover Requirements When the Message Store Is Installed on the Secondary Cisco Unity Server

Failover Requirements When the Message Store Is Installed on the Primary Cisco Unity Server

Failover Requirements for Separating Cisco Unity Servers by a Firewall

Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites


Note For standby redundancy requirements, see the "Requirements for Standby Redundancy" section.


Failover Requirements When the Message Store Is Installed on a Separate Platform

Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay.

When the Cisco Unity servers are installed in the same site, the network must meet the requirements listed in the "Network Requirements" section. The minimum bandwidth requirement also applies to the bandwidth between the Cisco Unity servers.

When the Cisco Unity servers are installed in separate sites, the network must meet the requirements listed in the "Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites" section.

One Cisco Unity server is designated the primary server, and the other Cisco Unity server is designated the secondary server.

Both Cisco Unity servers must be member servers in the same Active Directory domain. Do not install Active Directory on either Cisco Unity server.

When servers are installed in different locations, each location must have a domain controller/global catalog server.

The names of both Cisco Unity servers must be unique in the first 14 characters.

Both Cisco Unity servers must use the same Exchange server as the partner server.

Exchange Server must be installed on computers other than the Cisco Unity servers.

If Exchange Server 2003 administration software is already installed on the Cisco Unity servers because you are upgrading from an earlier version of Cisco Unity, you are not required to remove it.

If Exchange Server 2003 administration software is not already installed on the Cisco Unity servers, do not install it. The Cisco Unity System Setup Assistant automatically installs Microsoft Messaging API and Collaboration Data Objects, which performs the same function for Cisco Unity 8.0 that Exchange administration software performed for earlier versions of Cisco Unity.

Both Cisco Unity servers must connect to the same phone system.

Both Cisco Unity servers must have the same enabled features and configurations.

Either SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition must be installed on both the primary and secondary servers. (Neither SQL Server 2005 Express nor MSDE 2000 is supported on either server with Cisco Unity failover.)

Cisco Unity directory and message store services must log on by using the same domain accounts on both the primary and secondary servers.

MSSQLSERVER and SQLSERVERAGENT services on both Cisco Unity servers must be configured to log on as the same domain account, and the account must belong to the Local Administrators group on each server. SQLSERVERAGENT on the primary server must be able to log on to SQL Server on the secondary server by using Windows NT authentication.

All software must be installed on the same drive and directories on the primary and secondary servers.

The same version of Windows must be installed on both Cisco Unity servers.

Failover Requirements When the Message Store Is Installed on the Secondary Cisco Unity Server


Caution If the message store is already installed on a separate platform, do not change the existing Cisco Unity failover configuration to move Exchange to the secondary Cisco Unity server. Otherwise, Cisco Unity failover is not supported. Only new installations of Cisco Unity with failover can be configured with Exchange on the secondary server.

Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay.

When the Cisco Unity servers are installed in the same site, the network must meet the requirements listed in the "Network Requirements" section. The minimum bandwidth requirement also applies to the bandwidth between the Cisco Unity servers.

When the Cisco Unity servers are installed in separate sites, the network must meet the requirements listed in the "Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites" section.

One Cisco Unity server is designated the primary server, and the other Cisco Unity server is designated the secondary server.

You must use one of the following Active Directory configurations:

Both Cisco Unity servers are member servers in the same Active Directory domain.

The secondary server is a domain controller, and the primary server is a member server in the secondary server domain.

When servers are installed in different locations, each location must have a domain controller/global catalog server.

The names of both Cisco Unity servers must be unique in the first 14 characters.

Both Cisco Unity servers must use the same Exchange server as the partner server.

Exchange Server 2003 must be installed on the secondary server and must not be installed on the primary server.

If Exchange Server 2003 administration software is already installed on the primary server because you are upgrading from an earlier version of Cisco Unity, you are not required to remove it.

If Exchange Server 2003 administration software is not already installed on the primary server, do not install it. The Cisco Unity System Setup Assistant automatically installs the Exchange software that Cisco Unity requires.

Both Cisco Unity servers must connect to the same phone system.

Both Cisco Unity servers must have the same enabled features and configurations.

The Cisco Unity system must be installed in the Voice Messaging configuration. For information on the maximum number of subscribers supported in this configuration, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

Either SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition must be installed on both the primary and secondary servers. (Neither SQL Server 2005 Express nor MSDE 2000 is supported on either server with Cisco Unity failover.)

Cisco Unity directory and message store services must log on by using the same domain accounts on both the primary and secondary servers.

MSSQLSERVER and SQLSERVERAGENT services on both Cisco Unity servers must be configured to log on as the same domain account, and the account must belong to the Local Administrators group on each server. SQLSERVERAGENT on the primary server must be able to log on to SQL Server on the secondary server by using Windows NT authentication.

All software must be installed on the same drive and directories on the primary and secondary servers.

The same version of Windows must be installed on both Cisco Unity servers.

Failover Requirements When the Message Store Is Installed on the Primary Cisco Unity Server

Installing Exchange on the primary server is supported.

However, in a failover configuration with Exchange Server 2003 installed on one of the Cisco Unity servers, we recommend that you install Exchange on the secondary server rather than on the primary server. This ensures that when failover occurs, subscribers continue to have access to the voice messages in Exchange. For the system requirements for the recommended configuration, see the "Failover Requirements When the Message Store Is Installed on the Secondary Cisco Unity Server" section.


Caution If the message store is already installed on a separate platform, do not change the existing Cisco Unity failover configuration to move Exchange to the primary Cisco Unity server. Otherwise, Cisco Unity failover is not supported. Only new installations of Cisco Unity with failover can be configured with Exchange on the primary server.

The following requirements are for installing Exchange 2003 on the primary server in a failover configuration:

Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay.

When the Cisco Unity servers are installed in the same site, the network must meet the requirements listed in the "Network Requirements" section. The minimum bandwidth requirement also applies to the bandwidth between the Cisco Unity servers.

When the Cisco Unity servers are installed in separate sites, the network must meet the requirements listed in the "Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites" section.

One Cisco Unity server is designated the primary server, and the other Cisco Unity server is designated the secondary server.

You must use one of the following Active Directory configurations:

Both Cisco Unity servers are member servers in the same Active Directory domain.

The primary server is a domain controller, and the secondary server is a member server in the primary server domain.

When servers are installed in different locations, each location must have a domain controller/global catalog server.

The names of both Cisco Unity servers must be unique in the first 14 characters.

Both Cisco Unity servers must use the same Exchange server as the partner server.

Exchange Server 2003 must be installed on the primary server and must not be installed on the secondary server.

If Exchange Server 2003 administration software is already installed on the secondary server because you are upgrading from an earlier version of Cisco Unity, you are not required to remove it.

If Exchange Server 2003 administration software is not already installed on the secondary server, do not install it. The Cisco Unity System Setup Assistant automatically installs the Exchange software that Cisco Unity requires.

Both Cisco Unity servers must connect to the same phone system.

Both Cisco Unity servers must have the same enabled features and configurations.

The Cisco Unity system must be installed in the Voice Messaging configuration. For information on the maximum number of subscribers supported in this configuration, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

Either SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition must be installed on both the primary and secondary servers. (Neither SQL Server 2005 Express nor MSDE 2000 is supported on either server with Cisco Unity failover.)

Cisco Unity directory and message store services must log on by using the same domain accounts on both the primary and secondary servers.

MSSQLSERVER and SQLSERVERAGENT services on both Cisco Unity servers must be configured to log on as the same domain account, and the account must belong to the Local Administrators group on each server. SQLSERVERAGENT on the primary server must be able to log on to SQL Server on the secondary server by using Windows NT authentication.

All software must be installed on the same drive and directories on the primary and secondary servers.

The same version of Windows must be installed on both Cisco Unity servers.

Failover Requirements for Separating Cisco Unity Servers by a Firewall

Revised May 3, 2010

The network must meet the requirements listed in the "Network Requirements" section.

Separating Cisco Unity servers by a firewall is not supported for the failover configuration in which Exchange is installed on the secondary server.

The primary server can be separated by a Cisco ASA firewall from the following servers only in a specific configuration:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

For information on configuring the ASA firewall, see the "Requirements for Configuring a Cisco ASA Firewall for Cisco Unity" section. Other firewalls are not supported.

If the Cisco Unity system includes a voice-recognition server, separating the Cisco Unity servers by a firewall is not supported. Both Cisco Unity servers must be on the same side of a firewall as a Cisco Unity voice-recognition server.

The partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server with which the partner server communicates.

Cisco Unity failover was designed with the expectation that the primary server generally would be the active server. So, the secondary server must be used as the active server only for brief periods. The problem with the primary server must be resolved promptly, and the primary server must be made the active server again at the earliest opportunity.

When separating the primary and secondary servers from one another or from other servers by a firewall, the applicable TCP and UDP ports must be open in the firewall. For details on the TCP/UDP ports used by Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter of the Security Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Failover Requirements for Installing Cisco Unity Servers in Separate Buildings or Sites

Revised May 3, 2010

The path of connectivity between the Cisco Unity servers must be gigabit speed or higher with no steady-state congestion.

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 Cisco Unity servers can be separated by a Cisco ASA firewall from the following servers only in a specific configuration:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

For information on configuring the ASA firewall, see the "Requirements for Configuring a Cisco ASA Firewall for Cisco Unity" section. Other firewalls are not supported.

The partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server which with the partner server communicates.

If the Cisco Unity system includes a voice-recognition server, separating the Cisco Unity servers by a firewall is not supported. Both Cisco Unity servers must be on the same side of a firewall as a Cisco Unity voice-recognition server.

When separating the Cisco Unity primary or secondary servers from one another or from other servers by a firewall, the applicable TCP and UDP ports must be open in the firewall. For details on the TCP/UDP ports used by Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter of the Security Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Requirements for Standby Redundancy

Standby Redundancy Requirements When the Message Store Is Installed on a Separate Platform

Standby Redundancy Requirements When Exchange Server 2003 Is Installed on the Primary Cisco Unity Server

Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall


Note For failover requirements, see the "Requirements for Cisco Unity Failover" section.


Standby Redundancy Requirements When the Message Store Is Installed on a Separate Platform

Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay.

The network must meet the requirements listed in the "Network Requirements" section.

There must be a minimum connection of 100 Mbps between the primary and secondary Cisco Unity servers.

One Cisco Unity server is designated the primary server, and the other Cisco Unity server is designated the secondary (or standby) server.

Both Cisco Unity servers must be member servers in the same Active Directory domain. Do not install Active Directory on either Cisco Unity server.

When servers are installed in different locations, each location must have a domain controller/global catalog server.

The names of both Cisco Unity servers must be unique in the first 14 characters.

Both Cisco Unity servers must use the same Exchange server as the partner server.

Exchange Server must be installed on computers other than the Cisco Unity servers.

If Exchange Server 2003 administration software is already installed on the Cisco Unity servers because you are upgrading from an earlier version of Cisco Unity, you are not required to remove it.

If Exchange Server 2003 administration software is not already installed on the Cisco Unity servers, do not install it. The Cisco Unity System Setup Assistant automatically installs the Exchange software that Cisco Unity requires.

The primary Cisco Unity server must be located in the same LAN as the partner Exchange server.

Both Cisco Unity servers must have the same enabled features and configurations.

Either SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition must be installed on both the primary and secondary servers. (Neither SQL Server 2005 Express nor MSDE 2000 is supported on either server with Cisco Unity standby redundancy.)

Cisco Unity directory and message store services must log on by using the same domain accounts on both the primary and secondary servers.

MSSQLSERVER and SQLSERVERAGENT services on both Cisco Unity servers must be configured to log on as the same domain account, and the account must belong to the Local Administrators group on each server. SQLSERVERAGENT on the primary server must be able to log on to SQL Server on the secondary server by using Windows NT authentication.

All software must be installed on the same drive and directories for both primary and secondary servers.

The same version of Windows must be installed on both Cisco Unity servers.

Standby Redundancy Requirements When Exchange Server 2003 Is Installed on the Primary Cisco Unity Server


Caution If the message store is already installed on a separate platform, do not reconfigure the existing Cisco Unity system to move Exchange to the primary Cisco Unity server. Otherwise, Cisco Unity standby redundancy is not supported. Only new installations of Cisco Unity with standby redundancy can be configured with Exchange on the primary server.

Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay.

The network must meet the requirements listed in the "Network Requirements" section.

There must be a connection of 100 Mbps between the primary and secondary Cisco Unity servers.

One Cisco Unity server is designated the primary server, and the other Cisco Unity server is designated the secondary (or standby) server.

This configuration is supported only when Cisco Unity is installed in the Voice Messaging configuration.

Both Cisco Unity servers must be member servers in the same Active Directory domain. Do not install Active Directory on either Cisco Unity server.

If the Cisco Unity servers are being installed into an existing forest, both data centers must have one or more DC/GCs and one or more DNS servers.

If the Cisco Unity servers are being installed into a new forest, both must be DC/GCs in the same Active Directory domain and have one or more DNS servers.

The names of both Cisco Unity servers must be 14 characters or shorter.

If Exchange Server 2003 administration software is already installed on the secondary server because you are upgrading from an earlier version of Cisco Unity, you are not required to remove it.

If Exchange Server 2003 administration software is not already installed on the primary and secondary servers, do not install it. The Cisco Unity System Setup Assistant automatically installs the Exchange software that Cisco Unity requires.

Both Cisco Unity servers must use the same Exchange server as the partner server.

Both Cisco Unity servers must have the same enabled features and configurations.

Either SQL Server 2005 Standard Edition or SQL Server 2000 Standard Edition must be installed on both Cisco Unity servers. (Neither SQL Server 2005 Express nor MSDE 2000 is supported on either server with Cisco Unity standby redundancy.)

Cisco Unity directory and message store services must log on by using the same domain accounts on both the primary and secondary servers.

MSSQLSERVER and SQLSERVERAGENT on both Cisco Unity servers must be configured to log on as the same domain account, and the account must belong to the Local Administrators group on each server. SQLSERVERAGENT on the primary server must be able to log on to SQL Server on the secondary server by using Windows NT authentication.

All software must be installed on the same drive and directories for both Cisco Unity servers.

The same version of Windows must be installed on both Cisco Unity servers.

Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall

Revised May 3, 2010

The network must meet the requirements listed in the "Network Requirements" section.

The primary server can be separated by a Cisco ASA firewall from the following servers only in a specific configuration:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

For information on configuring the ASA firewall, see the "Requirements for Configuring a Cisco ASA Firewall for Cisco Unity" section. Other firewalls are not supported.

The partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server that the partner server communicates with.

Cisco Unity standby redundancy was designed with the expectation that the primary server generally would be the active server. So, the secondary server must be used as the active server only for brief periods. The problem with the primary server must be resolved promptly, and the primary server must be made the active server again at the earliest opportunity.

When separating the Cisco Unity primary and secondary servers from one another or from other servers by a firewall, the applicable TCP and UDP ports must be open in the firewall. For details on the TCP/UDP ports used by Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter of the Security Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Requirements for Cisco Unity Phone View

Cisco Unity integrated with a supported version of Cisco Unified Communications Manager. For compatibility information, see SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express or SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

A supported Cisco Unified IP Phone model, with the supported Cisco Unified Communications Manager version firmware installed. For supported phone models, see the "Supported Phone Models for Use with Cisco Unity Phone View" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/support/8xcusupp.html.

The calling number that Cisco Unified Communications Manager presents to Cisco Unity must be a valid Directory Number (DN) in the list of phone devices that Cisco Unity retrieves from the phone system. Phone View may not work correctly with masked DNs.

Requirements for More Than 96 Voice Messaging Ports or More Than 7,500 Subscribers on a Cisco Unity Server

A supported platform. See the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.


Note Some servers that support more than 96 voice messaging ports do not support more than 7,500 subscribers.


The /3GB and /userva=2800 switches must be added to the Windows boot.ini file.

In the Cisco Unity Tools Depot, in the Advanced Settings Tool, the Messaging-72 or More Voice Ports-Enable Low-Fragmentation Heap setting must be enabled.

Available Languages for Cisco Unity Components

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

Cisco Personal Communications Assistant

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Belgium, English-United States, French, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Colombia, Spanish-Spain

Cisco Personal Communications Assistant Help

English-United States

Cisco Unity Administrator

English-United States, French-France, German, Japanese

Cisco Unity Administrator Help

English-United States, Japanese

Cisco Unity Phone View

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Netherlands, English-United States, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Portugal, Russian, Spanish-Spain

System prompts

Arabic-Saudi Arabia, Catalan-Spain, Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Belgium, Dutch-Netherlands, English-Australia, English-Canada, English-New Zealand, English-United Kingdom, English-United States, English TTY/TDD-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Norwegian-Bokmål, Polish, Portuguese-Brazil, Portuguese-Portugal, Russian, Spanish-Colombia, Spanish-Spain, Swedish, Welsh-Wales

Text-to-speech engine

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Netherlands, English-United Kingdom, English-United States, French-Canada, French-France, German, Italian, Japanese, Korean, Norwegian-Bokmål, Portuguese-Brazil, Portuguese-Portugal, Spanish-Spain, Swedish

ViewMail for Outlook

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Netherlands, English-United States, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Colombia, Spanish-Spain

ViewMail for Outlook Help

English-United States

Voice-recognition engine

English-United States

Product documentation for administrators/installers

English-United States, Japanese

Product documentation for end users

English-United States, Japanese

Numeric and Alphabetic Codes for Supported Languages in Cisco Unity

Use the numeric codes in Table 3 when you are using the Cisco Unity Bulk Import wizard and a CSV file to create or update users. Enter the applicable four- or five-digit numeric code in the CALLERS_LANGUAGE and SUBSCRIBERS_LANGUAGE columns for each user.

For more information, see the "Using the Cisco Unity Bulk Import Wizard to Create Multiple Subscriber Accounts" section in the "Managing Subscriber Accounts in Cisco Unity 8.x" chapter of the System Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.html.

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

Table 3 Codes for Languages Supported in Cisco Unity 

Language
Numeric Code
Alphabetic Code

Arabic-Saudi Arabia

1025

ARA

Catalan-Spain

1027

CAT

Chinese-Hong Kong SAR

3076

ZHH

Chinese-PRC

2052

CHS

Chinese-Taiwan

1028

CHT

Czech

1029

CSY

Danish

1030

DAN

Dutch-Belgium

2067

NLB

Dutch-Netherlands

1043

NLD

English-Australia

3081

ENA

English-Canada

4105

ENC

English-New Zealand

5129

ENZ

English-United Kingdom

2057

ENG

English-United States

1033

ENU

English TTY/TDD-United States

33801

ENX

French-Canada

3084

FRC

French-France

1036

FRA

German-Germany

1031

DEU

Hungarian

1038

HUN

Italian-Italy

1040

ITA

Japanese

1041

JPN

Korean

1042

KOR

Norwegian-Bokmål

1044

NOR

Polish

1045

PLK

Portuguese-Brazil

1046

PTB

Portuguese-Portugal

2070

PTG

Russian

1049

RUS

Spanish-Colombia

9226

ESO

Spanish-Spain (Traditional Sort)

1034

ESP

Swedish

1053

SVE

Welsh-Wales

1106

CYM


Characteristics of Cisco Unity Configurations

See the applicable section:

Cisco Unity Unified Messaging Configuration

Cisco Unity Voice Messaging Configuration

Cisco Unity Unified Messaging Configuration

The Cisco Unity Unified Messaging configuration has the following characteristics:

The Cisco Unity server handles only voice messages and, optionally, text-to-speech (TTS) playback of email messages. Voice and email messages are stored on the message store servers.

Subscribers check messages by using the phone, the Cisco Unity Inbox, or an email client. (The Cisco Unity Inbox is accessed through the Cisco Personal Communications Assistant.)

Cisco Unity administration may be performed over the network.

Subscribers have access to the Cisco Unity Assistant through the Cisco PCA.

Voicemail and email attributes on subscriber accounts may be administered from a single location by using the Cisco Unity Administrator.

Cisco requires that anyone installing a Cisco Unity server as a Unified Messaging server be certified as a Microsoft Certified System Engineer.

Cisco Unity Voice Messaging Configuration

The Cisco Unity Voice Messaging configuration has the following characteristics:

The Cisco Unity server handles only voice messages.

Subscribers check messages by using the phone or from the Cisco Unity Inbox (accessed through the Cisco Personal Communications Assistant).

Subscribers have access to the Cisco Unity Assistant through the Cisco PCA.

Cisco Unity administration may be performed over the network.

Email attributes, if any, and voicemail attributes on subscriber accounts must be administered separately.