Migration and deployment checklist

Last Updated : Dec 21, 2020 |
Use the following checklist to complete the migration of CS 1000 configuration to Device Adapter.
Note:
All documents referenced in this section are available on the Avaya Support Portal at https://support.avaya.com/.
Step
Action
Description
UNIStim / TDM / Both
Approximate time required
Maintenance window required
1
CS 1000 discovery.
Determine existing deployment elements:
  • Get KRS records for CS 1000 and associated applications.
  • Run orderpro and generate the summary and detail report.
  • Determine licensing requirements from the summary report.
  • Determine gateway and cabinet layout from the detail report.
  • Determine trunking, RAN, Music, BRI, RLC, and other elements from the detail and summary reports.
  • Determine applications in use such as AACC, CallPilot, and others.
  • Create a summary of the system to be used in the migration discussion.
Both
2
User migration discovery.
  • Determine the strategy for migrating users to Avaya Aura®.
  • Use ProVision or another tool to retrieve the TNB information to determine user eligibility for the migration to Device Adapter.
Both
3
Determine migration approach.
Users who cannot be migrated to Device Adapter must be moved to other gateways. This includes rewiring phone connections and necessary software configuration changes.
Both
4
Determine migration dial plan.
Examine the existing dial plans to build the migration dial plan approach:
  • Determine conflicts between systems.
  • Determine vacant number routing.
  • Determine session management.
Both
5
Design the Avaya Aura® solution to accommodate migration and finished states.
  • Avaya Aura® core
  • Applications
  • Licensing requirements
  • Hardware and software
  • Trunking
Both
6
Define the transition plan.
  • Number of phases.
  • Phased approach or flash cut.
  • Parallel system connectivity.
  • CS 1000 software levels and features for integration during migration.
  • Message waiting lamp.
Both
7
Deploy Avaya Aura® core and applications.
  • Core deployment.
  • PSTN connectivity.
  • Connectivity to CS 1000 for migration strategy.
Both
8
Ensure System Manager, Session Manager, and Communication Manager are deployed, active, and ready to accept the migrated CS 1000 configuration. Make test call with 2 Aura SIP sets (96xx).
See the following documents for information and procedures:
  • Deploying Avaya Aura® System Manager
  • Deploying Avaya Aura® Session Manager
  • Deploying Avaya Aura® Communication Manager
Note:
Information and procedures may be required from additional documents in the product suite depending on individual network and installation environments.
Both
Prerequisite
No
9
Install and configure Avaya Aura® Device Services if Corporate Directory support is part of the solution.
See Configuring Corporate Directory support.
Both
Prerequisite
No
10
Prepare a Personal Directory backup XML file.
See Exporting Personal Directory data.
Note:
Configure the Personal Directory backup rule to specify the external FTP server where the backup file should be placed.
UNIStim
30-60 minutes
No
11
Prepare a CS 1000 Call Server database backup archive. This will be used later to migrate custom feature key labels.
See Communication Server 1000E Maintenance for information and procedures on creating this backup file.
UNIStim
15-30 minutes
No
12
Record the CS 1000 properties used by the migration process.
Record the following properties.
  • Node IP and Node ID.
  • Codec list including payload size, jitter settings, and VAD.
  • DTLS policy and client authentication settings.
  • System-wide LD 15/21 custom timers for interdigit + dialtone (DIDT) and busy/overflow tone (BOTO).
  • LD 17/22:
    • PCML: companding law
    • MSEC: media system security policy, secured number of packets, session key validity time
    • IDLE_SET_DISPLAY: Idle set display string
    • DLAC: default "log all calls" option
  • LD 17/97 (Analog Set Timers):
    • Minimum Switchhook Flash
    • Maximum Switchhook Flash
    • Off Hook Validation
    • Dial Pulse
    • Interdigit
    • Dial Pulse On
    • Post Flash
  • LD 56:
    • Note if the tones and cadences are configured for specific country requirements. Avaya Device Adapter Snap-in provides an option to set a COUNTRY parameter that applies country specific tones and cadences. It will not provide an ability to configure custom tones and cadences.
  • LD 117:
    • prt zdst: phone time & date parameters: GMT offset, dst parameters
UNIStim
60-90 minutes
No
13
Plan and configure the primary and secondary Session Manager and Communication Manager assigned to each user; including dial plan implementation.
See Avaya Aura®Solution Design Considerations and Guidelines for information on this planning task.
Note:
The following considerations should also be noted.
  • Signaling locations must be administered using IP address patterns.
  • Media locations must be administered using IP address patterns.
  • Select ElementsSession ManagerApplication ConfigurationApplications from the menu in System Manager and confirm an Application is created for each Communication Manager.
  • Log in to Communication Manager using SSH and verify that SIP-Signaling group, SIP-trunk group, AAR dial table, Extensions, Codec settings, CompandingLaw, and RoutePattern are configured.
  • Verify Communication Manager licensing has enough SIP stations, SIP Off-pbx stations, and SIP trunks to support your desired configuration.
Important:
The ProVision tool does not migrate TN media security policy CLS (MSNV, MSAW). The Administrator should record these for every phone and then implement them through a service profile Media security attribute.
Both
4-6 hrs
No
14
Migrate the CS 1000 endpoint-related data and Media Gateway configuration with the ProVision tool.
See Migrating the endpoint and MGC-related data.
Note:
Select ElementsCommunication ManagerEndpointsManage Endpoints from the menu in System Manager to verify or edit imported endpoints.
Both
2-4 hrs
No
15
Deploy and configure Avaya Breeze® platform.
See Avaya Breeze platform deployment checklist.
Both
60-90 minutes
No
16
Deploy and configure Avaya Device Adapter.
See Snap-in deployment checklist.
Both
30-45 minutes
No
17
Import the Personal Directory data for UNIStim endpoints.
See Importing Personal Directory data for UNIStim endpoints from CS 1000.
UNIStim
60-90 minutes
No
18
Perform the necessary DHCP configuration to prepare for updating the S1 and S2 IP addresses of the UNIStim endpoints.
2-4 hrs
No
19
Import Media Gateway Controller configuration into System Manager.
See Importing Media Gateway Controller configuration.
TDM
No
20
Switch the UNIStim endpoints from CS 1000 to Device Adapter.
Endpoint firmware upgrades automatically.
UNIStim
Endpoint switch to Device Adapter takes 15-30 minutes if using DHCP.
Endpoint upgrade takes 5-10 minutes.
Yes
21
Configure Media Gateway Controllers for Device Adapter environment.
Media Gateway Controllers migrated from CS 1000 using ProVision do not need to be added to the solution using System Manager.
If you are adding a new Media Gateway Controller to the solution, see Configuring Media Gateway Controllers for the configuration procedure.
Before you install a new MGC that is shipped from a factory or upgrade an existing MGC, enable the Enable legacy loadware upgrades attribute on System Manager. After the MGC is installed or upgraded, disable the Enable legacy loadware upgrades attribute.
For more information, see MGC installation, upgrade, and registration process.
TDM
22
Register Media Gateway Controllers.
Perform the following tasks for Media Gateway Controllers migrated from CS 1000:
  1. Use SSH or a serial connection to connect to the MGC.
  2. Remove MGC from the security domain.
    Important:
    Removing MGC from the security domain reverts it to local authentication. Note the local password as this is the only way to access the MGC until it registers with Device Adapter.
  3. Change the Call Server IP address to the Avaya Breeze® platform Cluster IP address.
  4. Save the new configuration.
  5. Reboot the MGC.
TDM
Yes
23
Configure IP security for Media Gateway Controllers.
See Configuring IP security.
TDM
5 minutes
No