Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016
294
a
Place the master config file and the key config file onto the provisioning server that
the handset is programmed (through SLIC or manually) to access.
b
Plug in (or turn on) the phone and allow it to find and load the file. Do this for all your
phones.
Once this is done the phones will be able to decrypt any files that use this key. They
will also encrypt files uploaded to the server if you configure it this way. (per step 4)
However, they do not have the encrypted config files yet so they will not be able to
make calls, etc., just yet.
c
Once the key has loaded to the phone, the key1.cfg file is no longer necessary and
the master config file must be edited to include the encrypted config files. For
greatest security you can remove these two files from the server and store them
securely for later use and configure a new master config file as described in step 6.
You can also comment out the commands or change the device.set parameter to
zero. But be aware that the master config file cannot be encrypted.
4
(Optional) Add
<sec.encryption>
parameters
to phones’ site.cfg config file (or other
config file that all encrypted phones will access).
The
<sec.encryption>
parameters specify whether the phone uploads its
configuration files in an encrypted or unencrypted format. See
5
Encrypt the config files used by the phones.
Use the
configFileEncrypt.exe
program to encrypt the config files used by the
phones.
We recommend that you rename the encrypted file so that it is obvious it is encrypted.
For example, here we rename the site.cfg file to site-cfg.enc when we encrypt it using
the encryption command. Use the same key name in the command that you just loaded
on the phones! This is the command format:
> configFileEncrypt.exe -i site.cfg -o site-cfg.enc1 -k key1.key
The command has these components:
»
-i [the un-encrypted filename]
»
-o [the encrypted filename]
»
-k [the key filename]
Run
configFileEncrypt.exe
on each config file used by the phones, except of
course, the master config file.
Securely store the unencrypted files, just as you stored the key file in step 3c.
Caution: If using a Linux computer to generate the encrypted files
Check the encrypted files to ensure they are not altered when you copy them from
a computer running the Linux operating system to a computer running the Microsoft
Windows operating system. See
