Certificates issued by a third party

Last Updated : Aug 19, 2016 |

The use of third party certificates is optional. Third party certificates are not required.

A third party CA can be a commercial vendor such as VeriSign and Symantec, or an enterprise-run CA that is maintained by the customer’s IT department. You can create third party certificates using openssl or open source tools such as EJBCA (http://www.ejbca.org).

Use this checklist for using third party Identity Certificates.

#

Action

Link

1

Add the third party Root Certificate to Communication Manager.

Repeat this step for each Communication Manager that is connected to the Session Manager.

Adding a third party Root Certificate to Communication Manager.

2

Add the third party Root Certificate CA to 96xx phones.

Adding a third party root certificate CA to 96xx phones.

3

Add the third party Root Certificate CA to the trusted list for any other adjunct device that uses TLS to connect to Session Manager through SIP.

For example, Avaya Voice Portal and Meeting Exchange.

4

Replace the Session Manager SIP and HTTP Identity Certificates.

Installing third party certificates on Session Manager.

5

Add the third party certificate to the trusted list.

Adding trusted certificates.