TMS CCC and JAVA - Clarification

[Jescobar27]

I have looked through the forums enough to know that TMS is VERY picky about the version of Java installed on the local machine used to acess the Conference Control Center.

Is there a definitive guide to which versions of Java work with which versions of TMS and/or how multiple Java installations might affect this delicate balance? We have had Hell keeping Java updated while also ensuring that we are able to access TMS. Also, in your personal experiences, which browsers do you find work best with TMs?

We run TMS 13.2.1 and usually access the CCC from Windows 7 x64 machines. Any assistance/clarification would be much appreciated.

[mahkrish · Accepted solution]

Hi Juan,

The problem was corrected on the TMS side in 13.2.2. This was due to BUG # CSCub01168.

Below is the snippet of BUG # CSCub01168.

[Java 7 introduced a defect (Java bug ID 6997116) which caused conferences in Conference  Control Center  not to load.

This was partly fixed in Java 7 update 7, but there were still image loading issues that have now  been resolved with a Java rendering function change in Cisco TMS

See here for the 13.2.2 software installation package, and here for the release notes.

TMS is only tested with IE and Firefox.

Please refer to the TMS 14.1 installation guide.

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/install_guide/Cisco_TMS_install_guide_14-1.pdf

BR/Mahesh Adithiyha

[Kjetil Ree]

Hi,

There are other Java issues as well in addition to what Mahesh mentions. See CSCug37698, fixed in TMS 14.2. The new problems seem to have been introduced around Java 7 update 11.

My favorite browser for the CCC (highly subjective): Chrome.

Regards,

Kjetil

[Magnus Ohm]

Hi Juan

TMS 14.2 is now released and is available on Cisco.com

/Magnus

[Jescobar27]

The response is much appreciated. We will find time to upgrade in the near future.

[Jescobar27]

Thank you for your response. It seems that we need to get with the times to eliminate some of these headaches. We often deploy new Java updates to help avoid vulnerabilities, which often breaks our TMS access. It helps to know that this is a known issue with our version.