This is a cumulative hotfix that includes multiple fixes addressing issues including the following: meeting rooms not loading, slides not showing up in Connect viewers, missing call-in info, false disconnect messages, Video Chat Plug-in preview, Web AV issues with H.323 devices, web client performance, IOS detection, stuck pointers, Java detection issues, non-alphanumerics in polling questions, appshare viewers see gray screen.
This fix provides the following enhancements to IBM Sametime Meeting Server 8.5.2 Interim Feature Release 1 (IFR 1):
Empty File Content
With this fix installed, empty file content (e.g. slides in Sametime Connect, files in web browser) should no longer be handed to a client by the WebSphere Application server.
Missing Call-In Information
With this fix installed, call-in information will now be displayed from within the meeting room if available.
False Network Disconnection
With this fix installed, you should no longer see the "Unable to Connect to Sametime Server" dialog when in fact your client is able to communicate with the server.
Support for IBM Sametime Video Chat Plug-in for IBM Connections Technology Preview
With this fix installed, it is possible to use the IBM Sametime Video Chat Plug-in for IBM Connections Technology Preview with Sametime 8.5.2 IFR 1.
Sametime IOS client detection
With this fix installed, if you join a meeting room from an IOS mobile device, and you have the Sametime IOS mobile client installed, we will launch the mobile client; otherwise we will use the browser web UI for the meeting.
Web client meeting room performance improvements
Web AV dialout and Join with H323 devices
This fixed an issue where Web AV users were unable to dial H323 device using "Join call with telephone or vide device" and "Join with sip and video device" join call options.
Previously, if a client was sharing a pointer on a document, and then lost his connection, the pointer was "stuck" in the meeting unless the same user later went back into the meeting and shared a pointer again. Now the pointer is removed when the user leaves the meeting.
Java detection issues
Upgrading to Oracle JVM Java 7 update 4 or Java 6 update 33 or later caused the screen sharing Java detection to fail when attempting to share your screen in IE. This seemed to be an issue introduced by the upgraded Oracle plug-in or its interaction with IE. We found a workaround that corrects the issue, so you can now successfully share your screen with the latest versions of Java from Oracle.
Polling questions not displayed correctly
If you enter certain non-alphanumeric characters in a polling question or answer, they do not appear correctly in the New Poll dialog, the response dialog, the results dialog, or the discussion area when the results get posted. These characters, like < and &, were incorrectly being interpreted as HTML. These characters are now displayed correctly.
Appshare viewers see gray screen
When User A is sharing their screen, and User B starts sharing their screen using Let Me Share..., occasionally some users do not see the new share. They see a gray area where the shared screen should be, but they can see the cursor move. Leaving the meeting and coming back in resolves the problem. We fixed some timing issues on the server and in the web client to fix this intermittent problem.
Prerequisite: The Sametime System Console must be at version 8.5.2 IFR 1. If not, then you will see a failure message during the fix install noting an incorrect version level. Refer to Installing Sametime 8.5.2 Interim Feature Release 1 on the Sametime System Console to get started.
This fix must be installed on top of a Sametime Meeting Server 8.5.2 Interim Feature Release 1 (IFR 1). If the server is running 8.5.2 (without the IFR 1 update), then the IFR 1 update will be automatically installed.
To install this fix on a Sametime Meeting Server node, follow these steps:
- Download the fix JJON-92FQZX from IBM Fix Central.
- Shut down the Sametime Meeting Server.
- Copy the file you downloaded onto the Sametime Meeting Server.
- Extract the file on the server file system.
- Apply the fix by running the appropriate update command:
- If running on the Microsoft Windows operating system, run the update.bat batch file.
- If running on the AIX, Linux, or Solaris operating systems, run the update.sh script.
6. Follow the instructions on-screen until the installation completes.
If you are running a multi-node (cluster) configuration, then repeat these instructions on each node.