Filter
Top Products
Configuring SSL certificates
Cisco TelePresence ISDN Gateway 2.1 Online help (Printable format) 120 of 135
field shows 'Key matches
certificate' then the data is securely
encrypted in both directions.
Local certificate configuration
Certificate
If your organization has bought a
certificate, or you have your own way of
generating certificates, you can upload it.
Browse to find the certificate file.
Private key
Browse to find the private key file that
accompanies your certificate.
Private key
encryption
password
If your private key is stored in an
encrypted format, you must enter the
password here so that you can upload the
key to the ISDN Gateway.
Trust store
You can upload a 'trust store' of
certificates that the ISDN Gateway will use
to verify the identity of the other end of a
TLS connection.
If you have a trust store certificate on the
ISDN Gateway, you can delete it; to do so,
click Delete trust store.
The trust store must be in '.pem' format.
Note that uploading a new trust
store replaces the existing store.
Certificate
verification
settings
Choose to what extent the ISDN Gateway
will verify the identity of the far end for a
connection:
No verification: all outgoing
connections are permitted to
proceed, even if the far end does
not present a valid and trusted
certificate.
Outgoing connections only:
outgoing connections are only
permitted if the far end has a
certificate which is trusted.
Outgoing connections and
incoming calls: outgoing
connections and incoming
connections for SIP calls using
TLS must have a certificate which
is trusted otherwise the ISDN
Gateway will not allow the
connection to proceed.
The trust store contains 'master'
certificates that can be used to
verify the identity of a certificate
presented by the far end.
Outgoing connections are
connections such as SIP calls
which use TLS.