Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Deploying audio and video
Audio and video features are provided primarily by the IBM® Sametime® Media Manager, which supports point-to-point and multipoint calls. The Sametime Media Manager uses standard audio and video codecs so that it works with products from other audio and video vendors.
Installing Sametime® Media Manager
The IBM® Sametime® Media Manager is an optional component that runs on a WebSphere® Application Server and provides audio and video features for a Sametime deployment. It requires a Sametime Community Server. You must complete a guided activity for every component, which creates a deployment plan for the installation program. You must have a deployment plan for every Media Manager component before you start installing any component.
Sametime® Media Manager
The IBM® Sametime® Media Manager is available for installing on the Linux™ or Windows™ platforms only. The Sametime Video Manager and Sametime Video MCU components run only on Linux, and can be used only with the Sametime Conference or Sametime Complete offerings.
Installing the Sametime® Media Manager's combined PR+CF components
Install the IBM® Sametime® Media Manager's SIP Proxy/Registrar and Conference Manager on the same computer. This option requires that you created a deployment plan using the Install PR+CF option. You must also have created all other deployment plans for Media Manager components you plan to install separately. The combined components cannot be clustered for high availability; if you expect to require clustering in the future, you should install the SIP Proxy/Registrar and the Conference Manager on separate computers now.
Disabling token authentication on the Conference Manager
This release does not support token authentication, so disable the feature on the IBM® Sametime® Media Manager's Conference Manager component.

Disabling token authentication on the Conference Manager

This release does not support token authentication, so disable the feature on the IBM® Sametime® Media Manager's Conference Manager component.

About this task

To disable token validation on the Conference Manager, set the property TURNTokenAuthEnabled to false.

Procedure

On the server hosting the Conference Manager's deployment manager, locate the stavconfig.xml in the deployment manager's profile.
The Sametime System Console is typically used as the deployment manager but is not required; your deployment may use a different server for that purpose. The stavconfig.xml is typically stored in the following location for the deployment manager:
```
Dmgr_install_root/config/cells/Cell_name/nodes/Node_name/servers/Server_name
```
Open the file for editing.

Locate the TURNTokenAuthEnabled setting and set its value to false.

<configuration lastUpdated="1226425838277" name="TURNTokenAuthEnabled" value="false"/>

Save and close the file.
If there is one Conference Manager, restart it now. If you deployed a cluster of Conference managers, synchronize all nodes in the cluster as follows:
1. In the deployment manager's Integrated Solutions Console, click System Administration > Nodes.
2. In the nodes table, select all nodes in the cluster.
3. Click the Full Resynchronize button at the beginning of the table.