After the device boots up, it displays a security certificate error. The problem persists after subsequent reboots.
Cause
Some required certificates might not be downloaded to the device through the TRUSTCERTS parameter.
Solution
Procedure
Check the following to ensure that you have defined the TRUSTCERTS parameter correctly for the required certificate files to be downloaded to the device:
Check and ensure all required certificates for services to be run on the device are included in the list of certificates defined in the TRUSTCERTS parameter.
Ensure that URLs or file paths to the certificate files are correctly defined in the TRUSTCERTS parameter value.
Ensure that the TRUSTCERTS parameter value does not exceed the limit of 4000 characters.
Tip:
Avoid using long absolute URLs to the certificate files. Instead, copy the files to the file server and provide relative file paths.
When using Avaya Aura® Device Services, ensure that the TRUSTCERTS parameter value defined in the 46xxsettings.txt file has the same set of certificates as the value defined in Avaya Aura® Device Services. However, the syntax does not need to be the same. The certificate file paths or the order of the certificates in the list need not be the same in the parameter value in the 46xxsettings.txt file and Avaya Aura® Device Services. When using Avaya Aura® Device Services, you must use absolute file paths in the parameter value.
