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.

These vulnerabilities affect TelePresence administration software for CTS 1.10, and TX 6.1. x. The TelePresence administration software must be upgraded to the following releases to address this vulnerability:

IX 8.1.2

TX 6.1.12

CTS 1.10.15

CTS 1.9.11

Note These vulnerabilities are not fixed in CTS 1.9.11. However, the CTS 1.9 system must be upgraded to release 1.9.11 for compatibility with the updated TX 6.1.12 and CTS 1.10.15 releases.

Cisco has performed regression testing to test the OpenSSL vulnerability for TelePresence calls to and from endpoints running the different software versions. Table 1 shows the software versions in which the calls between selected endpoints were verified as secure with the updated releases.

New in TX Release 6.1.7

New Behavior for Touch 12 Device When Joining Meetings

Note You will not see these screens if your network uses the Cisco TelePresence Management Suite (TMS) for meeting scheduling.

If you are in a call, and wish to join a scheduled conference, the choice to Join has been replaced with Join & End Current Call.

In an AutoConnect meeting, the choice to join the meeting is disabled, and is replaced by text saying that the meeting will automatically connect.

If a meeting includes only one TelePresence room, and no WebEx OneTouch (also known as one-button-to-push) number has been defined, the text in the meeting informs you that the meeting only includes the TelePresence room.

New in TX Release 6.1.5.1

This release 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.

New in TX Release 6.1.1

Microsoft Lync 2013 Support

TX Release 6.1.1 offers support for Microsoft Lync 2013 clients.

Changes to the Appearance of the Presentation on the Main Screen When Using Layout Control

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).

Note Some presentation resolutions do not take up the full space of the main display; for this reason, a black bar or border appears on the screen

New in TX Release 6.1.0

Layout Control

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.

CLI Commands to Enable or Disable the Automatic Sharing of Presentations

By default, systems running TX software automatically share a presentation when you connect your presentation source (for example, a PC) to the TX system. This behavior is known as “auto-share”.

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.

New in Release TX 6.0.5

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.

New in Release TX 6.0.3

This software release supports the new release of TelePresence Server 3.1. Additionally, the following feature is new in this release:

TelePresence Management Suite (TMS) Integration

Note This feature requires TMS version 14.3 or later.

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.

Figure 2 TMS Meeting Extension Prompt to Administrator

If you tap Yes, your meeting length extends, and all call participants see an alert like the one shown in Figure 3.

New in Release TX 6.0.2

The following feature is new in this release:

Audio and Camera Switching Tests

Note This feature is only present in TX 1300 47 and TX 1310 65 systems.

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.

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.

Screen Dimming

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.

TIP Support

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.

Starting with TX 6, TIP version 8 is supported. TIP version 8 includes support for the following features:

Video resolution of 640×360 (360p)

BFCP as an option for presentation sharing

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.

Video Bandwidth Allocation Weighting

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.

This feature is supported on the following Cisco TelePresence endpoints:

The following systems support the bandwidth allocation feature:

Cisco TelePresence System 500-32

Cisco TelePresence System TX1300 47

Cisco TelePresence System TX1310 65

Cisco TelePresence System TX9000

Cisco TelePresence System TX9200

Important Notes for TX 6 Releases

Blurred Motion for Moving Objects (Motion Handling)

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 pixelated 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.

Low motion handling (for example, a hand wave leaving streaks or tracks for a few seconds on the screen) has also been seen under the following circumstances:

Note While you can improve the streaking issue by mitigating the following causes, in some cases this problem cannot be entirely eliminated.

– 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.

– Networks with high latency; any latency in your networks can lower the motion handling

– Networks with a lot of jitter or dropped packets

Choppy or Distorted Music or Other Continuous Sound when Sharing Presentation Audio

Immersive Cisco TelePresence systems use an Acoustic Echo Canceler (AEC) to make human speech sound as clear as possible for the best possible collaboration experience.

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.

System Behavior During Times of Network Congestion

Anything that degrades network performance can affect Cisco TelePresence voice and video quality and, in some cases, can cause a call to drop. Sources of network degradation can include, but are not limited to, the following activities:

– Administrative tasks such as an internal port scan or security scan

– Attacks that occur on your network, such as a denial-of-service attack

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.

