© 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
Dec 18, 2015
© 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 unifiedmessaging 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 1All 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 2All 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 onlyDC/GCExchange 2000
DC
DC
[email protected] [email protected]
Exchange2000
Exchange
2000
Exchange aliases (to the left of the @ symbol) in both directories must be identical.
Existing Directoryand Forest
New DirectoryNew Forest
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-5
File Server
DC/GC
Cisco UnityDC
DC
New Cisco Unity Server(Member Server) Backup
Restore
Exchange2000
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 voice-mail 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
E-mail Alias: [email protected]
Voice-Mail Alias: [email protected]
Note: Voice mail and unified messaging licensing not supported on same server
File Server
DC/GC
DC
DC CiscoUnity
Member Server
Exchange
2000
Exchange2000
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
VM–[email protected] directory objects are migrated to the [email protected] mailbox and user account with the Migrate Subscriber Data tool.
File Server
DC/GC
DC
DC CiscoUnity
Example: Strategy 2—Postmigration
Strategy 2: Postmigration• Migrate Subscriber Data tool
to move voice-mail subscriber attributes.
• Third-party utility can be used to move voice messages, or users can forward them via Cisco Unity Inbox.
Exchange2000
Exchange2000
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-8
UnifiedMessaging
VoiceMail
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
X X
X X
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 e-mail and voice mail.
• Voice-mail 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
Exchange2000
DC/GCDC CiscoUnity
Member Server
VoiceMailOnly
DCExchange
2000
Example: Client Access Strategy 2
[email protected]@Companyname.com
• 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 voice-mail 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 voice-mail-only Cisco Unity system to a unified messaging system.
• There are premigration path considerations for moving a voice-mail-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 voice-mail-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 voice-mail 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.