Ports used by the Sametime Community Server

IBM® Sametime® uses a number of ports on the server. This topic lists the default ports and their uses.

You can use the Sametime System Console to configure the ports on which the Sametime services listen for Connections from clients.

The port settings for all services can be accessed from the Configuration > Connectivity > Networks and Ports options of the Sametime System Console.

HTTP Services, Domino® Services, LDAP Services, and Sametime intraserver ports

The following ports are used by the Sametime HTTP Services, IBM Domino Application Services, and LDAP Services.

Table 1. HTTP Services, Domino Services, LDAP Services, and Sametime intraserver ports

Default ports used by the Sametime HTTP Services, IBM Domino Application Services, and LDAP Services are explained in this table.
Default Port Purpose
Port 80 If the administrator allows HTTP tunneling on port 80 during the Sametime installation, the Community Services multiplexer on the Sametime Community Server listens for HTTP connections from web browsers, Sametime Connect Client clients, Sametime Meeting Room clients, and Sametime Recorded Meeting clients on port 80.

If the administrator does not allow HTTP tunneling on port 80 during the Sametime installation, the Domino HTTP server listens for HTTP Connections on this port.

Alternate HTTP port (8088) If the administrator allows HTTP tunneling on port 80 during the Sametime installation (or afterward), the Domino HTTP server on which Sametime is installed must listen for HTTP Connections on a port other than port 80. The Sametime installation changes the Domino HTTP port from port 80 to port 8088 if the administrator allows HTTP tunneling on port 80 during a Sametime Community Server installation.
Note: If the administrator allows HTTP tunneling on port 80 during the Sametime installation, web browsers make HTTP Connections to the Community Services multiplexer on port 80, and the Community Services multiplexer makes an intraserver connection to the Sametime HTTP server on port 8088 on behalf of the web browser.

This configuration enables the Sametime Community Server to support HTTP tunneling on port 80 by default following the server installation.

Port 389
Port 443 The Domino HTTP server listens for HTTPS Connections on this port by default.

This port is used only if you have set up the Domino HTTP server to use Secure Sockets Layer (SSL) for web browser Connections. To configure the Sametime HTTP server to use SSL for Web browser Connections, see About SSL and Sametime.
Port 1352 The Domino server on which Sametime is installed listens for Connections from Notes® clients and Domino servers on this port.
Port 9092 The Event Server port on the Sametime Community Server is used for intraserver Connections between Sametime components. Make sure that this port is not used by other applications on the server.
Port 9094 The Token Server port on the Sametime Community Server is used for intraserver Connections between Sametime components.

If this port is used by multiple applications, refer to the topic Token server port for a discussion on resolving access to this port.

Community Services ports

The following ports are used by the Sametime Community Services. Most of these ports are configurable.

Table 2. Community Services ports

Default ports used by the Sametime Community Services are explained in this table.
Default Port Purpose
Port 1516 Community Services listens for direct TCP/IP Connections from the Community Services of other Sametime Community Servers on this port. If you have installed multiple Sametime Community servers, this port must be open for presence, chat, and other Community Services data to pass between the servers.

The communications that occur on port 1516 also enable one Sametime Community Server to start a meeting on another server (or "invite" the other server to the meeting).
Port 1533 The Community Services listen for direct TCP/IP Connections and HTTP-tunneled Connections from the Community Services clients (such as Sametime Connect Client and Sametime Meeting Room clients) on this port.
Note: The term "direct" TCP/IP connection means that the Sametime client uses a unique Sametime protocol over TCP/IP to establish a connection with the Community Services.

The Community Services also listen for HTTPS Connections from the Community Services clients on this port by default. The Community Services clients attempt HTTPS Connections when accessing the Sametime Community Server through an HTTPS proxy server. If a Sametime client connects to the Sametime Community Server using HTTPS, the HTTPS connection method is used, but the data passed on this connection is not encrypted.

If the administrator does not allow HTTP tunneling on port 80 during the Sametime installation, the Community Services clients attempt HTTP-tunneled Connections to the Community Services on port 1533 by default.

Port 80 If the administrator allows HTTP tunneling on port 80 during the Sametime installation, the Community Services clients can make HTTP-tunneled Connections to the Community Services multiplexer on port 80.
Note: When HTTP tunneling on port 80 is allowed during the Sametime installation, the Community Services multiplexer listens for HTTP-tunneled Connections on both port 80 and port 1533. The Community Services multiplexer simultaneously listens for direct TCP/IP Connections on port 1533.
Port 8082 When HTTP tunneling support is enabled, the Community Services clients can make HTTP-tunneled Connections to the Community Services multiplexer on port 8082 by default. Community Services clients can make HTTP-tunneled Connections on both ports 80 and 8082 by default.

Port 8082 ensures backward compatibility with previous Sametime releases. In previous releases, Sametime clients made HTTP-tunneled Connections to the Community Services only on port 8082. If a Sametime Connect Client client from a previous Sametime release attempts an HTTP-tunneled connection to a Sametime Community Server, the client might attempt this connection on port 8082.