Configuring TMS Messaging Settings (6.0.3 and above)

If your system is integrated with TMS, see the following notes:

– 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.

– When you configure the setup buffer feature, then schedule a meeting, the meeting start and end times will appear incorrect in TMS or Outlook.

– 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)

Systems Cannot be Connected to a Router

Be sure that you connect your TelePresence system to a switch; this device cannot be directly connected to a router.

Upgrading TX9x00 Endpoint from CTS Release 1.9.x to TX 6

All Cisco TelePresence TX9000 series endpoints must be upgraded to software release 1.9.3 or later before they can be upgraded to release TX 6.

Call Control Device Requirement

Cisco TelePresence software release TX 6 is only compatible with the Touch 12, not the IP Phone.

Touch 12 Directory Button

After upgrading your system software and rebooting your endpoint, the Touch 12 device Directory button might not appear immediately. Wait 10 to 25 minutes for the button to appear.

High Definition Presentation Cables

The High Definition (HD) Presentation feature works with both VGA and custom digital cables.

Web Browser Support

The Cisco TelePresence System Administration interface is supported on Internet Explorer (IE) versions 6, 7, 8 and 9, as well as Firefox version 3.6, 5 and 9.

Headset Support

Headsets are supported on the CTS 500 Series only.

Setting the Device Type

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.

Viewing Presentations on Laptops

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.

Command-Line Interface (CLI) Restrictions

Avoid using the following commands to collect call status logs while in an active call:

– file tail

– ipsla

– tcpdump

Using these commands during an active CTS call can cause high CPU usage and may bring calls down.

Endpoints That Cannot Share or Receive Presentations

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:

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 following is an overview of the configuration steps:

1. Upload attached srtp.lua script to your ASR1k.

2. Define two SDP editors, for example to_rtp_avp and to_rtp_savp.

3. Configure a script set, as shown in the following example:

script-set 2 lua

script srtp

filename bootflash:srtp.lua

load-order 100

type full

complete

active-script-set 2

4. Use the SDP editor on both the inbound and outbound adjacencies:

– Ask SBC to modify the SDP calling to_rtp_avp before-receive

– And calling to_rtp_savp after-send

editor-type editor

editor-list before-receive

editor 1 to_rtp_avp

editor-list after-send

editor 1 to_rtp_savp

5. Create three editor headers:

a. tp-to-x-supported

b. tp-to-supported

c. tp-add-x-srtp-fb

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:

Supported TX Auxiliary Devices

NoteUsing 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.

The Cisco TelePresence system works best when suitable devices are attached using good quality cables and connectors. Cisco does not supply the cable that connects auxiliary devices to the codec.

Displays

This section describes the display choices you have with your Cisco TelePresence System and includes the following topics:

Qualified Cisco Displays

The following display is qualified for use with Cisco TelePresence System running CTS or TX software:

55-inch display, part number CTS-MON-55-WW.

Before use, turn off all on-screen display (OSD) capability for the displays. This prevents the display from showing messages after you stop sharing a presentation.

To turn off OSD, complete the following steps.

Tip Perform these steps using the remote control that comes with the system, or use the joystick control on the back of the display.

Step 1 Turn the display on.

Step 2 Press MENU on the remote, or press the center of the joystick and move the joystick to select the menu option (the choice on the left), to bring up the menu for the display.

Step 3 Using the up and down arrows, navigate to System in the menu panel.

Step 4 Press Enter if using a remote, or press the center of the joystick if using the joystick on the display, to select the System choice.

Step 5 Using the up and down arrows, navigate to General and press either Enter on the remote, or the center of the joystick on the display.

Note This choice does not appear initially. Scroll down to see it.

Step 6 Navigate to OSD Display and press Enter or the center of the joystick.

Step 7 Set all three OSD choices (Source OSD, No Signal OSD, and MDC OSD) to Off (the default is On) to disable OSD messages.

Step 8 Press EXIT on the remote, or move the joystick to the previous menu choices, until the menu no longer displays.

Using Non-Qualified Displays With your Cisco 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.

When qualifying a display for use with your TelePresence system, consider the following:

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.

Document Cameras

The following WolfVision document cameras have been tested for use with TX systems:

