® Media Manager runs on WebSphere
® Application Server to provide audio visual services for chats and meetings. It requires a Sametime
Media Manager uses the Session Initiation Protocol (SIP) to provide support for point-to-point and multipoint calls. It is designed to support standard audio and video codecs so that it works with other external audio and video vendors.
Media Manager uses three components. In a small deployment, the Sametime
Media Manager components can all be installed on one server, but in an enterprise deployment, you should install each of the components on its own server.
- Conference server
The Conference server manages all conferences, including point-to-point and multipoint. It works with the client to establish the SIP session for the call. It hosts the internal TCSPI adapter and optionally an external TCSPI adapter.
The Conference server requires access to LDAP, Meetings (optional), and Proxy/Registrar (including transport protocol: UDP, TCP, TLS). The Conference server will handle workload management for conference sessions among the switchers.
- Proxy and Registrar
The Proxy and Registrar is responsible for location service and forwarding SIP messages to a destination. It requires access to LDAP. You may also install and configure a database to be used with it.
- Packet switcher
The Packet switcher is responsible for receiving and sending media streams from endpoints to other endpoints in a conference. The Switcher works on audio streams to determine the active video stream to send to the participants, a process known as Voice-Activated Switching (VAS).
The Packet switcher requires access to LDAP, Conference server, and media ports (1 or a range of ports for audio, and 1 or a range of ports for video). If the switchers are installed on the same machine, ensure that are no port conflicts.
Security is enabled by default. Use TLS or SSL to allow servers to communicate. TLS transport is recommended when using media encryption.
Parent topic: What is Sametime?