Ports used by Sametime

HCL Sametime uses several ports on the server. This topic lists the default ports and their uses. If firewalls are in use in your environment, all traffic on these ports should be permitted bidirectionally.

HCL Sametime Community Server Ports

The Default ports used by the Sametime Community Services are explained in this table.

Table 1. Ports used by the HCL Sametime Community Server
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 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)	The administrator can optionally enable HTTP tunneling on port 80. The Domino HTTP server on which Sametime is installed must listen for HTTP Connections on a port other than port 80. The HTTP server can be changed to port 8088 to allow the Community Services to listen on port 80. 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.
Port 389	This is the port for unsecure communications from the Community server to the LDAP server.
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 browsers.
Port 636	The Community server communicates with LDAP securely using this port for directory services.
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.
Port 27017	The Community server communicates with MongoDB over this port. MongoDB is used for persistent chat.
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. Community server listens on this port for communications from the Sametime Proxy Server.
Port 1533	The Community Services listen for direct TCP/IP Connections and HTTP-tunneled Connections from the Community Services clients (such as Sametime Connect) 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.
Port 80	The Domino server on which Sametime is installed listens on port 80 by default for HTTP connections. As an optional configuration, the server can be configured for HTTP tunneling on port 80. In this configuration, 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 configured, 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 from a previous Sametime release attempts an HTTP-tunneled connection to a Sametime Community Server, the client might attempt this connection on port 8082.

Sametime Proxy Server Ports

The Default ports used by the Sametime Proxy Services are explained in this table.

Table 2. **Sametime Proxy Server Ports**
Default Port	Purpose
Port 1516	Sametime Proxy server retrieves community services information from the Sametime Community server on this port. Information about users such as their LTPA token, presence, status and chats is transferred over this port between servers.
Port 8443	This is the default HTTPS port for the Proxy server, it is configurable. Many customers change the default port to well-known HTTPS port 443.
Port 27017	The Proxy server communicates with the MongoDB server on this port.
Port 443	Proxy server can be configured to listen for HTTPS requests over port 443. The Proxy server communicates with Google’s Firebase Cloud Messaging servers, which provides notifications to Android devices on port 443. Proxy server connects to Apple’s Push Notification Service over port 443.

Sametime Meeting Server Ports

The Default ports used by the Sametime Meeting Services are explained in this table.

Table 3. Sametime Meeting Server
Default Port	Purpose
Port 443	Sametime Meeting clients connect to the Meeting server using HTTPS on port 443. Sametime Meeting server connects to Sametime Proxy server on port 443, required to authenticate users.
Port 10000	Audio and video clients use this UDP port to stream media data when deploying Sametime Meeting Server on Docker.
Port 30000	Audio and video clients use this UDP port to stream media data when deploying Sametime Meeting Server on Kubernetes.
19302	This UDP port is the default STUN port used by both the client and meeting server for NAT traversal.
27017	Sametime Meeting server connects to MongoDB server to provide support for moderated meeting rooms and reserved meeting names.