VZ-C12 (Ceiling mounted)

VZ-C32 (Ceiling mounted)

VZ-C323 (Third Generation product line)

VZ-9plus (Desktop unit)

VZ-123 (All)

Video Signal Splitters

The following video signal splitters have been tested for use with the CTS systems:

Exceptions with Other Cisco Devices

During a secure SIP call between a TX9x00 system and an MXP1700 system, when the TX9x00 shares a presentation, the call becomes audio-only and the MXP1700 sees a frozen video screen. (CSCub99572)

No Video on H.323 EX60

During a point-to-point call, no video appears on remote H.323 EX60 endpoint after TX9x00 system performs a hold-and-resume or adds an audio participant to the call. (CSCub97552)

640x480 Resolution Causes Dropped Presentation

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)

Hold-and-Resume on SX20

During a call between a TX9000 and an SX20, when the SX20 performs a hold-and-resume, the SX20 loses incoming video. (CSCuf75845)

Image Distortion in Jabber Call

Slight image distortion may occur during a call between a mobile device using Jabber and one of the following systems: CTS 500-32, CTS 13x0 or TX9x00. (CSCuh52517)

Image Distortion in MCU Conference with C20 Endpoint

During an MCU conference between two TX endpoints an a C20 endpoint, when TX shares a presentation and then performs a hold-and-resume, the presentation appears green. (CSCui02876)

TMS Alerts and Prompts

Some TMS alerts and prompts appear even while the system is not in a call. (CSCug52535)

Exceptions with Third-Party Endpoints

500 Internal Server Error from Cisco Unified CM 8.6.2

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 Cisco TelePresence System Release TX 6.1.12

Unresolved Caveats in Release 6.1.12

There are no unresolved caveats in this release.

Resolved Caveats in Release 6.1.12

CSCuy54628

Symptom Cisco TelePresence 1310, Cisco TelePresence System 1000, Cisco TelePresence System 1100, Cisco TelePresence System 1300, Cisco TelePresence System 3000 Series, Cisco TelePresence System 500-32, Cisco TelePresence System 500-37, and Cisco TelePresence TX 9000 Series includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs:

This bug has been opened to address the potential impact on this product.

Conditions Exposure is not configuration dependent.

Cisco TelePresence System Software Release 1.10.12 and later releases and Cisco TelePresence System Software TX Release 6.1.9 and later releases are affected by the following Common Vulnerability and Exposures (CVE) IDs:

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product. Additional information on Cisco's security vulnerability policy can be found at the following URL:

Symptom Cisco TelePresence 1310 ; Cisco TelePresence System 1000 ; Cisco TelePresence System 1100 ; Cisco TelePresence System 1300 ; Cisco TelePresence System 3000 Series ; Cisco TelePresence System 500-32 ; Cisco TelePresence System 500-37 ; Cisco TelePresence TX 9000 Series includes a version of ntpd that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs:

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

Symptom Cisco TelePresence Administration Software includes a version of the Hypertext Preprocessor (PHP) software that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE-2015-6831, CVE-2015-6832 and CVE-2015-6833

Conditions Device with default configuration.

Workaround Not currently available.

CSCux20885

Symptom No media on calls into a Cisco TelePresence Server conference that are intercepted by an SBC's (Session Border Controller) IVR (interactive voice response) system until a hold/resume is performed.

Conditions Calls through an SBC/IVR into a TelePresence Server conference while running CTS releases earlier than 1.10.14 and TX releases earlier than 6.1.11

Workaround After connecting to the TelePresence Server conference, perform a hold/resume to re-establish an audio/video connection.

CSCuw81902

Symptom Scrolling through the directory on the Touch12 panel does not display more than 55 entries.

Conditions A TX endpoint running releases after TX 6.1.7 (16). More than 55 users contained in the directory. Note that this caveat does not apply to the CTS system as it only applies to the TX.

Workaround While searching through the Directory on the Touch 12, narrow search scope to end up with a subset of entries so they are less than 55

CSCuu82518

Symptom This product includes a version of OpenSSL that is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2015-4000, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1791, CVE-2014-8176

Conditions Exposure is not configuration dependent. The following product lines are affected: CTS500-32, CTS1100, CTS1300, CTS3200, and TX9200. Currently latest code runs OpenSSL 1.0.1m. An update to the OpenSSL code is required.

