Configuring SSL certificates for WebSphere SIP proxy servers for use with the IP routing Load Balancer

To enable TLS SIP Traffic, you must configure the WebSphere® SIP proxy server to use the same SSL certificate as the IP routing Load Balancer.

About this task

When you created server and client SSL profiles for the IP routing Load Balancer, a public key was created. The WebSphere SIP proxy server must use the same public key to be able to accept TLS packets from the IP routing Load Balancer.

Procedure

This procedure assumes you used Open SSL, a free open source Certificate Authority distributed by Red Hat Linux™, to issue and sign keys when you set up the IP routing Load Balancer for TLS SIP traffic. If you used another Certificate Authority to set up the IP routing Load Balancer, use the same one for configuring the WebSphere SIP proxy server now.
  1. Import the Certificate Authority public key to the Deployment Manager.
  2. Request a personal certificate for the Deployment Manager from the Certificate Authority.
  3. Sign the personal certificate request using the Certificate Authority.
  4. Import the signed certificate to the Deployment Manager.
  5. Configure the WebSphere DefaultTrustStore and DefaultKeyStores to use the signed certificate.