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.
Deploying an IBM® SIP Edge Proxy server to support audio and video in the extranet
The IBM® SIP Edge Proxy server is a SIP application installed over an IBM WebSphere® Application Server. Since there is no specific installer for the IBM SIP Edge Proxy server, you use the IBM Sametime® Media Manager's SIP Proxy/Registrar installer, and then perform manual steps to configure the IBM SIP Edge Proxy server. Read the system requirements to ensure that you know the minimum supported software requirements.
Installing the IBM® SIP Edge Proxy Server in a cluster
To install the IBM® SIP Edge Proxy Server, complete the following tasks.
Installing an IBM® SIP Edge Proxy server
You cannot install an IBM® SIP Edge Proxy server directly onto a computer because there is no package called IBM SIP Edge Proxy server. Instead, you first install a Sametime® SIP Proxy/Registrar, and then you remove the Sametime functionality from the server. You can then install the IBM SIP Edge Proxy server onto that computer.
Setting custom properties for the primary or secondary node
Complete this task for each server in the cluster.

Setting custom properties for the primary or secondary node

Complete this task for each server in the cluster.

Procedure

In the WebSphere® Integrated Solutions Console, log in as the WebSphere administrator to the deployment manager that manages the IBM® SIP Edge Proxy Server.
Browse to Servers > Clusters > WebSphere application server clusters.
Click the SIP Edge proxy server cluster that you created in the previous section.
In the Additional Properties section, click Cluster members.
Select the cluster member being updated.
In the Container settings section, click SIP Container Settings > SIP Container.
In the Additional Properties section, click Custom properties.
Make sure that the property com.ibm.ws.sip.sent.by.host is set to the IP/FQDN of the computer running the cluster member you selected in Step 5. Update the custom property if required and save the changes to the master repository.
If you are setting custom properties on the first (primary) node, continue to the next step. If you are setting custom properties on secondary nodes, this task is complete.
If you are setting custom properties on the first node, go back to the custom properties panel and remove the com.ibm.ws.sip.security.trusted.iplist custom property. Click OK and save the changes to the master repository.