Workaround Not Available

Caveats in the Cisco TelePresence System Release TX 6.1.10

The following sections show the resolved and unresolved caveats for this software release.

When an unsecured CUCM cluster sends an empty CTL file to TelePresence Immersive endpoints (CTS, TX, and IX), the endpoint attempts to download a signed config file from the TFTP server. Since the CUCM cluster is nonsecure, only unsigned files are available. This causes the endpoint to not receive any config updates, possibly leading to it not registering with CUCM, in which case calls are not possible.

Conditions When nonsecure CUCM that was previously secure is sending an empty CTL file to the endpoint.

Workaround Delete CTL from CUCM and clear security credentials on the endpoint.

CSCuv81870

Symptom DTMF events have inconsistent event timestamps.

Conditions Each DTMF event should have the same timestamp. When the same event does not, a remote system receives incorrect digits.

Workaround There is no workaround.

Caveats in the Cisco TelePresence System Release TX 6.1.9

The following sections show the resolved and unresolved caveats for this software release.

Caveats in the Cisco TelePresence System Release TX 6.1.8

Unresolved Caveats in Release TX 6.1.8

There are no unresolved caveats in this release.

Resolved Caveats in Release TX 6.1.8

CSCur48604

Symptom When Address Resolution Protocol (ARP) requests are sent to Cisco TelePresence immersive systems, the system’s internal address (i.e. 192.168.x.1) is being returned, rather than the system’s actual network address.

Conditions This is seen only when 802.1x is enabled.

Workaround One likely cause of the problem is an external device on the network segment that is pinging, or sending ARP requests to the 192.168.x.1 address. So, a workaround would be to remove that device.

Caveats in the Cisco TelePresence System Release TX 6.1.5

Unresolved Caveats in Release TX 6.1.5

There are no unresolved caveats for this release.

Resolved Caveats in Release TX 6.1.5

CSCuj40627

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.

Conditions When a CTS or TX endpoint with Touch Panel is already in a call and receives another call.

Workaround There is no workaround.

CSCum75022

Symptom A secure call cannot see the presentation for a multipoint call when dialed into an MCU.

Conditions This condition occurs when there is a mix of secure and non-secure endpoints in a multipoint call.

Unresolved Caveats in Release TX 6.1.3

Resolved Caveats in Release TX 6.1.3

Symptom During an MCU call, when sharing presentation with 1440x900 or 1280x800 resolutions, the remote endpoints cannot see the presentation.

Conditions This condition only occurs when the resolution is at 1440x900 and 1280x800 pixels.

Workaround Use another resolution to share the presentation.

CSCul18329

Symptom When upgrading to 1.10.4, 802.1X authentication fails in a 802.1X MAC Authentication Bypass (MAB) network configuration and there isn't a way to disable it on the codec.

Conditions The codec is plugged into a port with 802.1X authentication enabled.

Workaround Disable 802.1X on the network port.

CSCun68503

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.

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.

Unresolved Caveats in Release TX 6.1.2

Resolved Caveats in Release TX 6.1.2

Symptom Missing or partially-incomplete translations appear on the Touch 12 when a User Locale other than English is specified.

Conditions On new TelePresence system installations, if the unit is upgraded to 6.1.1 before the user locale is specified, the translations will not display on the Touch 12 device.

Workaround After you configure the user locale, downgrade to TX software release 6.1.0 and then back to release 6.1.1, or upgrade to TX software release 6.1.2.

CSCul56741

Symptom When a Cisco Desktop Collaboration Experience DX650 receives 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.

Conditions This condition has been seen in a point-to-point call between a DX650 and CTS-500, or between a DX650 and a CTS-1000. The Cisco Unified Communications Manager version was 10.0.

Workaround There is no workaround.

CSCum86504

Symptom Temperature monitoring from SNMP can fail to work after the system has been monitored for a long period of time (one week or more).

Conditions The left or right displays of multi-display systems can show invalid temperature information after a week of monitoring using SNMP.

Workaround There is no workaround.

CSCum97942

Symptom An SNMP walk procedure reports that the right and/or left codecs are in an error condition.

