>[software] [scripts] # password
passwd: password expiry information changed.
Setting password for user usmcli:
Password: usmcliadmin
Retype new password: usmcliadmin
passwd: password updated successfully
SFTP setup completed.

1. create_export_user.enc
2. load_locations_query.enc
3. load_lbo_query.enc
4. data_extractor.enc

• run (select create_export_user.enc)
• run (select load_locations_query.enc)
• run (select load_lbo_query.enc)

1. active template directory—the new Dial Plan model directory for Cisco HCS 8.x releases or the current Dial Plan model directory for all Cisco HCS 9.x releases
   
2. new template directory—the new Dial Plan model directory
   
   Figure 4. Location of the Model Directory
   
   

   The structure of the Model directory is as follows:

   Figure 5. Directory Structure for Model Directory
   
   

   The structure of the BaseDP directory is as follows:

   Figure 6. Directory Structure for Base DP
   
   

   The CountryDP-Packages directory contains one folder for each country. The structure of the CountryDP-Packages directory is as follows:

   Figure 7. Directory Structure for Country Dial Plans
   
   

   The Directory Structure for each country module is as follows:

   Figure 8. Directory Structure for Country Module
   
   
3. Unified CDM location data file—select the location data file extracted in Extract Data from Cisco Unified CDM.
   
4. Unified CDM LBO data file—select the LBO data file extracted in Extract Data from Cisco Unified CDM.
   

• Country codes of the countries available on Unified CM.
• ISO code for Countries. You can find this information by examining the base dial plan data sheet for each country. The country dial plans are located in the Dial Plan Model directory. If the ISO code is not found, the omission is flagged.
• Customer ID of all the customers provisioned in Unified CM.
• Location information:
  • Location id (xx)
  • Country of Location
  • Country ISO Code
  • Local Breakout (LBO) is based on the existence of the AddPlusxx partition in Unified CM. The tool uses the extracted LBO information to associate call types to LBO routing.
  • Site Partition if it exists. It is used when rebuilding Calling Search Spaces.
  • Located Based Routed Identifier (LRID) (Column G). If the LRID is blank you can find it in the Location Information under General Administration.
  • If the location is a Linked Location, put an * in the column. Fill in the Site ID of the parent location. (This information is not used)
  • Area Code or NatCode (Column I). If the NatCode is blank you can find the NatCode in the Location Information under General Administration.
  • Customer ID
  • LBO Call Types. If LBO data has not been extracted, manually fill in the LBO Call types for each of the rows that have AddPlusxxx in the LBO Column.

The dpmig tool generates a Summary page as shown in the following figure. Row 9 and all subsequent rows list the locations configured in Unified CM. There is one row for each location (site). Row 2 lists all Transactions in the Dial Plan Model that are ignored by the dpmig tool (see Table 1 ). You can add more transactions to the row, which are then ignored by the tool. Row 3 lists some of the Route Partitions (see Table 2). The dpmig tool ignores all the Translation and Route Patterns associated with these Route Partitions.

Figure 9. Output of Summary Page

Figure 12. Submit Confirmation

Figure 13. Audit Report Output

Each element (row) provides the following information:

• State: Refer to Step 5 for a description of how each action changes the state of the record.
• Note: Any note returned by the tool or by Unified CM.
• Transaction Name: Name of the transaction. The transaction name is empty if the dpmig tool cannot determine the type of transaction.
• Model Name: The Model Name of the element record. The Model Name is empty if the dpmig tool cannot determine the model of the element record.

• UNPROCESSED—The tool could not process the record from the spreadsheet because it lacks the complete information. You can edit the record and complete the information. You can manually change the state from UNPROCESSED to any state listed below.
• ACTIVE—This record is active in Unified CM. No search was necessary to find the matching instantiated record.
• INSTANTIATED—This record is included in Unified CM. No search was needed to find the matching record.
• UNCHANGED—No differences were found between the included (instantiated) data and the one from Unified CM for the specific dial plan element.
• COMMENT—Any record for a location that is not being migrated.
• CUSTOM(ADD) —The element appears in Unified CM but does not exist in the Dial Plan Model. This mismatch could be due to customizations or Translation and Route Patterns that were added using Enhanced Number Translations.
• CUSTOM(REMOVE)—The element does not exist in Unified CM, but is available in the Dial Plan Model.
• CUSTOM(UPDATE)—The element in the Dial Plan Model and the existing Unified CM do not match.

1. Match each Transformation Pattern in the Cisco Unified Communications Manager with the corresponding Transformation Pattern Transaction in the Dial Plan Model. Use the AutoFilter command in the Excel worksheet and then select the Route Partition from the Route Partition Column.
2. Compare each column to ensure that the columns are the same.
3. To update a column, update the worksheet information, and then change the state in the first column to UPDATE.
4. To delete a row, change the state in the first column to REMOVE.

If more locations are to be migrated, then rename the file to file_generate.xls, identify the locations to be migrated, and re-run the migration step until all locations have been migrated.

After all locations are migrated, modify the location agnostic transaction from #REMOVE to REMOVE to remove the location agnostic elements.