Manuals / Cisco Systems / Computer Equipment / Network Router

Cisco Systems OL-14619-01 manual Serial SMDI, MCI, or MD-110 Integration with Analog PIMG Units

Models: OL-14619-01

1 106

Download 106 pages 43.76 Kb

Page 61

Serial (SMDI, MCI, or MD-110) Integration with Analog PIMG Units

Chapter 6 Integrating Cisco Unity with the Phone System

How an Integration Works

Serial (SMDI, MCI, or MD-110) Integration with Analog PIMG Units

The phone system sends call information and MWI requests through the data link, which is an RS-232 serial cable that connects the phone system and the master PIMG unit. Voice connections are sent through the analog lines between the phone system and the PIMG units. The PIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initialization Protocol (SIP). Figure 6-4shows the connections for a serial integration by using analog PIMG units.

Figure 6-4 Connections for a Serial (SMDI, MCI, or MD-110) Integration by Using Analog PIMG Units

Additional

slave PIMG units

as needed

Slave PIMG unit

(calls only)

LAN/WAN

Master PIMG unit

Phone(SMDI data and calls) system

Analog lines

RS-232 serial cable

Network connections

Cisco Unity

server

153567

TIMG Integration

The phone system sends call information and MWI requests through the data link, which is an RS-232 serial cable that connects the phone system and the master TIMG unit. Voice connections are sent through the T1 digital lines between the phone system and the TIMG units. The TIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initialization Protocol (SIP). Figure 6-5shows the connections.

Design Guide for Cisco Unity Release 5.x

	OL-14619-01	6-5

Image 61

Cisco Systems OL-14619-01 manual Serial SMDI, MCI, or MD-110 Integration with Analog PIMG Units, TIMG Integration

Contents

