Cisco Systems OL-14619-01 manual Network Connection Optional for Some Configurations

Page 21

Chapter 2 Cisco Unity Concepts

Hardware Components of a Cisco Unity System

information). All voice cards must be installed in the expansion chassis; they cannot be split between the server and the expansion chassis, because all of the cards must be connected to one another by using a single H.100 cable.

One or More Message-Store Servers (Optional for Some Configurations)

For Cisco Unity systems configured for Unified Messaging, the message store software (IBM Lotus Domino or Microsoft Exchange) must be installed on a server other than the Cisco Unity server.

For Cisco Unity systems configured for Voice Messaging, Exchange can be installed on the Cisco Unity server or on a separate server. Domino must be installed on a separate server.

The number of subscribers homed on the Cisco Unity server cannot exceed the maximum listed for that type of server on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

One or More Dedicated Domain Controllers/Global Catalog Servers (Exchange Only, Large Voice Messaging Configurations Only)

For large Voice Messaging configurations, one or more dedicated domain controllers/global catalog (DC/GC) servers may be required. For more information, see Chapter 3, “Network Infrastructure Requirements.”

Cisco Unity Bridge Server (Required Only for Interoperating with Avaya Voice Messaging Systems)

If the customer wants Cisco Unity to interoperate with an Avaya voice messaging system, a dedicated Cisco Unity Bridge server is required. For more information, see the following documents:

For information on how Cisco Unity can send voice messages to Avaya and receive voice messages from Avaya, see the applicable version of the Networking Guide for Cisco Unity Bridge at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

For requirements for connecting Cisco Unity and Avaya, see the System Requirements, and Supported Hardware and Software for Cisco Unity Bridge at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Network Connection (Optional for Some Configurations)

For Cisco Unity systems that are configured for Unified Messaging, a network connection is required.

For Cisco Unity systems that are configured for Voice Messaging, a network connection is required only if the customer wants to do one or more of the following:

Use Domino for the message store.

Integrate Cisco Unity with an IP phone system (for example, Cisco Unified Communications Manager).

Administer Cisco Unity over the network.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

2-5

 

 

 

Image 21
Contents Americas Headquarters Design Guide for Cisco UnityDesign Guide for Cisco Unity Release N T E N T S Workstations Authentication Centralized Voice Messaging Configuration Viii Document Conventions AudienceSupport Policy for Optional Third-Party Software Cisco Product Security Overview Xii Design Guide Overview Product Area Design or Feature DocumentationDesign Guide for Cisco Unity Bridge at Page Design Guide Overview Design Guide for Cisco Unity Release How Cisco Unity Works Cisco Unity ConceptsVoice Messaging Unified MessagingHardware Components of a Cisco Unity System Cisco Unity Supported Platforms List at One or More Cisco Unity ServersNetwork Connection Optional for Some Configurations Software Components of a Cisco Unity System Where Cisco Unity Stores DataVoice Messages Are Stored in Domino or Exchange DominoExchange Enabling Cisco Unity Servers to Communicate with One Another Networking Guide for Cisco Unity at Some Configuration Settings Are Stored in the Registry Availability of Network Resources Name ResolutionAvailability of Message Store Servers Domain Controller Access and AvailabilitySizing and Scaling Cisco Unity Servers Using Firewalls with Cisco UnityNumber of Voice Ports Storage Capacity for Voice MessagesHow Codecs Affect the File Size of Voice Messages Audio CodecsInteroperability Among Multiple Voice-Messaging Systems TTS, TTY, Pocket PCs, and Hand-Held ComputersAudio Codec Quality RatingDeployment Models Unified Messaging with Customer-Provided Infrastructure Multi-Site WAN with Distributed Messaging Voice Messaging with Customer-Provided InfrastructurePhysical Placement and Network Infrastructure Active Directory Considerations Considerations for Customer-Provided InfrastructureDesign 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 Domino Address Book Terminology Maximum Number of Cisco Unity SubscribersElement Name Changes That csAdmin Makes to the Domino Address BookChanges That csClient Makes to the Mail File Windows Domains and Domino Domains Server PlacementActive Directory Accounts and Permissions AuthenticationDomino Permissions Cisco Unity Subscribers and Domino UsersDomino Clusters Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing Backing Up and Restoring DataUnified Messaging Configurations Unified Messaging, No Domino ClusterServers Requirements and Recommendations Voice Messaging Configuration Criteria for a Supported ConfigurationUnified Messaging, Domino Cluster Deploying Cisco Unity for Lotus Domino Network Services Administrative Access and ControlDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Overview Integrating Cisco Unity with the Phone SystemHow an Integration Works Lines and Cables to Make Physical Connections Integration with Cisco Unified Communications ManagerDigital Integration with Digital Pimg Units Dtmf Integration with Analog Pimg Units LAN/WAN Timg IntegrationSerial Integration with Voice Cards Dtmf Integration with Voice CardsConnections for a Serial Integration by Using Voice Cards Settings in the Phone System and in Cisco UnityCall Control General Integration Issues Sccp SIP FeatureIntegrating Cisco Unity with the Phone System Option Considerations Description Cisco Unified Communications Manager Security FeaturesDescription Setting Effect When Data Is EncryptedDisabling and Re-Enabling Security Settings for Individual Voice Messaging PortsPacketization 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 Supported SIP Integrations Cisco Unity Failover with SIP TrunksSIP Compliance Description of Pimg Integrations Dtmf Integration with Analog Pimg Units Description of Timg Integrations Firmware Updates Serial Integrations Setup and ConfigurationCisco Unity Failover Increasing Port CapacityMultiple Integration Support/Branch Office Consolidation Cisco Unity FailbackIntegrating with Multiple Phone Systems Requirements for Integrations with Multiple Phone Systems Using Sccp Phone Systems with Other IntegrationsAlternate Extensions Optional Integration FeaturesReasons to Use Alternate Extensions How Alternate Extensions WorkMWIs for Extensions on a Non-Integrated Phone System Alternate MWIsCentralized Voice Messaging OL-14619-01 OL-14619-01 Failover Cisco Unity Failover and Standby RedundancyStandby Redundancy Cisco Unity Failover and Standby Redundancy Cisco Unity Failover and Standby Redundancy Pstn WAN Diagram of a Standby Redundancy ConfigurationOL-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