Cisco Unity Design Process—Presales - PowerPoint PPT Presentation

cisco unity design process presales n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Cisco Unity Design Process—Presales PowerPoint Presentation
Download Presentation
Cisco Unity Design Process—Presales

play fullscreen
1 / 16
Cisco Unity Design Process—Presales
172 Views
Download Presentation
mariel
Download Presentation

Cisco Unity Design Process—Presales

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Cisco Unity Design Process—Presales Understanding Cisco Unity Configurations and Messaging Models

  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. Example: Voice-Messaging Configuration 1 VM.com • Windows 2000 Server • Active Directory and DNS* (Selected Subscriber Data) • Cisco Unity • Exchange 2000 Server (Voice Messages) • SQL Server 2000 or MSDE (Subscriber Data) 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 • Windows 2000 Server • DNS* DNS Host Server in the Customer’s Existing Domain • 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. Client Workstation (Optional)

  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) A.com Cisco Unity Server (Domain Controller/Global Catalog Server—Cisco Unity Subscriber Only) Cisco Unified CallManager or Other Phone System Exchange 2000 Administrative Group • Windows 2000 Server • Exchange 2000 Server (Voice Messages) Partner Exchange 2000 Server (Cisco Unity Voice Messages Only) • Windows 2000 Server • Exchange 2000 Server (Voice Messages) Exchange 2000 Server (Cisco Unity Voice Messages Only) • Windows 2000 Server • DNS* B.com • Optionally: • Cisco Unity Inbox • Cisco Personal Communications Assistant DNS Host Server in the Customer’s Existing Domain *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. Client Workstation (Optional)

  5. Example: Voice-Messaging Configuration 3 Cisco Unity Server Exchange 2000 Administrative Group • Windows 2000 Server • Exchange 2000 Server (Voice Messages) Partner Exchange 2000 Server Additional Exchange 2000 Servers • Windows 2000 Server • Exchange 2000 Server (Voice Messages) • Windows 2000 Server • Active Directory and DNS Domain Controller/Global Catalog Server • Optionally: • Cisco Unity Inbox • Cisco Personal Communications Assistant Client Workstation ViewMail for Outlook

  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. Example: Single Site DC DDNS Exchange 2000 WAN Cisco Unified Call Manager1 Cisco Unified Call Manager2 DC/GC DDNS CiscoUnity Workgroup Customername.com

  8. Cisco Unified Call Manager1 Cisco Unified Call Manager2 Workgroup Example: Multisite WAN with Centralized Messaging Customername.com Headquarters DC DDNS Exchange 2000 Branch 1 WAN WAN Branch 2 DC/GC DDNS Cisco Unity

  9. Cisco Unified Call Manager1 Cisco Unified Call Manager2 Workgroup Example: Multisite WAN with Distributed Messaging Customername.com West Coast Office East Coast Office Cisco Unity1 Partner Server Exchange 2000 DC DDNS Cisco Unity2 WAN WAN DC/GC DDNS Cisco Unity2 Partner Server Exchange 2000 DC/GC DDNS Cisco Unity1

  10. Cisco Unified Call Manager1 Cisco Unified Call Manager1 Cisco Unified Call Manager2 Cisco Unified Call Manager2 Workgroup Workgroup Example: Disaster Recovery or System Redundancy Site MAN DC/GC DDNS Cisco Unity Exchange 2000 DC/GC DDNS Cisco Unity Exchange 2000

  11. Cisco Unified Call Manager1 Cisco Unified Call Manager1 Cisco Unified Call Manager2 Cisco Unified Call Manager2 Distributed Call-Processing Model WAN DC GC DDNS DC GC DDNS Cisco Unity1 Cisco Unity2 Exchange 2000 Exchange 2000

  12. Cisco Unity Deployment Models Combined with IP Telephony Models

  13. Cisco Unity Digital Networking • Dialing domains • Auto Attendant features • Directory searches • Distribution lists • Cross-server logon

  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. 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.