Audio and video deployment plans

When deploying Sametime® Media Manager components, you must create the deployment plans and install the servers in a specified sequence, depending on your deployment options.

When deploying audio and video services, keep in mind the following best practices:
  • In the Sametime System Console, create deployment plans for the Sametime Conference Manager, Sametime SIP Proxy/Registrar, Sametime Video Manager, and Sametime Video MCU before you install any of these components.
    The sequence in which you create the deployment plans depends on your Sametime Media Manager topology:
    • Separate Sametime SIP Proxy/Registrar and Conference Manager components:
      1. Sametime SIP Proxy/Registrar
      2. Sametime Video Manager
      3. Sametime Conference Manager
      4. Sametime Video MCU
    • Combined Sametime SIP Proxy/Registrar and Sametime Conference Manager on one computer:
      1. Sametime Video Manager
      2. Combined Sametime SIP Proxy/Registrar and Sametime Conference Manager ("PR+CF" option)
      3. Sametime Video MCU
    You must install the components in the same sequence that you created the deployment plans.
  • The Video Manager and the Video MCU each must be on its own computer. Best practice calls for 16 core, 16 GB for each computer.
  • SIP Proxy/Registrar and Conference Manager can be installed separately or together on the same computer.
  • The Sametime System Console can only administer one Sametime Media Manager instance. Some individual components of the Media Manager may be individually clustered to provide failover and high availability, deployed as standalone servers, or installed on the same server - but only one Media Manager deployment can be administered from a given Sametime System Console.
Rules for each component include the following:
  • SIP Proxy/Registrar can be clustered using WebSphere® Network Deployment
  • Conference Manager can be clustered using WebSphere Network Deployment
  • Video Manager can be clustered. The Video Manager installs as a standard node (not a primary or secondary node) with its own load balancer. You can install several Video Managers with an IP sprayer in front of them for redundancy and failover.
  • Video MCU runs on a separate WebSphere node and cannot be clustered. To support a higher number of simultaneous audio and video conferences, you can install several Video MCU servers, each on its own box, with a load balancer in front of them. The Video Manager handles the workload distribution among the Video MCUs. When deploying Video MCUs and Video Managers, you install Video MCUs first, then add them to the Video Managers.

The Media Manager does not work when installing with a DNS alias. You must configure the computer with a fully qualified host name (including domain part) and use this for the installation. This name does not need to be configured anywhere else and the client does not see it. Ask your IBM® representative for detailed sizing information in a defined environment.

The Video MCU is not administered from the Sametime System Console, so it is not affected by this limitation; however the Conference Manager and the SIP Proxy/Registrar components are administered from the Sametime System Console, so your planning must take this limitation into consideration.
  • A Conference Manager cluster and a SIP Proxy/Registrar cluster can both be administered from the same Sametime System Console. This is the recommended topology for enterprise customers.
  • The Video MCU and Video Manager use SIP ports 5060 or 5061. Their Sametime System Console management port is TCP 8443

Web client users can access Media Services when you enable the Meeting Services for awareness through the Sametime Proxy Server. The Sametime Proxy Server provides the Web A/V Client plug-in to users.