Checking for port conflicts between Sametime and WebSphere proxy server

If the IBM® Sametime® Media Manager's SIP Proxy/Registrar Server and the WebSphere® Application Server SIP Proxy server are running on the same computer, avoid problems by verifying that the IBM WebSphere Application Server SIP Proxy Server is listening on the correct ports and is not in conflict with the IBM Sametime SIP Proxy/Registrar Server running on the same computer.

About this task

Follow these steps to compare the SIP ports used by the WebSphere Application Server SIP Proxy with those used by the Sametime SIP Proxy/Registrar Server cluster member running on the same computer. If your cluster has both Sametime and WebSphere proxy server running on multiple nodes, be sure to check the ports on each node.

Procedure

On the node being checked, log in to the Integrated Solutions Console as the WebSphere administrator.
Check the ports used by the WebSphere Application Server SIP Proxy server:
1. Click Servers > Server Types > WebSphere proxy servers.
2. In the list of proxy servers, click the node's WebSphere Application Server SIP Proxy server to open its Configuration page.
3. In the "Communications" section, click Ports.
4. Write down the values assigned to the following ports:
  - PROXY_SIP_ADDRESS
  - PROXY_SIPS_ADDRESS
Check the ports used by the Sametime SIP Proxy/Registrar cluster member running on the same computer.
1. Click Servers > Server Types > WebSphere application servers.
2. In the list of application servers, click the name of the Sametime SIP Proxy/Registrar to open its Configuration page.
3. In the "Communications" section, click Ports.
4. Write down the values assigned to the following ports:
  - SIP_DEFAULTHOST
  - SIP_DEFAULTHOST_SECURE

Results

The ports are in conflict if the WebSphere Application Server SIP Proxy server is listening on the same ports as the Sametime SIP Proxy/Registrar.

What to do next

Your next task depends on whether there is a port conflict to resolve:

If the ports are in conflict, proceed to Changing a WebSphere proxy server's port settings.
If the ports are not in conflict, then the WebSphere proxy server configuration is complete. Skip to Installing IBM Load Balancer.