PDF(7.1 KB) View with Adobe Reader on a variety of devices
Updated:October 29, 2014
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to solve the problem of when the Cisco TelePresence Managment Suite (TMS) reports a 'No HTTP response' message for a system.
Cisco recommends that you have knowledge of Cisco TMS.
The information in this document is based on Cisco TMS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
If you click Force Refresh it clears the error, but the error returns later.
Cisco TMS reports 'No HTTP response' for a system.
If the status can be cleared when you click Force Refresh, but returns later, this is a symptom that the Cisco TMS Database Scanner service cannot reach this system. Check whether a web proxy that requires authentication is present on the network, because this blocks traffic from the Cisco TMS services. If such a proxy is present, set up your network so that traffic between Cisco TMS and the endpoint is not routed through it or is trusted without requiring authentication.
If the status is not cleared when you click Force Refresh, connect to the system with the web browser on the Cisco TMS server itself. If you are unable to connect to it over HTTP or HTTPS, log in to the system over Secure Shell (SSH) or telnet and ensure that it accepts HTTP or HTTPS connections. Also, in order to ensure that Cisco TMS has the system's correct IP address or hostname, complete these steps: