Cisco Systems OL-14619-01 manual Networking Guide for Cisco Unity at

Page 25

Chapter 2 Cisco Unity Concepts

Where Cisco Unity Stores Data

The directory replicates the information to all Domino servers in the domain (for Domino) or domain controllers and global catalog servers in the forest (for Exchange), which ensures that Cisco Unity has the required access to information.

For detailed information on adding two or more Cisco Unity servers to the same Domino domain or Active Directory forest, see the Networking Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

Enabling Communication (Interoperability) Between Cisco Unity and Other Voice Messaging Systems

Cisco Unity supports several methods for allowing communication between Cisco Unity and other voice messaging systems:

VPIM (Voice Profile for Internet Mail) is a digital protocol for transferring voice messages between different voice messaging system. To send and receive voice messages by using VPIM, the customer creates a delivery location object for each remote voice messaging system. The third-party voice messaging server must adhere to the VPIM v2 protocol.

As with the primary location objects, which allow one Cisco Unity server to send messages to subscribers who are associated with another Cisco Unity server, delivery location objects contain the information necessary for Cisco Unity subscribers to exchange voice messages with people who are using another voice messaging system.

The Audio Messaging Interchange Specification analog (AMIS-a) protocol provides an analog mechanism for transferring voice messages between different voice messaging systems. To send and receive voice messages by using AMIS, the customer creates a delivery location object for each remote voice messaging system.

The Cisco Unity Bridge acts as a networking gateway between Cisco Unity servers and Octel servers. The Bridge communicates with Octel servers by using the OctelNet analog protocol; it communicates with Cisco Unity servers by using the Digital Networking protocol, which is based on the VPIM protocol, with proprietary extensions.

Because the servers use different protocols, the Bridge uses nodes to translate messages as appropriate for each server. For the Octel node, the Cisco Unity Bridge maintains a table that contains the Octel server name, unique serial number, and phone number. For the Cisco Unity node, the Bridge maintains another table that contains the Cisco Unity server name, assigned serial number, and domain name. By using these two tables, the Cisco Unity Bridge server can, for example, receive a message from an Octel node, look up the routing information from the

Cisco Unity node table, reformat the information for the destination Cisco Unity node, and then send the message to the Cisco Unity node.

For more information on how Cisco Unity works with other voice messaging systems, see the

Networking Guide for Cisco Unity at

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

Data That Appears in Both the SQL Server 2000 Database and in the Address Book/Directory Is Automatically Synchronized

Some Cisco Unity information is stored in both the SQL Server 2000 database and in the address book/directory. This data can be changed both from within Cisco Unity (for example, subscriber information can be changed by using the Cisco Unity Administrator), and from outside Cisco Unity (for example, subscriber information can be changed by using Active Directory Users and Computers).

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

2-9

 

 

 

Image 25
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 AuthenticationCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing 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 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 Integration with Cisco Unified Communications Manager Lines and Cables to Make Physical ConnectionsDigital 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 Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP 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