After you create clusters of Sametime® Media Manager Conference
Manager components and SIP Proxy/Registrar components, configure the
Conference Manager cluster to work with the WebSphere® proxy server that is used by
the SIP Proxy/Registrar cluster (so that the two clusters share the
proxy server).
Before you begin
Create and configure the Conference Manager and SIP Proxy/Registrar
clusters.
About this task
By default, a Conference Manager is configured to access
the SIP Proxy/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.
Procedure
- On the server that is being used as the deployment manager,
open the
stavconfig.xml file for editing.The stavconfig.xml is
located at:
dm_install_root/config/cells/cell_name/nodes/node_name/servers/server_name
For
example:
config/cells/bassMediaCell1/nodes/bassMediaNode1/servers/STMediaServer
- Modify the following settings:
| Option | Description |
|---|
| SIPProxyServerHost |
Do one of these according to your configuration:
- Use the host name of the computer where the WebSphere proxy server is installed for
the SIP Proxy/Registrar cluster.
- If your configuration includes multiple WebSphere proxy servers
behind a load balancer, use the cluster address which points to the
WebSphere proxy servers.
|
| SIPProxyServerPort |
If you are using TLS, use the PROXY_SIPS_ADDRESS port value
of the same WebSphere proxy
server (used by the SIP Proxy/Registrar cluster). If you are using
TCP, use the PROXY_SIP_ADDRESS port value of the same WebSphere proxy server (used by the SIP
Proxy/Registrar cluster). If you deployed a load balancer in
front of the SIP Proxy/Registrar cluster, use the load balancer's
host name and port. |
For example:
<configuration lastUpdated="1226425838277" name="SIPProxyServerHost"
value="wasproxy_pr.acme.com"/>
<configuration lastUpdated="1226425838277" name="SIPProxyServerPort" value="5080"/>
- Save and close the file.
- Repeat for every Conference Manager in the cluster.