Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Systems Behind a Firewall/NAT
Systems behind a firewall or NAT are supported for booking, getting software upgrades, receiving phone books and
being part of the statistics created in Cisco TMS.
being part of the statistics created in Cisco TMS.
Every 15 minutes and on boot, these systems send a Keep Alive signal which Cisco TMS responds to. Cisco TMS
cannot contact the systems outside of these exchanges. The system status information for remote endpoints is
therefore limited.
cannot contact the systems outside of these exchanges. The system status information for remote endpoints is
therefore limited.
Unified CM
Note that Unified CM-registered systems must not be placed behind a firewall or NAT.
Booking
Some limitations apply when booking conferences that involve endpoints behind a firewall:
■
Cisco TMS cannot make an endpoint behind a firewall dial out. The endpoint must therefore either be dialed
into, or the person operating the endpoint must manually dial in to the conference.
into, or the person operating the endpoint must manually dial in to the conference.
■
When booking conferences that include multiple endpoints behind a firewall as Automatic Connect, the
conference must include an MCU or local endpoint with embedded multisite support.
A point-to-point conference with Automatic Connect will not work for two systems behind a firewall/NAT, but
will work as expected if one of the endpoints is local.
conference must include an MCU or local endpoint with embedded multisite support.
A point-to-point conference with Automatic Connect will not work for two systems behind a firewall/NAT, but
will work as expected if one of the endpoints is local.
Statistics and monitoring
Statistics and monitoring of remote systems work the same way as for systems that are on the LAN, by sending
HTTP feedback to Cisco TMS.
HTTP feedback to Cisco TMS.
■
Status and detailed call information (status.xml and history.xml) are sent to Cisco TMS every 15 minutes.
■
Any changes to the configuration of the system (configuration.xml) will also be sent with the Keep Alive signal
every 15 minutes.
every 15 minutes.
Ad hoc calls will not be shown for systems behind a firewall, as TMSLiveService is not able to contact the system to
get information about the call. For more information, see
get information about the call. For more information, see
Software Upgrades
When scheduling an upgrade for a system behind a firewall/NAT:
1.
Cisco TMS will report that the upgrade went successfully, but the upgrade will have been put on hold.
2.
The next time Cisco TMS receives a boot event from the system, the system will receive notice that an
upgrade has been scheduled . In the reply to the boot event, Cisco TMS will send the endpoint a URL where it
can get the software package.
upgrade has been scheduled . In the reply to the boot event, Cisco TMS will send the endpoint a URL where it
can get the software package.
This URL is defined in Administrative Tools > Configuration > Network Settings > General Network Settings
pane > URL Where Software Packages Can Be Downloaded.
pane > URL Where Software Packages Can Be Downloaded.
Phone Books
The corporate phone book will work in the same way as if the system was located on a LAN; the endpoint will request
phone book information from Cisco TMS, and the response will be returned as search results.
phone book information from Cisco TMS, and the response will be returned as search results.
The legacy global phone book format is not supported for remote systems.
41
Cisco TelePresence Management Suite Administrator Guide
System Management Overview