Preventing the Media Manager from connecting to specific Community Servers
If the Sametime® Media Manager is deployed in an environment containing a cluster of Sametime Community Servers where one or more Community Servers are not configured to accept connections from the Media Manager, you can blacklist those Community Servers to prevent inadvertent connection errors.
About this task
Audio and video features in Sametime will not function unless the Media Manager can successfully connect to all Community Servers of which it is aware. In some situations, your Sametime deployment might include a cluster of Community Servers where some of those servers do not accept connections from the Media Manager. If the Media Manager attempts a connection it will fail and audio/video services will not be available to users. You can prevent these inadvertent connection attempts by blacklisting the unavailable Community Servers.
For example, suppose you configure the Media Manager to connect to a Community Server cluster (specified in the stavconfig.xml file) and the Media Manager successfully connects to a particular Community Server. The connected Community Server's own names.nsf file resolves other Community Servers through the primary names.nsf and da.nsf files, and informs the Media Manager that there are additional Community Servers within the community. The Media Manager automatically attempts to connect to those additional Community Servers but fails for any Community Server that is not configured to accept the connection.
When this happens, users may see the green telephone icon when they start their Sametime client and connect to a community, but the icon will turn gray when a Community Server connection fails, and that user will not have access to audio and video features.
[4/19/11 16:08:45:006 EDT] 0000003c ServerManager >
com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
ENTRY Logged out from: Fully_qualified_Community_Server_Name due to ST
reason: -2147483129, desc: ST_CONNECT_HOST_UNREACHABLE, event:
com.lotus.sametime.community.LoginEvent Id: 80000002
[4/19/11 16:08:45:006 EDT] 0000003c ClusterManage 3
com.lotus.sametime.telephonymanager.cluster.ClusterManager
serverLoggedOut Server name: Fully_qualified_Community_Server_Name,
Server URL: NotAParticipatingCommServer, reason: -2147483129
[4/19/11 16:08:45:006 EDT] 0000003c ServerManager W
com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
reason = 80000207
[4/19/11 16:09:47:084 EDT] 00000045 ServerManager >
com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
ENTRY Logged out from: Fully_qualified_Community_Server_Name due to ST
reason: -2147483108, desc: ST_CONNECT_NOT_PRIVILEGED, event:
com.lotus.sametime.community.LoginEvent Id: 80000002
To prevent the Media Manager from attempting to connect to unavailable Community Servers, create a blacklist file listing the Community Servers to avoid, and store it on the server hosting the Sametime Conference Manager component as explained.