Table Of Contents
System Requirements for Cisco Unity Connection Release 9.x
Hardware Requirements
Supported Optional Hardware
Software Requirements
Software Requirements—Cisco Unity Connection Server
Software Requirements—Administrator Workstations (Cisco Unity Connection and Cisco Unity Connection SRSV )
Software Requirements—User Workstations
Requirements for the Phone System Integration
Licensing Requirements
Requirements for Using Unified Messaging Features
Unified Messaging Requirements: Synchronizing Connection and Exchange Mailboxes (Single Inbox)
Unified Messaging Requirements: SpeechView Transcriptions
Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech
Unified Messaging Requirements: Accessing Calendar Information for Meetings
Unified Messaging Requirements: Accessing Exchange Contact Information
Requirements for Using Voice-Recognition Features
Requirements for Using SpeechView Transcriptions
Requirements for Accessing the Connection Web Tools Through the Cisco PCA
Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Web Inbox
Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Mini Web Inbox
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 Connection Voice Messages by Using an IMAP Email Client
Requirements for Accessing Connection Voice Messages by Using Cisco Unified Personal Communicator
Requirements for Accessing Connection Voice Messages by Using Cisco Mobile and Cisco Unified Mobile Communicator
Requirements for Accessing Connection Voice Messages by Using Cisco Unified Messaging with IBM Lotus Sametime
Requirements for Accessing Connection Voice Messages by Using Visual Voicemail
Requirements for Accessing Connection Voice Messages by Using RSS Readers
Requirements for Accessing Exchange Email Messages By Using Text to Speech
Requirements for Accessing Calendar Information for Meetings
Requirements for Accessing Exchange Contact Information
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 9.x Cluster
Connection Cluster Requirements When the Servers Are Installed in the Same Building or Site
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
Requirements for VPIM Networking
Requirements for Using a Provisioning Application
Requirements for Migrating from Cisco Unity Connection 1.x to Version 9.x
Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity Connection Version 9.x By Using a Flash Cutover
Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version 9.x By Using a Gradual Migration
Requirements for Installing Cisco Unity Connection on a Virtual Machine
Directory Object Limits for Cisco Unity Connection 9.x
Available Languages for Cisco Unity Connection 9.x Components
Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection 9.x
System Requirements for Cisco Unity Connection Release 9.x
Revised May 24, 2013
This document lists requirements for a Cisco Unity Connection version 9.x system. It contains the following sections:
•
Hardware Requirements
•Software Requirements
•Requirements for the Phone System Integration
•Licensing Requirements
•Requirements for Using Unified Messaging Features
•Requirements for Using Voice-Recognition Features
•Requirements for Using SpeechView Transcriptions
•Requirements for Accessing the Connection Web Tools Through the Cisco PCA
•Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Web Inbox
•Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Mini Web Inbox
•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 Connection Voice Messages by Using an IMAP Email Client
•Requirements for Accessing Connection Voice Messages by Using Cisco Unified Personal Communicator
•Requirements for Accessing Connection Voice Messages by Using Cisco Mobile and Cisco Unified Mobile Communicator
•Requirements for Accessing Connection Voice Messages by Using Cisco Unified Messaging with IBM Lotus Sametime
•Requirements for Accessing Connection Voice Messages by Using Visual Voicemail
•Requirements for Accessing Connection Voice Messages by Using RSS Readers
•Requirements for Accessing Exchange Email Messages By Using Text to Speech
•Requirements for Accessing Calendar Information for Meetings
•Requirements for Accessing Exchange Contact Information
•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 9.x Cluster
•Requirements for Cisco Unity Connection Networking
•Requirements for Using Single Sign-On Feature
•Requirements for VPIM Networking
•Requirements for Using a Provisioning Application
•Requirements for Migrating from Cisco Unity Connection 1.x to Version 9.x
•Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity Connection Version 9.x By Using a Flash Cutover
•Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version 9.x By Using a Gradual Migration
•Requirements for Installing Cisco Unity Connection on a Virtual Machine
•Directory Object Limits for Cisco Unity Connection 9.x
•
•Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection 9.x
Hardware Requirements
•A server that meets Cisco Unity Connection specifications. See the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Caution If you try to install version 9.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 9.x Supported Platforms List to verify platform specifications, particularly regarding memory and processor speed.
•If you are upgrading from an earlier version of Connection or migrating from Cisco Unity to Connection 9.x, you may need to replace the existing server, or add memory and/or replace hard disks for the installation to complete successfully and for Connection to function properly. For information on whether your current server is supported for Connection 9.x and, if so, whether you need to upgrade the hardware, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
•If you are adding features, for example, Cisco Unity Connection Networking, a Connection cluster, or single inbox, you may need to replace hard disks or add memory to the Connection server for the feature to be supported. For more information, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
Supported Optional Hardware
The following optional hardware is supported for use with Cisco Unity Connection 9.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
•Software Requirements—Administrator Workstations (Cisco Unity Connection and Cisco Unity Connection SRSV )
•Software Requirements—User Workstations
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 (Cisco Unity Connection and Cisco Unity Connection SRSV )
Revised May 24, 2013
•To access web applications on the Cisco Unity Connection and Cisco Unity Connection SRSV server, the operating system and web browser must be compatible with the version of 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 9.x and Cisco Unity Connection SRSV
Operating System
on Administrator Workstation
|
Browser on Administrator Workstation
|
Microsoft Windows Vista
(32 bit and 64 bit)
|
•Microsoft Internet Explorer 7.0, 8.0 and 9.0(1)(32 bit)
•Mozilla Firefox 3.6, 10
|
Microsoft Windows XP
|
•Microsoft Internet Explorer 7.0 and 8.0
•Mozilla Firefox 3.6, 10.
|
Mac OS X 10.4 and later
|
•Mozilla Firefox 3.6, 10
•Safari 5.1
|
Red Hat Enterprise Linux
|
Mozilla Firefox 3.6, 10
|
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
|
Note•Cisco Unity Connection Administration (CUCA) is now supported over both IPv4 and IPv6. However, to access CUCA over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
•On RHEL, the IPv6 address is supported only through DNS.
•On Mozilla Firefox 10, the IPv6 address is supported only through DNS.
Note Cisco Unity Connection Web Interface drop down menus: Cisco Unity Connection Administration(CUCA) and Cisco Personal Communications Assistant(CPCA) are not supported for Google Chrome.
Caveats:
•Comet notification is not supported on Mozilla Firefox 3.6 over IPv6.
•The recording on MAC operating system is supported by the telephone record and playback (TRAP) functionality only, PC based recording is not supported.
•The Play functionality is supported via phone only as the Quick Time 64 bit plug-in is not available for Microsoft Internet Explorer 9.
Table 2 lists software required for correct browser configuration.
Table 2 Software Required for Correct Browser Configuration on Administrator Workstations for Cisco Unity Connection 9.x and Cisco Unity Connection SRSV
Browser
|
Required Software
|
Firefox
|
The following software, depending on the operating system:
•With Mac OS X:
–Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x).
–Java Embedding Plugin for Mac OS X version 0.9.5 or later.1
•With Linux:
–ALSA driver version 1.0.9 or later
–Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x).
•With Windows, Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x).
|
Internet Explorer
|
Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x).
|
Software Requirements—User Workstations
•The operating system and Web browser(s) on user workstations must be compatible with the version of Connection that you are installing, to allow users to access the 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 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 Connection voice messages, the email application must be compatible with the version of 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 9.x
Browser
|
Required Software
|
Firefox
|
The following software, depending on the operating system:
•With Mac OS X:
–Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x) or later.
–Java Embedding Plug-in for Mac OS X version 0.9.5 or later.1
•With Linux:
–ALSA driver version 1.0.9 or later
–Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x) or later.
•With Windows, Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x) or later.
|
Internet Explorer
|
Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x) or later.
|
Safari
|
Java 2 Platform, Standard Edition (J2SE) Runtime Environment 6 (1.6.x) or later.
|
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 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:
•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.
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
Revised November 23, 2012
In Cisco Unity Connection 9.0(1), the licenses for Connection are managed by the Enterprise License Manager (ELM) server. The following are the license tags supported by Connection 9.0(1) in conjunction with the ELM server:
•CUC_BasicMessaging: Allows you to use the following Connection features:
–Synchronization of Connection and Exchange mailboxes (single inbox)
–Calendar information for meetings
–Exchange contact information
–Intrasite/intersite networking
–VPIM networking
–Personal call transfer rules
–Users with Connection mailboxes
–Users with IMAP or Single Inbox access to voice messages
–Recording length
–Phone interface (TUI)
–Cisco Unity Connection Mini Web Inbox
–Cisco Unity Connection Web Inbox
–Cisco Unity Connection ViewMail for Microsoft Outlook 8.0 and later
–IMAP email client
–Cisco Unified Personal Communicator
–Cisco Mobile and Cisco Unified Mobile Communicator
–Cisco Unified Messaging with IBM Lotus Sametime
–Visual Voicemail
–RSS readers
–Cisco Unity Connection Phone View
•CUC_SpeechView: Allows you to use SpeechView standard transcription service.
•CUC_SpeechViewPro: Allows you to use SpeechView professional transcription service.
•CUC_SpeechConnectPort: Allows you to use Speech Connect, text-to speech, and voice-recognition features.
•CUC_EnhancedMessaging: Allows you to use Cisco Unity Connection SRSV feature.
Requirements for Using Unified Messaging Features
See the applicable section:
•Unified Messaging Requirements: Synchronizing Connection and Exchange Mailboxes (Single Inbox)
•Unified Messaging Requirements: SpeechView Transcriptions
•Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech
•Unified Messaging Requirements: Accessing Calendar Information for Meetings
•Unified Messaging Requirements: Accessing Exchange Contact Information
Unified Messaging Requirements: Synchronizing Connection and Exchange Mailboxes (Single Inbox)
Revised January 15, 2013
•Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
–Exchange Server 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with 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 2 or later (All editions are supported.)
To synchronize Connection and Exchange 2007 mailboxes, you must install Connection 8.5(1) Service Update 1 (SU 1) or later.
–Exchange Server 2003 with Service Pack 2 (All editions are supported.)
To synchronize Connection and Exchange 2003 mailboxes, you must install 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.You can configure Connection to synchronize voice messages in 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 Connection's integration with Microsoft BPOS Dedicated environments, see the "Cisco Unity Connection 9.x Overview" chapter of the Design Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/design/guide/9xcucdgx.html.
•Microsoft Office 365 is supported with Cisco Unity Connection. 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 Connection integration with Microsoft Office-365, see the "Configuring Cisco Unity Connection 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/9x/unified_messaging/guide/9xcucumgx.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. Connection supports a maximum of 20 unified messaging services per Connection server.
•Depending on the number of voice messaging ports on each 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 Connection clusters, see the "Requirements for a Cisco Unity Connection 9.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 Connection configuration is sufficient for a maximum of 2000 users and 80 milliseconds of round-trip latency between 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" chapter of the Design Guide for Cisco Unity Connection Release 9.x. at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/design/guide/9xcucdgx.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 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 Connection voice messages in Exchange, but users will not have the functionality provided by ViewMail for Outlook.
For information on 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 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 Connection are still removed from user mailboxes and are replaced with a recording that tells the user "This message is expired."
The synchronization of voice messages in Connection and Exchange Mailboxes for single inbox (SIB) users is now supported over both IPv4 and IPv6.
Note Single Inbox over IPv6 is supported only for Exchange 2007 and Exchange 2010.
Unified Messaging Requirements: SpeechView Transcriptions
The SpeechView feature—which provides transcriptions of voice messages—is supported with Cisco Unity Connection.
•Required licenses must be installed on the Enterprise License Manager (ELM) server to use SpeechView service.
•Users must be assigned to a class of service enabled for using SpeechView transcriptions of voice messages.
For Connection 9.0(1) requirements, see the "Requirements for Using SpeechView Transcriptions" section.
Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech
•Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
–Exchange Server 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with 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 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.
Microsoft Office 365 emails configured with Connection are 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. Connection supports a maximum of 20 unified messaging services per Connection server.
Note Text-to-speech with Exchange 2007 and 2010 is now supported over both IPv4 and IPv6. However, to access Text-to-speech over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
For Connection 9.0(1) requirements, see the "Requirements for Accessing Exchange Email Messages By Using Text to Speech" section.
Unified Messaging Requirements: Accessing Calendar Information for Meetings
Cisco Unity Connection integrated with a supported application for calendar information:
•When accessing Exchange calendars, Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
–Exchange Server 2010 with Update Rollup 3 or later (All editions are supported.)
–Exchange Server 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with Service Pack 1 (All editions are supported.)
–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.
Microsoft Office 365 calendars configured with Connection are 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. Connection supports a maximum of 20 unified messaging services per Connection server.
Note Accessing Exchange 2007/2010 calendars is now supported over both IPv4 and IPv6. However, to access Exchange 2007/2010 calendars over IPv6 address, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
For Connection 9.0(1) requirements, see the "Requirements for Accessing Calendar Information for Meetings" section.
Unified Messaging Requirements: Accessing Exchange Contact Information
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 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with 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 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. Connection supports a maximum of 20 unified messaging services per Connection server.
•Microsoft Office 365 contacts configured with Connection are supported.
Note Accessing Exchange 2007/2010 contacts is now supported over both IPv4 and IPv6. However, to access Exchange 2007/2010 contacts over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
For Connection 9.0(1) requirements, see the "Requirements for Accessing Exchange Contact Information" section.
Requirements for Using Voice-Recognition Features
•Required licenses must be installed on the Enterprise License Manager (ELM) server.
•Users must be assigned to a class of service enabled for using voice recognition.
•Phone systems must be configured to send calls to 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
The SpeechView feature—which provides transcriptions of voice messages—is supported with Cisco Unity Connection.
•Required licenses must be installed on the Enterprise License Manager (ELM) server to use SpeechView service.
•Users must be assigned to a class of service enabled for using SpeechView transcriptions of voice messages.
For Connection 9.0(1) requirements, see the "Unified Messaging Requirements: SpeechView Transcriptions" section.
Requirements for Accessing the Connection Web Tools Through the Cisco PCA
Messaging Assistant web tool
•Users must be assigned to a class of service enabled for using the Messaging Assistant.
•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.
Web Inbox web tool
•Users must be assigned to a class of service enabled for using the Web Inbox and RSS feeds.
•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.
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.
Note Cisco Personal Communications Assistant (CPCA) is now supported both over IPv4 and IPv6. However, to access CPCA over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Web Inbox
•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.
Note Web Inbox is now supported over both IPv4 and IPv6. However, to access Web Inbox over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Voice Messages by Using the Cisco Unity Connection Mini Web Inbox
•Make sure the trusted certificate of the certification authority is added to the Trusted Root Store on the user workstations in order to access the notifications via email and the voice message via Connection Mini Web Inbox. For more information on how to configure the trusted certificate on Cisco Unity Connection, refer to the "Securing Cisco Unity Connection Administration, Cisco PCA, and IMAP Email Client Access to Cisco Unity Connection 9.x" chapter of the System Administration Guide for Cisco Unity Connection Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.html.
•Make sure to perform the steps to configure the HTML notification on user workstation. For more information on how to configure the HTML notifications, refer to the "Configuring Cisco Unity Connection9.x for HTML-based Message Notification" section of the "Configuring an Email Account to Access Cisco Unity Connection 9.x Voice Messages" chapter of the User Workstation Setup Guide for Cisco Unity Connection, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/user_setup/guide/9xcucuwsx.html.
•Make sure to perform the steps to configure the Connection Mini Web Inbox on user workstation. For more information on how to configure the Connection Mini Web Inbox, refer to the "Configuring Internet Explorer 8 for Cisco Unity Connection Mini Web Inbox" section of the "Configuring an Email Account to Access Cisco Unity Connection 9.x Voice Messages" chapter of the User Workstation Setup Guide for Cisco Unity Connection Release 9.x, available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/user_setup/guide/9xcucuwsx.html.
•Audio Playback on Computer
–Mozilla Firefox 10 plays voice messages on Cisco Unity Connection Mini Web Inbox using HTML 5 Audio (.wav format).
–Microsoft Internet Explorer 8, Microsoft Internet Explorer 9, and Mozilla Firefox 3.6 require the compatible Quick Time Plug-in to play the voice messages.
•Audio Recording on Computer
–Microsoft Internet Explorer 8, Microsoft Internet Explorer 9, Mozilla Firefox 3.6, and Mozilla Firefox 10 require the compatible Adobe Flash Player.
Caveats:
•On Microsoft Internet Explorer 9 (64 bit) - Play is supported via phone only as the Quick Time 64 bit plug-in is not available for Internet Explorer 9.
•On MAC OS - The recording on MAC OS is supported by telephone record and playback functionality only, computer based recording is not supported.
For 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.
Note Mini Web Inbox is supported over both IPv4 and IPv6. However, to access Mini Web Inbox over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Voice Messages by Using Cisco Unity Connection ViewMail for Microsoft Outlook 8.0(1)
•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
•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.
Cisco Unity Connection ViewMail for Microsoft Outlook 8.5 and later now support the single sign-on functionality. For more information, refer to the "Support For Single Sign-On in ViewMail for Outlook(VMO)" section of the Release Notes for Cisco ViewMail for Microsoft Outlook Release 8.6(5) available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/vmo/release/notes/865cucvmorn.html.
Note Cisco Unity Connection ViewMail for Microsoft Outlook (VMO) 8.6(7) is supported over both IPv4 and IPv6. For more information on VMO 8.6(7) over IPv6 support, see Release Notes for Cisco ViewMail for Microsoft Outlook Release 8.6(7) at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/vmo/release/notes/867cucvmorn.html.
Requirements for Accessing Connection Voice Messages by Using an IMAP Email Client
•Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.
•A supported IMAP email client 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.
•Sound card, speakers, and media player on user workstations.
Note Accessing Connection voice messages using IMAP clients is now supported over both IPv4 and IPv6. However, to access voice messages using IMAP clients over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Connection Voice Messages by Using Cisco Unified Personal Communicator
•Users must be assigned to a class of service that is enabled for accessing voice messages by using a unified client.
•A supported version of Cisco Unified Personal Communicator 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, 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 9.x.
Cisco Unified Personal Communicator versions 8.0 and later support IMAP IDLE.
Requirements for Accessing 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.
Note Cisco 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 Connection servers, see the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Requirements for Accessing Connection Voice Messages by Using Cisco Unified Messaging with IBM Lotus Sametime
•Users must be assigned to a class of service that is enabled for accessing voice messages by using an IMAP client.
•A Cisco Unified Messaging with Lotus Sametime version supported for use with the 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.
•Sound card, speakers, and media player.
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 9.x.
Note Cisco 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 Connection servers, see the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Requirements for Accessing Connection Voice Messages by Using Visual Voicemail
•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/ps9929/prod_release_notes_list.html.
Requirements for Accessing 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.
Note RSS feeds is now supported over both IPv4 and IPv6. However, to access RSS feeds over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Exchange Email Messages By Using Text to Speech
•Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
–Exchange Server 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with 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 2 or later (All editions are supported.)
–Exchange Server 2003 with Service Pack 2 (All editions are supported.)
•Exchange server(s) in a supported Windows domain configuration. Table 4 lists the supported configurations.
Table 4 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 domain controller/global catalog server.
•Exchange server is a Windows Server 2003 member server.
|
One server running
Exchange Server 2003
|
•Exchange server is a Windows Server 2003 domain controller/global catalog server.
•Exchange server is a Windows Server 2003 member server.
|
•The Cisco Unity Connection server and the Exchange server(s) must be located in the same local-area network.
For Connection 9.x requirements, see the "Unified Messaging Requirements: Accessing Exchange Email Messages By Using Text to Speech" section.
Note Text-to-speech over Exchange 2007 and 2010 is now supported over both IPv4 and IPv6. However, to access Text-to-speech over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Calendar Information for Meetings
Cisco Unity Connection integrated with a supported application for calendar information:
•Exchange Server 2010 with Update Rollup 3 or later (All editions are supported.)
•Exchange Server 2010 with Service Pack 2(All editions are supported.)
•Exchange Server 2010 with Service Pack 1 (All editions are supported.)
•Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)
•Exchange Server 2003 with Service Pack 2 (All editions are supported.)
For Connection 9.x requirements, see the "Unified Messaging Requirements: Accessing Calendar Information for Meetings" section.
Note Accessing Exchange 2007/2010 calendars is now supported over both IPv4 and IPv6. However, to access Exchange 2007/2010 calendars over IPv6 address, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
Requirements for Accessing Exchange Contact Information
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 2010 with Service Pack 2(All editions are supported.)
–Exchange Server 2010 with 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 2 or later (All editions are supported.)
–Exchange Server 2003 with Service Pack 2 (All editions are supported.)
For Connection 9.x requirements, see the "Unified Messaging Requirements: Accessing Exchange Contact Information" section.
Note Accessing Exchange 2007/2010 contacts is now supported over both IPv4 and IPv6. However, to access Exchange 2007/2010 contacts over IPv6, Connection platform must be configured in Dual (IPv4/IPv6) mode. For more information on Configuring IPv6 settings, see "Adding or Changing the IPv6 Addresses of Cisco Unity Connection" chapter of Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/upgrade/guide/9xcucrugx.html.
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 September 14, 2012
•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
•Cisco Unity Connection integrated with a supported LDAP directory. Table 5 lists supported directories and the 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 Connection accesses for synchronization and for authentication become unavailable.
Table 5 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
|
Sun ONE Directory Server 5.2 and later
|
No
|
•When you are using Active Directory, you can integrate a single Connection server with more than one user search base, but all user search bases must be in the same Active Directory forest. To integrate Connection with more than one forest, you must install one digitally networked Connection server per forest.
•When you are configuring 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 ONE directory server, you can integrate a single Connection server with more than one user search base, but all user search bases must be in the same tree. To integrate Connection with more than one tree, you must install one digitally networked Connection server per tree.
Requirements for a Cisco Unity Connection 9.x Cluster
See the applicable section:
•Connection Cluster Requirements When the Servers Are Installed in the Same Building or Site
•Connection Cluster Requirements When the Servers Are in Separate Buildings or Sites
Connection Cluster Requirements When the Servers Are Installed in the Same Building or Site
•Both servers must meet specifications according to the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
•For a cluster with two physical servers, both must have the same platform overlay.
•For a cluster with two virtual machines, both must have the same virtual platform overlay.
•For a cluster with one physical server and one virtual machine:
–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 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 Connection servers must be collocated.
•Both Connection servers must be located in the same local-area network.
•Both Connection servers must have a minimum 100 Mbps connection to the network.
•The maximum round-trip latency must be no more than 5 ms.
•The network must use the following load-balancing techniques for connections to the Connection servers:
–The Connection servers are assigned a common DNS name with the Connection publisher server first.
–All user client and administrator sessions connect to the Connection publisher server. If the Connection publisher server stops functioning, the user client and administrator sessions must connect to the Connection subscriber server.
–Phone systems must attempt to route incoming calls to the Connection subscriber server. If no voice messaging ports are available to answer calls on the Connection subscriber server, the phone systems must route calls to the Connection publisher server.
•The Connection servers must not be separated by a firewall.
•Both Connection servers must have the same software and engineering-special versions installed.
•Both Connection servers must have the same enabled features and configurations.
•Both Connection servers must connect to the same phone system(s).
•If the Connection servers contain dual NICs, the two NICs on each 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 Connection, a memory upgrade. To determine whether your server requires a memory upgrade, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
•For selected servers supported for earlier versions of Connection, replacement hard disks. To determine whether your server requires hard-disk replacement, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
Note The Connection cluster feature is not supported for use with Cisco Unified Communications Manager Business Edition.
Connection Cluster Requirements When the Servers Are in Separate Buildings or Sites
•Both servers must meet specifications according to the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
•For a cluster with two physical servers, both must have the same platform overlay.
•For a cluster with two virtual machines, both must have the same virtual platform overlay.
•For a cluster with one physical and one virtual machine:
–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 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 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 60 ms.
•The network must use the following load-balancing techniques for connections to the Connection servers:
–The Connection servers are assigned a common DNS name with the Connection publisher server first.
–All user client and administrator sessions connect to the Connection publisher server. If the Connection publisher server stops functioning, the user client and administrator sessions must connect to the Connection subscriber server.
–Phone systems must attempt to route incoming calls to the Connection subscriber server. If no voice messaging ports are available to answer calls on the Connection subscriber server, the phone systems must route calls to the 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 9.x" chapter of the Security Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/security/guide/9xcucsecx.html.
•Both Connection servers must have the same software and engineering-special versions installed.
•Both Connection servers must have the same enabled features and configurations.
•Both Connection servers must be configured to be in the same time zone.
•Both Connection servers must connect to the same phone system(s).
•If the Connection servers contain dual NICs, the two NICs on each 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 Connection, a memory upgrade. To determine whether your server requires a memory upgrade, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
•For selected servers supported for earlier versions of Connection, replacement hard disks. To determine whether your server requires hard-disk replacement, see the applicable server-specific table in the Cisco Unity Connection 9.x Supported Platforms List.
•The 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 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
•Requirements for Intersite Networking
Requirements for Intrasite Networking
Intrasite networking uses SMTP to provide directory synchronization and message networking among Cisco Unity Connection servers.
Connection version 7.x servers, version 8.x, and version 9.x servers can coexist in the same site as long as each 7.x server meets all the applicable requirements in the System 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 9.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 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html..
•The virtual directory created by the networked Connection servers must not exceed the maximum total numbers of objects listed in Table 7 in the "Directory Object Limits for Cisco Unity Connection 9.x" section.
Note Intrasite networking is not supported for use with Cisco Unified Communications Manager Business Edition.
Requirements for Intersite Networking
You can use intersite networking to link one Cisco Unity Connection site to another Connection site. Or you can use it to link a 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 Connection server or cluster in the Cisco Voicemail Organization must be at version 9.x, and must meet all applicable requirements listed in this document.
•Each Connection site must meet the requirements listed in the "Requirements for Intrasite Networking" section.
•Each Connection site gateway must be able to route SMTP messages to the remote site gateway (when two Connection sites are linked) or to the Microsoft Exchange organization for delivery to the Interoperability Gateway for Microsoft Exchange (when a 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 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 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
•The virtual directory created by the networked sites must not exceed the maximum total numbers of objects listed in Table 7 in the "Directory Object Limits for Cisco Unity Connection 9.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.
Note Intersite networking is not supported for use with Cisco Unified Communications Manager Business Edition.
Requirements for Using Single Sign-On Feature
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(1).
•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, 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 9.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 Connection 9.x and the following messaging systems:
•Cisco Unity Connection 9.x, 8.x, 7.x, and 2.x.
•Cisco Unity Connection in Cisco Unified Communications Manager Business Edition 9.x, 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 9.x" chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.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 Connection application.
Requirements for Migrating from Cisco Unity Connection 1.x to Version 9.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 9.x are different from requirements for Connection 1.x. The system must meet Connection 9.x requirements to receive support from Cisco TAC.
A migration from Connection version 1.x to 9.x has the following requirements:
•All applicable requirements listed in this document.
•Connection 1.2. If the Connection server is running version 1.1, you must upgrade to version 1.2 before you can migrate to version 9.x.
•A server that is supported for use with Connection and that meets Connection 9.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Connection 1.x are supported for use with Connection 9.x.) For information on supported Connection servers, including specifications on individual servers, see the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Caution If you try to install version 9.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 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 9.x Supported Platforms List.
Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity Connection Version 9.x By Using a Flash Cutover
Caution Requirements for Cisco Unity Connection are different from requirements for Cisco Unity. The system must meet Connection 9.x requirements to receive support from Cisco TAC.
A migration from Cisco Unity version 4.0(3) or later to Connection 9.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 Connection and that meets Connection 9.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Cisco Unity are supported for use with Connection.) For information on supported Connection servers, including specifications on individual servers, see the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Caution If you try to install version 9.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 Connection 9.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 9.x Supported Platforms List.
Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version 9.x By Using a Gradual Migration
Caution Requirements for Cisco Unity Connection are different from requirements for Cisco Unity. The system must meet Connection 9.x requirements to receive support from Cisco TAC.
A migration from Cisco Unity to Connection 9.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 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 Connection and that meets Connection 9.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Cisco Unity are supported for use with Connection.) For information on supported Connection servers, including specifications on individual servers, see the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Caution If you try to install version 9.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
For information on installing other Cisco Unified Communications applications on the same physical server on which Connection is installed, see the Unified Communications Virtualization wiki at http://cisco.com/go/uc-virtualized.
•Connection version 8.0(2) or later.
Connection 7.1(3) is required to migrate from a physical server running Connection 7.1(2) or earlier to a virtual server when the physical Connection server is not supported for use with Connection 9.x. However, after you complete the migration, you must upgrade the Connection virtual machine to version 8.0(2) or later. Running an earlier version in a production virtual environment is not supported.
•A physical host that meets Connection specifications and that is supported for use in a virtualized environment. See the Cisco Unity Connection 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
•The applicable edition of VMware vSphere ESXi Version 4.0 Update 1 or ESXi Version 4.1 installed on the host server on which the Connection virtual machine will run:
–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.
•For VMware configurations supporting 300GB and 500GB vDisks: The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size large enough to allow for the intended size of the virtual hard disk for the Connection virtual machine. For example, a block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.
•When deployed with the ESXi4.1, Cisco Unity Connection will support the VMware Boot from SAN functionality. See http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#ESXi_Support_for_Messaging_and_Presence_Applications for more information.
•Unity Connection 8.0(2) and later can be run on specification based hardware from Cisco, HP and IBM. However, some restrictions are applied. See http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support for more information.
•The support for the Input/Output devices on the servers that are running Connection as a virtual appliance has been enhanced to include FCoE and Cisco Converged Network adapters. See http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support#IO_Devices for more information.
•Unity Connection 8.0(2) and later now support FC, FCOE, iSCSI, and NFS SAN environments with some restrictions. See http://docwiki.cisco.com/wiki/Shared_Storage_Considerations for more information.
•For list of VMware features that are supported for Connection, see http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_Feature_Support_for_Messaging_and_Presence_8.0.282.29_through_8.6.281.29.
•Accessing a USB key is not supported.
•Oversubscribing processors and memory is not supported.
•At least one processor core must be available for the VMware hypervisor.
•All virtual disks assigned to the Connection virtual machine must be configured in independent-persistent mode, which provides the best storage performance.
•A network time protocol (NTP) server must be accessible to the Connection server.
•When configuring a Connection cluster, you can install Connection on one physical server and one virtual machine, or on two virtual machines, but the two virtual machines must be on separate physical hosts. When using blades as hosts, we recommend that the blades be on separate chassis.
Directory Object Limits for Cisco Unity Connection 9.x
Revised December 19, 2012
This section contains two tables that list directory object limits.
Table 6 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 Connection servers, the limits in Table 6 apply to each Connection server in the site or organization.
Table 7 applies to the virtual directory created by the networked Connection servers. When 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 9.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Table 6 Directory Object Limits for a Connection 9.x Server
Directory Object
|
Connection Version 9.0(1) Limit
|
Classes of service
|
3.000
|
Call handlers
|
40,000
|
Call routing rules
|
1,200
|
Mailbox stores
|
5
|
Search spaces
|
2000
|
Partitions
|
2000
|
User-defined contacts
|
100,000
|
VPIM locations
|
100
|
The limits in Table 7 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 Connection version 9.x, if the individual server platforms support the limits, you can have 10 locations in one site with 10,000 Connection users each, or 20 locations in two sites with 5,000 Connection users each.)
Table 7 Directory Object Limits for a Connection 9.x Site or Cisco Voicemail Organization
Directory Object
|
Connection
Version 9.x Limit
|
Connection locations
|
10 per site
|
VPIM locations
|
100 per site
|
Intersite links
|
1 per site
|
Total number of Connection users and administrator-defined contacts
|
100,000
|
System distribution lists
|
100,000
|
Members per system distribution list
|
25,000
|
Total number of distribution list members across all system distribution lists
|
1.5 million
|
Nested lists within a distribution list
|
20
|
Search spaces
|
10,000*
|
Partitions
|
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 9.x Components
Revised March 05, 2013
Note Languages are not licensed, and Connection 9.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 the Cisco Unity Connection 9.x Supported Platforms List (http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.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 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 ViewMail for Microsoft Outlook 8.5 and later
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
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
Cisco Unity Connection Mini Web Inbox
English-United States
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 9.x
Use the numeric codes in Table 8 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 9.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/9x/user_mac/guide/9xcucmacx.html.
Use the alphabetic codes to interpret language-related log entries and error codes.
Table 8 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
|
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.
Feedback
