Cisco Cisco TelePresence Management Suite (TMS) Version 15 Document
Conferencing Products
Cisco TMS Behind Firewall mode
Supported
No
Changes to
Requirements
Requirements
This system type is not supported by Behind Firewall mode, so its configuration and network
requirements do not change.
requirements do not change.
Cisco TMS Secure-Only mode
Supported
Yes
Changes to
Requirements
Requirements
The network requirements change in that HTTP and SNMP will not be used and no longer are
required. All connectivity to the system will be via HTTPS (TCP Port 443) inbound and
outbound with the system. When enabled, the management URL setting in the managed
system will be changed to HTTPS instead of HTTP.
required. All connectivity to the system will be via HTTPS (TCP Port 443) inbound and
outbound with the system. When enabled, the management URL setting in the managed
system will be changed to HTTPS instead of HTTP.
Device Notes/Limitations
When using scheduling features of Cisco TMS with the MCU, conferences should only be started
from Cisco TMS. Creating conferences outside of TMS, such as via the auto-attendant or permanent
conferences on the MCU may cause aliasing or capacity conflicts which may lead to failure of
scheduled conferences
from Cisco TMS. Creating conferences outside of TMS, such as via the auto-attendant or permanent
conferences on the MCU may cause aliasing or capacity conflicts which may lead to failure of
scheduled conferences
Cisco TMS must be able to read the gatekeeper and/or SIP registrar from the MCU to allow
scheduling of the MCU. So MCUs reachable only via SIP Trunk and not registration will not be
schedulable in Cisco TMS.
scheduling of the MCU. So MCUs reachable only via SIP Trunk and not registration will not be
schedulable in Cisco TMS.
Nodes defined as a slave in a cluster can be added to Cisco TMS, but their functionality will be
reduced to only monitoring Connection Status. Clustered MCUs should have their master node
added into Cisco TMS to schedule and manage the MCU functions of the cluster.
reduced to only monitoring Connection Status. Clustered MCUs should have their master node
added into Cisco TMS to schedule and manage the MCU functions of the cluster.
Use of the SNMP service in the MCU is optional. If not enabled, automatic discovery of the MCU is
not available, and the MCU must be added as with the ‘Non-SNMP’ option enabled when adding it
into Cisco TMS.
not available, and the MCU must be added as with the ‘Non-SNMP’ option enabled when adding it
into Cisco TMS.