Conditions This condition occurs during normal SNMP monitoring.

Workaround Ignore the error. The system functions normally and there is no impact or error on the system.

CSCun37251

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.

Conditions This condition is intermittent. The endpoints will record high values for audio add-in calls that never occurred.

Workaround The condition corrects itself.

CSCui32881

Symptom The display and the Cisco Touch device do not complete the bootup procedure after a peripheral upgrade.

Conditions During the peripheral firmware update for the display, the display and Touch device do not boot successfully.

Workaround Reboot the system manually.

CSCui58400

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.

Conditions This condition arises when Favorites using URIs are configured for your CTS or TX system.

Workaround There is no workaround.

CSCui72815

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.

Conditions This condition arises when a CTS 500-32 or CTS 500-37 is muted and receives another incoming call.

Workaround Mute the CTS again.

CSCuj08081

Symptom After upgrading to TX release 6.1, a Cisco TelePresence System TX9000 or TX9200 shows purple video on all three displays.

Conditions This condition occurs on the TX9000 or TX9200 during a system upgrade.

Workaround Adjust the camera by completing the following steps:

Step 1Assemble the camera target and attach the target to the center segment of the table.

Conditions This condition is encountered on systems running Cisco TelePresence System TX software 6.1.0 and earlier.

Workaround There is no workaround.

CSCuj70026

Symptom A Cisco TelePresence System 3000, 3010, 3200, 3101, or TX9000 system intermittently shows as an audio conference, and a blank display is seen on one or two of the three screens.

Conditions This condition is seen when a call is going through an MCU with a Cisco TelePresence System 3000, TX1310-65, and TX9000.

Workaround There is no workaround.

CSCul13329

Symptom A Cisco TelePresence Systems (CTS) in a secure call will not hear audio participants after the SIP Session Refresh timer.

Conditions This issue is present in the following circumstances:

Secured CTS audio only call to an IP Phone.

Secured CTS to CTS call with an audio add-in participant.

Workaround Complete the following steps:

1. Issue a hold/resume sequence on the CTS endpoint.

2. Set the call to non-secure.

CSCul24865

Symptom Video corruption is seen between a Cisco TelePresence System TX9000 and a Lync 2013 client.

Conditions This condition is seen when in a call between a Cisco TelePresence CTS or TX system and a Lync client.

Workaround There is no workaround.

CSCul39348

Symptom When you specify the SNMP trap receiver information in Unified CM, that information is not shown in the Configuration > SNMP Settings area of the Cisco TelePresence Administration GUI.

Conditions This condition occurs when you specify an SNMP v3 trap receiver username of ‘admin’ in Unified CM.

Workaround Do not use 'admin' as the SNMP v3 trap receiver username.

CSCul48364

Symptom Directories do not appear on the Touch device of your TelePresence system.

Conditions This condition occurs only with Cisco Unified Communications Manager (Unified CM) 10.0, and only after an upgrade to TX 6.1.0 or CTS 1.10.3.

Workaround There is no workaround.

CSCum20626

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.

Conditions This condition is seen only when an endpoint running TX software release 6.1 joins the call.

Workaround There is no workaround. In some cases, performing a Hold, then a Resume on the endpoint fixes the audio problem.

CSCum50926

Symptom The power button for the document camera is grayed out.

Conditions This condition is seen after you manually power off the camera.

Workaround Power cycle the document camera.

Caveats in the Cisco TelePresence System Release TX 6.1.0

The following sections show the resolved and unresolved caveats for TX software release 6.1.0.

Unresolved Caveats in Release TX 6.1.0

CSCue02793

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.

Conditions This condition occurs during microphone troubleshooting and does not affect system troubleshooting or the functioning of the microphone, only the appearance of the icons.

Workaround There is no workaround.

CSCuf47245

Symptom After upgrading your system, the Cisco TelePresence System 500-32 changes from Headset to Speaker mode. No audio can be heard during a video conference.

Conditions This condition occurs after an upgrade from 6.0.0 to 6.0.1.

Workaround In the Cisco Touch console for the system, navigate to More > Settings > Meeting Volume, and move the slider button for Audio Mode from Speaker to Headset.

CSCue31615

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.

Conditions This problem occurred under the following test conditions:

