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 for Media Manager services
This topic provides an overview of peer-to-peer and n-way voice and video communication in IBM® Sametime®. It describes the Sametime servers and server components, and third party components, used in voice and video.
Audio and video deployment scenarios
This topic surveys the IBM® Sametime® voice and video deployment scenarios available based on your environment and resources. This topic can help you decide which deployment is right for you.
Voice and video with NAT
A client accessing the IBM Sametime® Media Manager for audio and video servers must go through a Sametime TURN Server when a NAT (Network Address Translation) device is present.

Voice and video with NAT

A client accessing the IBM Sametime® Media Manager for audio and video servers must go through a Sametime TURN Server when a NAT (Network Address Translation) device is present.

When there are internal NAT devices that separate clients from Sametime components in internal networks, you must deploy the Sametime TURN Server next to the Sametime Media Manager. This will enable internal users to go through a NAT device, find their IP address, and negotiate an audio/video session.

The graphic that follows shows how a client accessing the Media Manager for audio and video servers must go through a TURN Server when a NAT (Network Address Translation) device is present.

Client accessing Media Manager for audio/video servers uses TURN Server when a NAT device is present.