© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-1 Migrating from Voice Mail to Unified Messaging Migrating Voice Mail to Unified Messaging and Interoperability

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-2 Unified Messaging Migration Path Strategies Two strategies to use to enable a unified messaging migration path: Strategy 1 –Install Cisco Unity into its own forest or domain Strategy 2 –Integrate Cisco Unity into an existing forest or domain

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-3 Considerations When Choosing a Migration Strategy Strategy 1 All new hardware Create a new forest with all the steps for a separate infrastructure. Do not modify the schema until the actual migration time. Create storage capacity. Create system security or Firewalls. Create a backup schedule and implement backup hardware. Strategy 2 All current Infrastructure must be checked for readiness or made ready for Cisco Unity. Modify the schema. Check storage capacity. Create system security or Firewalls. Include Cisco Unity servers in the backup schedule to existing backup hardware.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-4 Migration Strategy 1 Strategy 1: Premigration Separate Exchange servers and DC/GC can be used. File Server DC/GC Cisco Unity Voice Mail only DC/GC Exchange 2000 DC Exchange 2000 Exchange aliases (to the left of symbol) in both directories must be identical. Existing Directory and Forest New Directory New Forest

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-5 File Server DC/GC Cisco Unity DC New Cisco Unity Server (Member Server) Backup Restore Exchange 2000 Example: Strategy 1—Migration Strategy 1: Migration New Cisco Unity server must be the same version as the old Cisco Unity server. Old Cisco Unity server is still serving as voic server. Run DBWalker utility on old server before backup. Back up data using Cisco Unity DiRT or Veritas Backup Executive. Restore data using Cisco Unity DiRT restore process. Remove old Cisco Unity server.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-6 Fred Alias: Voic Alias: Note: Voice mail and unified messaging licensing not supported on same server File Server DC/GC DC Cisco Unity Member Server Exchang e 2000 Example: Strategy 2—Premigration Strategy 2: Premigration Cisco Unity is installed into existing forest or domain as a member server. Exchange can be installed on box, or external server can be used. Hide voice mailboxes so they are not visible in the global address book.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-7 directory objects are migrated to the mailbox and user account with the Migrate Subscriber Data tool. File Server DC/GC DC Cisco Unity Example: Strategy 2—Postmigration Strategy 2: Postmigration Migrate Subscriber Data tool to move voic subscriber attributes. Third-party utility can be used to move voice messages, or users can forward them via Cisco Unity Inbox. Exchange 2000

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-8 Unified Messaging Voice Mail X *Used for account and system management, not voice mail retrieval Outlook Voice Mail for OutLook; G.729a support (uses Windows Media Player) Outlook Web Access No support for G.729a Cisco Personal Communications Assistant (CPCA) Cisco Unity Inbox Cisco Unity Assistant* Cisco Unity Administrator* Telephone XX XX X What Are the Client Message Retrieval Options for Voice Mail and Unified Messaging?

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-9 What Are the Cisco Unity Assistant and Cisco Unity Administrator Access Issues in Strategy 2? Issues Unified Messaging deployments are not complicated because there is only one account for and voice mail. Voic deployments use multiple accounts. Each account has a unique SID. Use the GrantUnityAccess utility to link the accounts.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-10 File Server Exchange 2000 DC/GCDCCisco Unity Member Server Voice Mail Only DC Exchange 2000 Example: Client Access Strategy 2 and Fred logs into domain with Fred account. Cisco Unity subscriber account is linked with VM-Fred account. Fred account cannot be authenticated by Cisco Unity.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-11 What Are the Cisco Unity Assistant and Cisco Unity Administrator Access Solutions? Solutions Configure Internet Explorer to prompt for a username, password, and domain. Run GrantUnityAccess utility to link the SID from domain accounts with the SID for voic accounts. If the SIDs reside in different forests, a trust must be configured to allow the voice-messaging forest to trust the corporate forest before GrantUnityAccess will work.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-12 Summary Deployment requirements include sizing and scaling, codecs, firewalls, third-party applications, and TAC access. Two strategies can be used to enable future unified messaging upgrades: Cisco Unity installed into its own forest or domain and Cisco Unity integrated into an existing forest or domain. Identify possible migration paths from a voic -only Cisco Unity system to a unified messaging system. There are premigration path considerations for moving a voic -only Cisco Unity system to a unified messaging system.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-13 Summary (Cont.) Voice mail and unified messaging characteristics for client message retrieval vary. Client access is complicated when Cisco Unity is installed as a voic -only solution. The main issue is with authentication. Solutions for Cisco Unity Assistant issues include setting up Internet Explorer to prompt for a username, password, and domain; running the GrantUnityAccess utility to link the SID from domain accounts with the SID for the voic accounts and, if the SIDs reside in different forests, configuring a trust to allow the voice-messaging forest to trust the corporate forest before granting Cisco Unity access.

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