1. The CTS 500-32 called a system using a Cisco TelePresence Codec C40.

2. The CTS 500-32 shared a presentation at a resolution of 1680x1050

3. The CTS 500-32 performed a hold and resume operation

4. The CTS 500-32 added an audio-only endpoint

5. The CTS 500-32 changes the resolution of the presentation to 640x480

After these steps were performed, the presentation was not seen by the C40.

Workaround There is no workaround.

CSCue26291

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.

Conditions This condition occurs when there are a large number of entries in the directory.

Workaround There is no workaround.

CSCuh17942

Symptom One-way video is seen at the start of a call between a Jabber client that has been configured to never start calls with video and a CTS or TX system.

Resolved Caveats in Release TX 6.1.0

Symptom When using a Cisco TelePresence System 500-32, the Presentation-in-Picture (PiP) does not display.

Conditions This condition occurs with a Cisco TelePresence System 500-32 that uses a Cisco Unified IP phone for call control.

Workaround There is no workaround.

CSCuh52517

Symptom Slight image distortion may occur during a call between a mobile device using Jabber and one of the following systems: CTS 500-32, CTS 1300, CTS TX 1310, TX9000 or TX9200.

Conditions This condition may occur during a call between Jabber and some Cisco TelePresence systems.

Workaround There is no workaround.

CSCui65472

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.

Conditions This condition occurs during a multi-point call using a TelePresence Server, and not enough ports were available for all three segments of an immersive system.

Workaround Make sure that you allow the correct amount of resources during a multipoint call.

Caveats in the Cisco TelePresence System Release TX 6.0.5

The following sections show the resolved and unresolved caveats for TX software release 6.0.5.

Unresolved Caveats in Release TX 6.0.5

Resolved Caveats in Release TX 6.0.5

CSCug80344

Symptom You experience one-way audio during a conference.

Symptom You experience one-way audio during a conference.

Conditions The following conditions cause the issue:

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.

2. You add another CTS or TX system to the call.

Workaround Hold, and then resume, the conference.

You can prevent this issue by calling the CTS or TX system first, then placing the interop call.

CSCui78297

Symptom Video flashes or blinks on and off during a conference.

Conditions Users dialing in to a conference using the TelePresence server with a minimum release of 3.1(1.95) can see colored lines or bars during a conference.

Workaround If your TelePresence server is running release 3.1(1.95) software or later, make sure that you are running a minimum of TX release 6.0.5 software on all your TX systems.

Caveats in the Cisco TelePresence System Release TX 6.0.4

The following sections show the resolved and unresolved caveats for TX software release 6.0.4.

Unresolved Caveats in Release TX 6.0.4

Symptom During an MCU conference between two TX endpoints an a C20 endpoint, when TX shares a presentation and then performs a hold-and-resume, the presentation appears green.

Conditions Issue occurs during an MCU conference.

Workaround There is no workaround.

Resolved Caveats in Release TX 6.0.4

CSCue57735

Symptom During a TelePresence conference that includes multiple endpoints, an audio-only IP Phone transfers the call to an EX endpoint. When the EX endpoint presses hold and resume, BFCP fails.

Conditions Issue occurs during a call with multiple endpoints, including one IP Phone and one EX endpoint.

Workaround There is no workaround.

CSCue82478

Symptom After 15 to 30 minutes of presentation sharing from CTS to LifeSize, the LifeSize image begins to flicker intermittently between the incoming CTS video and presentation.

Conditions CTS and LifeSize remain in a non-secure SIP call for 15 to 30 minutes.

Workaround Unshare the presentation on CTS, then share again.

CSCue95364

Symptom SNMP logs do not include the IP address(es) of the server(s) performing the queries.

Conditions Issue occurs when collecting SNMP logs.

Workaround Change the SNMP logging level using CLI commands.

CSCuh18153

Symptom When a TX or CTS system joins an MCU call as the first participant, the audio prompt that plays is corrupted slightly.

Conditions Issue occurs when CTS/TX enters an MCU call as the first participant.

Workaround There is no workaround.

CSCuh54966

Symptom Video corruption occurs during a call from CTS to MCU.

Conditions Issue occurs after a CTS running 1.10.1-43 and above calls an MCU.

