Introduction

The clustering of Lotus Sametime Media Manager 8.5.1 components involve many details that if overlooked or missed may cause different types of errors within the media manager components and the Lotus Sametime 8.5.1 client. This document provides a simple checklist for creating and properly configuring media manager cluster environment and it must be used in conjunction with the Sametime info center which covers the clustering setup in full detail.

The cluster deployment scenario described in this article should only be taken as a reference for understanding the configuration steps. Depending upon your organization's needs you should perform proper sizing and then start deploying the Media Manager cluster.

Cluster scenario

Ideally you should use separate machines for every Media Manager component but you can still create a media manager cluster environment using at least two machines. machine1 and machine2. On machine1 you will have the Conference Manager and SIP Proxy/Registrar primary nodes, WebSphere Proxy for SIP Proxy Registrar cluster and the first Packet Switcher and on machine2 you will have the Conference Manager and SIP Proxy/Registrar secondary nodes, WebSphere Proxy for Conference Manager cluster and a second Packet Switcher.

Proxy/Registrar cluster setup

1. In Sametime System Console create a deployment plan for 'Media Manager - Proxy/Registrar' with Primary Node option for machine1.
2. Also create a deployment plan for 'Media Manager - Proxy/Registrar' with Secondary Node option for machine2.
3. Install Proxy/Registrars on both machines.
4. Run the cluster guided activity from SSC for Media Manager - Proxy Registrar and select SSC deployment manager as the DM of the cluster
5. From SSC integrated solutions console, create a WAS proxy server for the Proxy Registrar cluster on the primary node. In the 'SIP Proxy Server Settings > SIP proxy settings' section of the WAS proxy set the "Default cluster" field to use the SIP PR cluster.
6. In SSC integrated solutions console go to Environment->Virtual Hosts->sip_proxyreg_host->Host Aliases and verify that it contains the SIP/SIPS ports used by each cluster member and also by the WAS proxy. You must delete all the hostnames which use a FQDN, there should only be hostnames with * as their name.
7. Start the Proxy Registrar cluster and its associated WAS proxy from SSC integrated solutions console.

Conference Manager cluster setup

1. In Sametime System Console create a deployment plan for 'Media Manager - Conference Manager' with Primary Node option for machine1.
2. Also create a deployment plan for 'Media Manager - Conference Manager' with Secondary Node option for machine2.
3. Install Conference Managers on both machines.
4. Run the cluster guided activity from SSC for Media Manager - Conference Manager and select SSC deployment manager as the DM of the cluster
5. From SSC integrated solutions console, create a WAS proxy server for the Conference Manager cluster on the secondary node. In the 'SIP Proxy Server Settings > SIP proxy settings' section of the WAS proxy set the "Default cluster" field to use the CM cluster.
6. Again in SSC integrated solutions console go to Environment->Virtual Hosts->default_host->Host Aliases and verify that it contains the SIP/SIPS ports used by each cluster member and also by the WAS proxy. You must delete all the SIP/SIPS port entries where the hostnames contains a FQDN, these ports should only have hostnames with * as their name.
7. Modify the SIPProxyServerHost and SIPProxyServerPort values in the stavconfig.xml file under the DM profile for each Conference Manager node so that they points to the WAS proxy host/port of the Proxy Registrar. Make sure that you use the PROXY_SIPS_ADDRESS port value of the WAS Proxy.
8. Add the IP addresses of Conference Manager primary and secondary nodes in the community server's trusted IP list.
9. Start the Conference Manager cluster and its WAS proxy from SSC integrated solutions console.

Packet Switcher cluster setup

1. In Sametime System Console create a deployment plan for 'Media Manager - Packet Switcher' with Primary Node option for machine1.
2. Also create a deployment plan for 'Media Manager - Packet Switcher' with Primary Node option for machine2.
2. Install the Packet Switcher on both machine
3. Modify the stavconfig.xml file on the Packet Switcher so that its SIPProxyServerHost and SIPProxyServerPort values point to the WAS proxy host/port of the Proxy Registrar and its ConferenceServerHost and ConferenceServerPort values point to the WAS proxy host/port of the Conference Manager. Make sue that you use the PROXY_SIPS_ADDRESS port value of the WAS Proxy.
4. Restart both Packet Switcher servers

Security configuration

1. Extract the certificate from one server's store type and add it to another server's store type, see details below and also consult info center for detailed steps.

