Meeting Server ports

Meeting Server

The following ports are used on the Sametime Meeting Server. Most of these ports are configurable.

In a cluster environment, the servers need to talk to each other and to an IBM WebSphere HTTP proxy server. That communication is on ports 9080 and 9443 because in that deployment the WebSphere HTTP proxy server is facing the client. The clients still talk to the Meeting Server on ports 80 and 443, but all backend connectivity is done on ports 9080 and 9443. Therefore, if you look at a Meeting Server and are looking for connections on port 80, you may see none because you are in a cluster and the WebSphere HTTP proxy server is handling those connections. You'll see connectivity on 9080 and 9443.

Deploying a WebSphere Application Server SOAP port is complicated and might include ports in addition to 8880, especially if there is more than one Sametime product on a specific computer. Usually the firewall openings are configured prior to the deployment, when your understanding of the port configuration is still incomplete. To have a smoother deployment, you can add port ranges - for example 8880 - 8890 and 8600 - 8610. For example, when a Sametime Proxy Server node in the DMZ is federated into the internal Sametime System Console cell, it needs one port for Sametime System Console to Sametime Proxy Server Deployment Manager communication and another port for the Sametime Proxy Server primary node communication - which is on the same computer. You might also need port 8601 when you want to update the Sametime Proxy Server configuration through the Sametime System Console.