Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved caveats
Cisco TelePresence Video Communication Server X7.2.2 Software Release Notes
Page 18 of 50
Resolved caveats
The following issues were found in previous releases and were resolved in X7.n.
Resolved in X7.2.2
Identifier
Summary
CSCue41065
Symptoms: Data loss on upgrades, typically X7.1 -> X7.2.1. Typically lost data is NTP, DNS,
Admin Accounts, TimeZone, and all but two Option Keys.
Conditions: Upgrading to X7.2.1.
Workaround: Reboot into the previous image, and try the upgrade again.
Admin Accounts, TimeZone, and all but two Option Keys.
Conditions: Upgrading to X7.2.1.
Workaround: Reboot into the previous image, and try the upgrade again.
CSCue41164
Symptoms: Time synchronization problems and the raising of NTP server-related alarms.
Conditions: Only applies when running as a Virtual Machine.
Workaround: Configure the VMware host and the VCS with the same NTP server.
Conditions: Only applies when running as a Virtual Machine.
Workaround: Configure the VMware host and the VCS with the same NTP server.
CSCub63112
Symptoms: Calls to TelePresence Conductor fail. Error message on the Conductor policy
service page on the VCS is:
"Failed: SSL connect error. Last connection attempt: 2012-06-11 14:38:04 "
Conditions: Non AES VCS attempting to communicate with a Conductor
Workaround: None.
service page on the VCS is:
"Failed: SSL connect error. Last connection attempt: 2012-06-11 14:38:04 "
Conditions: Non AES VCS attempting to communicate with a Conductor
Workaround: None.
CSCub42318
Symptoms: A VCS will see slowly climbing memory usage, eventually seeing the swap
partition be used and performance drop, and occasionally crashes due to delayed database
access.
Conditions: This only affects clustered VCSs that are doing millions of searches.
Workaround: Monitor memory usage by doing the following as root:
partition be used and performance drop, and occasionally crashes due to delayed database
access.
Conditions: This only affects clustered VCSs that are doing millions of searches.
Workaround: Monitor memory usage by doing the following as root:
cat /proc/meminfo | grep Committed_AS
If usage exceeds 4.5GB, the VCS should be rebooted.
If usage exceeds 4.5GB, the VCS should be rebooted.
CSCuc13370
Symptoms: Event Log does not respect the value set under Maintenance > Logging > Log
Level on the web in X7.2. It always defaults to level 1, the least verbose. This means when
selecting "View all events associated with this call" hyperlink for a call, less detail is displayed
than expected.
Conditions: Seen with Cisco VCS running X7.2. X7.1 and previous versions of VCS
software are not affected by this issue.
Workaround: None.
Level on the web in X7.2. It always defaults to level 1, the least verbose. This means when
selecting "View all events associated with this call" hyperlink for a call, less detail is displayed
than expected.
Conditions: Seen with Cisco VCS running X7.2. X7.1 and previous versions of VCS
software are not affected by this issue.
Workaround: None.
CSCuc40064
Symptom: VCS B2BUA does not advertise the maximum bit rate correctly for CIF and QCIF.
When CIF (2500) and QCIF (1800) are being signaled, the maxbr is set to 1800 (meaning the
ability to receive 250 kbps for CIF has disappeared).
Conditions: VCS B2BUA in use for Lync integration.
Workaround: None.
When CIF (2500) and QCIF (1800) are being signaled, the maxbr is set to 1800 (meaning the
ability to receive 250 kbps for CIF has disappeared).
Conditions: VCS B2BUA in use for Lync integration.
Workaround: None.
CSCuc75149
Symptoms: Call from Lync to Polycom HDX registered on H323 fails.
Conditions: In the case of a Lync to H323 call, the SimultaneousCapabilities in the TCS do
not match provided capability in the table, leading to the call failing to a Polycom HDX
endpoint.
Workaround: None, however calls from HDX to Lync work as expected.
Additional information: This is caused by incorrect entries in the AlternativeCapabilitySet in
the TerminalCapabilitySet sent by the VCS.
Conditions: In the case of a Lync to H323 call, the SimultaneousCapabilities in the TCS do
not match provided capability in the table, leading to the call failing to a Polycom HDX
endpoint.
Workaround: None, however calls from HDX to Lync work as expected.
Additional information: This is caused by incorrect entries in the AlternativeCapabilitySet in
the TerminalCapabilitySet sent by the VCS.
CSCuc98344
Symptoms: The Subzones page on VCS does not show all subzones, and is missing all
buttons on the lower part of the page.
Conditions: This can be seen if the VCS has a high number of subzones combined with a
high number of calls and/or registrations associated with these subzones. In addition, the
Apache error.log file may show entries similar to:
PHP Fatal error: Maximum execution time of 30 seconds exceeded in
/share/web/lib/statusadaptationlayer.php on line 199
buttons on the lower part of the page.
Conditions: This can be seen if the VCS has a high number of subzones combined with a
high number of calls and/or registrations associated with these subzones. In addition, the
Apache error.log file may show entries similar to:
PHP Fatal error: Maximum execution time of 30 seconds exceeded in
/share/web/lib/statusadaptationlayer.php on line 199