Creating Self-Signed Certificates For Tls Contexts - AudioCodes Mediant 4000 SBC User Manual

Session border controller
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

User's Manual
7.
Click OK to confirm key generation; the device generates a new private key, indicated
by a message in the Certificate Signing Request group:
8.
Continue with the certificate configuration by either creating a CSR or generating a
new self-signed certificate.
9.
Save the configuration with a device reset for the new certificate to take effect.
10.6

Creating Self-Signed Certificates for TLS Contexts

The following procedure describes how to assign a certificate that is digitally signed by the
device itself to a TLS Context. In other words, the device acts as a CA.
To assign a self-signed certificate to a TLS Context:
1.
Before you begin, make sure of the following:
You have a unique DNS name for the device (e.g.,
dns_name.corp.customer.com). The name is used to access the device and
therefore, must be listed in the server certificate.
No traffic is running on the device. The certificate generation process is disruptive
to traffic and should be done during maintenance time.
2.
Open the TLS Contexts table (see ''Configuring TLS Certificate Contexts'' on page
103).
3.
In the table, select the required TLS Context index row, and then click the Change
Certificate link located below the table; the Change Certificates page appears.
4.
Under the Certificate Signing Request group, in the 'Subject Name [CN]' field, enter
the fully-qualified DNS name (FQDN) as the certificate subject.
Version 7.2
Figure 10-7: Indication of Newly Generated Private Key
10. Configuring SSL/TLS Certificates
113
Mediant 4000 SBC

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mediant 4000b sbc

Table of Contents