Dialogic® Diva® SIPcontrolTM Software Configuration
page 30
Security Profiles
When you use the Transport Layer Security (TLS) protocol for secure communication, you need to set various
security settings.
The following menus are available for configuration:
•
Upload Certificate And Key Files
below
•
Upload Certificate And Key Files
For authentication and data encryption, certificates need to be installed on the computer with the Diva SIPcontrol
software and on remote computers. When a secure domain is opened, server and client authenticate each other
with a so called "SSL handshake". With this handshake, the identity of a user is certified and the user can be
trusted. All necessary certificates are provided by a Certificate Authority (CA) and they are issued for one domain
name. For test purposes or internal usage, you can also create and sign your own self-signed certificate, e.g.,
with one of the many tools available on the internet, just google for "self-signed certificate" and you will find a
list of possible tools. But you need to be aware that self-signed certificates do not provide the same security as
CA-signed certificates. All files need to be in "pem" format, that means base-64-encoded.
The screen below shows the web interface with no certificates uploaded.
To upload a certificate:
1.
Click
Browse
, in the
File Upload
window go to the folder where the certificate file is located, and click
Open
.
2.
In the Diva SIPcontrol software web interface click
Upload
. After the certificates are uploaded web interface
looks like this:
Certificate authority file:
This file is the root certificate, which is used to sign a certificate. It is only needed for
MTLS or TLS authentication.
With this file, the CA ensures that the public key contained in the certificate belongs to
the server stated in the certificate.
Certificate file:
This file is also generated from the CA and it contains the public key of the server on
which the Diva SIPcontrol software is installed. This file is used for encrypting of
information.
Key file:
This file contains the private key for each endpoint, and it is used for decrypting of
information. The key file must not be password protected.
