LifeSize Gateway-PRI, Руководство пользователя

Страница: 97 / 196

Configuring the LifeSize Gateway 89
Configuring Gateway Settings
C
ONFIGURING
G
ATEWAY
E
NCRYPTION
The LifeSize Gateway supports encrypted calls over IP networks. The
encryption conforms to the H.325 standard and supports the following
encryption algorithms:
DES—With an encryption key of 56 bits
AES—With an encryption key of 128 bits
Gateway encryption operates in one of the following modes or can be disabled
entirely:
Best effort —Implements a “best effort” encryption algorithm. If an
endpoint supports encryption, it connects in an encrypted way. If not,
it connects without encryption.
Encryption required —Only connects encrypted calls. Encryption
can either be AES 128 or DES 56. The LifeSize Gateway does not
allow non-encrypted calls to connect.
Strong encryption required —Only allows AES 128 encrypted
calls. The LifeSize Gateway does not allow endpoints that do not
support AES 128 to connect.
Note (Gateway-PRI only) An encrypted call uses double the resources of a
regular call for all bandwidth rates. Gateway capacity when encryption is
supported is therefore half of regular LifeSize Gateway capacity, rounded up to
the nearest whole call.
Table 3-11 summarizes the encryption-related capabilities that the LifeSize
Gateway offers.
Table 3-11 Gateway Supported Encryption Capabilities
Mode Capabilities
Encryption off Priority 1: No encryption
Best effort Priority 1: AES 128
Priority 2: DES 56
Priority 3: No encryption
Encryption required Priority 1: AES 128
Priority 2: DES 56
Strong encryption required Priority 1: AES 128