Appendix C. Sametime 8.5.2 Network-Related Resources
This chapter provides network-related resources pertaining to the installation, configuration, troubleshooting, or tuning of Sametime 8.5.2.
Topics covered in this chapter include:
Required ports for Sametime servers
Running with IPv6 addressing
Understanding NAT and Sametime
Troubleshooting or tuning your network for Sametime
Additional monitoring and tuning resources
Sample network configurations
Required ports for Sametime servers
The following tables include those ports that are required for the various Sametime components. Unless otherwise stated, they refer to TCP ports that should be open for traffic in and out of the firewall. An "X" in the following columns signifies that the port specified is used on the client side of the Sametime environment.
Sametime System Console ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
8700 |
Provides default browser access to the SSC. | |
8701 |
Provides HTTPS browser access to the SSC. | |
9080 |
Port used by the Sametime Community Server to access the SSC HTTP port. | |
9443 |
Port used by the Sametime Community Server to access the SSC HTTPS port. | |
50000 |
SSC database port used by installation manager utilities, post-registration utilities, and Sametime Meeting Server. |
Sametime Community Server ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
80 |
The Sametime Community Server listens for the SSC on port 80. | |
Alternate HTTP port (8088) |
If HTTP tunneling on port 80 is configured during the Sametime Community Server installation or afterward, the Domino HTTP server, on which the Sametime Community Server is installed, must listen for HTTP connections on a port other than port 80. | |
389 |
The Sametime Community Server connects to the LDAP server on port 389 if configured to connect to an LDAP server. | |
443 |
The Domino HTTP server listens for HTTPS connections from the SSC 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. | |
1352 |
The Domino server, on which Sametime Community Server is installed, listens for Notes clients and Domino server connections on port 1352. | |
9092 |
Port 9092 is the Event Server port on for the Sametime Community Server and is used for server connections between Sametime components. | |
9094 |
Port 9094 is the Token Server port on the Sametime Community Server and is used for server connections between Sametime components. |
Sametime Community Services (CS) ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
1516 | Port 1516 is used by CS to listen for direct TCP/IP connections from the Community Services of other Sametime Community Servers. This port must be open for chat, awareness, and other Community Services' data to pass between the servers. |
X |
1533 | The Community Services listen for direct TCP/IP connections and HTTP-tunneled connections from the Community Services clients (such as Sametime Connect and Sametime Meeting Room clients) on this port. |
X |
80 | If HTTP tunneling was configured on port 80 during the Sametime Community Server installation, the Community Services clients can make HTTPtunneled connections to the Community Services multiplexer on port 80. But the CS multiplexor listens for HTTP-tunneled connections on both port 80 and 1533. The CS multiplexer simultaneously listens for direct TCP/IP connections on port 1533. |
X |
8082 | When HTTP tunneling support is enabled, the CS clients can make HTTP-tunneled connections to the CS multiplexor 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. |
X |
Sametime Classic Meetings ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
554 |
The Sametime Classic Recorded Meeting client attempts a direct RTSP TCP/IP connection to the Recorded Meeting Broadcast Services on the Sametime Community Server on port 554. |
X |
1533 |
Port 1533 is used by the Sametime Classic Meeting Room client when the user attends an instant or scheduled meeting through a web browser. |
X |
8081 |
The Meeting Room client uses port 8081 to connect with the Meeting Services on the Sametime Community Server. |
X |
Sametime Proxy Server port | ||
---|---|---|
Default port |
Purpose | |
8880 | The SSC accesses the Deployment Manager Simple Object Access Protocol (SOAP) port. This is used for server-to-server communication and the port may vary depending on how WAS was configured. |
Sametime Media Manager Server ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
9080 |
Port 9080 is an HTTP port used for the management of audio/video calls. In a cluster, HTTP ports are proxied through a WebSphere Proxy Server. | |
42000-43000 |
Sametime Media Manager Packet Switcher routes audio data through a range of ports starting with 42000 through 43000. It uses values as needed in increments of two. If encryption is enabled (SRTP), the numbers to be used will be odd numbers. |
X |
46000-47000 |
Sametime Media Manager Packet Switcher routes video data through a range of ports starting with 46000 through 47000. It uses values as needed in increments of two. If encryption is enabled (SRTP), the range starts with an odd port number. |
X |
5060 and 5061 |
The Conference Manager and Packet Switcher are SIP applications, and therefore use WebSphere SIP container ports. | X |
5080/5081 |
The SIP Proxy Registrar uses these ports for client registration. |
X |
8880 |
Port 8880 is used for server-to-server communication. The SSC accesses the Deployment Manager SOAP port. |
X |
Sametime Meeting Server ports | ||
---|---|---|
Default port |
Purpose |
Used By Client |
443 | In a single node environment using HTTPS that bypasses the WAS Proxy, the Lotus Sametime Meeting Server listens for data from the Lotus Sametime Meeting Room client over this connection. | X |
80/443 | Meeting server deployed with WAS Proxy will listen on these ports for client connections. | X |
9080 | Port 9080 is used in a single node or multiple node environment when Lotus Sametime Meeting Server listens for data from the Lotus Sametime Meeting Room client over this connection when HTTP bypasses the WAS Proxy. | X |
9443 | In a multiple node environment using HTTPS, the Lotus Sametime Meeting Server listens for data from the Lotus Sametime Meeting Room client that is passed through the WAS Proxy. | X |
8880 | Port 8880 is used for server-to-server communication. The SSC accesses the Deployment Manager SOAP port. |
Sametime SIP Proxy and Registrar ports | ||
---|---|---|
Default port |
Purpose |
Used By Client |
5080-5081 |
SIP messaging uses these ports in a Media Manager deployment where the SIP Proxy and Registrar runs on a separate virtual host. |
X |
5060-5061 |
Ports are used in a multi-server Media Manager deployment where the SIP Proxy and Registrar runs on a separate host. |
X |
Sametime TURN Server ports | ||
---|---|---|
Default port |
Purpose |
Used by Client |
3478 |
UDP or TCP Port for basic STUN/TURN handling. This port should be open for internal and external access. |
X |
49152-65535 |
UDP Ports for dynamic packet allocation. These ports should be available for internal client access. |
X |
Sametime Packet Switcher (MCU) ports (internal use) | ||
---|---|---|
Default port |
Purpose |
Used by Client |
39000 |
UDP audio port for the MCU in single port mode. |
X |
40000 |
UDP video port for the MCU in single port mode. |
X |
42000-43000 |
UDP audio ports for the MCU in multi-port mode. |
X |
46000-47000 |
UDP video ports for the MCU in multi-port mode. |
X |