P a g e
|
22
UCM Security Manual
•
TLS Self-Signed CA
This is used when UCM acts as a client, to authenticate the server. If the server the UCM connecting
to uses a self-signed certificate, you should have their certificate installed here so authenticity of
their certificate can be verified. If the server uses a certificate that is signed by one of the larger
CAs, you should install a copy of server CA certificate here.
•
TLS Cert
This is used when UCM acts as a server. It’s sent to the client during TLS handshake. The TLS
Cert should include the key and server certificate. The “common name” field in the server certificate
should match the server host (either IP or domain name). This is required if the client side is another
UCM (not a standard, some clients do not have this requirement for server authentication). If not
matching, authentication on the UCM (client) fails and the TLS connection cannot get established.
•
TLS Do Not Verify
This is effective when UCM acts as a client. If set to “Yes”, the server’s certificate (sent to the client
during TLS Handshake) won’t be verified. Considering if two UCMs are peered, since the default
certificate built in UCM at the factory has “common name” equaling “localhost” which is not a valid
IP address, authentication will fail for sure. So, this is the default setting to avoid authentication
failure when using default certificate. Please note skipping verification won’t have effect on
encrypting SIP messages. If set to “No”, UCM (client) will verify the server’s certificate using “TLS
Self-Signed CA”.
Please note that administrator also needs configure “SIP Transport” to be “TLS” on the SIP endpoint device
to encrypt SIP messages sent to the UCM.