Table Of Contents
Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x
PART 1: Supported Hardware for Use with Cisco Unity 7.x
Support for Windows 2000 on Servers Without a Windows 2000 Platform Configuration Disc
Supported Phone System Integrations
Supported IP Phone System Integrations
Supported Phone System Integrations Through PIMG or TIMG Units
Other Supported Phone System Integrations
Supported Phone Models for Use with Cisco Unity Phone View
PART 2: Supported Optional Software for Use with Cisco Unity 7.xAdditional Supported Optional Software
Unsupported Third-Party Software
PART 3: Cisco Unity Support PoliciesSupport Policy for AMIS Voice Messaging Systems
Support Policy for Antivirus Software
Support Policy for Apache Tomcat Upgrades
Support Policy for Backup Software
Support Policy for Hardware Virtualization Environments
Support Policy for IBM Lotus Domino Critical Fixpacks
Support Policy for Microsoft Data Execution Prevention
Support Policy for Microsoft Service Packs and Updates
Support Policy for Monitoring Software
Support Policy for Optional Software
Support Policy for Storage Area Networks
Support Policy for VPIM Voice Messaging Systems
Support Policy for Windows Automatic Update
Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x
Revised May 6, 2010This document lists hardware and software that are supported for use with a Cisco Unity system running version 7.x, and Cisco Unity support policies regarding hardware and software. It is divided into four parts:
PART 1: Supported Hardware for Use with Cisco Unity 7.x
PART 2: Supported Optional Software for Use with Cisco Unity 7.x
PART 3: Cisco Unity Support Policies
Running any application or service on the Cisco Unity server other than those described as supported in this document, or as supported or required in cross-referenced documents is not supported.
Note
For Cisco Unity requirements information, refer to System Requirements for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html.
PART 1: Supported Hardware for Use with Cisco Unity 7.x
•
•
•
•
•
•
Support for Windows 2000 on Servers Without a Windows 2000 Platform Configuration Disc
Revised October 30, 2008Cisco provides Microsoft Windows Server 2003 Platform Configuration discs for every currently shipping server qualified for use with Cisco Unity, but provides Windows 2000 Server Platform Configuration discs only for selected servers. You can install Windows 2000 Server on servers for which no Platform Configuration discs exist, but you must use a retail Windows disc and the hardware drivers provided by the server manufacturer.
If an issue is found to be related to the hardware drivers provided by the manufacturer, Cisco will evaluate the problem, and, as appropriate, issue a field notice, post an update, or direct the customer to updates on the vendor's website.
Cisco encourages customers to contact the hardware supplier for best practices regarding maintenance of their hardware and to apply standard driver updates that are minor in scope and risk, as appropriate. When the updates have been formally released by the hardware manufacturer, Cisco will support Cisco Unity running on servers on which the updates have been applied.
Supported Phone System Integrations
Cisco Unity integrates with the following phone systems:
•
•
•
Cisco Unity also supports integrations with multiple phone systems at one time. (Refer to the Multiple Phone System Integration Guide for Cisco Unity 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/integration/multiple_integration/guide/cuintmultiple.html. All 5.x content applies to version 7.x as well.)
Phone configuration files (.ini files) for recently qualified phone system integrations that are not yet available on Cisco Unity discs can be downloaded from the Cisco Unified Communications Applications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=280384298 (click Voice Mail and Unified Messaging > Cisco Unity).
Supported IP Phone System Integrations
•
•
•
Note
In addition, the Cisco Unified CM integrations support the use of Survivable Remote Site Telephony (SRST) installed on Cisco IOS platforms at remote sites.
For the supported versions of Cisco Unified CM and Cisco Unified CM Express, refer to the applicable document, depending on the integration type:
•
•
Supported Phone System Integrations Through PIMG or TIMG Units
Revised June 19, 2008Table 1 lists the supported circuit-switched phone systems with which Cisco Unity can integrate through PIMG or TIMG units (media gateways).
Table 1 Supported Phone System Integrations Through PIMG or TIMG Units
Media Gateways
Required Components1Any phone system that provides a serial data link (SMDI, MCI, or MD-110 protocol) to the master PIMG unit
Serial (SMDI, MCI, or MD-110)
Analog PIMG unit
•
(available from Cisco)•
•
Any phone system that provides a serial data link (SMDI, MCI, or MD-110 protocol) to the master TIMG unit
Serial (SMDI, MCI, or MD-110)
TIMG unit
•
(available from Cisco)•
•
Avaya Definity G3
Digital
Digital PIMG unit
•
•
In-band
TIMG unit
•
•
Avaya Definity ProLogix
Digital
Digital PIMG unit
•
•
Avaya S8300, Avaya S8500, and Avaya S8700
Digital
Digital PIMG unit
•
•
Avaya S8500 and Avaya S8700
In-band
TIMG unit
•
•
Mitel SX-200
Digital
Digital Mitel PIMG unit
•
•
Mitel SX-2000
Digital
Digital Mitel PIMG unit
•
•
NEC NEAX 2400
Digital
Digital PIMG unit
•
•
Nortel Meridian 1
(includes Succession, and SL 1)Digital
Digital PIMG unit
•
•
Rolm 9751 9005
Digital
Digital (Rolm) PIMG unit
•
•
Rolm 9751 9006
Digital
Digital (Rolm) PIMG unit
•
•
Siemens Hicom 300 E (European)
DTMF
Analog PIMG unit
•
•
Siemens Hicom 300 series
(North American)Digital
Digital PIMG unit
•
•
1 For recommendations and additional information on these components, see the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.
Other Supported Phone System Integrations
Table 2 lists other supported circuit-switched phone systems with which Cisco Unity can integrate (for example, through voice cards).
Caution
Table 2 Other Supported Phone System Integrations
Voice Cards
Required Components1Alcatel 4400
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Avaya Definity G3
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Avaya Definity Gx
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
•
(available from Cisco)•
•
Avaya Definity ProLogix
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Avaya Merlin Legend
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Centrex
(Avaya 1AESS, Avaya 5ESS, and Nortel DMS100)Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
•
ECI Coral III
(also marketed as
Tadiran Coral III)Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Ericsson MD-110
Serial (MD-110)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Fujitsu 9600
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Intecom E14 Millennium
Serial (SMDI)
Dialogic D/240PCI-T1
(24-port T1 card) only. See the "Supported Voice Cards" section.•
(available from Cisco)•
Intecom IBX S/80
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Matra 6500
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Mitel SX-200
DTMF (ONS)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Mitel SX-2000
DTMF (ONS)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
NEC NEAX 2000
Serial (MCI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
NEC NEAX 2400
Serial (MCI)
All voice cards. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Nortel Meridian 1
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
•
(available from Cisco)•
•
QSIG-enabled phone system
IP
N/A
•
•
QSIG or DPNSS phone system
IP
N/A
•
•
Rockwell Spectrum ACD
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
Siemens 9751 9006i
DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Siemens Hicom
300 series E CSDTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Syntegra ITS
(Requires an existing integration with Cisco Unified CM)Serial (SMDI)
Voice cards are not used.
•
(available from Cisco)•
•
•
Teltronics 20-20 LX
(Formerly Harris 20-20 LX)DTMF
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
Toshiba CTX 670
Serial (SMDI)
All voice cards except D/240PCI-T1. See the "Supported Voice Cards" section.
•
(available from Cisco)•
•
1 For recommendations and additional information on these components, see the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.
2 PBXLink boxes currently in use are supported when the system in upgraded to the shipping version of Cisco Unity (this support continues until May 15, 2011). However, PBXLink boxes cannot be ordered for a new Cisco Unity system.
3 Cisco EGW 2200 currently in use is supported when the system in upgraded to the shipping version of Cisco Unity (this support continues until August 7, 2011). However, Cisco EGW 2200 cannot be ordered for a new Cisco Unity system.
Supported Voice Cards
Table 3 lists supported voice cards for the Cisco Unity server.
We recommend using the newer Universal (3.3Vdc or 5Vdc dual voltage) PCI versions of the Intel Dialogic D/120JCT-LS and the D/120JCT-Euro cards, rather than the older single-bus voltage (5Vdc) versions of the cards.
Note that older (Revision 1) LS and LS-Euro cards are still supported for use with Cisco Unity 7.x versions, but they cannot be ordered for new Cisco Unity 7.x installations. In addition, the older LS cards can be used only when they are appropriate for the available slots in the Cisco Unity server or expansion chassis.
Caution
D/41E-PCI and D/240PCI-T1 cards currently in use are still supported for use with Cisco Unity 7.x. However, the cards cannot be ordered for a new system or as replacement cards for an existing system. For additional information, refer to End-of-Sale and End-of-Life Announcement for the 4-Port Analog Conventional PCI and T1 Voice Integration Cards for Cisco Unity Software at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_eol_notices_list.html.
When two or more cards are being installed, the cards must be connected by using an H.100 cable.
ISA voice cards are not supported.
Caution
Table 3 Supported Voice Cards
Intel Dialogic D/41E PCI
(conventional PCI, 4-port analog card)None
(Supported for use in an existing system only, cannot be ordered.)
United States and Canada
D/120JCT-LS
RJ-11
Intel Dialogic D/41JCT-LS
(uPCI, 4-port analog card)D41JCTLS
United States and Canada
D/120JCT-LS
RJ-11
Intel Dialogic D/41JCT-Euro
(uPCI, 4-port analog card)D41JCTLSEURO
All countries that require CE conformity, Hong Kong, Australia, and New Zealand
D/120JCT-Euro (Rev. 1)3
RJ-11
Intel Dialogic D/120JCT-LS
(conventional PCI, Rev 1, 12-port analog card)D120JCTLS
United States, Canada, Singapore, Malaysia, Taiwan, South Korea, and India.
D/41EPCI,
D/41JCT-LS,
D/120JCT-LS (Rev. 2)RJ-14
Intel Dialogic D/120JCT-LS
(uPCI, Rev 2, 12-port analog card)D120JCTLSU
United States, Canada, Singapore, Malaysia, Taiwan, South Korea, and India.
D/41EPCI,
D/41JCT-LS,
D/120JCT-LS (Rev. 1)RJ-14
Intel Dialogic D/120JCT-Euro
(uPCI, Rev 1, 12-port analog card)D120JCTLSUEU
(Supported for use in an existing system only, cannot be ordered.)
All countries that require CE conformity, Hong Kong, Australia, and New Zealand
D/41JCT-Euro,
D/120JCT-Euro (Rev. 2)RJ-14
Intel Dialogic D/120JCT-Euro
(uPCI, Rev 2, 12-port analog card)D120JCTLSUEU2
All countries that require CE conformity, Hong Kong, Australia, and New Zealand
D/120JCT-Euro (Rev. 1)3
RJ-25
Intel Dialogic D/240PCI-T1
(conventional PCI, 24-port T1 card)None
(Supported for use in an existing system only, cannot be ordered.)
United States and Canada
None
RJ-45
1 The SKU, or stock-keeping unit, is the product identifier that Intel Dialogic assigned to the voice card. If you order the voice card from Intel Dialogic, you can use the SKU to ensure that you are ordering the correct version.
2 For specific country or region applicability questions, contact Cisco prior to order placement.
3 Do not combine both D/120JCT-Euro (Rev 2) voice cards and D/41JCT-Euro voice cards in the Cisco Unity server. When both types of voice cards are in the same Cisco Unity server, they will not function correctly.
Supported Phone Models for Use with Cisco Unity Phone View
Revised <TBD>For both SIP and SCCP phones, the following Cisco Unified IP Phone models are supported: 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE. In addition, the following Cisco Unified IP Phone models are supported with phone load 8-3-4SR1 or later: 7942G, 7945G, 7962G, 7965G, and 7975G.
For SCCP phones, 7940G and 7960G models are also supported.
If a user experiences problems using Phone View on a phone model that is not listed, the feature should be disabled for that user.
Phone View does not work with the following phones: 7902G, 7905G, 7910G, 7910G+SW, 7912G, 7920, and Cisco IP Communicator.
Supported Optional Hardware
Revised August 26, 2008The following optional hardware is supported for use with Cisco Unity 7.x:
•
•
•
•
•
The following out-of-band management cards are supported for use with Cisco Unity 7.x:
•
•
•
•
See also the "Additional Supported Optional Software" section for software that is supported for use in conjunction with the management cards to remotely restart the Cisco Unity server.
Unsupported Hardware
Hardware that has not been qualified for use with Cisco Unity is not supported for use on or connected to a Cisco Unity server. Cisco TAC will ask that it be removed, disconnected, or disabled during troubleshooting.
•
•
PART 2: Supported Optional Software for Use with Cisco Unity 7.x
•
•
•
•
•
•
•
Caution
Supported Antivirus Software
The following antivirus software has been qualified by Cisco for use with Cisco Unity 7.x:
•
•
•
–
–
–
–
•
–
–
–
–
•
–
–
–
See also the "Support Policy for Antivirus Software" section.
Supported Fax Server Software
Table 4 lists fax servers supported for use with Cisco Unity 7.x, when installed with an Exchange or Domino gateway.
Install the fax cards, fax server software, and dedicated fax lines on the fax server. Installing fax software on the Cisco Unity server is not supported. Refer to the fax server documentation for a list of supported cards and integration methods.
Fax servers supported for use with Cisco Unity 7.x—when installed with an Exchange gateway and using the TIFF-F file format with images encoded so that there is only one image strip per facsimile page—are also supported for use with VPIM.
Supported Monitoring Software
The following monitoring software has been qualified by Cisco for use with Cisco Unity 7.x:
•
•
•
•
–
–
•
See also the "Support Policy for Monitoring Software" section.
Additional Supported Optional Software
Revised May 14, 2009The following optional software has been qualified by Cisco for use with Cisco Unity 7.x:
•
•
•
•
•
•
•
–
–
•
Note that using Terminal Services on a Cisco Unity server is not supported for some operations. For more information, refer to the "Limitations and Restrictions" section of the applicable Cisco Unity release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
•
•
See also the "Support Policy for Optional Software" section.
Unsupported Third-Party Software
Third-party software that has not been qualified for use with Cisco Unity is not supported. Cisco TAC will ask that it be removed during troubleshooting.
•
•
•
PART 3: Cisco Unity Support Policies
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Support Policy for AMIS Voice Messaging Systems
Cisco Unity 7.x with Microsoft Exchange and Cisco Unity 7.x with IBM Lotus Domino support version 1 of the Audio Messaging Interchange Specification analog (AMIS-a) protocol, which allows subscribers to exchange voice messages with other voice messaging systems.
Cisco support policy is that customers can use AMIS Networking to exchange voice messages between Cisco Unity and a third-party voice messaging system provided that the third-party system complies with the AMIS-a version 1 protocol.
Note
For information on using AMIS in Cisco Unity, refer to the applicable guide:
•
•
(Note that AMIS Networking will not function when Cisco Unity is integrated with Cisco Unified CM Express versions 3.2 and earlier. Refer to caveat CSCsb81232 in Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.)
Support Policy for Antivirus Software
Cisco support policy is that customers can deploy third-party antivirus software on the Cisco Unity server. However, Cisco expects that customers (or their systems integration partners) will have tested the interoperability of such products with Cisco Unity before the products are deployed, to mitigate the risk of problems being discovered within the production environment between Cisco Unity and the third-party products loaded on the Cisco Unity server.
If a customer calls Cisco TAC with a problem, a Cisco TAC engineer may require that such third-party software be turned off or even removed from the Cisco Unity server during the course of troubleshooting. If it is determined that the interoperability between the third-party software and Cisco Unity was the root cause of the problem, then the third-party software will be required to be disabled or removed from the Cisco Unity server until such time that the interoperability issue is addressed, so that the customer can continue to have a functional Cisco Unity system.
Before installing any qualified Microsoft service pack on the Cisco Unity server, confirm that the manufacturer of any optional third-party software or hardware that you plan to install on the Cisco Unity server—or that is already installed—also supports the service pack for use with its product.
Support Policy for Apache Tomcat Upgrades
Apache Tomcat software is automatically installed on the Cisco Unity server during the installation of the Cisco Unity software. Because the Tomcat software is customized to provide Cisco Personal Communications Assistant (PCA) functionality, downloading an updated version of Tomcat software from the Apache website and installing it on the Cisco Unity server is not supported. Doing so will cause the Cisco PCA to stop working properly. However, installing Tomcat software patches is supported.
Support Policy for Backup Software
Cisco support policy is that customers can deploy third-party software for backup on the Cisco Unity server. However, Cisco expects that customers (or their systems integration partners) will have tested the interoperability of such products with Cisco Unity before the products are deployed, to mitigate the risk of problems being discovered within the production environment between Cisco Unity and the third-party products loaded on the Cisco Unity server.
If a customer calls Cisco TAC with a problem, a Cisco TAC engineer may require that such third-party software be turned off or even removed from the Cisco Unity server during the course of troubleshooting. If it is determined that the interoperability between the third-party software and Cisco Unity was the root cause of the problem, then the third-party software will be required to be disabled or removed from the Cisco Unity server until such time that the interoperability issue is addressed, so that the customer can continue to have a functional Cisco Unity system.
Before installing any qualified Microsoft service pack on the Cisco Unity server, confirm that the manufacturer of any optional third-party software or hardware that you plan to install on the Cisco Unity server—or that is already installed—also supports the service pack for use with its product.
Note
For information on backing up Cisco Unity, refer to the applicable guide:
•
•
Support Policy for Hardware Virtualization Environments
Revised May 6, 2010A Cisco Unity system can be virtualized in a Unified Messaging or Voice Messaging configuration. In addition:
•
•
A mix of virtual and nonvirtual machines can be run, including the servers in a Cisco Unity failover pair.
For requirements, recommendations, policies, and performance metrics, see the Design Guide for Cisco Unity Virtualization on Cisco.com at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html.
Support Policy for IBM Lotus Domino Critical Fixpacks
All Critical Fixpacks are automatically supported.
Support Policy for Microsoft Data Execution Prevention
Cisco support policy is that customers can deploy Microsoft Data Execution Prevention (DEP). However, we have found, in some customer environments, that DEP prevents Cisco Unity services from starting or causes the services to shut down. If a customer calls Cisco TAC with a problem and DEP is identified as being the cause of the problem, a Cisco TAC engineer may require the customer to revise the DEP monitoring policy to exclude monitoring of all Cisco Unity services.
For information on determining the current DEP policy settings and on reconfiguring these settings, refer to Microsoft Knowledge Base articles KB875352 and KB912923. For a list of Cisco Unity services, refer to the "Cisco Unity 5.x Services" appendix in the applicable guide:
•
•
Note
Support Policy for Microsoft Service Packs and Updates
Microsoft provides monthly updates for Windows, Exchange, SQL Server, MSDE, Internet Explorer, and IIS. These updates (known by a variety of names, including security rollup patches, security updates, critical updates, patches, and hot fixes) are limited to changes that fix specific problems. They do not include general defect fixes or new functionality. All of these Microsoft updates are qualified by Cisco from the day that Microsoft releases them. We recommend that you evaluate Microsoft updates in accordance with your server-software-maintenance policy to determine when to update the Cisco Unity server. If your company does not have a policy, we recommend that Microsoft updates be applied to the server as they are released. Cisco TAC provides support for a Cisco Unity system on which such updates have been installed.
Microsoft also occasionally releases service packs, which contain fixes generated since the general product release, including most fixes that were released as updates. Because the service pack scope is broad, each service pack must be thoroughly tested to ensure that changes do not adversely affect Cisco Unity. Cisco TAC does not support new service packs until they have been qualified for use with Cisco Unity.
Do not install a service pack that has not been qualified, or Cisco TAC will not help you resolve problems until you uninstall it.
Within 60 days of an applicable Microsoft service pack release, Cisco will announce whether the service pack can be applied to released Cisco Unity versions. If so, the new service pack becomes the recommended service pack for Cisco Unity.
Updates and service packs can be applied to other non-Cisco Unity servers such as IBM Lotus Domino or Exchange mail servers. Cisco does not require such updates and service packs to be applied to infrastructure servers and clients unless they are to resolve specifically identified problems that relate to the interactions between Cisco products and a customer's infrastructure. When applying a mail server service pack, we recommend following Microsoft's best practices of applying the service pack level to all mail servers within the organization. Client PCs and voice-mail access devices (PDAs, etc.), as well as mail servers, domain controllers, and global catalog servers may all be considered part of the customer's infrastructure.
Cisco will support—at most—two service packs of a given Microsoft component as recommended for major and minor releases of Cisco Unity. When a subsequent service pack is released, Cisco will drop support for the oldest service pack as being recommended in the next major or minor release of Cisco Unity.
When a service pack is qualified as recommended for use with Cisco Unity, it is supported for all currently supported versions of Cisco Unity, unless a specific Cisco product version is noted as being required in order to support the recommended service pack.
Support Policy for Monitoring Software
Cisco support policy is that customers can deploy third-party software for monitoring on the Cisco Unity server. However, Cisco expects that customers (or their systems integration partners) will have tested the interoperability of such products with Cisco Unity before the products are deployed, to mitigate the risk of problems being discovered within the production environment between Cisco Unity and the third-party products loaded on the Cisco Unity server.
If a customer calls Cisco TAC with a problem, a Cisco TAC engineer may require that such third-party software be turned off or even removed from the Cisco Unity server during the course of troubleshooting. If it is determined that the interoperability between the third-party software and Cisco Unity was the root cause of the problem, then the third-party software will be required to be disabled or removed from the Cisco Unity server until such time that the interoperability issue is addressed, so that the customer can continue to have a functional Cisco Unity system.
Before installing any qualified Microsoft service pack on the Cisco Unity server, confirm that the manufacturer of any optional third-party software or hardware that you plan to install on the Cisco Unity server—or that is already installed—also supports the service pack for use with its product.
Support Policy for Optional Software
Cisco support policy is that customers can deploy third-party software for backup, monitoring, and security on the Cisco Unity server. However, Cisco expects that customers (or their systems integration partners) will have tested the interoperability of such products with Cisco Unity before the products are deployed, to mitigate the risk of problems being discovered within the production environment between Cisco Unity and the third-party products loaded on the Cisco Unity server.
If a customer calls Cisco TAC with a problem, a Cisco TAC engineer may require that such third-party software be turned off or even removed from the Cisco Unity server during the course of troubleshooting. If it is determined that the interoperability between the third-party software and Cisco Unity was the root cause of the problem, then the third-party software will be required to be disabled or removed from the Cisco Unity server until such time that the interoperability issue is addressed, so that the customer can continue to have a functional Cisco Unity system.
Before installing any qualified Microsoft service pack on the Cisco Unity server, confirm that the manufacturer of any optional third-party software or hardware that you plan to install on the Cisco Unity server—or that is already installed—also supports the service pack for use with its product.
Support Policy for Storage Area Networks
Added October 15, 2008When Cisco Unity is installed in a Unified Messaging configuration, an IBM Lotus Domino or Microsoft Exchange message store can be stored in any storage area network configuration supported by IBM or Microsoft, respectively. (Cisco does not provide technical support for message-store servers.)
When Cisco Unity is installed in a Voice Messaging configuration, neither Domino nor Exchange message stores can be stored on a storage area network.
The Cisco Unity database cannot be stored on a storage area network.
Support Policy for VPIM Voice Messaging Systems
Cisco Unity 5.0 and later with Microsoft Exchange 2000/2003 and Cisco Unity 5.0 and later with IBM Lotus Domino support Voice Profile for Internet Mail (VPIM) version 2, which allows the exchange of voice, fax, and text messages with other voice messaging systems. VPIM can also be used for messaging between Cisco Unity servers that use different directories, including messaging between Cisco Unity with Exchange and Cisco Unity with Domino systems.
The remote voice messaging system(s) with which Cisco Unity will be networked cannot be in the same Exchange organization as the Cisco Unity server.
Cisco support policy is that customers can use VPIM Networking to exchange voice messages between Cisco Unity and a third-party voice messaging system provided that the third-party system complies with the VPIM version 2 specification, as defined in Internet RFC 2421. Refer to the Open Group (opengroup.org) VPIM website for conformance statements and the RFC 2421 VPIM v2 specification.
Note
VPIM fax encoding is based on the TIFF-F specification. For information on fax servers supported for use with Cisco Unity with VPIM, see the "Supported Fax Server Software" section.
Note
For information on using VPIM in Cisco Unity, refer to the applicable guide:
•
•
Support Policy for Windows Automatic Update
Windows Automatic Update (WAU) is supported on a Cisco Unity 7.x server when the option Notify Me Before Downloading Any Updates and Notify Me Again Before Installing Them on My Computer is selected. (Note that if Cisco Unity Platform Configuration discs Revision 12 or later are used to configure the platform for the Cisco Unity server, then WAU is disabled.)
Caution
Most of the benefit of WAU is related to patching security vulnerabilities in Windows. If the Cisco Unity server is configured for Voice Messaging and is not connected to a network or the Internet, the server has no security vulnerabilities that updates from WAU would prevent. For the Voice Messaging configuration, Cisco strongly discourages you from connecting the Cisco Unity server to the Internet only to use WAU.
PART 4: Related Documentation
Compatibility Information
For compatibility information, refer to the following documents at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html:
•
•
•
Requirements Information
For requirements information, refer to the following documents at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html:
•
•
•
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
