Whether the MCU is able to use encryption or not.
When encryption status is Enabled, the MCU advertises itself as being able to use encryption and will use encryption if required to do so by an endpoint. If this setting is Enabled, you can enable or disable the use of encryption on a per- conference basis.
If this setting is Disabled, no conference will be able to use encryption.
The default encryption setting for new scheduled | When you (or another user) create a new | ||
conferences (on the | > | conference (by choosing | and clicking |
page). |
| ), you can set the encryption | |
|
| setting for the conference to be either Allowed or | |
|
| Required. This control defines which option is | |
|
| selected by default. However, when creating a | |
|
| conference this can be changed. |
|
|
| ||
When enabled, this setting forces encryption to | Changing this setting will have no effect on | ||
be used for new ad hoc conferences. | currently active ad hoc conferences; however, | ||
|
| when an ad hoc conference is running, whether | |
|
| or not encryption is required for that conference | |
|
| can be configured (go to | , select the |
|
| conference you require and select the |
|
|
| tab). |
|
|
| ||
Select the setting for media encryption for SIP | For more information refer to Using encryption | ||
calls: |
| with SIP, below. |
|
All transports: If encryption is used for a | When disabled, the MCU will not advertise that | ||
call, the media will be encrypted using | it is able to encrypt using SRTP. It is only | ||
SRTP regardless of transport mechanism | necessary to disable SRTP if it is causing | ||
used for call control messages. | problems. |
| |
Secure transports (TLS) only: If encryption is used for a call, the media will only be encrypted in calls that are set up using TLS.
Disabled: SRTP will not be used for any calls. The MCU will not encrypt media for SIP calls.
135
