Creating transports for load balancing in a SIP Proxy/Registrar cluster
If you installed multiple IBM® WebSphere® proxy servers for a cluster, you will need to configure additional transport chains for use with a load balancer. Configure the complete set of transport chains on every proxy server in the cluster.
Procedure
- On the WebSphere proxy server, log in to the Integrated Solutions Console as the WebSphere administrator.
- In the navigator, click .
- In the proxy servers table, click on the name of the server that you want to configure.
- On the Configuration page, look under "Proxy Settings", expand SIP Proxy Server Settings, and then click SIP proxy server transports.
- Modify the transport for TCP (non-secured) Connections
by adding the non-secured load balancer port as follows:
- In the Transport chains table, click on SIP_PROXY_CHAIN.
- On the SIP_PROXY_CHAIN page, look in the "Transport Channels" section and click TCP inbound channel.
- In the Port list, select PROXY_SIP_ADDRESS_LB.
- Type the port value.
- Click OK to save the updated transport chain.
- Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
- Modify the transport for TLS (secure) Connections by adding
the secure load balancer port as follows:
- In the Transport chains table, click on SIPS_PROXY_CHAIN.
- On the SIPS_PROXY_CHAIN page, look in the "Transport Channels" section and click TCP inbound channel.
- In the Port list, select PROXY_SIPS_ADDRESS_LB.
- Type the port value.
- Click OK to save the updated transport chain.
- Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
- Repeat this task for every WebSphere proxy server that is used with the cluster.