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.
Configuring anonymous authentication in the SIP Proxy/Registrar
If you want users to participate in audio and video conferences anonymously through their Sametime® browser clients, you must enable anonymous authentication on the SIP Proxy/Registrar.
Enabling anonymous authentication through the Trust Association Interceptor
WebSphere® Application Server requires the anonymous Trust Association Interceptor (TAI) to be enabled to allow access to anonymous Sametime® browser clients using audio-visual features.

Enabling anonymous authentication through the Trust Association Interceptor

WebSphere® Application Server requires the anonymous Trust Association Interceptor (TAI) to be enabled to allow access to anonymous Sametime® browser clients using audio-visual features.

About this task

Use this procedure to enable anonymous authentication with SIP (not secure). If you are using SIPS, set enable.anonymous.token.auth.tai to true by completing the procedure Adding Trust Association properties to enable anonymous authentication.

Procedure

Log in to the Integrated Solutions Console for the SIP Proxy/Registrar.
Click Security > Global security.
Click Web and SIP security > Trust association.
In the "Additional Properties" section, click Interceptors.
Click com.ibm.sip.auth.AnonymousAuthTAI.
Find the custom property anonymous.user.id. Add the property if it does not exist.
For its value, use the same anonymous user ID that you mapped to the anonymous security role for the SIP Proxy/Registrar (for example, anonymous@example.com).
Find the custom property enable.anonymous.auth.tai. Set the value to true to enable anonymous authentication.
Click Apply and then Save.
Restart all WebSphere Application Server processes.