Table of Contents
- What’s New
- Important Notes for TX 6 Releases
- Supported TX Auxiliary Devices
- Software Agreements and Licensing
- Exceptions with Other Cisco Devices
- Exceptions with Third-Party Endpoints
- Cisco TelePresence Software Compatibility and Device Interoperability
- Caveats in Release TX 6
- Caveats in Prior TX Releases
- Related Documents
- Obtaining Documentation and Submitting a Service Request
Note Cisco TelePresence software release TX 6.x is only compatible with the following TelePresence systems: CTS 500-32, TX1300-47, TX1310-65, TX9000 and TX9200. TX 6.x is only compatible with the Touch 12 call control device, not the IP Phone.
- New in TX Release 6.1.6
- New in TX Release 22.214.171.124
- New in TX Release 6.1.5
- New in TX Release 6.1.4
- New in TX Release 6.1.3
- New in TX Release 126.96.36.199
- New in TX Release 6.1.2
- New in TX Release 6.1.1
- New in TX Release 6.1.0
- New in Release TX 6.0.5
- New in Release TX 6.0.4
- New in Release TX 6.0.3
- New in Release TX 6.0.2
- New in Release TX 6.0.1
- New in Release TX 188.8.131.52
- New in Release TX 6.0.0
See the “Caveats in the Cisco TelePresence System Release TX 6.1.6” section for a complete list of caveats.
TX release 184.108.40.206 fixes the GNU Bash Environment Variable Command Injection Vulnerability (Shellshock). This vulnerability is being tracked by the Cisco Defects & Enhancements Tracking System (CDETS) number CSCur05163.
TX release 6.1.2 resolves system issues and enhances the user experience; there are no new features. See the “Caveats in the Cisco TelePresence System Release TX 6.1.5” section for more information.
TX release 6.1.4 fixes various OpenSSL issues and upgrades the version of the Apache HTTP server. For additional information, see the “Caveats in the Cisco TelePresence System Release TX 6.1.4” section.
TX release 6.1.3 adds a command-line interface (CLI) command to disable or enable 802.1x authentication. For more information, see the documentation for the set dot1x command in the Cisco TelePresence System Command-Line Interface Reference Guide.
For additional caveats that were fixed in TX release 6.1.3, see the “Caveats in the Cisco TelePresence System Release TX 6.1.3” section.
TX release 220.127.116.11 fixes the OpenSSL Heartbleed Vulnerability. This vulnerability is being tracked by the Cisco Defects & Enhancements Tracking System (CDETS) number CSCuo20210.
In addition, an enhancement (CSCuo30624) has been added to allow a Locally Significant Certificate (LSC) to be installed and used by the Key Exchange process to establish Datagram Transport Layer Security (DTLS) sessions between endpoints. See the “Caveats in the Cisco TelePresence System Release TX 18.104.22.168” section for more information.
TX release 6.1.2 resolves system issues and enhances the user experience; there are no new features. See the “Caveats in the Cisco TelePresence System Release TX 6.1.2” section for more information.
The following features are new for Release 6.1.1. See the “Caveats in the Cisco TelePresence System Release TX 6.1.1” section for a complete list of caveats.
When you use the Layout Control feature to move presentation to the main screen, previous releases of TX software cut the presentation off below the camera. TX Release 6.1.1 allows the presentation to be shown full-screen at some presentation resolutions (for example, 1080p and 720p).
The following features are new for Release 6.1.0. See the “Caveats in the Cisco TelePresence System Release TX 6.1.0” section for a complete list of caveats.
This feature allows you to move the presentation content from the presentation display up to the main screen. You can also split the content on the main screen between conference participants and presentation content.
For more information, refer to the “Understanding Layout Control (Moving Presentation Content Onto the Main Display Screen—Cisco TelePresence TX1310 65, TX9000, and TX9200 Systems Only)” and “Using the Layout Control Feature” sections in the Cisco TelePresence System User Guide, Software Release TX 6.
If you are sharing a presentation on a TX system outside of a call, and you receive a call, you cannot disable auto-sharing. In this case, you receive the prompt to share, even if auto-sharing is turned on.
In other cases, to disable auto-sharing, enter the set presentation auto-share disable command. After auto-sharing is disabled, each time a user plugs in the presentation, the Touch device displays a Presentation Privacy Alert message such as the one shown in Figure 1. You then tap the Touch screen to select whether to share the presentation or not.
For more information about these commands, see the documentation for the set presentation auto-share and show presentation auto-share commands in the Cisco TelePresence System Command-Line Interface Reference Guide.
Note You must upgrade your system to a minimum of TX release 6.0.5 if your TelePresence Server is running software release 3.1(1.95) or later; otherwise, you might see colored lines or bars on the screen during a conference. See CSCui78297 for more information.
See the “Caveats in the Cisco TelePresence System Release TX 6.0.5” section for a complete list of caveats.
TX release 6.0.4 resolves system issues and enhances the user experience; there are no new features. See the “Caveats in the Cisco TelePresence System Release TX 6.0.4” section for more information.
This software release enhances the use of TMS as a call scheduling and management platform. If your system uses TMS, some new messages appear on your Touch 12 device. For example, if you are the video conference master (VC master) of your meeting, a prompt appears a few minutes before your meeting ends that gives you the option to extend your meeting. See Figure 2 for an example of this prompt.
If you tap Yes, your meeting length extends, and all call participants see an alert like the one shown in Figure 3.
For more information about the messages that appear on the Touch 12, refer to the System Alerts and Meeting Messages chapter of the Cisco TelePresence System User Guide, Software Release TX 6. For more information about TMS, refer to the Cisco TMS support documentation.
This software release includes a troubleshooting test in the CTS administration GUI that allows you to ensure that the cameras switch correctly to the active participant. Although there are three cameras in these systems, there is only one outgoing audio and video stream. When a participant in the room begins speaking, the system switches the camera to the segment with the active participant.
TX 6.0.1 software also resolves the camera brightness issue that was fixed in software release TX 22.214.171.124. See the “Caveats in the Cisco TelePresence System Release TX 6.0.1” section for more information.
Software release TX 126.96.36.199 resolves a camera brightness issue found in systems that upgrade to TX 6.0 from CTS software release 1.9 or earlier. If your system uses TX release 6.0.0, upgrading to TX 188.8.131.52 will not affect your system.
Some systems running TX release 6.0.0 may require an adjustment of the camera’s white balance. For more information, refer to the “Adjusting the White Balance for Your System” section of the Administration Guide for Cisco TelePresence Software Release TX 6. If you encounter issues with this procedure, contact your Cisco technical support representative.
Note If you are installing a new TelePresence system, and plan to upgrade to TX 6 software after installation, Cisco strongly recommends that you complete your camera hardware setup after upgrading rather than before.
The 60 fps main video feature enables Cisco TelePresence endpoints running TX 6 to send main video at a frame rate of 60 fps with 1080p quality (1080p 60). It provides improved clarity, sharper images, and an increased number of pixels, simulating a higher resolution. It also offers smoother motion handling, less blurriness, and reduced motion streaks.
- All versions of the Cisco TelePresence C90, C60, C40, and C20
- Cisco TelePresence EX90, EX60
- 720p 60 is supported during point-to-point calls and multipoint calls supported by the Cisco TelePresence Server version 2.3.
For more information, refer to the “60 fps Main Video” section of the Administration Guide for Cisco TelePresence Software Release TX 6.
This software release supports the use of 802.1X authentication for port-based access control. For more information and instructions about configuring this feature, refer to the “802.1X Authentication” section of the Administration Guide for Cisco TelePresence Software Release TX 6.
You can now take a snapshot of the presentation that is being shared during a conference, and make annotations to that snapshot. For more information, refer to the “Annotating Presentations” section of the Cisco TelePresence System User Guide.
This software release supports using a URI string (for example, email@example.com) to place a call. For more information, refer to the “Dialing a URI String Using the Keyboard” section of the Cisco TelePresence System User Guide.
- Cisco TelePresence System 500-32
- Cisco TelePresence System TX1300 47
- Cisco TelePresence System TX1310 65
- Cisco TelePresence System TX9000
- Cisco TelePresence System TX9200
For more information about the HD video feature, refer to the “High-Definition Presentation” section of the Administration Guide for Cisco TelePresence Software Release TX 6.
Cisco provides a locale pack file bundle on cisco.com that supports several languages other than English. For more information, refer to the “Installing Language Versions” section of the Cisco Unified Communications Manager Configuration Guide for the Cisco TelePresence System.
To save power and extend the life span of the Cisco TelePresence Touch 12 device, the Touch 12 dims during non-business hours, as defined in Unified CM. When dimming is active, the screen is dimmed and the home button is glowing. The system becomes active when the screen or a hard button is touched, and stays on until the system has been idle for one hour.
For more information, refer to the “Screen Dimming” section of the Cisco Unified Communications Manager Configuration Guide for the Cisco TelePresence System.
Cisco TelePresence endpoints are designed to work with any device that implements the TelePresence Interoperability Protocol (TIP) and adheres to the interoperability requirements described in Cisco's published TIP Implementation Profiles.
Cisco tests interoperability with TIP devices based on market priority. The Cisco Technical Assistance Center (TAC) accepts calls related to interoperability with third-party endpoints and devices to troubleshoot and identify the root cause of issues. These calls must come from customers with a valid support agreement.
The Video Bandwidth Allocation Weights parameter allows you to balance the bandwidth ratio for main video and presentation video during a conference. Use this feature when the amount of session bandwidth that is used by a Cisco TelePresence endpoint to send audio, main video, and presentation video media streams exceeds the amount of available session bandwidth.
For more information about configuring the weighting feature, refer to the “Video Bandwidth Allocation Weights” section of the Administration Guide for Cisco TelePresence Software Release TX 6.
Motion handling defines the degree of compression within the encoding algorithm to either enhance or suppress the clarity of the video when motion occurs within the image. High motion handling results in a smooth, clear image even when a lot of motion occurs within the video (people waving their hands, for example). Low motion handling results in a noticeable choppy, blurry, grainy, or pixelized image when people or objects move.
Cisco TelePresence provides you with a way to customize the motion handling. Although the Cisco TelePresence cameras can operate at a resolution of up to 1080p with a maximum frame rate of 60 frames per second (1080p 60), the codec can encode and compress the video into either 1080p or 720p resolutions at three different motion-handling levels per resolution providing you with the flexibility of deciding how much bandwidth is available in your network.
Instead of a sliding scale, Cisco uses the terms Good, Better, and Best. Best motion handling provides the clearest image and uses the most bandwidth. Good motion provides the least-clear image and uses the least bandwidth. For more information, refer to the “Understanding How Endpoints Determine fps and Video Quality” section of the “TX Software Features” chapter of the Administration Guide for Cisco TelePresence Software Release TX 6.
– Under certain lighting conditions (for example, the light from an upper fixture leaving a shadow on a participant). Some lighting conditions cause low motion handling when the codec applies auto-correction to the broadcast image.
– Using lighting that is in the lower range of recommended lux (closer to 200 in the 200-400 lux range). For more information, see the lighting recommendations section in the “Room Requirements for the Cisco TelePresence System TX9000 and TX9200” chapter of the Cisco TelePresence System TX9000 and TX9200 Assembly, First-Time Setup, and Field-Replaceable Unit Guide.
Any sound that is continuously played (such as music) as the audio portion of a presentation can sound choppy or distorted during a Cisco TelePresence conference. To remove echo, AEC changes the loudness of the audio coming from the system loudspeaker when it detects sound locally (on the near end). When the loudspeakers are playing presentation audio, this change in loudness may lead to noticeable choppiness or distortion.
Muting the system microphones on both the near and far end can reduce the AEC effects when you share presentation audio; however, any endpoint that is not muted will still experience the same choppiness and distortion.
These network disturbances can affect the voice and/or video quality of a Cisco TelePresence conference, and in some cases, can cause the call to drop. To reduce or eliminate any adverse effects to a TelePresence conference, schedule any administrative network tasks during a time when the Cisco TelePresence system is not being used, or exclude TelePresence systems from the testing.
– Some TMS features (such as the setup buffer or meeting extension alert) are disabled by default. These features must be enabled on the TMS administrative interface before they will work with the Cisco TelePresence system. After you configure the features in the TMS administrative interface, TMS updates itself automatically according to the interval specified in the field System Force Refresh Interval (in hours). Alternately, you can apply your settings immediately by navigating to Administrative Tools > Configuration > Network Settings and scrolling down to the TMS Services area. In the field Enforce Management Settings on Systems, click Enforce Now. If this field is set to Yes, TMS updates your system automatically when you configure features. For more about TMS features, refer to the “New Conference” section of the latest Cisco TelePresence Management Suite Administrator Guide.
– Some TMS meeting alerts and prompts may appear even when your system is not in a call. (CSCug52535)
– When the administrator uses the TMS administrative interface to delete an active meeting, the TelePresence system exits the meeting but still shows the scheduled meeting and the Join button on the Touch 12. (CSCug32505)
Whenever possible register your device to the Unified CM to configure the correct device type before calibrating the camera. To perform camera calibration if your system is not registered to the Unified CM, use the set ctstype command.
The VGA cable interface requires a 60 hertz refresh rate, but some laptops receive 60hz but do not send 60hz. For best results when viewing presentation displays on your laptop, try to disable and re-enable sending presentation video. On your PC, press Fn+F7 to disable the presentation first and then use Fn+F7 to enable the presentation again. This function is not necessary on Mac systems.
Some telepresence endpoints do not support the ability to share or receive presentations. If you encounter an endpoint that does not support presentations, the CTS displays the following notification on the main screen:
For information about MXP support for Cisco TelePresence, refer to the document Cisco TelePresence TX System Software Version Compatibility and Interoperability with Other Devices.
Customers who are deploying their B2B infrastructure with secure trunks to ASR/SBC secured by using TLS/Encryption, may experience call drops unless specific scripts are installed and configured on the ASR/SBC devices. Once the scripts and configuration are in place, certain SDP attributes are manipulated to enable SBC to unblock the SIP messages to and from Unified CM.
The first two are used in the inbound side, which will detect if any X-cisco-srtp-fallback tag gets into the supported header and then adds an srtp-fb header that includes the X-cisco-srtp-fallback tag (if present). The third one changes the internal srtp-fb header to the supported header prior to sending on the wire. The following is an example configuration:
Note Using External Devices with Your Cisco TelePresence System—Cisco cannot guarantee the performance of any external device, so Cisco recommends that you choose good quality external devices to optimize the performance of your TelePresence system.
If you decide to use another auxiliary display, Cisco TelePresence systems are designed to work with any Full HD monitor that connects to the system using a standard HDMI or DVI interface. Note that the connector on the TelePresence side is an HDMI connector, so either an HDMI-to-HDMI cable or an HDMI-to-DVI cable is required.
Cisco highly recommends the use of commercial or professional-grade displays with your Immersive TelePresence system. Off-the-shelf consumer displays or TV monitors are not recommended, as they typically have shorter life spans and require a remote control to operate.
- The display should offer native support for 1080p60 over an HDMI or DVI interface.
- The display should become active when a video signal is presented, and should go to sleep when no video signal is presented.
- The display should not require any user interaction (such as a remote control or button press) to become active from standby, sleep or deep sleep modes.
- The ability to switch off On-Screen Display (OSD) messages is highly desirable. No error messages, status messages or splash screens should be visible on the screen when a presentation image is shared or unshared.
- If the display supports multiple inputs, the ability to lock the display to a given input is highly desirable. Otherwise, the time required to show presentation content can be unpredictable. If automatic scanning of ports is supported, the feature should be disabled.
- The Video Electronics Standards Association (VESA) Display Power Management Signaling (DPMS) should be present. Some consumer-grade displays, especially those designed to be used as television displays, do not use DPMS.
For complete software licensing information, access the Cisco TelePresence Administration Software Licensing Information page on Cisco.com at the following link:
During a H.323 call between a CTS 500-32 system and a C40 system, if the CTS shares a presentation and then changes the presentation resolution to 640x480, the local presentation disappears. The remote C40 system can still see the presentation. (CSCue31615)
A CTS or TX endpoint is in a call with a LifeSize endpoint. The CTS/TX endpoint is registered to Cisco Unified CM, and the LifeSize endpoint is registered to VCS. After the CTS/TX goes on hold and then resumes the call, the Unified CM sends a 500 Internal server error message. The call is dropped. (CSCtz05200)
- Caveats in the Cisco TelePresence System Release TX 6.1.6
- Caveats in the Cisco TelePresence System Release TX 6.1.5
- Caveats in the Cisco TelePresence System Release TX 6.1.4
- Caveats in the Cisco TelePresence System Release TX 6.1.3
- Caveats in the Cisco TelePresence System Release TX 184.108.40.206
- Caveats in the Cisco TelePresence System Release TX 6.1.2
- Caveats in the Cisco TelePresence System Release TX 6.1.1
- Caveats in the Cisco TelePresence System Release TX 6.1.0
- Caveats in the Cisco TelePresence System Release TX 6.0.5
- Caveats in the Cisco TelePresence System Release TX 6.0.4
- Caveats in the Cisco TelePresence System Release TX 6.0.3
- Caveats in the Cisco TelePresence System Release TX 6.0.2
- Caveats in the Cisco TelePresence System Release TX 6.0.1
- Caveats in the Cisco TelePresence System Release TX 6.0.0
Symptom The Ignore button does not ignore or cancel a call to the endpoint when it is already in a call. The screen “Incoming call...” screen is displayed, “Ignore” is pressed but the far side endpoint will continue to ring the endpoint and The Incoming call...” screen will continue to be displayed.
Symptom Earlier versions of OpenSSL have vulnerabilities that are being tracked by the Cisco Product Security Incident Reponse Team (PSIRT). For more information, refer to the PSIRT notice at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140605-openssl (Cisco login required).
- TX9000, TX9200, TX1310-65 and CTS500-32: 1.9.x, 6.0.x, 6.1.0, 6.1.2, and 6.1.3
- CTS3000, CTS3010, CTS3200, CTS3210, CTS1000, CTS1100, CTS1300 and CTS500-37: 1.8.x, 1.9.x, 1.10.0, 1.10.1, 1.10.2, 1.10.3, 1.10.4, 1.10.5, and 1.10.6
Symptom This caveat removes the requirement that the TFTP server have a certificate entry in the Certificate Trust List (CTL) of the codec. However, the signer of the configuration file that is downloaded from the TFTP server must still appear in the CTL of the codec, or the file fails validation.
- Cisco TelePresence System 500-32
- Cisco TelePresence System 500-37
- Cisco TelPresence System 1000
- Cisco TelePresence System 1100
- Cisco TelePresence System 1300
- Cisco TelePresence 1310
- Cisco TelePresence System 3000 Series
- Cisco TelePresence TX 9000 Series
- TX9000, TX9200, TX1310-65 and CTS500-32: 6.0. x, 6.1.0, 6.1.1, and 6.1.2
- CTS3000, CTS3010, CTS3200, CTS3210, CTS1000, CTS1100, CTS1300 and CTS500-37: 1.10.0, 1.10.1, 1.10.2, 1.10.3, 1.10.4 and 1.10.5
Symptom A manufacturer-installed certificate (MIC) can only be generated only during manufacturing. Because of OpenSSL Heartbeat Extension Vulnerability, if a MIC has been exposed, the system is susceptible to attacks even after applying the Heartbleed patch. This caveat adds an enhancement to allow a locally significant certificate (LSC) to be used by the Key Exchange process to establish Datagram Transport Layer Security (DTLS) sessions between endpoints.
Conditions This condition might arise for any TelePresence systems that are affected by the Heartbleed vulnerability. See CSCuo20210 for a list of the systems and software. There is also a Cisco security advisory at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140122-cts.
Symptom When a Cisco Desktop Collaboration Experience DX650 receves a packet loss notification, it sends an Instantaneous Decoder Refresh (IDR) request to a Cisco TelePresence System 500-32, 500-37, or 1000, using a Real-Time Transport Control Protocol (RTCP) Full Intra Request (FIR). However, the Cisco TelePresence System does not send any IDR response to the DX650.
Symptom Cisco TelePresence System (CTS) and TX Series endpoints will experience media service restarts on all three codecs if the legacy encoder bit rate is mistakenly set to anything lower than 704kbps during a call.
Symptom A CTS or TX system running TX software contains both users that are synchronized using the Lightweight Directory Access Protocol (LDAP) and users that are manually entered using Unified CM (Favorites). For manually-entered users (users not added using LDAP), the Touch device displays does not correctly display URIs. If there is a URI rather than a telephone Number entered in Unified CM for the user, the Touch device displays the entry, but instead of the green button, a grey box is shown with “no information available” displayed.
Symptom A Cisco TelePresence System (CTS) 500-32 or CTS 500-37 that uses a Cisco Unified IP Phone for call control receives a call, and the call is muted. If a second call is received and answered by the CTS, and first call is unmuted.
For more information, see the “Setting Up the Cameras” section of the “First-Time Setup” chapters in the Cisco TelePresence System TX9000 and TX9200 Assembly, First-Time Setup, and Field-Replaceable Unit Guide.
- Secured CTS audio only call to an IP Phone.
- Secured CTS to CTS call with an audio add-in participant.
Symptom Other rooms are not able to hear audio from a Cisco TelePresence System TX9000 running TX software release 6.1 when dialed to a Cisco TelePresence Multipoint Switch (CTMS) secure static bridge.
Symptom When performing microphone configuration in the Hardware Setup > Troubleshooting > Microphones area of the Cisco TelePresence Administration GUI, the icons for the microphones that appear on the main display do not match the icons that appear in the GUI. The GUI shows three dots below the microphones, whereas the display does not show the dots.
Symptom During a point-to-point call between a CTS500-32 and a C40, the user shares a presentation, then changes the resolution of the display. After the resolution change, the presentation could not be seen on the far side.
Symptom When a directory with a large number of entries (128,000) is searched on the Cisco Touch device, the search results are not consistent. For example, a “no results found” is returned, even when the user is in the directory.
- Enable option in Jabber for Windows to never start calls with video.
- Place a call from Jabber to CTS endpoint
- See one way video (CTS to Jabber).
- Jabber starts video
- See 2-way video, as expected
- Jabber stops video
- No video either direction
CSCuj08081 (Now resolved in 6.1.1)
CSCul48364 (Now resolved in 6.1.1)
Symptom During a multipoint call, a multi-screen immersive system can be appear as a single-screen endpoint because of insufficient system resources (insufficient ports). In this case, the screen will not switch to the active speaker and remains on the center segment, even if no participants are in that segment.
1. You place a call from a TX system to another system that is not a CTS (CTS 1000, 1100, 1300-65, 3000, 3010, 3200, or 3210) or TX (TX1310-65, TX9000, or TX9200) system. This type of call is known as an interop call.
Symptom During a point-to-point call between a TelePresence endpoint and an interop endpoint, a third endpoint calls the interop endpoint, and the three endpoints enter a conference (either an MCU or TelePresence conference). If it is an MCU conference: after entering the conference, the TelePresence endpoint does not see any incoming video, and the shared presentation appears on the center screen. If it is a TelePresence conference: only XGA resolution is supported and all other resolutions are disabled.
Symptom When the administrator uses the TMS administrative interface to delete an active meeting, the TelePresence system exits the meeting but still shows the scheduled meeting and the Join button on the Touch 12.
Symptom The presentation freezes at the remote sites when content is being sent after 2-3 hours on a call using the TelePresence Server. The presentation was frozen on all 1.9.5 endpoints, including CTS 1300, 500-32, 500-37, TX1310, CTS1100, CTS1300, and not frozen on endpoints running 1.9.2. CTS3000 running 1.9.5 is presenting in this case. This condition appears whether the presentation display is a monitor or a projector, or is using an external presentation display.
Conditions This condition occurs during an ad-hoc, secure conference using a Cisco TelePresence Server running TS 3.1 with a system running CTS software release 1.10.1 or earlier, or TX software release 6.0.2 or earlier.
Symptom During a multipoint call where one participant is a Cisco Unified IP Phone connected via audio add-in, an endpoint shares a presentation. When the IP Phone goes on hold, the presentation (on the endpoint that performed the audio add-in) appears green or disappears. Other endpoints can still see the presentation.
Symptom For systems configured for TMS integration, the Join button appears on the Touch 12 ten minutes before the meeting start time, even if no setup buffer was configured. The button does not work until the meeting start time.
Symptom During a H.323 call between a CTS 500-32 system and a C40 system, if the CTS shares a presentation and then changes the presentation resolution to 640x480, the local presentation disappears. The remote C40 system can still see the presentation.
Symptom When a TX9000 user annotates a presentation shared from another endpoint, taps Done, and then performs a hold-and-resume, the annotations still appear on the TX9000 Touch 12 device upon resume. The other endpoint cannot see the presentation and does not regain control, despite the TX9000 completing the annotation.
Symptom When a user shares a presentation during a call and uses the PiP feature, the presentation flashes, disappears and then reappears if the presenter activates the Self View feature. Self View then appears in the background with the presentation in front.
Symptom When sharing a presentation using the presentation cable with the VGA connector and using an adapter, and then disconnecting the presentation source, the system does not unshare the presentation automatically. The system still recognizes the adapter (which is still attached to the presentation cable with VGA connector) as the presentation source. Then the system shows an error message.
Symptom The Touch 12 device requires the user to enter a full e-mail address (rather than just a user ID) in order to share CTRS videos. Entering a partial e-mail address makes an error message appear.
Symptom After unplugging the ethernet cable from a CTS 500-32 system with a document camera connected, the web GUI no longer recognizes all peripheral devices. The web GUI shows a red “X” in place of “V” status for all of these devices for more than five minutes after disconnecting the ethernet cable.
Symptom When a CTS 1300 or CTS 500 system shows a presentation and enters Self View mode, then dismisses or times out of Self View, the Self View image continues to display as a background image behind the presentation. In the CTS 1300, the Self View image does not disappear until the system enters a call. In the CTS 500, the Self View image tears down after 4 to 5 seconds.
Symptom A Cisco TelePresence TC endpoint makes a secure point-to-point call to a CTS or TX endpoint, and the center CTS or TX screen is displayed on the TC. If the TC user attempts to switch the screen in view by tapping on the corresponding microphone, the TC screen sometimes goes blank.
Symptom After pressing Presentation > Annotate > Cancel on the Touch 12 device several times in a row, a screenshot of the presentation displays on the Touch 12 screen, despite the request to cancel the action.
Conditions Issue occurs during a point-to-point call between a TX9x00 system and a remote H.323 EX60 endpoint, either when TX9x00 resumes a call after holding or when TX9x00 adds an audio participant.
Workaround Log in to VCS via ssh as admin, run the command xconf zones, and find the zone that points towards your CUCM. It will have a unique number, in this case 4: *c xConfiguration Zones Zone 4 Name: “CUCM 101". Then run the command xConfiguration Zones Zone 4 Neighbor Interworking SIP Encryption EncryptSRTCP: Yes, replacing “4” with your zone profile number.
Conditions The issue occurs when the document camera is replaced while the system is on. Power cycling the document camera does not work. An error also occurs when the admin tries to ping the document camera.
Conditions An endpoint with TX 6.0 software and 720p/60fps resolution calls a second endpoint with older CTS software and 1080p resolution that is not configured for 60fps. During the call, the TX transmits 720p video while the other CTS transmits 1080p video, when they should both shift to 720p video automatically.
Conditions Issue may occur under certain conditions: when endpoint is configured to use a static IP address, a VLAN is configured on the same switch port as the endpoint, the endpoint finishes booting up before the switch is online, or the endpoint reboots after a power outage.
Workaround Configure the VLAN for the CTS using the administrative interface. Navigate to Configuration > Network Settings > Administrative VLAN ID. If the issue occurs due to a power outage, power cycle the endpoint.
See the Cisco TelePresence Administration Software Release Notes home page on Cisco.com for information about prior CTS releases:
- Cisco TelePresence System Administration Guide home page on Cisco.com.
Products > TelePresence > Cisco TelePresence Endpoints > Your TelePresence System
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:
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.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.