After you create clusters of IBM
® Sametime Media Manager Conference Manager components and SIP Proxy and Registrar components, configure the Conference Manager cluster to work with the IBM WebSphere
® proxy server that is used by the SIP Proxy and Registrar cluster (so that the two clusters share the proxy server).
Before you begin
Create and configure the Conference Manager and SIP Proxy and Registrar clusters.
About this task
By default, a Conference Manager is configured to access the SIP Proxy and Registrar component directly, and must be reconfigured to communicate with a cluster. Modify the Conference Manager's stavconfig.xml
file to access the WebSphere
proxy server used by the SIP Proxy Registrar cluster. The WebSphere
proxy server will direct SIP requests to available nodes in the cluster. Complete this task for every Conference Manager in the cluster.
Parent topic: Configuring the Conference Manager cluster
Next topic: Restarting and synchronizing nodes in the Conference Manager cluster
- On the server that is being used as the Deployment Manager, open the stavconfig.xml file for editing.
is located at:
- Modify the following settings:
|SIPProxyServerHost||Use the host name of the computer where the WebSphere proxy server is installed for the SIP Proxy and Registrar cluster.|
|SIPProxyServerPort||Use the PROXY_SIPS_ADDRESS port value of the same WebSphere proxy server (used by the SIP Proxy and Registrar cluster).|
<configuration lastUpdated="1226425838277" name="SIPProxyServerHost"
<configuration lastUpdated="1226425838277" name="SIPProxyServerPort" value="5080"/>
- Save and close the file.
- Repeat for every Conference Manager in the cluster.