Cisco Systems OL-14619-01 manual Storage Capacity for Voice Messages, Number of Voice Ports

Page 30

Chapter 3 Network Infrastructure Requirements

Sizing and Scaling Cisco Unity Servers

Maximum Number of Users on Dedicated Domino or Exchange Servers

You should not allow the Domino or Exchange servers to service the maximum number of Domino or Exchange users that IBM Lotus or Microsoft allow. In addition, servers qualified by Cisco as Exchange message store servers for use with Cisco Unity have a maximum number of Exchange users, and the customer should not allow the number of users on these servers to reach the maximum.

You should also be careful not to exceed the disk capacity for the information store. For example, in order to enable recovery if the information store is corrupted, Microsoft recommends that the total size of an Exchange information store never exceed 50 percent of the capacity of the drive on which the information store is installed. For more information, see the Microsoft website.

Storage Capacity for Voice Messages

For Cisco Unity systems that are configured for Voice Messaging, base the server requirements on the total number of voice storage minutes required for each subscriber. A supported Cisco Unity server generally provides storage for 20 to 30 minutes of voice messages per subscriber for the maximum number of subscribers supported on that server.

For Cisco Unity systems that are configured for Unified Messaging, it is not possible to base server requirements on the total number of voice storage minutes required for each subscriber, because the message store also includes e-mail messages and possibly faxes. However, you can calculate the storage requirement for the desired number of voice storage minutes and add that to the current mailbox limits.

If the customer is replacing an existing voice messaging system with Cisco Unity, it may be possible to obtain information from the existing system on the average number of minutes of voice messages that subscribers currently have. You can then multiply the average number of minutes by the recording size per minute—according to the codec that Cisco Unity will use to record messages—to arrive at the average amount of disk space required for voice messages per subscriber.

Start with a one-to-one correlation of legacy voice messaging system to Cisco Unity. If the legacy system handles a larger capacity than the largest Cisco Unity server, consider splitting the legacy subscriber population onto more than one Cisco Unity server by extension number ranges or prefixes. It is not necessary to segment subscribers onto backend message stores by extension number ranges or prefixes but it may be easier to manage.

For more information, see the “How Codecs Affect the File Size of Voice Messages” section on page 3-5.

Number of Voice Ports

To determine the number and configuration of voice ports required, you can start with the existing voice messaging system, if applicable. This may give you some idea how many ports are required for taking voice messages, for turning message waiting indicators on and off, and for message notification.

In a Unified Messaging configuration, Cisco Unity uses telephone record and playback (TRAP), to allow subscribers who use Notes or Outlook for voice messaging to play and record voice messages over the phone rather than by using speakers and a microphone. This feature is especially desirable when subscribers work in cubicles, where there is a lack of privacy. However, when a subscriber plays or records a message by using TRAP, a port on the Cisco Unity server is used. (No port is used when a subscriber uses speakers and a microphone to play and record messages.) If the customer wants subscribers to use TRAP, calculations for the total number of voice ports required will need to take this into account.

For Cisco Unity failover, the primary and secondary servers must have the same number of ports.

Design Guide for Cisco Unity Release 5.x

3-4

OL-14619-01

 

 

Page 29 Page 31
Image 30
Page 29 Page 31
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 Permissions Cisco Unity Subscribers and Domino UsersDomino Clusters Message Routing Client Access LicensesCisco Unity and the Domino Address Book Backing Up and Restoring DataUnified Messaging Configurations Unified Messaging, No Domino ClusterServers Requirements and Recommendations Voice Messaging Configuration Criteria for a Supported ConfigurationUnified Messaging, Domino Cluster 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 Lines and Cables to Make Physical Connections Integration with Cisco Unified Communications ManagerDigital 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 Supported SIP Integrations Cisco Unity Failover with SIP TrunksSIP 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 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