1 / 9

The Design Process—Planning

The Design Process—Planning. Understanding Capacity-Planning Considerations. 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

varsha
Download Presentation

The Design Process—Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Design Process—Planning Understanding Capacity-Planning Considerations

  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. 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. 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. 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. Example: Cisco Unity Platform Overlays * 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. WAN Cisco Unified Call Manager1 Cisco Unified Call Manager2 Workgroup Example: Exchange Topology Site A Site B Exchange 2000 DC DDNS DC/GC DDNS Exchange 2000 DC/GC DDNS CiscoUnity CiscoUnity

  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.

More Related