1725-86984-000_P.docx
September 2016
192
Chapter 10:
System-Level Parameters
Certain parameters address system-level settings, such as DHCP.
Configuration File Encryption
You can encrypt configuration files (excluding the master configuration file), contact directories,
and configuration override files. See
Encrypting Configuration Files
configuration files. This section allow you to regulate the behavior of encrypted files.
Summary
Parameter
Used to:
sec.encryption.upload.callLists
Specify if the call list overrides file should be encrypted when it is uploaded
from the handset to the server
Specify if configuration files uploaded from the handset to the provisioning
server should be encrypted
Specify if the contact directory is encrypted when it is uploaded from the
handset to the provisioning server
sec.encryption.upload.overrides
Specify if the configuration overrides file should be encrypted when it is
uploaded from the handset to the server
device.sec.configEncryption.key
Specify an encryption key so the handset can download encrypted files from
the provisioning server.
Table 10-1: Configuration File Encryption
Parameter
Permitted Values
Default
sec.encryption.upload.callLists
1
0 or 1
0
The encryption on the handset-specific call lists that is uploaded to the provisioning server.
If 0, the file is uploaded unencrypted, and overwrites whatever handset-specific configuration file is on the server,
even if the file on the server is encrypted.
If 1, the call list is uploaded encrypted regardless of how it was downloaded. The file replaces any existing
handset-specific call lists file on the server.
sec.encryption.upload.config
0 or 1
0
The encryption on the handset-specific configuration file created and uploaded to the provisioning server when the
user selects
Upload Configuration
from the handset menu.
If 0, the file is uploaded unencrypted, and overwrites whatever handset-specific configuration file is on the server,
even if the file on the server is encrypted.
If 1, the file is uploaded encrypted and replaces any existing handset-specific configuration file on the server.
sec.encryption.upload.dir
1
0 or 1
0
The encryption on the handset-specific contact directory that is uploaded to the provisioning server.
If 0, the directory is uploaded unencrypted regardless of how it was downloaded, the directory replaces whatever
handset-specific contact directory is on the server, even if the file on the server is encrypted.
If 1, the directory is uploaded encrypted regardless of how it was downloaded. The file replaces any existing
handset-specific contact directory file on the server.
