Cisco Systems OL-14619-01 manual Requirements for Integrations with Multiple Phone Systems

Page 87

Chapter 6 Integrating Cisco Unity with the Phone System

Integrating with Multiple Phone Systems

Requirements for Integrations with Multiple Phone Systems

Cisco Unity has the following requirements for multiple phone system integrations:

All phone system and Cisco Unity server requirements have been met. See the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuratio n_guides_list.html.

There must be an adequate number of voice messaging ports on the Cisco Unity server to connect to the phone systems. This number must not exceed the number of ports that are enabled by the Cisco Unity license files.

For a single Cisco Unity server (or a failover pair), all extensions must be unique. The dial plans for the phone systems must not overlap.

If overlapping dial plans cannot be avoided, you must install a Cisco Unity server for each phone system, digitally network the servers, and set up dialing domains to accommodate the overlapping dial plans. See the applicable Networking Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

For limitations on combinations for multiple phone system integrations, see the “Combination Limitations for Multiple Phone System Integrations” section in the Multiple Phone System Integration Guide for Cisco Unity 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuratio n_guides_list.html.

Using SCCP Phone Systems with Other Integrations

The SCCP phone system type includes integrations through SCCP (Skinny Call Control Protocol) with Cisco Unified Communications Manager and with Cisco Unified Communications Manager Express.

For Cisco Unified CM phone systems, you can add Cisco Unified CM clusters in UTIM as separate phone system integrations or as new clusters to an existing Cisco Unified CM integration. For more information, see the “Creating an Integration with a Second Cluster of Cisco Unified Communications Manager” section in the applicable Cisco Unified CM integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_g uides_list.html.

Cisco Unity can integrate with Cisco Unified CM Express in SRST mode. For details, see the Integrating Cisco Unity with Cisco Unified CME-as-SRSTapplication note at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/prod_troubleshooting_guides_list.html.

Notes for PIMG Integrations

There is no limit on the number of PIMG units that you can use. If you want to connect PIMG units to different phone systems, add the PIMG units that are connected to one phone system to one integration, and add the PIMG units that are connected to a different phone system to another integration.

 

 

Design Guide for Cisco Unity Release 5.x

 

 

 

 

 

 

OL-14619-01

 

 

6-31

 

 

 

 

 

Image 87
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 Domino Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System Voice Messages Are Stored in Domino or ExchangeExchange 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 CodecsQuality Rating TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems Audio CodecDeployment 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 Backing Up and Restoring Data Client Access LicensesCisco Unity and the Domino Address Book Message RoutingUnified 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 Establishing Support Policies Administrative Access and ControlNetwork Services Deployment Tasks for Unified Messaging ConfigurationsOperational 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 IntegrationsHow Alternate Extensions Work Optional Integration FeaturesAlternate Extensions Reasons to Use Alternate ExtensionsMWIs 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