Workaround There is no workaround.

CSCuh64139

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.

Conditions A conflict in BFCP server mode occurs between the TelePresence endpoint and the server (whether MCU or TelePresence server). The conflict disables BFCP server mode.

Workaround Press hold and resume on the TelePresence endpoint.

Caveats in the Cisco TelePresence System Release TX 6.0.3

The following sections show the resolved and unresolved caveats for TX software release 6.0.3.

Unresolved Caveats in Release TX 6.0.3

CSCug32505

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.

Conditions Issue occurs when an active meeting is canceled by the administrator using the TMS administrative interface.

Workaround Wait for a few seconds until the meeting information and Join button disappear.

CSCug52535

Symptom Some TMS alerts and prompts appear even while the system is not in a call.

Conditions The TelePresence system is managed by TMS but is not in a call.

Workaround There is no workaround.

CSCuh39653

Symptom Occasionally, the call duration timer on the Touch 12 device does not update immediately when a call starts.

Conditions Issue occurs after a call starts between a TX9000 and a CTS 500-32.

Workaround There is no workaround.

CSCuh52517

Symptom Slight image distortion may occur during a call between a mobile device using Jabber and one of the following systems: CTS 500-32, CTS 13x0 or TX9x00.

Conditions Issue may occur during a call between Jabber and some Cisco TelePresence systems.

Workaround There is no workaround.

Resolved Caveats in Release TX 6.0.3

CSCuf52211

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.

The same condition is seen on systems using CTMS without the TelePresence Server; however this condition is seen after a longer time (more than 13 hours).

Conditions This condition is seen on CTS endpoints running 1.9.5 and connected to CTMS (1.9.3) and TPS 2.3 (1.57).

Workaround Press Hold and Resume to resolve this problem.

CSCug94889

Symptom Systems running CTS or TX software are dropped during a conference using the Cisco TelePresence Server.

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 Security icon on CTS shows non-secure when in a secure conference

Symptom

Conditions The conference is running on Telepresence Server 3.1 or above and at some point in the past a non-secure call was part of this conference.

Workaround There is no workaround.

CSCuf32686

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.

Conditions One participant on an IP Phone is connected by way of an audio add-in; then, another endpoint shares a presentation. The IP Phone goes on hold.

Workaround Perform one of the following actions:

1. Unshare, then share the presentation by tapping the UnShare option on the Touch Panel, then tapping Share.

2. Issue a Hold/Resume sequence from the endpoint that added the audio participant into the call.

3. Disconnect and reconnect the presentation source by unplugging the presentation cable, then plugging it back in.

If you perform this action before the hold/resume action completes, perform it again after the endpoint resumes the call.

4. Have a non-host site that is not sharing the presentation add the audio-only participant into the call.

CSCug28175

Symptom During a point-to-point call between a TX9x00 system and a TX1310 65 system, a shared presentation may appear pixelated intermittently on the remote endpoint.

Conditions This issue occurs during a point-to-point call between a TX9x00 system and a TX1310 65 system, where one system shares a presentation.

Workaround There is no workaround.

CSCug59813

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.

Conditions Issue occurs on a TX endpoint integrated with TMS after scheduling a one-button-to-push meeting using the TMS administration interface.

Workaround Configure a 10-minute setup buffer using the TMS administration interface, which will allow the button to work.

CSCug96878

Symptom The Live Desk button on the Touch 12 device does not work when used with TX9x00 systems. An error message appears: “There is no Live Desk number configured.”

Conditions The Live Desk number is configured properly in Unified CM.

Workaround There is no workaround. Upon reboot, the button functions correctly for 15 minutes before failing to work again.

Caveats in the Cisco TelePresence System Release TX 6.0.2

The following sections show the resolved and unresolved caveats for TX software release 6.0.2.

Unresolved Caveats in Release TX 6.0.2

CSCue31615

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.

Conditions Issue occurs during an H.323 call between a CTS 500-32 and a C40, where a presentation is shared.

Workaround Change the presentation resolution to a higher resolution.

CSCue90168

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.

Conditions Issue occurs during a TelePresence Server call between TX9000 and another endpoint that shares a presentation.

Workaround There is no workaround.

CSCue90221

Symptom Self view may take 1-2 seconds to turn on.

