ROME HRS migration tools

During a VSXi to ROME HRS (External Route Server) migration it will be necessary to convert some of the data from VSXi to HRS. These scripts will help accomplish this task:

1. Convert DMT to JD. Where the DMT is being used for number blocking or jurisdictional determination this table will convert a DMT to JD format.
   1. Usage: convert-dmt.js DigitMappingExportLarge.xml 
2. Convert specific Route Tables. It is very common that the migration is only needed for specific (large) tables. Prior importing the converted routes to HRS you must already have all Route Tables and SubIDs created in addition to carriers.
   1. Usage: convert-routes-specificRT-final.js 0 64 142
      1. where 0 is routes_0.XML and 64 is routes_64.XML (65 XML route files exported by the VSXi).
      2. 142 is the route table to filter.
3. Convert Routes. Given a VSXi.xml routes file, it will create ROME.xml routes. Prior importing the converted routes to HRS you must already have all Route Tables and SubIDs created in addition to carriers.
   1. Usage: convert-routes.js vsxi.xml, where vsxi.xml is one file containing VSXi formatted routes.
4. Convert trunk to carriers. This script can be used to create carriers using information from HRS trunks. This can be used post-Replace Carrier Configuration.
   1. convert-trunk-to-carrier.js Trunks.xml
5. Convert VSXi resources to ROME trunks. Similar to "Replace Carrier Configuration".
   1. convert-vsxiresource-to-trunk.js Resources.xml N where N is the switch ID in HRS.

Scripting Environment

These scripts are written in Node.js. They can be run from a shell as long as the dependencies are installed. These are the steps to do that:

• sudo apt-get update
• sudo apt-get install nodejs
• sudo apt-get install npm
• nodejs -v (for reference my environment was running node.js 4.2.6)

These scripts are supported as-is and provided as a reference if you want to make modifications.