Nortel SMC 2450, Руководство по внедрению

Страница: 157 / 262

Secure UNIStim deployment Page 157 of 260
Secure Multimedia Controller Implementation Guide
using insecure UNIStim, provided the action byte is not set to 6 in the phone
configuration or through DHCP.
Reenabling Secure UNIStim
When Secure UNIStim is turned on again in an installation that is already
primed with phone fingerprints, the clients reconnect using the fingerprints
already installed on the IP phones.
Client policy and client firmware policy issues
The client subnet consists of IP phones with and without the capabilities to
run secure UNIStim. The i2050 is one example of an IP phone that does not
support secure UNIStim.
SMC provides options to configure client firmware policies based on the
client firmware version and client policies based on client IP address and
subnet information. These policies impact client connectivity in the following
ways:
• allow or deny a client non-secure register request
• force a client to upgrade from non-secure to secure UNIStim
• allow or deny client fingerprint update based on client address
information
• allow or deny client fingerprint update based on client firmware version
• allow or deny client session caching based on client address information
• allow or deny client session caching based on client firmware version
This section provides specific examples to clarify how to apply these policies
to serve your specific needs.
IMPORTANT!
IP phones that are already running Secure UNIStim have a key
fingerprint installed on them. This prevents them from connecting
securely with another SMC that doesn’t support the same private key,
either as a primary or a secondary key.