Home
Welcome to the HCL Sametime® 11.6 administration documentation
Planning
This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
Network planning for meetings

Welcome to the HCL Sametime® 11.6 administration documentation
- 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.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
  - Sametime vs Sametime Premium
    This section provides a comparision chart between Sametime and Sametime Premium.
  - System requirements
    This section provides minimum system requirements for HCL Sametime 11.6 and Sametime 11.6 Meetings. Higher maintenance levels, such as fix packs and service packs, may be supported as they become available.
  - MongoDB
    This section describes why MongoDB is required for HCL Sametime and the deployment options.
  - LDAP
    HCL® Sametime® utilizes either a native Domino directory or an LDAP directory for user authentication. This topic provides information on LDAP directory planning. The LDAP server should be set up and running before deploying Sametime.
  - Sametime Community and Proxy servers
    This section describes the functionality of each Sametime® product and the servers or services required for each product.
  - Meetings server - FAQ
    Sametime 11.6 Meetings are an all-new meeting experience. Sametime 11.6 meetings have a new deployment model on Docker or with Kubernetes. For more detail, see the topic docker_kubernetes.html.
  - Sametime clients
    HCL Sametime 11 deployments support the following Sametime client types
  - 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. To learn more about which clients are supported by each of the servers, see the topic Sametime Serves.
  - Network planning for meetings
  - Clustering and high availability
    This topic explains the high availability capabilities of Sametime Community services and example deployment scenarios.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Network planning for meetings

Sametime meetings generate two types of traffic: web traffic and RTP media streams. Web traffic is standard HTTPS. And, media streams by default use UDP for optimal performance. If the UDP service is unavailable, enabling TCP for RTP media streams is supported.

To support the Sametime default configuration, use the following ports for client access:

For Kubernetes deployments: TCP port 443 and UDP port 30000
For Docker deployments: TCP port 443 and UDP port 10000

If you enable TCP for media streams, you can configure it to use TCP port 443. However, it does not send media streams as HTTPS data. Confirm with your security and firewall teams that this non-standard use of HTTPS port 443 will be permitted.

The amount of bandwidth consumed by Sametime Meetings depends on several factors, such as the quality of video being shared, the number of video and audio streams being shared, and more. The default limit for simultaneous video stream is 5. Increasing this value affects bandwidth consumption.

You must discuss the design of your Sametime deployment with your network and security teams before implementation. Many common network layer devices and technologies introduce latency, which can degrade the user experience. Identify all potential bottlenecks, for example, firewall, proxy, VPN, packet shapers, and intrusion prevention devices before deploying servers.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.