• Certificate Hostname Validation
• Verify Certificate Key Usage
• Verify Certificate Revocation
5. On the web interface, click Save.
Related links
Enabling the Avaya IX CU360 advanced settings on page 37
Advanced SIP field descriptions
Name Description
Transport Outbound Call The option to configure the protocol to use for the outgoing calls.
You can use TLS to secure the calls.
Use TLS The option to configure Avaya IX
™
CU360 to enable the TLS functionality.
Verify Certificate The option to configure Avaya IX
™
CU360 to use only TLS to connect to
other devices. These devices must have security certificates that Avaya
IX
™
CU360 can verify.
Certificate Hostname
Validation
The option to configure the host name validation level.
• Accept Validated Only: Avaya IX
™
CU360 only processes security
certificates with validates host names. This is the default policy for
certificate host name and key use validation.
• Accept Validated or same default certificate: Avaya IX
™
CU360
processes certificates that are validated or are the same as the
certificates that Avaya IX
™
CU360 uses.
• Accept All: Avaya IX
™
CU360 processes all security certificates and
does not validate host names.
Verify Certificate Key Usage The option to configure the certificate key use level.
If you enable this option, Avaya IX
™
CU360 processes only certificates
that contain values for the key use parameters — Key Usage or Extended
Key Usage.
Verify Certificate
Revocation
The option to configure Avaya IX
™
CU360 to verify security certificate
revocation.
• Yes always: Avaya IX
™
CU360 checks all certificates for revocation.
Avaya IX
™
CU360 rejects certificates for which it cannot verify
revocation.
• Yes if possible: Avaya IX
™
CU360 checks all certificates for
revocation. Avaya IX
™
CU360 rejects revoked certificates, but
processes certificates for which it cannot verify revocation.
• No: Avaya IX
™
CU360 does not check certificates for revocation.
Advance administration
April 2020 Installing and Administering Avaya IX Collaboration Unit CU360 98
Comments on this document? infodev@avaya.com