Why does TMS report "No HTTP response" for an MXP system when you can connect to it with your web browser?

Available Languages

Updated:April 23, 2015
Document ID:112579

Bias-Free Language

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.

Introduction

This article relates to Cisco TelePresence Management Suite.

Q. Why does TMS report "No HTTP response" for an MXP system when I can connect to it using my web browser?

A. TMS needs to use HTTP or HTTPS to connect to MXP systems.

Ensure that the network allows HTTP or HTTPS from the TMS server by using the web browser on the TMS server itself. If you can connect to the MXP system from the TMS server, but not from the TMS application:

  1. In TMS, go to Systems > Navigator.

  2. Select the endpoint and click on its Connection tab.

  3. Ensure that the IP or DNS address for the system is correct.

  4. Also check whether there is a web proxy on the network that requires authentication, as this blocks TMS services.

Related Information

Revision History

Revision Publish Date Comments
1.0
23-Apr-2015
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products