Home
Planning
Planning is critical to a successful deployment. Many deployment problems, growth problems, and capacity problems occur because not enough time is taken to carefully plan a deployment. Plan your IBM® Sametime® installation by determining features needed, reviewing system requirements, determining capacity requirements, and the servers and computers needed for your deployment.
Planning Sametime® features
This section describes best practices, requirements, tips, and things you should know when planning for instant messaging and presence services, meeting services, web client services, audio and video services, broadcast communities and persistent chat rooms, including IBM® Sametime® services in the extranet for remote users and customers. Included in this section are several sample topologies, everything from simple internal meetings to voice and video for intranet and extranet users.
Planning TURN services to traverse NAT
The IBM® Sametime® TURN Server works with Sametime Media Manager, enabling clients to communicate across a NAT or firewall during a multimedia session.
Planning a cluster of TURN Servers
Deploying multiple IBM® Sametime® TURN Servers requires a special configuration to ensure that external clients can access the servers using public IP addresses.

Planning a cluster of TURN Servers

Deploying multiple IBM® Sametime® TURN Servers requires a special configuration to ensure that external clients can access the servers using public IP addresses.

When you deploy multiple TURN Servers, you treat them as a cluster and deploy a load balancer in front of them. The load balancer accepts requests from external clients and distributes them among the TURN Servers to prevent overloading a single server. When each TURN Server responds directly to a client, it uses its own local IP instead of the load balancer's public IP that the client originally accessed. This causes a problem because the external client does not recognize the TURN Server's own IP address, cannot access the TURN Server (hosted behind a firewall) directly to verify it, and rejects the connection.

To resolve this problem, you can deploy the TURN Servers using one of the following configurations, which enable the TURN Servers to provide public IP addresses when responding to the external clients: