Home
HCL Sametime® Administration Guide 12
Planning
This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
Planning the network topology and connectivity
This topic explains how Sametime components are connected and the default ports that are used. There are also example topologies to illustrate how Sametime can be deployed in different scenarios.
Ports used by Sametime services
Sametime services use several ports for communication. If firewalls are in use in your environment, all traffic on these ports should be permitted bidirectionally.

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
  - Sametime versus Sametime Premium
    Depending on the Sametime product that is installed, detemines which Sametime features are available. HCL Sametime provides secure real-time communication across devices, and HCL Sametime Premium expands those features to include video and file sharing.
  - Prerequistes
    Before you being the install process, ensure that your environment includes all prerequistes and system requirements.
  - Platforms
  - Meeting server FAQ
    The Meeting server routes media traffic.
  - Planning the network topology and connectivity
    This topic explains how Sametime components are connected and the default ports that are used. There are also example topologies to illustrate how Sametime can be deployed in different scenarios.
    - Planning considerations for chat
    - Considerations for Sametime Premium
    - Considerations for telephony
      Integration with the Teamcall Message Gateway (TMG) application from iLink, telephony services can be added to your Sametime environment to allow for telephone access to chats and meetings.
    - Ports used by Sametime services
      Sametime services use several ports for communication. If firewalls are in use in your environment, all traffic on these ports should be permitted bidirectionally.
  - Network planning for meetings
  - Clustering and high availability
    High availability and high capacity configuration for Sametime is achieved in different ways depending on which component is being configured for HA. See the topics below to learn more about chat, meetings and MongoDB.
  - Managing Sametime features
    HCL Domino users are entitled to limited use of HCL Sametime chat capabilities.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Ports used by Sametime services

Sametime services use several ports for communication. If firewalls are in use in your environment, all traffic on these ports should be permitted bidirectionally.

Table 1. Ports used by Sametime services
Port Number	Description
389	Used for unsecure communications from the Sametime server to the LDAP server.
443	Used for HTTP commnications over a secure connection.
636	Use for secure communications with LDAP for directory services.
1516	Used as an internal port between the community and proxy pods.
1533	Used to listen for direct TCP/IP connections from Sametime Connect clients. A Direct TCP/IP connection is when a Sametime client uses a unique Sametime protocol over TCP/IP to establish a connection with community services.
1935	Used when streaming YouTube videos.
5280, 5222	Used to reach the service Cluster IP for Jitsi. In Kubernetes environments, for websockets to function properly the video pods using node port must be able to reach the service Cluster IP for Jitsi on ports 5280 and 5222. See the Websockets fail to load after installing Sametime 11.6 or 12.0.x on Kubernetes article for more information.
8000	Used to listen for HTTP communications. All communication over this port is redirected to HTTPS port 443. Port 8000 is the default port assigned during the product install process.
10000	Used by audio and video clients to stream media data when deploying Sametime on Docker.
19302	This UDP port is the default STUN port used by both the client and meeting server for NAT traversal.
27017	Used for communication with the MongoDB.
30000	Used by audio and video clients to stream media data when deploying Sametime on Kubernetes.