Deploying instant messaging, meetings, web clients, audio, and videoAdded by IBM on November 23, 2011 | Version 1 (Original)
|To provide all client features to users, plan to deploy Sametime® Community Servers, Sametime Meeting Servers, Sametime Proxy Servers, and Sametime Media Manager components.
To provide all client features to users, plan to deploy Sametime
® Community Servers, Sametime
Meeting Servers, Sametime
Proxy Servers, and Sametime Media Manager components.
The following components must be deployed in a Sametime
environment that combines instant messaging and presence with meetings that enable audio and video features:
- Sametime System Console - used for managing and administering servers from a central location
- LDAP directory
- Sametime Community Server
- Sametime Meeting Server - required when browser-based clients are using the Sametime web audio-visual plugin for meetings
- Sametime Connect client, Sametime client embedded in Notes®, or Sametime browser client
- Sametime Proxy Server - provides an integrated web chat client and presence; required for Sametime browser clients
- Sametime Media Manager - provides audio and video features in the Sametime client and in meetings
The following components can optionally be deployed:
- Sametime Gateway - extends instant messaging to external communities
- Sametime Bandwidth Manager - enables you to assign maximum levels of bandwidth usage to users based on policy settings
- Sametime TURN Server - enables Sametime clients running release 8.5.2 or later to send and receive audio and video communications across a NAT (Network Address Translator) or firewall when direct peer-to-peer communications are not possible.
Audio-visual components provided with the Sametime Media Manager
The Sametime Media Manager comprises three components, which are installed on separate systems in a production environment.
Parent topic: Planning deployments with the Sametime Standard features you want
- Packet Switcher
Based on voice-activated switching, the Packet Switcher functions as an MCU (Multipoint Conferencing Unit) by routing audio and video data between participant endpoints. There can be one or more Packet Switchers in a deployment; the Conference Manager will distribute conferences over the available Packet Switchers. A Packet Switcher can only be registered with one Conference Manager (or cluster of Conference Managers). A Packet Switcher should not be a member of a WebSphere Application Server cluster; instead, each Packet Switcher is deployed as a non-clustered (primary) node.
- Conference Manager
Manages multipoint conferences by maintaining a dialog with each participant, and ensuring that all media flows between those participants. You can install multiple Conference Manager components and cluster them for high availability and failover.
- SIP Proxy/Registrar
Directs conference participants to Conference Manager servers and provides high availability and failover functionality. You can install multiple SIP Proxy/Registrar components and cluster them for high availability and failover.