Avaya J100 Series Installing And Administering page 161

Name
Upload Trusted Certificate
Trusted Certificates file to upload
Match Identity to trust certificate
RFC 5922 certificate compliance
Require Key Usage certificate
extension
Server Certificate re-check hours
Warning on number of days
before Certificate expiration
FQDN IP Mapping
Online Certificate Status Protocol (OCSP)
April 2020
Description
Specifies the trusted certificate used by the phone. You can also
browse and upload the certificates from the local PC by clicking
Browse > Import.
Specifies the name of the certificate file to be uploaded.
The valid value is a string os up to 255 ASCII characters. File
names must be separated by commas without any intervening
spaces.
The default value is empty.
Specifies the status of the TLS server identification.
The options are:
• Yes (default)
• No
Specifies whether to enable or disable validating the SIP server
certificate for RFC 5922 compliance.
The options are:
• Enable (default)
• Disable
Specifies whether to enable or disable checking for Key Usage
extensions.
The options are:
• Enable (default)
• Disable
Specifies the time interval in hours for rechecking the expiration
and revocation status of the certificates used to establish any
existing TLS connections.
The valid value is an integer from 0 to 32767. The default value is
24 hours.
Specifies the number of days before the expiration of a certificate
that a warning must first appear on the phone screen.
The valid value is an integer from 0 to 99. The default value is 60
days.
Specifies a FQDN contained in the certificate when an IP address
is used to establish the connection. The parameter is a comma-
separated list of names or value pairs where the name is an FQDN
and the value is an IP address.
The valid value is a string of up to 255 characters without any
intervening spaces. The default value is empty.
Installing and Administering Avaya J100 series IP Phones in an Open SIP
Comments on this document? infodev@avaya.com
Configuring the phone using the web interface
environment
Table continues...
161