Cisco Systems OL-14619-01 manual Support Policy for Optional Third-Party Software

Page 10

Preface

Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and Software

For descriptions and the URLs of Cisco Unity documentation on Cisco.com, see the Documentation Guide for Cisco Unity. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.ht ml.

In particular, note:

•For system requirements, and lists of supported hardware and software, the System Requirements for Cisco Unity Release 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

•For a list of servers that meet Cisco Unity specifications, the Cisco Unity Supported Platforms List, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

•For client workstations, a list of the software that is compatible with the version of Cisco Unity that you are installing, and a list of messaging clients that are compatible with the version of Cisco Unity that you are installing, the Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.ht ml.

Support Policy for Optional Third-Party Software

The Cisco support policy states 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. Such testing is essential in mitigating the risk that problems between Cisco Unity and the third-party products loaded on the Cisco Unity server will be discovered within the production environment.

If a customer calls the Cisco Technical Assistance Center (TAC) with a problem, a Cisco TAC engineer may require that optional 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, the Cisco TAC engineer will require that the third-party software be disabled or removed from the Cisco Unity server until the interoperability issue is addressed so that the customer can continue to have a functional Cisco Unity system.

Before installing any qualified optional 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.

Design Guide for Cisco Unity Release 5.x

 

x

OL-14619-01

 

 

 

Page 9 Page 11
Image 10
Page 9 Page 11
Contents Design Guide for Cisco Unity Americas HeadquartersDesign Guide for Cisco Unity Release N T E N T S Workstations Authentication Centralized Voice Messaging Configuration Viii Audience Document ConventionsSupport Policy for Optional Third-Party Software Cisco Product Security Overview Xii Product Area Design or Feature Documentation Design Guide OverviewDesign Guide for Cisco Unity Bridge at Page Design Guide Overview Design Guide for Cisco Unity Release Cisco Unity Concepts How Cisco Unity WorksUnified Messaging Voice MessagingHardware Components of a Cisco Unity System One or More Cisco Unity Servers Cisco Unity Supported Platforms List atNetwork Connection Optional for Some Configurations Voice Messages Are Stored in Domino or Exchange Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System DominoExchange Enabling Cisco Unity Servers to Communicate with One Another Networking Guide for Cisco Unity at Some Configuration Settings Are Stored in the Registry Name Resolution Availability of Network ResourcesDomain Controller Access and Availability Availability of Message Store ServersUsing Firewalls with Cisco Unity Sizing and Scaling Cisco Unity ServersStorage Capacity for Voice Messages Number of Voice PortsAudio Codecs How Codecs Affect the File Size of Voice MessagesAudio Codec TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems Quality RatingDeployment Models Unified Messaging with Customer-Provided Infrastructure Voice Messaging with Customer-Provided Infrastructure Multi-Site WAN with Distributed MessagingPhysical Placement and Network Infrastructure Considerations for Customer-Provided Infrastructure Active Directory ConsiderationsDesign Guide for Cisco Unity Release Exchange Considerations All Versions Exchange Considerations That Apply Only Exchange Considerations for Cisco-Provided, Dedicated Infrastructure OL-14619-01 Overview of Cisco Unity with Domino and Notes Maximum Number of Cisco Unity Subscribers Domino Address Book TerminologyChanges That csAdmin Makes to the Domino Address Book Element NameChanges That csClient Makes to the Mail File Server Placement Windows Domains and Domino DomainsAuthentication Active Directory Accounts and PermissionsCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Message Routing Client Access LicensesCisco Unity and the Domino Address Book Backing Up and Restoring DataUnified Messaging, No Domino Cluster Unified Messaging ConfigurationsServers Requirements and Recommendations Criteria for a Supported Configuration Voice Messaging ConfigurationUnified Messaging, Domino Cluster Deploying Cisco Unity for Lotus Domino Deployment Tasks for Unified Messaging Configurations Administrative Access and ControlNetwork Services Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow an Integration Works Integration with Cisco Unified Communications Manager Lines and Cables to Make Physical ConnectionsDigital Integration with Digital Pimg Units Dtmf Integration with Analog Pimg Units Timg Integration LAN/WANDtmf Integration with Voice Cards Serial Integration with Voice CardsSettings in the Phone System and in Cisco Unity Connections for a Serial Integration by Using Voice CardsCall Control General Integration Issues Feature Sccp SIPIntegrating Cisco Unity with the Phone System Option Considerations Cisco Unified Communications Manager Security Features DescriptionDescription When Data Is Encrypted Setting EffectSettings for Individual Voice Messaging Ports Disabling and Re-Enabling SecurityPacketization Sccp Integrations Only Sccp SIP Cisco 11 Cisco Unified Communications Manager Fallback with Pstn Cisco Unity to a branch office will fail Integrating by Using SIP Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP Compliance Description of Pimg Integrations Dtmf Integration with Analog Pimg Units Description of Timg Integrations Setup and Configuration Firmware Updates Serial IntegrationsIncreasing Port Capacity Cisco Unity FailoverCisco Unity Failback Multiple Integration Support/Branch Office ConsolidationIntegrating with Multiple Phone Systems Using Sccp Phone Systems with Other Integrations Requirements for Integrations with Multiple Phone SystemsReasons to Use Alternate Extensions Optional Integration FeaturesAlternate Extensions How Alternate Extensions WorkAlternate MWIs MWIs for Extensions on a Non-Integrated Phone SystemCentralized Voice Messaging OL-14619-01 OL-14619-01 Cisco Unity Failover and Standby Redundancy FailoverStandby Redundancy Cisco Unity Failover and Standby Redundancy Cisco Unity Failover and Standby Redundancy Diagram of a Standby Redundancy Configuration Pstn WANOL-14619-01 Voice-Recognition Access to Cisco Unity OL-14619-01 Migrating to Cisco Unity from Another Voice-Messaging System Migrating to Cisco Unity from Another Voice-Messaging System D E IN-2 IN-3 IN-4
Top Page Image Contents