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 SIP Proxy/Registrar separately
Install the IBM® Sametime® Media Manager's SIP Proxy/Registrar on its own computer. Installing a separate SIP Proxy/Registrar gives you the option of installing additional instances of the same server later, and then clustering them for high availability and failover. This option requires that you created a deployment plan using the Install SIP Proxy/Registrar option. You must also have created all other deployment plans for Media Manager components you plan to install separately.
Verifying a SIP Proxy/Registrar virtual host on a stand-alone server
Confirm that the ports used by the SIP Proxy/Registrar, part of the IBM® Sametime® Media Manager, are defined correctly for the sip_proxyreg_host virtual host. The virtual host must be correct after you can federate a primary node into the Sametime System Console.

Verifying a SIP Proxy/Registrar virtual host on a stand-alone server

Confirm that the ports used by the SIP Proxy/Registrar, part of the IBM® Sametime® Media Manager, are defined correctly for the sip_proxyreg_host virtual host. The virtual host must be correct after you can federate a primary node into the Sametime System Console.

About this task

Perform this task on a stand-alone SIP Proxy/Registrar. If you intend to cluster SIP Proxy/Registrars, skip this task.

Procedure

Log in to the Sametime System Console.
In the navigation tree, click Servers > Server Types > WebSphere application servers.
On the Status page, click the link for the server hosting the SIP Proxy/Registrar.
On the Configuration page, locate the Communications section, and then click on Ports.
In the Ports table, locate these ports and write down their port values.
- SIP_ProxyRegHOST
- SIP_ProxyReg_SECURE
- WC_defaulthost
In the navigation tree, click Environment > Virtual Hosts.
In the Virtual Hosts table, click sip_proxyreg_host.
In the Configuration page, look in the "Additional Properties" section and click Host Aliases.
Verify that the Host Aliases table contains only the three entries listed in step 5, (with * as the Host Name and the value you determined earlier from the Ports table). Delete all other entries.
Save the changes to the master configuration.
Log out of the Integrated Solutions Console.