Introduction
This document describes how to troubleshoot the issue of feedback to Cisco TelePresence Management Suite (TMS) being blocked by the network or web server.
Prerequisites
Requirements
Cisco recommends that you have knowledge of Cisco TMS.
Components Used
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.
System Feedback to Cisco TMS Blocked by the Network or Web Server
Cisco TMS relies on feedback sent from systems and verifies the endpoint that connects to it based on serial number, MAC address, and IP address. Most Cisco TelePresence and third-party systems send this feedback with anonymous HTTP or HTTPS connections which can be blocked if there is a web proxy on the network that requires authentication. In this case, you should speak to the administrator of the proxy to add an exception for traffic destined for Cisco TMS.
Firewalls can also block feedback to Cisco TMS if they block new connections from the system to Cisco TMS.
Tip: The Cisco TMS Support documentation outlines which ports and protocols must be available for each system type.
The last common connection failure occurs when an administrator manually modifies the Internet Information Services (IIS) configuration after Cisco TMS has been installed and disables anonymous access to the web directories.
Note: Anonymous access is only open to certain portions of Cisco TMS and must not be disabled because systems do not use usernames and passwords when they send feedback.
In order to correct any IIS misconfiguration, uninstall Cisco TMS and reinstall it. No data will be lost, as long as the database is left intact and the installer rebuilds the web site properties correctly.
Feedback