Presentation is loading. Please wait.

Presentation is loading. Please wait.

The Design Process—Planning

Similar presentations


Presentation on theme: "The Design Process—Planning"— Presentation transcript:

1 The Design Process—Planning
Understanding Infrastructure Considerations

2 Infrastructure Considerations
All Cisco Unity designs and deployments are shaped by three infrastructure considerations: Messaging Telephony Networking Type Fact Intro This topic explains that all Unity designs are shaped by infrastructure considerations, capacity planning considerations, and deployment considerations. Content Unity designs will all use an existing infrastructure or an infrastructure that is created and dedicated for Unity. For any Unity design to function properly, designers must consider infrastructure, capacity planning and deployment requirements. Failure to comply with these requirements could and often does severely impact the performance of Unity.

3 Messaging Infrastructure Considerations
Microsoft Exchange or IBM Lotus Domino? Exchange routing and administration groups Cisco Unity to use same domain controller and global catalog servers as Exchange 2000 or 2003 Domains and organization unit containers in which mailusers are located for Cisco Unity service account permissions In a Domino installation, operating system on Domino servers, Lotus DUCS Interoperability with another voice-messaging system? Client desktop operating system Cisco Unity logical survey

4 Example: Messaging Infrastructure
Exchange 2000 DC DDNS WAN Cisco Unified Call Manager1 Workgroup Call Manager2 DC/GC DDNS DC/GC DDNS Cisco Unity

5 Telephony Infrastructure Considerations
IP or circuit-switched PBX ? Physical placement of Cisco Unity (reminder)— PBX-Cisco Unity placement could be an issue. Telephone system maintenance Dial plans overlapping?

6 Networking Infrastructure Considerations
Name resolution or DNS Firewalls Gateways available for Cisco Unity to reach resources VLANS—Cisco Unity on data VLAN Bandwidth Minimum 100-Mbps connection Maximum 200-ms network latency Failover recommended 100-Mbps connection between primary and secondary servers

7 Example: Networking Infrastructure Considerations
Headquarters Exchange 2000 DC DDNS WAN WAN Cisco Unified Call Manager1 Workgroup Call Manager2 Internet Internet DC/GC DDNS Exchange 2000 DC/GC DDNS

8 Summary All Cisco Unity designs are shaped by three infrastructure considerations: messaging, telephony, and network. Cisco Unity will rely on the same domain controller and global catalog as the Exchange servers. Physical location and interoperability and flash-cut could be telephony issues. Network infrastructure issues include name resolution, access to network resources through gateways, firewalls, and bandwidth. The Cisco Unity logical survey will help identify these issues.

9


Download ppt "The Design Process—Planning"

Similar presentations


Ads by Google