Table of Contents
- What’s New
- Important Notes for 1.10.x Releases
- Supported CTS 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 the CTS 1.10 Releases
- Related Documents
- Obtaining Documentation and Submitting a Service Request
- New in Release 1.10.9
- New in Release 22.214.171.124
- New in Release 1.10.8
- New in Release 1.10.7
- New in Release 1.10.6
- New in Release 126.96.36.199
- New in Release 1.10.5
- New in Release 1.10.4
- New in Release 1.10.3
- New in Release 1.10.2
- New in Release 1.10.1
- New in Release 1.10.0
See the “Caveats in the Cisco TelePresence System Release 1.10.9” section for a complete list of caveats.
CTS release 1.10.8 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.
See the “Caveats in the Cisco TelePresence System Release 1.10.8” section for a complete list of caveats.
Release 1.10.7 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 1.10.7” section.
See the “Caveats in the Cisco TelePresence System Release 1.10.6” section for a complete list of caveats.
Release 188.8.131.52 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 184.108.40.206” section for more information.
See the “Caveats in Cisco TelePresence System Release 1.10.5” section for a complete list of caveats.
See the “Caveats in Cisco TelePresence System Release 1.10.4” section for a complete list of caveats.
Because systems running CTS software can decode a maximum of 30 frames per second (fps), and Lync clients intermittently exceed transmission rates of 30 fps, video conferences with a Lync client can have unacceptable quality. For better video quality, use a Cisco TelePresence server between the Lync client and Cisco TelePresence system.
See the “Caveats in Cisco TelePresence System Release 1.10.3” section for a complete list of caveats.
Note This feature requires TMS version 14.3 or later and requires the use of a Touch 12 device as your call control device. Systems that use a Cisco Unified IP Phone for call control cannot use this feature.
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 1 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 2.
For more information about the TMS 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.0. For more information about TMS, refer to the Cisco TMS support documentation.
See the “Caveats in Cisco TelePresence System Release 1.10.2” section for a complete list of caveats.
See the “Caveats in Cisco TelePresence System Release 1.10.1” section for a complete list of caveats.
See the “Caveats in Cisco TelePresence System Release 1.10.2” section for a complete list of caveats.
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 TX Software Release 1.10.
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” section of the Cisco TelePresence System User Guide.
This software release supports additional languages. These languages change the text that is shown on the Cisco TelePresence Touch 12 device and also affect some on-screen messages. 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.
Some legacy Cisco TelePresence immersive systems run video at a maximum of 5 frames per second (fps). In addition, some network conditions can cause your endpoint to downgrade to frame rates as low as 5 fps.
While 5 fps works well for static images such as presentations, videos with motion in them might not be smooth, and could have a jerky appearance. The illusion of motion in recorded or live media begins at 15 to 20 fps. While broadcasting video with 5 fps is acceptable, users can expect to see less realistic motion.
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.
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.
BFCP is a protocol for controlling access to the presentation resources in a conference. BFCP is not supported in CTS software releases prior to CTS Release 1.8. BFCP is enabled by default on all CTS endpoints beginning with CTS Release 1.8. Endpoints using CTS software prior to CTS Release 1.8 must either disable BFCP on all new SIP profiles in the Unified CM Administration interface or upgrade all CTS endpoints to CTS Release 1.8 or a later release.
Occasionally an audio addin call remains listed on the meeting participant Conference List even though the call has dropped. Due to the call preservation feature, the CTS waits for the Unified CM to send a BYE message before dropping an audio addin call. The CTS can enact several mechanisms to detect when the audio addin has dropped, including dropping the call when the phone has been rebooted.
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 System Software Version Compatibility - 1.10 Releases.
For all SCCP and SIP firmware upgrades from firmware release versions earlier than 8.3(3) to version 8.5(3) or a later release, you must first upgrade your firmware to version 8.5(2). Once you have upgraded to version 8.5(2), you can upgrade your Cisco Unified IP Phone to version 8.5(3) or a later release.
See the Installation Notes section of the Cisco Unified IP Phone Release Notes for Firmware Release 8.5(3) (SCCP and SIP) for download instructions.
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:
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.
When a CTS 3210, CTS 3200, CTS 3010, CTS 3000, CTS 1300-65, CTS 1100, CTS 1000, or CTS 500-37 is in a video call with a TIP endpoint, and an additional TIP endpoint is added to the call as a WebEx audio-only call, the audio-only TIP endpoint is not displayed in the list of users on the CTS IP Phone.
After system software is upgraded and the endpoint reboots, the Touch 12 device Directory button does not show the Directory tab, only the Favorites tab. Wait 10 to 25 minutes for the Directory tab to appear.
– 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 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)
– Disable and re-enable sending presentation video. On IBM laptops, perform an 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.
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.
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 CTS performance.
The CTS 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.
Caution In European Union countries, use only devices that are fully compliant with the EMC Directive [2004/108/EC].
For complete software licensing information, access the Cisco TelePresence Administration Software Licensing Information page on Cisco.com at the following link:
If a non-CTS endpoint using Cisco TelePresence MCU dials out with muted video and audio, then unmutes after CTS enters the call, CTS drops the call. CTS also drops the call if the remote MCU endpoint has an audio codec that is in AAC-LD format (RAW or LATM). (CSCud21801)
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)
- Caveats in the Cisco TelePresence System Release 1.10.9
- Caveats in the Cisco TelePresence System Release 1.10.8
- Caveats in the Cisco TelePresence System Release 1.10.7
- Caveats in the Cisco TelePresence System Release 1.10.6
- Caveats in the Cisco TelePresence System Release 220.127.116.11
- Caveats in Cisco TelePresence System Release 1.10.5
- Caveats in Cisco TelePresence System Release 1.10.5
- Caveats in Cisco TelePresence System Release 1.10.4
- Caveats in Cisco TelePresence System Release 1.10.3
- Caveats in Cisco TelePresence System Release 1.10.2
- Caveats in Cisco TelePresence System Release 1.10.1
- Caveats in Cisco TelePresence System Release 1.10.0
- Caveats in Prior CTS Releases
Symptom Cisco TelePresence Systems connected to a third party switch experience intermittent crashes where all services on the system are restarted, and the system is unable to connect to its secondary codecs since the /etc/host file is missing.
- Cisco TelePresence System 500-37 (PID: CTS-500)
- Cisco TelePresence System 1000 (PID: CTS-1000)
- Cisco TelePresence System 1100 (PID: CTS-1100)
- Cisco TelePresence System 1300-65 (PID: CTS-1300)
- Cisco TelePresence System 3000 (PID: CTS-3000)
- Cisco TelePresence System 3010 (PID: CTS-3010)
- Cisco TelePresence System 3200 (PID: CTS-3200)
- Cisco TelePresence System 3210 (PID: CTS-3210)
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 During a point-to-point or TelePresence server 1080p call, DSP code could reload after a long period of time (several hours or more). The user sees frozen video or video flashes for a couple of seconds. The call does not drop.
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 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, the first call is unmuted.
- Secured CTS audio only call to an IP Phone.
- Secured CTS to CTS call with an audio add-in participant.
Symptom The Cisco Unified IP phone component of the Cisco TelePresence system loses its registration to Cisco Unified Communications Manager after the system upgrades from a Cisco TelePresence Administration software release before 1.10.0 to a 1.10.x release. In addition, the phone becomes inoperable.
CSCul48364 (fixed in Release 1.10.4)
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.
Symptom During a conference with another Cisco TelePresence immersive endpoint running Release 1.9, the endpoint running 1.9 software shares a presentation. The endpoint running 1.10 software displays a cropped image of the presentation.
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 another endpoint that does not use MUX or TIP (known as an interop call), a third endpoint calls the VCS-registered 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 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.
Conditions If the bandwidth for your conference is less than 2 Mbps, TIP can fail. In this case, the presentation reverts to switched mode and non-immersive endpoints no longer share the presentation.
Symptom You place a call from a CTS or TX system registered to Unified CM to another Cisco TelePresence system registered to the Video Communication Server (VCS) by way of an H.323 SIP gateway. This type of call is known as an interop call.
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 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.
Conditions This condition occurs when the audio and video are sent securely, but the presentation (media) content is non-secure. The presentation media is sent securely in error, which leads to the pixelation of the image.
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 The Touch 12 device requires the user to enter a full e-mail address (rather than just a user ID) in order to share Cisco TelePresence Recording Server (CTRS) videos. Entering a partial e-mail address causes an error message to appear.
Conditions A CTS endpoint configured for the OffNet trunk setting calls another CTS endpoint. This other endpoint auto-answers the call, ignoring the OffNet configuration, which should disable auto-answer.
Conditions This condition is noticed when you log into Unified CM, navigate to Device > Phone, and select your Cisco TelePresence system. The Active Load ID field at the top of the screen shows the image in the factory slot, rather than slot 2.
Workaround To see the correct version of software for your system, log in to your Cisco TelePresence System Administration GUI. The Device Information screen, which is the first screen that you log into, shows you the software image that is loaded in slot 1, slot 2, and the factory slot. The software image that has the asterisk next to it is the software that the system loads after a reboot. Usually, this is the software image in slot 2. This software image is known as the Active Load in Unified CM.
Symptom If an interop endpoint using Cisco TelePresence MCU calls CTS with muted video and audio, then unmutes after CTS enters the call, CTS drops the call. Issue may occur if the remote MCU endpoint has an audio codec that is in AAC-LD format (RAW or LATM).
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.
- Cisco TelePresence Software Compatibility Matrix home page on Cisco.com.
- Cisco TelePresence System Troubleshooting Guide home page on Cisco.com.
- TelePresence - Main Page on Cisco.com
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.