Customers can install their own trusted certificates

Messaging and other applications running on a Messaging server rely on trusted certificates for secure interoperation.

Every time it starts, Messaging loads the following trusted certificates in its repository into its runtime memory:

Avaya Product Root Certificate Authority
SIP Certificate Authority
Motorola SSECA Root Certificate Authority
Spectel Root Certificate Authority

All of these certificates are concatenated in the all-ca.crt file in the repository.

By using the tlscertmanage command at the server command line, customers can load a third-party trusted certificate of their own trusted certificate into the Messaging repository for use the next time Messaging restarts.

Note

You must restart Messaging before it can recognize and use the newly-installed third-party certificate.

The all-ca.crt file can contain up to eight certificates, meaning that the customer may load up to four additional third-party certificates. If more than eight certificates are in the all-ca.crt file, Messaging loads the first eight then ignores the remaining certificates and generates a minor alarm and a syslog entry to notify the user that it could not load the file.