Cisco Systems OL-14619-01 manual Call Control

Page 64

Chapter 6 Integrating Cisco Unity with the Phone System

Sample Path for a Call from the Phone System to a Subscriber

If the phone system sends the necessary information and if Cisco Unity is configured correctly, an integration can provide the following integration functionality:

Call forward to personal greeting

Call forward to busy greeting

Caller ID

Easy message access (a subscriber can retrieve messages without entering an ID because Cisco Unity identifies the subscriber based on the extension from which the call originated; a password may be required)

Identified subscriber messaging (Cisco Unity identifies the subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated)

Message waiting indication (MWI)

Call Control

The phone system uses a set of signals to set up, monitor, and release connections for a call. Cisco Unity monitors call control signals to determine the state of the call, and uses these signals to respond appropriately to phone system actions and to communicate with the phone system. For example, a caller who is recording a message might hang up, so Cisco Unity detects that the call has ended and stops recording.

Depending on the phone system, the following types of call control signals are used:

Cisco Unified

For Skinny Call Control Protocol (SCCP) integrations, Cisco Unified

Communications

Communications Manager generates SCCP messages, which are translated by the

Manager

Cisco Unity-CM TSP into TAPI that Cisco Unity uses. Cisco Unity

 

actions—such as hook flash for transferring calls—are translated by the

 

Cisco Unity-CM TSP into the SCCP messages that Cisco Unified CM uses.

 

For SIP trunk integrations, Cisco Unified CM sends SIP messages, and

 

Cisco Unity sends SIP responses when a call is set up or terminated.

 

 

Circuit-switched

For PIMG/TIMG integrations, the phone system sends messages to the PIMG or

phone system

TIMG units, which send the applicable SIP messages to Cisco Unity. Cisco Unity

 

sends SIP responses when a call is set up or terminated, and the PIMG or TIMG

 

units communicate with the phone system.

 

For voice card integrations, the phone system generates and responds to in-band

 

signaling (for example, busy, disconnect, DTMF, and hook flash). The signaling

 

tones are translated by the Dialogic TSP into TAPI events that Cisco Unity can

 

use. Cisco Unity makes a telephony request such as “transfer,” which is translated

 

by the Dialogic TSP into the signal (hook flash) that the phone system can use.

 

 

Sample Path for a Call from the Phone System to a Subscriber

The following steps give an overview of a sample path that an external call can take when traveling from the phone system to a subscriber.

1.For Cisco Unified Communications Manager, when an external call arrives, the gateway sends the call over the LAN or WAN to Cisco Unified CM.

Design Guide for Cisco Unity Release 5.x

6-8

OL-14619-01

 

 

Image 64
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 Where Cisco Unity Stores Data Software Components of a Cisco Unity SystemVoice 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 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 MessagesTTS, TTY, Pocket PCs, and Hand-Held Computers Interoperability Among Multiple Voice-Messaging SystemsAudio Codec 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 PermissionsCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Client Access Licenses Cisco Unity and the Domino Address BookMessage 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 Administrative Access and Control Network ServicesDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow 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 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 Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP Compliance 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 SystemsOptional Integration Features Alternate ExtensionsReasons to Use Alternate 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