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.
Configuring a Sametime® Media Manager
This section describes how to configure the components of the Sametime® Media Manager.
Enabling HTTP Connect Tunneling for audio and video calls
If you are enabling HTTP Connect Tunneling for audio and video calls, configure the Sametime® SIP Proxy/Registrar and the Sametime TURN Server to listen on port 443. Install them on separate computers. Also, ensure that no other applications are listening on port 443 to avoid port conflict.
Enabling HTTP Connect on the Sametime® Conference Manager
HTTP Connect is used for tunneling SIP and RTP (STUN) data through an HTTP Proxy Server. This feature is available only for the Sametime® web audio-visual plugin for browser-based clients. Enable the HTTP Connect setting by editing the stavconfig.xml file on the Conference Manager's deployment manager.

Enabling HTTP Connect on the Sametime Conference Manager

HTTP Connect is used for tunneling SIP and RTP (STUN) data through an HTTP Proxy Server. This feature is available only for the Sametime® web audio-visual plugin for browser-based clients. Enable the HTTP Connect setting by editing the stavconfig.xml file on the Conference Manager's deployment manager.

Procedure

On the server hosting the deployment manager for the Conference Manager, open the stavconfig.xml file for editing. The stavconfig.xml file path is:
The Sametime System Console is typically used as the deployment manager for the Conference Manager.
Install_root/config/cells/Cell_name/nodes/Node_name/servers/Server_name

For example,

/opt/IBM/WebSphere/AppServer/config/cells/bassMediaCell1/nodes/bassMediaNode1/servers/STMediaServer
Set the value for HTTPConnectEnabled to true.
For example,
<configuration lastUpdated="1226425838277" name="HTTPConnectEnabled" value="true"/>
Save and close the file.
If the Conference Manager is clustered, synchronize all nodes in the cluster.
1. In the deployment manager's Integrated Solutions Console, click System Administration > Nodes.
2. Click Full Resynchronize.
3. Restart the Conference Manager.