Extract Certificate From	Store Type To Use	Add Certificate To	Store Type To Use
WAS Proxy for Proxy Registrar cluster	NodeDefaultKeyStore	Conference Manager	CellDefaultTrustStore and NodeDefaultTrustStore
WAS Proxy for Proxy Registrar cluster	NodeDefaultKeyStore	Packet Switcher	NodeDefaultTrustStore
WAS Proxy for Proxy Conference Manager	NodeDefaultKeyStore	WAS Proxy for Proxy Registrar cluster	CellDefaultTrustStore and NodeDefaultTrustStore
Packet Switcher	NodeDefaultKeyStore	WAS Proxy for Proxy Registrar cluster	CellDefaultTrustStore and NodeDefaultTrustStore
WAS Proxy for Proxy Conference Manager	NodeDefaultKeyStore	Packet Switcher	NodeDefaultTrustStore

2. Create a trusted IP custom property on both Proxy/Registrar servers and add the host name or IP of each machine where the Conference Manager and Packet Switcher are installed.
3. Restart all server in this order: 1. Proxy Registrar cluster 2. WAS Proxy of Proxy Registrar cluster 3. Conference Manager cluster 4. WAS Proxy of Conference Manager cluster 5. Packet Switcher.
4. You can verify the status of the servers using these URLs:
http://hostname:9080/stav/PacketSwitchStatus.jsp|http://hostname:9080/stav/PacketSwitchStatus.jsp">http://hostname:9080/stav/PacketSwitchStatus.jsp">http://hostname:9080/stav/PacketSwitchStatus.jsp|http://hostname:9080/stav/PacketSwitchStatus.jsp
http://hostname:9080/Registrar/RegistrationsTable.jsp|http://hostname:9080/Registrar/RegistrationsTable.jsp">http://hostname:9080/Registrar/RegistrationsTable.jsp">http://hostname:9080/Registrar/RegistrationsTable.jsp|http://hostname:9080/Registrar/RegistrationsTable.jsp
http://hostname:9080/ConferenceFocus/ConferenceFocusStatus|http://hostname:9080/ConferenceFocus/ConferenceFocusStatus">http://hostname:9080/ConferenceFocus/ConferenceFocusStatus">http://hostname:9080/ConferenceFocus/ConferenceFocusStatus|http://hostname:9080/ConferenceFocus/ConferenceFocusStatus
If you cant access these pages then make sure you are using the correct port. Check the value of WC_defaulthost port in the server for which you are trying to access the page and ensure that it is also listed in the virtual hosts.

Common Issues

Conference Manager and/or Packet Switcher logs show SIP timeout and other errors during SIP registration

See if any of the following fixes this problem
1. An incorrect SIP port of the WAS proxy of SIP Proxy/Registrar cluster may have been used in the stavconfig.xml files on the Conference Manager and Packet Switcher. Please note that the Proxy/Registrar doesn't use stavconfig.xml so you don't need to modify it on Proxy/Registrar. Verify that you have used the correct SIP port, if you are using TLS as the SIP transport protocol then you must use the PROXY_SIPS_ADDRESS port of the WAS proxy otherwise use the PROXY_SIP_ADDRESS port.
2. In the 'SIP Proxy Server Settings > SIP proxy settings' section of the Proxy/Registrar WAS proxy verify that the "Default cluster" field is set to use the PR cluster.
3. Verify that the ports are not blocked by the firewall.

SIP 401 errors in Conference Manager and/or Packet Switcher logs during SIP registration

Check the com.ibm.ws.sip.security.trusted.iplist custom property on Proxy/Registrar server and verify that it contains the IP address of the Conference manager and Packet Switcher machines.

An 'SECJ0128E: An unexpected exception occurred during Trust Association. The exception is java.lang.NullPointerException' exception occurs in the Media Manager logs

If you get this exception then you need to add this custom property in each of the STMediaServer of Conference Manager, Proxy/Registrar and Packet Switcher servers and restart them.

Name	Value
com.ibm.ws.sip.security.enable.digest.tai	false

Telephony icon is disabled in Lotus Notes Sametime embedded 8.5.1 client but its enabled in the Sametime Standard 8.5.1 client

1. From 'Manage policies' link on SSC, select 'Sametime Instant Messaging Default Policy' option inside the 'Instant Messaging' tab and verify that the 'Allow all Sametime Connect features to be used with integrated clients (IC)' is enabled. If not, then enable it and save the settings and restart the community server.
2. If the client error-log file show 'No trusted certificate found' warning then it probably means that the Notes client has rejected the server certificate because there was a mismatch between the issuer name and the SIP Proxy/Registrar hostname where the client wanted to open a TLS connection. To resolve this you need to make sure that all of the machines where SIP Proxy/Registrar cluster is installed are configured to use a single hostname.

	Table	Heading
a	Table	Row
b	Table	Row