 Feedback
|
Table Of Contents
Release Notes for Cisco TelePresence Recording Server, Release 1.6.x
Cisco TelePresence Software Compatibility Matrix
New and Changed Information in CTRS Release 1.6.3
New and Changed Information in CTRS Release 1.6.2
New and Changed Information in CTRS Release 1.6.1
Caveats for CTRS Release 1.6.x
CTRS Release 1.6.x Caveat Reference
Open Caveats for CTRS Release 1.6.x
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco TelePresence Recording Server, Release 1.6.x
Created: November 13, 2009Revised: February 22, 2011 OL-19548-04Contents
•
Cisco TelePresence Software Compatibility Matrix
•
•
•
•
•
Introduction
Release 1.6.0 is the first release of the Cisco TelePresence Recording Server (CTRS). CTRS allows users to do the following:
•
•
•
•
•
•
•
CTRS enables users to record in TelePresence Studio Mode. In Studio Mode, users can create team announcements, corporate messages, training modules, video blogs, and other similar recordings.
To record, users must have access to a CTS with CTRS functionality; they control recording through the CTS IP phone interface.
All recordings are HD video and audio. All recorded content, including materials that users choose to display on a device that is connected to the VGA input or through a document camera, is shown on the TelePresence monitor from the viewer's perspective. CTRS acts as a viewer endpoint in a TelePresence session and records what it sees.
Users can then share a recording by sending it to a recipient's e-mail address. To play a recording, the recipient must sign in to the CTRS browser-based end-user portal with a corporate username and password (LDAP username and password). If the recipient wants to play a recording on a TelePresence display, he or she must sign in to CTRS through the CTS IP phone user interface with a corporate username and personal identification number (PIN).
The CTRS requires an administrative user, who manages CTRS configuration and maintenance.
Cisco TelePresence Software Compatibility Matrix
For Cisco TelePresence software compatibility information, refer to the information located at the following URL:
http://www.cisco.com/en/US/products/ps8332/products_device_support_tables_list.html
Documentation Errata
Replacing a Hard Disk Drive
This section describes how to replace a hard disk drive in a Cisco MCS-7845-Ix server on which CTRS software is running.
Caution
Step 1
A backup of the CTRS configuration data may be needed if the scenario described in step 6 occurs. If this scenario occurs, the CTRS configuration data cannot be restored from a backup of the full system data, so make sure to perform a backup of the CTRS configuration data only.
Step 2
Step 3
Step 4
Step 5
Step 6
For complete information on how to install the software, see the Cisco TelePresence Recording Server Administration Guide at this location:
http://www.cisco.com/en/US/products/ps10341/prod_maintenance_guides_list.html
Step 7
Step 8
New and Changed Information in CTRS Release 1.6.3
The following caveats were fixed in CTRS Release 1.6.3:
•
•
•
New and Changed Information in CTRS Release 1.6.2
The following caveats were fixed in CTRS Release 1.6.2:
•
•
•
•
•
•
•
•
•
•
•
New and Changed Information in CTRS Release 1.6.1
The following caveats were fixed in CTRS Release 1.6.1:
•
•
•
•
Caveats for CTRS Release 1.6.x
Caveats were recorded in the following CTRS Release 1.6.x releases:
•
•
CTRS Release 1.6.x Caveat Reference
Table 1 summarizes caveats found in CTRS Release 1.6.x.
Open Caveats for CTRS Release 1.6.x
•
Symptom: During playback, if the user skips forward to the end of the recording, the progress bar goes to end and then restarts from beginning of the recording. The recording then plays back for 8 or 9 seconds. Also, the timer above the progress bar does not reflect the time accurately if when skipping quickly without 2 seconds between each skip.
Conditions: This symptom is seen when the user skips forward in a recording.
Workaround: None.
•
Symptom: Audio/video synchronization issues seen on CTS.
Conditions: If there is severe network impairment to only the audio or video port but not both, the CTS does not always recover from audio/video synchronization issues.
Workaround: Attempt playback when network conditions improve.
•
Symptom: Patch file cannot be seen.
Conditions: Usually occurs when downloading the patch file to a destination in which a file of the same name already exists.
Workaround: Rename the file, or delete the duplicate one with "[]."
•
Symptom: Second viewer sees what the first viewer saw after signout.
Conditions: The first viewer signs in to the end-user portal. The first viewer shares one of his/her videos with second viewer. The first viewer then signs out, and the second viewer signs in on the same computer. The second viewer can still sees the first viewer's last viewed page.
Workaround: None.
•
Symptom: CTRS uses LDAP library in CTS-Man, which is used to authenticate individual users who want to sign in to CTRS via LDAP. Group aliases should not be validated against LDAP servers.
Conditions: A user tries to share a recording with an e-mail alias.
Workaround: Do no share recordings with e-mail aliases.
•
Symptom: The user might not timeout right away when exiting UI. User times out a minute or so later.
Conditions: If the user configures the CTRS to sign out after "five minutes of inactivity" (User Portal User Preferences) but then immediately signs out, the user sees this symptom. [
Workaround: None.
•
Symptom: The user provides a description for a recording, but then the description field says, "No description provided."
Conditions: The user adds a long title (130 characters) and a short description to a recording. When the user launches the end-user portal, the description field says "No description provided." The administrative user interface shows both the title and description correctly.
Workaround: None.
•
Symptom: Admin user interface shows 500 Error.
Conditions: After changing the hostname, this problem occurs intermittently.
Workaround: Reboot the CTRS.
•
Symptom: In System Backup/Restore and Export Media files in the admin user interface, an error message is displayed when the admin schedules a weekly backup/restore or export with multiple weekdays selected or with only Sunday selected. The schedule is not triggered for the weekly setting with multiple weekdays checked or if only Sunday checked.
Conditions: This symptom is seen in Release 1.6.0.
Workaround: Set a daily schedule, or set a weekly schedule with only one weekday selected (but do not select Sunday).
•
Symptom: After importing a recording that includes presentation files, you notice that the presentation was not imported into the CTRS server.
Conditions: This issue can occur if the import was performed using a 1.6.2 or earlier CTRS.
Workaround: Copy the missing presentation file manually to the appropriate folder.
•
Symptom: Import screen returns error.
Conditions: If there is a filename with more than 10 digits, the user sees this symptom.
Workaround: Do not import this file.
•
Symptom: In User Management in the admin user interface, the administrative user can be deleted.
Conditions: This symptom is seen in Release 1.6.0.
Workaround: Do not delete the default administrative user. If other admin users are deleted, sign in as the default admin user and recreate other admin users. If all administrative users are deleted, the admin users are not able to sign in to admin user interface.
•
Symptom: A corrupted recording title shows in the end-user portal.
Conditions: If a recording in CIF format only is made public, this symptom is seen.
Workaround: Do not make CIF videos public.
•
Symptom: The user sees a frozen IP phone UI.
Conditions: After recording from an endpoint, the user reviews the recording. When the user pauses and stops multiple times, the progress bar moves as though playback is progressing, but the display is blank. After, the phone UI freezes. The UI unfreezes after the default timeout period has elapsed.
Workaround: Wait for the timeout period to elapse. An idle screen is then displayed. Or stop and start midlet services by selecting the Services button.
•
Symptom: The phone UI might show that it is unable to connect.
Conditions: In a scenario in which multiple recordings are being brought up simultaneously (approximately 23), this symptom might be seen.
Workaround: Retry recording or playback.
•
Symptom: In the Import Media page in IE 6, the user shows 50 items per page and selects more than 20 recordings. The user then clicks import. A JavaScript error occurs, and the import cannot be executed.
Conditions: This symptom is seen in Release 1.6.0.
Workaround: On the import page, import at most 20 recordings each time in IE 6. Or use IE 7 or IE 8 to import more than 20 recordings.
•
Symptom: HD version missing first 15 seconds, but SD version is fine.
Conditions: Packet loss occurs at the beginning of a recording. A full IDR is not received at the beginning.
Workaround: None
•
Symptom: Admin CLI access is denied with lines of java exceptions. Most GUI features are not available.
Conditions: CTRS is on 7845I2 or 7835I2 platform.
Workaround: Power cycle the server.
•
Symptom: While making or playing back a recording, the phone screen freezes when a user clicks the stop button.
Conditions: This issue can occur with CTRS 1.6.x and midlet 1-6-0.2S.
Workaround: This issue should resolve if you take one of the following actions:
•
•
•
Symptom: In the Import Media Files page of the CTRS Administrative UI, you changed the number of recordings displayed per page to 50, selected 20+ recordings, and clicked Import Files. As a result, a Javascript error occurs.
Conditions: This issue can occur under the following conditions:
•
•
Workaround: When using an Internet Explorer version 6 browser, select a maximum of 20 recordings to import at one time. To work around this limitation, you can use a version 7 or 8 Internet Explorer browser.
•
Symptom: A presentation recorded by a CTRS on a 1.7.0 CTS endpoint could not be played back on a 1.6.2 CTS endpoint.
Conditions: This issue occurred when recording with a CTRS running 1.6.2 software. Currently, a compatibility issue exists between a 1.6.2 CTRS and a 1.7.0 CTS endpoint.
Workaround: If recording a presentation on a 1.7.0 CTS endpoint, use a CTRS running software versions 1.7.0 or 1.6.3.
•
Symptom: A user might not be able to view a video through a CTS endpoint.
Conditions: This issue may arise if a user has more than 4300 recorded videos.
Workaround: Perform these steps in this order:
1.
2.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
