What is the "Behind Firewall" setting in TMS and why use it instead of "Reachable on Public Internet"?

Available Languages

Updated:April 23, 2015
Document ID:112582

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. What is the "Behind Firewall" setting in TMS and why use it instead of "Reachable on Public Internet"?

A. To find this setting:

  1. Go to Systems > Navigator and select the endpoint/system you want to configure.

  2. Click on the Connection tab.

  3. The System Connectivity setting has four options:

    • Inaccessible

    • Reachable on LAN

    • Reachable on Public Internet

    • Behind Firewall

When a system is configured as Reachable on Public Internet, TMS expects to be able to connect to it without being blocked by firewalls or NAT routers.

The Behind Firewall option allows TMS to operate with supported devices that it cannot connect to directly, such as those behind a firewall or NAT router as is common in home/SOHO setups.

Systems configured as Behind Firewall still send feedback to TMS for activity like other systems, but also poll TMS for any pending commands to be executed. Because of this, changes to systems set to Behind Firewall do not take effect immediately, but will be applied the next time the system contacts TMS, which is every 15 minutes.

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