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

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-2 Designing an Interoperable Solution Determine migration strategy Determine placement of Bridge servers Create dial plan strategy –Remote mailbox lengths –Serial and mailbox numbers Plan Bridge subscriber creation Decide where to install Cisco Unity Voice Connector or Interop Gateway

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-3 Determining a Migration Strategy Requirements analysis Define current Octel network Define goals of migration Define migration requirements –Examples: Design migration around removal of Serenade gateway Make the user accounts available for the users to pre- enroll

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-4 Cisco Unity Server Cisco Unified CallManager Legacy PBX Analog Lines IP SCCP (Skinny) Legacy Phone IP Phones Client Workstation T-1 Line Microsoft Exchange or Domino Message Store SMDI Link Legacy Voice- Mail System AMIS Connection, via Analog Lines Cisco 3600 Router Cisco Unity Bridge Server Analog Octel Networking Octel Example: Determining a Migration Strategy Typical migration scenario Dual-switch integration Message interchange (AMIS, Bridge, or VPIM) PSTN

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-5 Premigration Steps Before you begin a migration: Coordinate with Octel. Put a baseline Cisco Unity system in place and test. Build premigration Cisco Unity configurations. Upload premigration user information.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-6 Example: Determining a Migration Plan Examples of migration plans 1.Migrate an Aria site that uses Serenade. 2.Migrate a stand-alone Aria site. 3.Migrate campus. 4.Remove Serenade Gateway. 5.Migrate other locations.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-7 Where do the bridgehead server and Bridge server go? Bridgehead Server PSTN Octel Mail Placement of Bridge Servers Guidelines Separate, dedicated platform One server per Cisco Unity network Choose centrally located server as bridgehead

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-8 IP Network Cisco Unity Octel Mail Cisco Unity Dial ID = 5555 Dial ID = 8888 Dial ID = 7777 Developing a Numbering Plan Strategy Guidelines for numbering plan Establish fixed ID length Assign unique IDs Assign numbering range to pull IDs from Keep variable-length IDs in different numbering range

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1— Example: Numbering Plan Strategy Serial and mailbox numbers Node serial number defining location or node = 433 Mailbox number defining user mailboxes = 5654 and 5655

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1— Example: Numbering Plan Strategy (Cont.) Remote mailbox lengths How long is the mailbox identifier?

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-11 Planning for Cisco Unity Bridge Subscribers Cisco Unity configuration and permissions Class of service Restriction tables Public distribution lists Subscriber templates

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-12 Where do you place Cisco Unity Voice Connector? Bridgehead Server PSTN Octel Mail Cisco Unity Voice Connector on Exchange Server Planning for Cisco Unity Voice Connector Placement Guidelines Choose the correct Cisco Unity Voice Connector installation. Keep the Cisco Unity Voice Connector off the Cisco Unity server. Configure routing group connectors if needed.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-13 Where does Interop Gateway go? Bridgehead Server PSTN Octel Mail Planning for Interop Gateway Placement Guidelines The Interop Gateway is installed on the Cisco Unity server. The Cisco Unity server must be version 4.05 or later. All other Cisco Unity servers that will use this Cisco Unity server as a bridgehead server must be version 4.05 or later as well.

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-14 Summary Designing an interoperable solution requires careful planning for users and network resources. Migrating from an Octel solution to a Cisco Unity solution requires planning to ensure that the desired results are obtained. The Cisco Unity Bridge server needs to be placed as close to the Octel system as possible to keep from incurring large toll charges. Developing a numbering plan strategy is important to ensure that there is no overlap that could cause confusion. Bridge subscribers have to be planned on the same as any subscribers—determining the CoS, restrictions, and templates. Cisco Unity Voice Connector should be placed on the Exchange system that will be used as the gateway to the Cisco Unity Bridge. Interop Gateway is installed on the Cisco Unity server.

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