Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
■
If using Java JRE version 6, update 15 or later, you will need to de-select Enable the next generation Java plug-
in… under Advanced on the Java Control Panel to make the Graphic Monitor work as expected.
in… under Advanced on the Java Control Panel to make the Graphic Monitor work as expected.
Quicker Load of Monitor
When Cisco TMS is upgraded, users may experience that loading of
Conference Control Center
and
Graphical Monitor
are slowed down. This is caused by old versions of the .jar files in the Java Applet cache.
To fix the problem;
1.
Open the Java Control Panel (in your computer's Control Panel)
2.
Click the
General
tab.
3.
Click View...
4.
Go to
Temporary Internet Files
.
5.
Delete files with extension .jar.
Out of Memory
Depending on the number of systems in your Cisco TMS installation and the number of ongoing conferences, users
might experience memory problems with
might experience memory problems with
Conference Control Center
or
Graphical Monitor
. The reason for this is that
Java Applets as a default are only allowed to use 64 MB of memory. If you are having problems with out of memory
exceptions you will experience that the Applets might ‘hang' or seem very slow and find traces of
exceptions you will experience that the Applets might ‘hang' or seem very slow and find traces of
OutOfMemory
excep-
tions in the
Sun Java Console
found under the
Tools
menu in Internet Explorer. To avoid the problem you can increase
the maximum amount of memory these Applets can use.
Increase Maximum Amount of Memory
Open the
Java Control Panel
(in your computer's Control Panel), click the
Java
tab and click
View…
on the
Java Applet
Runtime Settings
. The
Java Runtime Settings
will show you the runtime versions currently installed on your machine.
Find the most recent 'Version' and add –
Xmx256
to the
Java Runtime Parameters
box (see screenshot below). This will
increase the maximum amount of memory the Applets can use from the default value of 64 MB to a maximum of 256 MB.
You can of course change the value to any amount you see fit.
You can of course change the value to any amount you see fit.
Phone Book Scenarios
This section covers troubleshooting scenarios related to Cisco TMS phone books as they may present both client-side
and in Cisco TMS.
and in Cisco TMS.
Phone Book (Corporate Directory) Errors
Message
Explanation or suggested solution
Table 175 Possible errors displayed on endpoint due to problems with corporate directory
278
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting