Workflow for BLF Updates

This document covers the workflow for updating the BLF configuration for clients with shared Google Docs spreadsheets.

  • Begin by opening the Google Docs spreadsheet containing the updated BLF information. Click somewhere within the spreadsheet, select all using Ctrl+A, and then copy the information using Ctrl+C.
  • Open a terminal and access the Papal Mainframe via ssh, select the PPT server, enter container 100 using sudo vzctl enter 100 and enter the home directory of the CTID whose BLF configuration you wish to update.
  • Create a new file for the BLF information. Please name the file with an appropriate description followed by an ISO standard formatted date (yyyymmdd) in order to promote consistency and prevent confusion. For example:
nano blfsidecar-20160114
  • Paste the BLF information from the Google Docs spreadsheet into the newly created file using Ctrl+Shift+V, save the file using Ctrl+O, and exit the file using Ctrl+X.

Note: A direct copy and paste from a Google Docs spreadsheet will not yield properly formatted CSV data. This won’t matter here, but may be a concern for other uses.

  • Using the makeblf command, generate a new BLF configuration file from the file you just created. For example:
makeblf blfsidecar-20160114 file
  • You will now have a properly formatted BLF configuration file with the name you specified above and the .cfg extension. Using our above example, the file would be named blfsidecar-20160114.cfg.
  • At this point you can now specify the new BLF configuration file inside individual phone configuration files. If your new BLF file is intended to replace an existing BLF file within several phone configuration files, you can use the sed command to change them all at once. Example usage follows. Do note the *cfg as the target, otherwise you may overwrite log files as well.
sed -i -e ’s/oldfile.cfg/blfsidecar-20160114.cfg/g’ *cfg
  • Congratulations, you may now have the customer reboot or reload the configuration on the affected phones.