1. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-1 Understanding Capacity-Planning Considerations The Design Process—Planning

2. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-2 Messaging Infrastructure Capacity Planning Cisco Unity voice mail only with independent mailstore –Messages kept on Cisco Unity server or offbox on Exchange servers specifically used for Cisco Unity voice messages Cisco Unity unified messaging –Cisco Unity obeys Exchange 2000 and 2003 storage limits –Mailbox size increased –Storage retention policy –Storage codec –Logon sessions increased Are messaging servers located by Cisco Unity or will new messaging servers be needed?

3. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-3 Telephony Infrastructure Capacity Planning Circuit-switched PBX integration method may require additional line cards for PBX. Traffic analysis –Auto Attendant –TRaP IP integration –Create voice-mail ports

4. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-4 Network Infrastructure Capacity Planning Additional domain controllers or global catalog servers? Domain controller can be on box in voice mail. Not an option for unified messaging. One domain controllers or global catalog for every four Exchange message stores. Active Directory size increases by about 10% with schema extensions. Cisco Unity can service one forest, up to three Windows sites in one Windows domain. Bandwidth is a consideration.

5. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-5 Cisco Unity Server Capacity Planning Number of subscribers Cisco Unity platform overlay Port usage Exchange or Domino topology –Location –Design rules One Cisco Unity can support 10 Exchange servers. One Cisco Unity per Exchange administrative group. One Cisco Unity per Domino domain.

6. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-6 Example: Cisco Unity Platform Overlays DescriptionPlatform Overlay Number 1Platform Overlay Number 2Platform Overlay Number 3 SpecificationsSingle processor 1-GB RAM 1 x 80-GB SATA hard drive or 2 x 80-GB SATA hard drives, RAID 1 Single processor 2-GB RAM 2 x 72-GB SCSI hard drives, RAID 1 Dual processors 4-GB RAM 4 x 72-GB SCSI hard drives, 2 x RAID 1 or 4 x 72-GB + 2 x 144-GB hard drives, 3 x RAID 1 Ports244872/96* TTS sessions122436 Voice-mail users (on-box Exchange message store) 100020004000 (3 x RAID 1 configuration only) Unified messaging users or Voice-mail users (off-box message store) 100020007500 Message store users (non-IMAP, off box) 100020004000 (3 x RAID 1 configuration only) Message store users (with Groupwise connector, off-box) 50012002500 Unity Inbox users50010001500 Usable as DC/GC ServerYes N/A * Starting with Unity 4.2(1), 96 ports currently supported for all integrations except integrations using Dialogic voice cards. 72 ports supported for Dialogic voice card integrations.

7. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-7 DC/GC DDNS Exchange 2000 DC/GC DDNS Cisco Unity DC DDNS Exchange 2000 Site ASite B WAN Example: Exchange Topology Cisco Unified Call Manager1 Workgroup Cisco Unified Call Manager2 Cisco Unity

8. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-8 Summary Taking time to adequately plan for capacity is critical for successful Cisco Unity deployments. Factors for capacity planning include mailstore, telephony, network, and Cisco Unity servers. Mailstore capacity planning should consider factors such as unified messaging vs. voice mail only and on-box vs. off-box message store. Telephony capacity planning will be influenced by the use of IP vs. circuit-switched PBX and possibly the number of voice-mail ports required. Networking capacity planning needs to consider access to resources such as domain controllers and global catalogs. Adequate bandwidth is an important consideration. Cisco Unity capacity planning is influenced by the messaging system topology, subscriber population, voice port usage, and design rules.

9. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-9