Sametime 8.5.2 Interim Feature Release 1 now includes a Tech Preview of the screen sharing feature for the Web Meetings Client on Mac OS X.

The counter for the specified log category has crossed the defined threshold.

The Solid database was restarted.

The specified process encountered a partial (or severe) initialization failure. If severe, it cannot continue.

In an IBM® Sametime® Unified Telephony deployment, the Telephony Control Servers and the Telephony Application Servers are administered from the CMP (Common Management Portal). The CMP is located on the Telephony Application Server and must be configured to communicate with the Telephony Control ...

The counter for the specified log category has crossed the defined threshold.

The swap space use has changed, but it is still above one of the configured thresholds.

Configured ticket pool disk partition is full.

Use Tivoli® System Automation for Multiplatforms to manage failover in IBM® Sametime® Unified Telephony.

The number of currently used semaphores is relatively high. Semaphore use checks are done periodically by audit and if this is a temporary situation which no longer exists during the next check cycle, a clearing event will be issued.

The Solid database is from an older version of Solid.

The available space in a file system is the space usable by nonsuperuser. The rest of the space is either used or reserved for superuser. Refer to man page df(1). The available space in a database depends on the type of database.

The named process is currently not running.

By default, a Media Server is installed on each Telephony Application Server within the IBM® Sametime® Unified Telephony deployment. You can optionally install one or more offboard Media Servers to improve performance.

IBM Tivoli® Directory Integrator (TDI) synchronizes and exchanges information between applications and directory sources. You use it to initially provision the IBM Sametime® Unified Telephony subscriber database on the Telephony Application Server with users from a source LDAP system, and keep the ...

The link to the backup FTP site from the usage collection server is down

This section describes how to monitor, provision, and update your IBM® Sametime® Unified Telephony environment.

Reports that the counter values has exceeded a defined threshold limit.

In an IBM Sametime Unified Telephony deployment, initialize a Telephony Application Server's persistent cache in chunks by resolving a specified number of user names at a time.

This topic is an overview of the steps necessary to configure a dialing plan.

Create one or more endpoints in an IBM® Sametime® Unified Telephony deployment.

Define an endpoint to connect IBM® Sametime® Unified Telephony to a customer’s PBX or gateway.

The license count is different between the two nodes of the cluster for the type identified by faulty Object.

Sametime® Unified Telephony deployment on a nonIP PBX is the simplest Sametime Unified Telephony installation. It requires that calls are intercepted between the PBX and the desk phone.

In an IBM® Sametime® Unified Telephony deployment, initialize a Telephony Application Server's persistent cache using the Java™ Toolkit CachedResolveBatchMode application.