Conditions Occurs when using the self view feature on a TX9x00 system.

Workaround There is no workaround.

CSCuf34335

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.

Conditions This issue occurs when a user shares a presentation and uses the PiP feature during a call, then activates the Self View feature.

Workaround Disconnect and reconnect the presentation cable.

Resolved Caveats in Release TX 6.0.2

CSCue01072

Symptom After rebooting, the Touch 12 device displays the wrong day and time.

Conditions Issue occurs after rebooting the Touch 12 device.

Workaround Wait 3 minutes until the device displays the correct day and time.

CSCug02498

Symptom After an EX60 system transfers a Cisco Unified Communication Integration Lync (CUCI Lync) call to a TX system, the TX does not send video to CUCI Lync.

Conditions Issue occurs during a call between CUCI Lync and a TX system.

Caveats in the Cisco TelePresence System Release TX 6.0.1

Unresolved Caveats in Release TX 6.0.1

CSCue38334

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.

Conditions The presentation source (computer) uses a VGA-to-DisplayPort adapter with the presentation cable to share a presentation.

Workaround Disconnect the adapter from the presentation cable after presentation sharing is finished.

CSCue87345

Symptom The CLI command set security authstring does not work.

Conditions This occurs when the user attempts to secure the CTS endpoint using an authentication string on the CLI.

Resolved Caveats in Release TX 6.0.1

CSCub62170

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.

Conditions Issue occurs on the Touch 12 device.

Workaround Enter a full e-mail address, including an at (@) sign, in order to share CTRS videos on the Touch 12.

CSCuc98622

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.

Conditions Issue occurs on a CTS 500-32 system with a document camera connected.

Workaround There is no workaround.

CSCud69699

Symptom When calling a CTS endpoint, the Cisco TelePresence SX20 system and the C-series codecs experience jitter.

Conditions Issue occurs during a point-to-point call between a CTS endpoint and a Cisco TelePresence SX20 system or a system using a C-series codec.

Workaround There is no workaround.

CSCue29156

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.

Conditions Issue occurs when a CTS 1300 or CTS 500 system enters and exits Self View mode while showing a presentation.

Workaround There is no workaround.

CSCue73846

Symptom After completing password recovery on a TelePresence system and clicking Save and Apply Config in Unified CM, the media service on the TelePresence system keeps restarting in an endless loop.

Conditions Issue occurs after completing password recovery on the TelePresence system Administration GUI and then clicking Save and Apply Config in Unified CM.

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.

Conditions Issue occurs sometimes, after more than 15 minutes have elapsed in the call.

Workaround Perform a hold-and-resume on the TC endpoint.

Caveats in the Cisco TelePresence System Release TX 6.0.0

The following sections show the resolved and unresolved caveats for TX software release 6.0.0.

Unresolved Caveats in Release TX 6.0.0

CSCub77746

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 both inside and outside a TelePresence call.

Workaround Press Done to exit the annotation screen.

CSCub97552

Symptom During a point-to-point call, no video appears on remote H.323 EX60 endpoint after TX9x00 system performs a hold-and-resume or adds an audio participant to the call.

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.

Symptom During a SIP call between a TX9x00 system and an MXP1700 system, when the TX9x00 shares a presentation, the call becomes audio-only and the MXP1700 sees a frozen video screen.

Conditions Systems are in a SIP call, and TX9x00 system shares a presentation with the MXP1700.

Workaround There is no workaround.

CSCuc99085

Symptom After replacing the document camera on a TX9000 system, the document camera power button on the Touch 12 device screen does not work.

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.

Workaround Reset the TelePresence system in Unified CM.

CSCud25240

Symptom Two endpoints, one configured for 720p resolution and the other for 1080p, stream different video resolution to each other instead of automatically shifting to the lower bandwidth.

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.

Symptom After booting up, an endpoint may fail to register to Cisco Unified CM or fail to restore network connectivity.

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.

CSCue11777

Symptom In a point-to-point call between a TX9x00 system and a CTS 3000 system, the negotiated bandwidth does not match.

Conditions Issue occurs during a call between a TX9x00 system running software release 6.0.0 and a CTS 3000 system running a software release greater than 1.9.3.

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:

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.