Install BDD

  1. Obtain a Bulk-Data-Download file (BDD) from Neustar.

  2. Uncomment the references to NumberUpdate in the ospadmin user profile (.bash_profile) and then reload the profile.

   $ vi /home/ospadmin/.bash_profile
   ~
   NumberUpdate_HOME=$Package_HOME/numberupdate
   export NumberUpdate_HOME
   ~
   $ . ~/.bash_profile
  1. Configure the NumberUpdate application to replicate the dynamic updates out to OSPrey by configuring the $NumberUpdate_HOME/etc/etc.etc configuration file.
   cd $NumberUpdate_HOME/etc
   vi etc.etc
   ~
   #NexusServers=127.0.0.1:5045
   NexusServers=127.0.0.1:5045,10.10.10.88:5045

   HTTPAuthenticationEnabled=true
   HTTPAuthenticationUserName=ospadmin
   HTTPAuthenticationPassWord=garethosp

The configuration shown above will update the $OSPrey_HOME/etc/ported_numbers.cfg & ported_regions.cfg files on the local OSPrey as well as the remote OSPrey. You will generate the ported .cfg files in subsequent step. Deposit and unpack the BDD file into the utils directory and take note of the last-transaction-id in the file name.

   cd $NumberUpdate_HOME/unix/utils
   gunzip -c bddfile.tar.gz | tar -xvf -
   ma/ma.block_BDD_PSTN_09-06-2010161947.145753389.bdd
   mw/mw.block_BDD_PSTN_09-06-2010161947.145753389.bdd

Execute the two conversion scripts that will generate the files ported_numbers.cfg & ported_regions.cfg.

   ./NPAC_BDD-2-OSPrey_ported_numbers.sh
   ./NPAC_BDD-2-OSPrey_ported_regions.sh

Edit the .last-transaction-id.memo file. The -1 should be replaced by the characters provided in the file name of the BDD.

   cd $NumberUpdate_HOME/etc
   vi .last-transaction-id.memo
   ~
   LastTransactionID=-1

Stop OSPrey server.

   cd $OSPrey_HOME
   ./stop_osp_server.sh

Copy new ported.cfg files to the etc directory.

   cd $OSPrey_HOME/etc
   cp $NumberUpdate_HOME/unix/utils/ported*.cfg .

Restart OSPRey.

   cd OSPrey_HOME
   ./start_osp_server.sh

After OSPrey is back up (the GUI is available), manually test the 2 NumberUpdate scripts before running the automated script.

   cd $NumberUpdate_HOME/unix/bin
   ./start_npac_download.sh
   ./start_npac_replicate.sh

If you are able to successfully download the file from Neustar (start_npac_download.sh), and successfully replicate updates to OSPrey (start_npac_replicate.sh), then you are ready to run the automated script.

   cd $NumberUpdate_HOME/unix/run
   ./run_NumberUpdate.sh

Note: You should already have a NumberUpdate utility schedule defined in the ospadmin user crontab schedule. The lines will have to be uncommented and set to suit your needs. The delete*.sh utility scripts can also be adjusted to suit your needs.

   Number Update utils
   10 2 * * * . ./.bash_profile ; $NumberUpdate_HOME/unix/utils/compress_log_files.sh
   20 2 * * * . ./.bash_profile ; $NumberUpdate_HOME/unix/utils/compress_archived_update_files.sh
   30 2 * * * . ./.bash_profile ; $NumberUpdate_HOME/unix/utils/delete_old_log_files.sh
   40 2 * * * . ./.bash_profile ; $NumberUpdate_HOME/unix/utils/delete_old_update_files.sh

Make certain that the auto-start links were successfully created during the OSPreyPackage installation. You need a stop symbolic link in /etc/rc0.d, and depending on the run-level of your system, your system will either utilize a start sym-link in /etc/rc3.d or /etc/rc5.d. You can confirm the run-level by checking /etc/inittab (id:3:initdefault:). Manually create the links below if they do not already exist.

   /etc/rc0.d/K53NumberUpdate -> /home/ospadmin/OSP/OSPreyPackage/numberupdate/unix/run/auto_run_stop_NumberUpdate.sh
   /etc/rc3.d/S53NumberUpdate -> /home/ospadmin/OSP/OSPreyPackage/numberupdate/unix/run/auto_run_stop_NumberUpdate.sh
   /etc/rc5.d/S53NumberUpdate -> /home/ospadmin/OSP/OSPreyPackage/numberupdate/unix/run/auto_run_stop_NumberUpdate.sh