Incoming signaling validation, Configuration file encryption – Polycom SOUNDPOINT SIP 2.2.0 User Manual
Page 97
Configuring Your System
4 - 49
Incoming Signaling Validation
The three optional levels of security for validating incoming network signaling
are:
• Source IP address validation
• Digest authentication
• Source IP address validation and digest authentication
Configuration changes can performed centrally at the boot server:
Configuration File Encryption
Configuration files (excluding the master configuration file), contact
directories, and configuration override files can all be encrypted.
For more information on encrypting configuration files including determining
whether an encrypted file is the same as an unencrypted file and using the
SDK to facilitate key generation, refer to
Encrypting Configuration Files
page
Configuration changes can performed centrally at the boot server:
Central
(boot server)
Configuration File:
sip.cfg
Specify the type of validation to perform on a request-by-request
basis, appropriate to specific event types in some cases.
•
For more information, refer to
on page
.
Note
The SoundPoint IP 300 and 500 phones will always fail at decrypting files. These
phones will recognize that a file is encrypted, but cannot decrypt it and will display
an error. Encrypted configuration files can only be decrypted on the SoundPoint IP
301, 320, 330, 430, 501,550, 600, 601, and 650 and the SoundStation IP 4000
phones.
The master configuration file cannot be encrypted on the boot server. This file is
downloaded by the bootROM that does not recognize encrypted files. For more
information, refer to
.
Central
(boot server)
Configuration File:
sip.cfg
Specify the phone-specific contact directory and the
phone-specific configuration override file.
•
For more information, refer to
on page
Configuration file:
<device>.cfg
Change the encryption key.
•
For more information, refer to refer to