The IBM® Sametime® Community Mux accepts
connections from clients, such as the IBM Sametime Connect client.
Use this task to enable or disable TLS on the Sametime Community Mux port.
You can also use this task to change the listening address and port,
although it is recommended you use the default port number, of 1533.
About this task
Define the IBM Sametime Community Mux port.
Procedure
- Log in to the Integrated Solutions Console.
- Click .
- In the Sametime Community
Servers list, click the deployment name of the server that you want
to change.
- Click the Connectivity tab.
- Under Client Connections, modify these fields:
- In the Host name field, specify
the host name or IP address that you want the Sametime Community Mux to
listen to. Leave the field blank to accept connections on all the
local addresses.
- In the Port field, specify the
port number that you want the Sametime Community Mux to
listen to. It is recommended to keep the default port number of 1533.
If a different port number is configured, it must be set to the same
port number in all Sametime clients
that connect to this Sametime Community
Mux.
- In the Client encryption mode field,
choose one of three options:
- Strict TLS - The Sametime Community Mux accepts
only TLS connections.
- Legacy Sametime encryption - The Sametime Community Mux does
not accept TLS connections. Instead, connections are encrypted using
the Diffie-Hellman key exchange and RC2 encryption, as in IBM Sametime 9 and earlier releases.
- Both allowed - The Sametime Community Mux allows
both legacy-encrypted connections and TLS connections over the same
port. This mode is suitable if some, but not all of the Sametime clients, have TLS
capability.
Note: Enabling TLS on this port requires setting up the TLS configuration.
It also requires that you enable TLS in Sametime clients.