Cisco Systems OL-14619-01 manual Integrating with Multiple Phone Systems

Page 86

Chapter 6 Integrating Cisco Unity with the Phone System

Integrating with Multiple Phone Systems

Assuming there are four phone systems from four different manufacturers (for example, Nortel, Avaya, NEC, and Siemens), four different integrations will be created on the Cisco Unity server to support the four phone systems. Across those four integrations, Cisco Unity can support 144 ports. For example:

•At the Seattle site, 15 PIMG units can be stacked to support 122 ports.

•At the New York site, two PIMG units can be stacked to support 16 ports.

•At the Tokyo site, one PIMG unit can be used to support four ports.

•At the Dallas site, one PIMG unit can be used to support two ports.

Even though the PIMG units come with eight ports, fewer than eight ports can be used on each unit.

If PIMG units will be placed across a WAN to support remote phone systems, proper codec selection, bandwidth capacity planning, and QOS planning are required. Both the G729a and G711 codec are supported by PIMG units and by Cisco Unity. Because PIMG units are Dialogic rather than Cisco devices, the use of location-based CAC is not applicable. The following network and bandwidth requirements are required when placing the PIMG across a WAN:

•For G.729a codec formatting, a minimum of 32.76 Kbps (assumes Ethernet, payload of 20 bytes, 5 percent overhead) guaranteed bandwidth for each voice messaging port

•For G.711 codec formatting, a minimum of 91.56 Kbps (assumes Ethernet, payload of 160 bytes, 5 percent overhead) guaranteed bandwidth for each voice messaging port

•No network devices that implement network address translation (NAT)

Note When the G.729a codec is used, Cisco Unity cannot perform silence detection. Using this codec may result in messages that have long trailing silence or that are entirely silent.

When placing PIMG units across a WAN, prioritize your call control and media traffic via proper QOS traffic, marking for voice traffic originating on the PIMG units. Set the Call Control QOS Byte and RTP QOS Byte on PIMG units to the following values:

Call Control QOS Byte

• PIMG units connect only to a LAN: 0 (CSCsb96387)

 

• PIMG units connect to a WAN: 104

 

 

 

RTP QOS Byte

•

PIMG units connect only to a LAN: 0 (CSCsb96387)

 

•

PIMG units connect to a WAN: 184

 

 

 

Note that the Call Control and RTP QOS byte parameters on PIMG units define a decimal value that represents QOS bit flags. These values can be interpreted as either IPv4 TOS or Differentiated Services Codepoint (DSCP). For more details, see the applicable PIMG User Guide.

Support for integrations with multiple circuit-switched phone systems up to a maximum of 144 ports allows Cisco Unity to consolidate multiple branch office sites into one centralized Cisco Unity server. For more information, see the “Integrating with Multiple Phone Systems” section on page 6-30.

Integrating with Multiple Phone Systems

Beginning with Cisco Unity 5.0(1), Cisco Unity supports as many integrations as necessary up to 144 ports. For example, you can create 144 integrations, each with only one port, for a total of 144 ports.

 

Design Guide for Cisco Unity Release 5.x

6-30

OL-14619-01

Page 85 Page 87
Image 86
Page 85 Page 87
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 PermissionsDomino Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Message Routing Client Access LicensesCisco Unity and the Domino Address Book Backing Up and Restoring DataServers Requirements and Recommendations Unified Messaging ConfigurationsUnified Messaging, No Domino Cluster Unified Messaging, Domino Cluster Voice Messaging ConfigurationCriteria for a Supported Configuration 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 Digital Integration with Digital Pimg Units Lines and Cables to Make Physical ConnectionsIntegration with Cisco Unified Communications Manager 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 SIP Compliance Supported SIP IntegrationsCisco Unity Failover with SIP Trunks 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