Use this procedure to replace an identity certificate issued by a CA other than the System Manager CA. A third party CA can be a commercial vendor, such as VeriSign or Symantec, or an enterprise-run CA maintained by your IT department. You can use this procedure when your third party identity certificate is about to expire and you need to replace it.
Obtain the new SIP identity certificate through a CSR or a PKCS#12 container.
Deploy the trusted third party root CA certificate on Avaya Breeze® platform.
Obtain the root CA certificate from the third party CA PKI administrator.
Add the root CA certificate into the Avaya Breeze® platform SECURITY_MODULE_SIP and WEBSPHERE trust stores.
Deploy the trusted third party root CA certificate on peer devices that connect SIP TLS to Avaya Breeze® platform.
Identity all the peer devices that connect to Avaya Breeze® platform through SIP over TLS. For example, Session Manager.
Obtain the root CA certificate.
Follow the peer device documentation on how to deploy the trusted CA certificates into their respective Trust Stores.
Replace the SIP identity certificate with a third party CA certificate.
Activate the new SIP identity certificate.
Verify the SIP TLS connections are now using the new identity certificate.
In System Manager, click Elements Session ManagerSystem StatusSIP Entity Monitoring.
Verify that the link status is UP for Avaya Breeze® platform entities that are TLS connected.
