Cisco Systems OL-14619-01 manual General Integration Issues

Page 65

Chapter 6 Integrating Cisco Unity with the Phone System

General Integration Issues

The corresponding step for circuit-switched phone systems, when an external call arrives via the PSTN, TI/PRI, DID or LS/GS analog trunks, is for the call to be routed through the phone system to the Cisco Unity voice mail pilot number.

2.The phone system routes the call to an available Cisco Unity extension (a voice messaging port).

3.Cisco Unity answers the call and plays the opening greeting.

4.During the opening greeting, the caller enters an extension. For example, the caller enters 1234 to reach a person with that extension.

5.Cisco Unity notifies the phone system that there is a call for extension 1234.

6.Depending on whether Cisco Unity is set up to perform a supervised transfer or a release transfer, the following occurs:

Supervised transfer

While Cisco Unity holds the call, the phone system attempts to establish a

 

connection with extension 1234.

 

If the line is available, the phone system connects the call from Cisco Unity to

 

extension 1234. The phone system and Cisco Unity drop out of the loop, and the

 

call is connected directly from the original caller to extension 1234.

 

If the line is busy or unanswered, the phone system gives that information to

 

Cisco Unity, and Cisco Unity performs the operation the subscriber has specified.

 

For example, Cisco Unity takes a message.

 

 

Release transfer

Cisco Unity passes the call to the phone system, and the phone system sends the

(blind transfer)

call to extension 1234 without waiting to determine whether the line is available.

 

Then the phone system and Cisco Unity drop out of the loop. In this configuration,

 

if the customer wants Cisco Unity to take a message when a line is busy or

 

unanswered, each phone must be configured to forward calls to Cisco Unity when

 

the line is busy or unanswered.

 

 

General Integration Issues

For a detailed list of the requirements for a specific integration, see the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_g uides_list.html.

If Cisco Unity is configured for failover, line connections between the phone system and the Cisco Unity servers are described in the following documents:

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.

The Failover Configuration and Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

In addition, consider the following list of integration issues:

Cisco Unified Communications Manager integrates with Cisco Unity only through a network connection.

Circuit-switched phone systems that connect to PIMG or TIMG units integrate with Cisco Unity only through a network.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

6-9

 

 

 

Image 65
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 Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing 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 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 Digital Integration with Digital Pimg Units Lines and Cables to Make Physical ConnectionsIntegration with Cisco Unified Communications Manager 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 SIP Compliance Supported SIP IntegrationsCisco Unity Failover with SIP Trunks 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