Cisco Systems OL-14619-01 manual TTS, TTY, Pocket PCs, and Hand-Held Computers, Audio Codec

Page 32

Chapter 3 Network Infrastructure Requirements

Audio Codecs

Table 3-1

Voice Message File Sizes and Audio Quality Ratings

 

 

 

 

 

Audio Codec

 

Approximate File Size, 1-Minute Message

Quality Rating

 

 

 

 

G.711

Mu-Law and A-Law

480 KB

Excellent

 

 

 

 

 

G.726

32 Kbps

 

240 KB

Fine

 

 

 

OKI ADPCM 8 kHz

240 KB

Fine

 

 

 

OKI ADPCM 6 kHz

180 KB

Fine

 

 

 

 

GSM 6.10

 

98 KB

Good

 

 

 

 

G.729a

 

60 KB

Good

 

 

 

 

 

TTS, TTY, Pocket PCs, and Hand-Held Computers

For Cisco Unity sites using Text to Speech (TTS), any supported codec can be used to record messages. However, TTS output is currently available only in G.711 and G.729a audio formats.

For Cisco Unity sites using TTY, G.711 is required. The TTY standard does not support other codecs.

GSM 6.10 is supported for playback on a Pocket PC, and is a higher quality recording format than MP3. G.711 and G.729a usually are not compatible with hand-held computers.

Interoperability Among Multiple Voice-Messaging Systems

If multiple Cisco Unity servers will communicate with one another via Cisco Unity Digital Networking or VPIM, or if Cisco Unity will communicate with other voice-messaging systems by using AMIS, the Cisco Unity Bridge, or VPIM, you must choose a compatible codec. Table 3-2shows a summary of codec considerations for Cisco Unity networking options.

Table 3-2 Networking Interoperability Comparison for Audio Codecs

Networking Option

Supported Codecs

 

 

AMIS

The AMIS protocol is not dependent on audio format.

 

The Cisco Unity servers can use any of the supported codecs.

 

 

Cisco Unity Bridge

Octel Analog Networking is not dependent on audio format.

 

The Cisco Unity servers must use either G.711 or G.729a in order to

 

communicate with the Cisco Unity Bridge servers.

 

 

VPIM

For inbound messages, Cisco Unity can convert voice messages to any codec

 

that Cisco Unity supports.

 

For outbound voice messages, Cisco Unity can either convert voice messages

 

to G.726 format or not convert at all. Not converting is useful when you are

 

using VPIM to send voice messages between Cisco Unity servers.

 

 

Design Guide for Cisco Unity Release 5.x

3-6

OL-14619-01

 

 

Image 32
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 PermissionsDomino Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Client Access Licenses Cisco Unity and the Domino Address BookMessage 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 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 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 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