Presentation is loading. Please wait.

Presentation is loading. Please wait.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales.

Similar presentations


Presentation on theme: "© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales."— Presentation transcript:

1 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales

2 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-2 Three Voice-Messaging Configuration Options Configuration 1: A voice-messaging-only configuration where everything is self-contained on a single Cisco Unity server Configuration 2: A voice-messaging-only multiserver configuration with a dedicated messaging infrastructure Configuration 3: A unified messaging configuration with one or more Cisco Unity servers servicing an existing messaging infrastructure

3 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-3 Example: Voice-Messaging Configuration 1 Windows 2000 Server Active Directory and DNS* (Selected Subscriber Data) Cisco Unity Exchange 2000 Server (Voice Messages) SQL Server 2000 or MSDE (Subscriber Data) Windows 2000 Server DNS* Optionally: Cisco Unity Inbox Cisco Personal Communications Assistant *If client workstations will be using the Cisco Unity Inbox or Cisco PCA, customers must either use the DNS host on the Cisco Unity server for name resolution or integrate DNS on the Cisco Unity server with their DNS host. Cisco Unified CallManager or Other Phone System Cisco Unity Server (Partner Exchange 2000 Server/ Domain Controller/ Global Catalog Server— Cisco Unity Subscribers and Voice Messages Only) Companyname.com VM.com DNS Host Server in the Customer’s Existing Domain Client Workstation (Optional)

4 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-4 Example: Voice-Messaging Configuration 2 Windows 2000 Server Active Directory and DNS* (Selected Subscriber Data) Cisco Unity SQL Server 2000 or MSDE (Subscriber Data) Windows 2000 Server Exchange 2000 Server (Voice Messages) Windows 2000 Server DNS* *If client workstations will be using the Cisco Unity Inbox or Cisco PCA, customers must either use the DNS host on the Cisco Unity server for name resolution or integrate DNS on the Cisco Unity server with their DNS host. Cisco Unified CallManager or Other Phone System Windows 2000 Server Exchange 2000 Server (Voice Messages) Optionally: Cisco Unity Inbox Cisco Personal Communications Assistant Cisco Unity Server (Domain Controller/Global Catalog Server— Cisco Unity Subscriber Only) A.com B.com Exchange 2000 Administrative Group Exchange 2000 Server (Cisco Unity Voice Messages Only) DNS Host Server in the Customer’s Existing Domain Client Workstation (Optional) Partner Exchange 2000 Server (Cisco Unity Voice Messages Only)

5 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-5 Example: Voice-Messaging Configuration 3 Cisco Unity Server Exchange 2000 Administrative Group Domain Controller/Global Catalog Server Client Workstation ViewMail for Outlook Partner Exchange 2000 Server Additional Exchange 2000 Servers Windows 2000 Server Exchange 2000 Server (Voice Messages) Windows 2000 Server Exchange 2000 Server (Voice Messages) Optionally: Cisco Unity Inbox Cisco Personal Communications Assistant Windows 2000 Server Active Directory and DNS

6 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-6 Cisco Unity Messaging Deployment Models Single site Multisite WAN with centralized messaging Multisite WAN with distributed messaging Disaster recovery or system redundancy site

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

8 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-8 DC/GC DDNS Exchange 2000 Headquarters Branch 1 DC DDNS Customername.com WAN Branch 2 Example: Multisite WAN with Centralized Messaging Cisco Unified Call Manager1 Workgroup Cisco Unified Call Manager2 Cisco Unity

9 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-9 Cisco Unity2 Partner Server Exchange 2000 DC/GC DDNS Cisco Unity1 Partner Server Exchange 2000 DC/GC DDNS Cisco Unity1 DC DDNS Cisco Unity2 WAN West Coast Office East Coast Office Customername.com WAN Example: Multisite WAN with Distributed Messaging Cisco Unified Call Manager1 Workgroup Cisco Unified Call Manager2

10 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-10 DC/GC DDNS Exchang e 2000 Cisco Unity MAN DC/GC DDNS Exchange 2000 Cisco Unity Example: Disaster Recovery or System Redundancy Site Cisco Unified Call Manager1 Workgroup Cisco Unified Call Manager2 Cisco Unified Call Manager1 Workgroup Cisco Unified Call Manager2

11 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-11 Cisco Unity1 Exchange 2000 Exchange 2000 Cisco Unity2 DC GC DDNS WAN DC GC DDNS Distributed Call-Processing Model Cisco Unified Call Manager1 Cisco Unified Call Manager2 Cisco Unified Call Manager1 Cisco Unified Call Manager2

12 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-12 Single-site call processing Single-site messaging Multisite IP WAN with centralized call processingMultisite IP WAN with centralized messaging Multisite IP WAN with centralized call processing Multisite IP WAN with distributed messaging Multisite IP WAN with distributed call processingMultisite IP WAN with centralized messaging Multisite IP WAN with distributed call processing Multisite IP WAN with distributed messaging Cisco Unity Deployment Models Combined with IP Telephony Models

13 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-13 Cisco Unity Digital Networking Dialing domains Auto Attendant features Directory searches Distribution lists Cross-server logon

14 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-14 Deployment Strategies for Migrating from Voice Mail to Unified Messaging Two strategies –Strategy 1 All new equipment; the only shared equipment is the phone system and the way the alias is built Separate forest New mailstores –Strategy 2 Same forest (modify schema) Use existing equipment for mailstores Alias must be unique form existing

15 © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-15 Summary There are three Cisco Unity configurations—Single-Server Voice Messaging, Multiserver Voice Messaging, and Unified Messaging. Cisco Unity deployment models can be either centralized or distributed. Cisco Unity deployment models are combined with the IP telephony deployment model for a total solution. Dialing domains are used with cross box logon or allow auto attendant transfers between Cisco Unity servers. Digital networking is the how Cisco Unity transfers messages between subscribers on different Cisco Unity servers. There are two deployment strategies to consider when deploying a voice mail to future unified messaging configuration.

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


Download ppt "© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales."

Similar presentations


Ads by Google