Figure 3-43: Ike Table Listing Loaded Certificate Files - AudioCodes Mediant 600 User Manual

Notes:

To apply the loaded certificate for IPSec negotiations:
1. Open the 'IKE Table' page (see Configuring the IP Security Proposal Table on page
92); the 'Loaded Certificates Files' group lists the newly uploaded certificates, as
shown below:

Figure 3-43: IKE Table Listing Loaded Certificate Files

2. Click the Apply button to load the certificates; future IKE negotiations are now
performed using the new certificates.
3.3.1.5.2 Client Certificates
By default, Web servers using SSL provide one-way authentication. The client is certain
that the information provided by the Web server is authentic. When an organizational PKI is
used, two-way authentication may be desired: both client and server should be
authenticated using X.509 certificates. This is achieved by installing a client certificate on
the managing PC, and loading the same certificate (in base64-encoded X.509 format) to
the device's Trusted Root Certificate Store. The Trusted Root Certificate file should contain
both the certificate of the authorized user and the certificate of the CA.
Since X.509 certificates have an expiration date and time, the device must be configured to
use NTP (see ''Simple Network Time Protocol Support'' on page 403) to obtain the current
date and time. Without the correct date and time, client certificates cannot work.
SIP User's Manual
•
The certificate replacement process can be repeated when necessary
(e.g., the new certificate expires).
•
It is possible to use the IP address of the device (e.g., 10.3.3.1) instead
of a qualified DNS name in the Subject Name. This is not recommended
since the IP address is subject to changes and may not uniquely identify
the device.
•
The server certificate can also be loaded via ini file using the parameter
HTTPSCertFileName.
64
Mediant 600 & Mediant 1000
Document #: LTRT-83308