Design Guide for Cisco Unity Americas HeadquartersRelease Revised May 6 Cisco Systems, Inc 170 West Tasman Drive San Jose, CA2008 Cisco Systems, Inc. All rights reserved Design Guide for Cisco Unity ReleaseNetwork Connection Optional for Some Configurations One or More Message-Store Servers Optional for Some ConfigurationsC O N T E N T S PrefaceWorkstations Audio CodecsVoice Messaging with Customer-Provided Infrastructure Domino Address Book TerminologyDeployment Tasks for Unified Messaging Configurations AuthenticationGeneral Integration Issues Voice Messaging ConfigurationOptional Integration Features Setup and ConfigurationMessaging Ports SCCP Integrations Only Alternate MWIsDiagram of a Standby Redundancy Configuration ConfigurationVoice-Recognition Access to Cisco Unity Migrating to Cisco Unity from Another Voice-Messaging SystemContents Design Guide for Cisco Unity Release viiiOL-14619-01 Audience PrefaceDocument Conventions Audience, page Document Conventions, pageSupport Policy for Optional Third-Party Software Cisco Product Security Overview Obtaining Documentation, Obtaining Support, and Security GuidelinesOL-14619-01 Preface Design Guide for Cisco Unity ReleaseDesign Guide Overview Design or Feature DocumentationC H A P T E R Product Areahttp//ciscounitytools.com/AppIPFaxConfigurationWizard.htm Chapter 8, “Voice-Recognition Access to Cisco Unity”Domino, see http//ciscounitytools.com/AppThirdPartyFaxConfig.htm ondesignguideslist.htmlOL-14619-01 Chapter 1 Design Guide Overview Design Guide for Cisco Unity ReleaseOL-14619-01 Chapter 1 Design Guide Overview Design Guide for Cisco Unity ReleaseCisco Unity Concepts Where Cisco Unity Stores Data, pageHow Cisco Unity Works How Cisco Unity Works, pageUnified Messaging Characteristics of Unified Messaging and Voice Messaging SystemsVoice Messaging Hardware Components of a Cisco Unity System Network Connection Optional for Some Configurations, pageOne or More Cisco Unity Servers, page One or More Cisco Unity Servers One or More Message-Store Servers Optional for Some Configurations Network Connection Optional for Some ConfigurationsSome Configuration Settings Are Stored in the Registry, page Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System Voice Messages Are Stored in Domino or ExchangeExchange All Subscriber Information Is Stored in a SQL Server 2000 DatabaseEnabling Cisco Unity Servers to Communicate with One Another Networking Guide for Cisco Unity at Some Configuration Settings Are Stored in the Registry Using Firewalls with Cisco Unity, page Name ResolutionNetwork Infrastructure Requirements Availability of Network ResourcesAvailability of Message Store Servers Domain Controller Access and AvailabilitySizing and Scaling Cisco Unity Servers Using Firewalls with Cisco UnityMaximum Number of Users on Dedicated Domino or Exchange Servers, page Storage Capacity for Voice Messages, page Number of Voice Ports, pageNumber of Voice Ports Storage Capacity for Voice MessagesMaximum Number of Users on Dedicated Domino or Exchange Servers How 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 RatingDesigning a Cisco Unity System with Exchange as the Message Store Physical Placement and Network Infrastructure, pageDeployment Models Deployment Models, pageVoice Messaging with Cisco-Provided, Dedicated Infrastructure Unified Messaging with Customer-Provided InfrastructureMulti-Site WAN with Distributed Messaging Voice Messaging with Customer-Provided InfrastructurePhysical Placement and Network Infrastructure Active Directory Considerations Considerations for Customer-Provided InfrastructureActive Directory Considerations, page Exchange Considerations All Versions, pageActive Directory Application Mode ADAM is not supported Exchange Considerations All Versions Exchange Considerations That Apply Only Exchange Considerations for Cisco-Provided, Dedicated Infrastructure Considerations for Cisco-Provided, Dedicated InfrastructureDesign Guide for Cisco Unity Release OL-14619-01Considerations for Cisco-Provided, Dedicated Infrastructure 4-10Design Guide for Cisco Unity Release OL-14619-01Voice Messaging Configuration, page Unified Messaging Configurations, pageCriteria for a Supported Configuration, page Windows Domains and Domino Domains, page Server Placement, pageMaximum Number of Cisco Unity Subscribers Client Access Licenses, page Backing Up and Restoring Data, pageDomino Address Book Terminology Domino Clusters, page Message Routing, pageElement Changes That csAdmin Makes to the Domino Address BookName Changes That csClient Makes to the Mail File Address Book Server, Message Store Server, and Mail Drop ServerElement NameWindows Domains and Domino Domains Server PlacementRevised May 6 Active Directory Accounts and Permissions AuthenticationCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing Notes Client on the Cisco Unity ServerUnified Messaging, No Domino Cluster Unified Messaging ConfigurationsServers Requirements and RecommendationsCriteria for a Supported Configuration Voice Messaging ConfigurationUnified Messaging, Domino Cluster gnguideslist.htmlEstablishing Support Policies, page Network Services, page Administrative Access and Control, pageDeployment Tasks for Unified Messaging Configurations, page Deploying Cisco Unity for Lotus DominoNetwork Services Administrative Access and ControlDeployment Tasks for Unified Messaging Configurations Establishing Support Policies5-13 Operational TasksCisco Unity 5.0 for Domino does not support Cisco Unity reports 5-14Integrating by Using SIP, page General Integration Issues, pageOptional Integration Features, page Centralized Voice Messaging, page Integrating Cisco Unity with the Phone Systemguideslist.html How an Integration WorksIntegration 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 Serial SMDI, MCI, or MD-110 Integration with Analog PIMG UnitsSerial Integration with Voice Cards DTMF Integration with Voice CardsConnections for an Integration by Using TIMG Units Figure 6-6 Connections for a DTMF Integration by Using Voice CardsCall Information Exchanged by the Phone System and Cisco Unity Settings in the Phone System and in Cisco UnityCall Control Sample Path for a Call from the Phone System to a SubscriberGeneral Integration Issues SCCP Feature6-10 Differences Between SCCP and SIP Integration Methods6-11 Considerations Option6-12 Cisco Unified Communications Manager Security Features, page Cisco Unified Communications Manager Security FeaturesWhen Data Is Encrypted, page Multiple Integrations Can Have Different Security Mode Settings, pageDescription 6-14Setting When Data Is EncryptedEffect 6-15Settings for Individual Voice Messaging Ports Multiple Integrations Can Have Different Security Mode SettingsDisabling and Re-Enabling Security 6-166-17 Packetization SCCP Integrations Only6-18 Multiple Cisco Unified Communications Manager Express Version SupportFeature SCCPMultiple Cisco Unified Communications Manager Express Routers Integrating with a Single Cisco Unity Server Figure 6-11 Cisco Unified Communications Manager Fallback with PSTN 6-20Call forward to busy greeting 6-21 Impact of Non-Delivery of RDNIS on Voice Mail Calls Routed via AARCall transfers Message waiting indication6-22 Integrating by Using SIPCisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP Compliance 6-236-24 Description of PIMG IntegrationsDigital Integration with Digital PIMG Units The phone system sends call information, MWI requests, and voice connections through the analog lines, which connect the phone system to the PIMG units. The PIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initiation Protocol SIP. Figure 6-13 shows the connections for a DTMF integration by using analog PIMG units 6-25DTMF Integration with Analog PIMG Units Serial SMDI, MCI, or MD-110 Integration with Analog PIMG Units6-26 Description of TIMG IntegrationsFirmware Updates Setup and ConfigurationSerial Integrations 6-27Cisco Unity Failover Increasing Port Capacity6-28 Multiple Integration Support/Branch Office Consolidation Cisco Unity Failback6-29 6-30 Integrating with Multiple Phone SystemsCall Control QOS Byte RTP QOS ByteRequirements for Integrations with Multiple Phone Systems Using SCCP Phone Systems with Other IntegrationsNotes for PIMG Integrations 6-31Alternate Extensions Optional Integration FeaturesReasons to Use Alternate Extensions How Alternate Extensions WorkAlternate MWIs Setting Up Alternate MWIs for Extensions on the Same Phone SystemMWIs for Extensions on a Non-Integrated Phone System 6-336-34 Centralized Voice MessagingMessage waiting indication MWI 6-35Chapter 6 Integrating Cisco Unity with the Phone System 6-36Centralized Voice Messaging Design Guide for Cisco Unity ReleaseFailover Cisco Unity Failover and Standby RedundancyComparison of Cisco Unity Failover and Standby Redundancy Comparison of Cisco Unity Failover and Standby Redundancy, pageStandby Redundancy Page The names of both Cisco Unity servers must be 14 characters or shorter Figure 7-1 Cisco Unity Standby Redundancy Example Diagram Diagram of a Standby Redundancy ConfigurationData Center primaryStandby Redundancy Design Guide for Cisco Unity Release Chapter 7 Cisco Unity Failover and Standby RedundancyOL-14619-01 C H A P T E R Voice-Recognition Access to Cisco UnityDesign Guide for Cisco Unity Release Chapter 8 Voice-Recognition Access to Cisco UnityOL-14619-01 C H A P T E R Migrating to Cisco Unity from Another Voice-Messaging SystemThe supporting infrastructure for example, message store servers, whether dedicated to IN-1 I N D EIN-2 Index IN-3Design Guide for Cisco Unity Release OL-14619-01Index Design Guide for Cisco Unity Release IN-4OL-14619-01