T3.1.1 Create the Cisco Unity system description -- the criteria necessary to build each Cisco Unity server you install. Include the following information:
T188.8.131.52 Cisco Unity system configurations -- How each Cisco Unity server should be configured including how you should set up your subscriber templates, classes of service, distribution lists, naming conventions, extensions, other subscriber data.
T184.108.40.206 Cisco Unity hardware configurations -- The physical layout of the hardware including how you plan to organize files and applications on the hard drives of each server.
T220.127.116.11 Cisco Unity networking configurations -- For each Cisco Unity server, detail the dialing plan that you use with Cisco Unity. Show how subscribers on each Cisco Unity server can be addressed by subscribers on other Cisco Unity servers or legacy voicemal systems. Show a digital networking table depicting how it will be set up for each Cisco Unity server.
T18.104.22.168 Physical network connectivity -- Show exactly how each Cisco Unity server connects to the network and communicates with each and every server that it services or depends upon. Show the IP addresses and server/DNS names of each server that Cisco Unity communicates with. Show switch port settings such as speed/duplex, VLAN, etc.
T3.1.2 Identify the Cisco Unity switch integration detail -- explain exactly how Cisco Unity will integrate with each switch that each Cisco Unity server services. This includes the voice ports and the switch-integration configuration.
T22.214.171.124 If you are using Dialogic gateways to integrate with a legacy PBX, document their IP addresses, switch port settings, physical location and connection to the PBX. Document PBX settings such as LTN assignments, hardware assignments, serial port settings, extension numbers, hunt group pilot numbers.
T126.96.36.199 If Cisco Unity is integrated with CallManager, show the network connection. Does it use the same VLAN or a different VLAN? Show the actual IP addresses on the cards
T3.1.3 Identify the Cisco Unity messaging infrastructure detail -- Include the following:
T188.8.131.52 Cisco Unity domain usage -- Indicate for each Cisco Unity server the domain names and domain controllers that Cisco Unity will use, and the Global Catalog server that Cisco Unity will use.
T184.108.40.206.1 Remember that Cisco Unity for Exchange must be installed into the same Windows site as the Exchange servers that it services and must use the same domain controller and Global Catalog server as these Exchange servers. List the directory OUs where all mail-enabled users are located in Active Directory for the same Exchange servers that Cisco Unity services.
T220.127.116.11.2 If your Cisco Unity design involves Domino only, you must indicate which Windows domain Cisco Unity is installed into. Remember that Cisco Unity uses the Windows domain and that Domino might not; also note that Cisco Unity's interaction with Domino primarily depends on DUC and the Domino domain and not the Windows domain, even though a Windows domain is required for Cisco Unity only. If you dedicate a Windows domain for your Cisco Unity installations, note that in your design. Also note how each Cisco Unity server accesses and uses the domain controller for the Windows domain where it is installed.
T18.104.22.168 Cisco Unity directory usage - Your directory capacity-planning exercise should have helped you determine the impact that legacy voice-messaging objects created in Active Directory have on your directory. Indicate location and where these objects will be created. Include particulars about the detail and activities involved in performing the schema extension, in the case of Active Directory, or in installing DUCS, in the case of Domino.
T22.214.171.124 Name resolution -- For each Cisco Unity server, indicate which name-resolution hosts will service Cisco Unity.
T126.96.36.199 Messaging system - For each Cisco Unity server, indicate which server will be its partner server and which servers Cisco Unity will service.
T188.8.131.52 Service accounts and administrative access -- Indicate how each Cisco Unity server will be accessed and how the service accounts will be used, as well as their names, their level of permissions, who will manage them, and what is necessary for management (such as password policies, permissions checks and verification, auditing, and so on).
T184.108.40.206.1 For each Cisco Unity server, note the service accounts that will be used or created for Cisco Unity.
T220.127.116.11.2 You also must consider how the servers will be accessed administratively. Is OS-level access treated differently than the Cisco Unity application level?
T18.104.22.168.3 If you plan to use an existing administrative policy or procedure within your organization, indicate that and note how it will be applied to Cisco Unity.
T22.214.171.124.4 When you indicate the accounts that you will use, you might want to address both the installation of and operations of Cisco Unity, which can be considered two different activities.
T126.96.36.199 End-user access -- For each Cisco Unity server, indicate which levels of access are to be allowed for your end users. Will it be TUI only? Are only some end-users allowed to access the GUI web? What about directly accessing the server? Are any end-users allowed or required to access the Cisco Unity server directly?
T188.8.131.52 Security considerations -- Make sure that you not only include security considerations in your design, but that you also use the lab trials and production pilot to ensure that Cisco Unity is capable of supporting whatever you indicate in your design,
T3.1.4 Indicate Cisco Unity administration and management design specifics. Address how Cisco Unity should be administered and indicate any design issues associated with your administrative plan. If bandwidth is an issue for remotely accessing the Cisco Unity System Administrator, or if you need to run remote administrative clients to access the server, indicate that in this section.
T184.108.40.206 Consider administrative access -- which accounts or which users need to access each Cisco Unity server and how.
T220.127.116.11.1 Your administrative plan should include how mail-enabled users are imported into Cisco Unity and also how those users are managed after they are imported.
T18.104.22.168.2 As a part of your design topology, indicate your administrative model and how it will support normal Cisco Unity administration, including subscriber management (subscribers, distribution lists, and so on), audio-text applications, and the Cisco Unity server system configuration, especially its connectivity to a legacy switch, Cisco Unified Communications Manager, or both.
T22.214.171.124.3 What tools do you use? Indicate this and set up a policy for how, when, and where these tools are used.
T126.96.36.199 Document Cisco Unity system management -- monitoring the server's resources and performance, as well as also proactively monitoring the server's ongoing, daily activity. This means that you will monitor Cisco Unity at different levels: the OS (event logs, SNMP service, Performance Monitor), Cisco Unity itself (traces, port status, Cisco Unity-specific performance activity, logs, and so on), application event viewer logs (possibly using the event-monitoring service), and other components, such as security, antivirus, and other management tools.
T188.8.131.52 Indicate the subscriber account-naming conventions, and make sure that your design uses the same naming conventions as your existing user accounts database.
T184.108.40.206 Indicate support considerations. Whom do subscribers call for problems? Whom do your tech support engineers contact for operational issues during each phase of the migration? How does moving from legacy voice messaging to unified messaging affect how subscribers are supported?
T3.1.5 Create and perform any customer certification testing (if required).
GOAL: Refine and finalize training materials and subscriber communications plans.
S3.1 Continue working on your subscriber preparation.
S3.1.1 Determine the scope of the migration from a legacy voicemail system to Cisco Unity.
S220.127.116.11 What data will need to migrate from the legacy voicemail system to Cisco Unity?
S18.104.22.168 Who will perform the research on the legacy voicemail system and mine the data?
S22.214.171.124 What access to systems or documentation will they require?
S126.96.36.199 How will you handle their requests for additional information?
S3.1.2 Continue to document the existing legacy voicemail configuration.
S188.8.131.52 What menu services are currently in use?
S184.108.40.206 What announcement services are being used? How will the new messages get recorded?
S220.127.116.11 How many system distribution lists are being used?
S18.104.22.168 What zero-out targets are used?
S22.214.171.124 How will the migration impact voicemail networking?
S126.96.36.199 Are there any special departments or groups that have unique configurations in the existing legacy voicemail system?
S3.1.3 Begin to develop your migration support plan.
S188.8.131.52 How soon before the Day 1 Cutover will subscribers be able to access the new voicemail system and record new personal greetings?
S184.108.40.206 How long after the Day 1 Cutover will subscribers be able to access old messages on the old voicemail system?
S220.127.116.11 What impact will the Day 1 Cutover have on the existing voicemail pilot numbers and remote access?
S3.1.4 Start thinking about your subscriber support strategy.
S18.104.22.168 Who will staff the help desk? How long will it be available to end-users? Will you have live bodies, a group mailbox or both? What turnaround time do you plan to commit to for new requests/problems?
S22.214.171.124 What printed documentation will you distribute?
S126.96.36.199 What web-based resources will you utilize?
S188.8.131.52 Think about having dedicated contact points per department.
S184.108.40.206 How will you communicate status to the end-user community?
S3.1.5 Continue work on your subscriber training plan.
S220.127.116.11 Who will need be trained?
S18.104.22.168 Who will be your trainers?
S22.214.171.124 What training documentation will be required?