Cisco Cisco TelePresence Management Suite (TMS) Version 15 Document
Conferencing Products
Multiple Network Interfaces
The MCU supports multiple network interfaces, and more than one network interface may be enabled
when used with Cisco TMS. However, all management and awareness of the device will only interact with
one port. The second port will not be visible in Cisco TMS views.
when used with Cisco TMS. However, all management and awareness of the device will only interact with
one port. The second port will not be visible in Cisco TMS views.
Network Requirements
To be managed by Cisco TMS
in the traditional ‘Managed by Cisco TMS’ mode, a system requires full bi-
directional communication over the IP network to Cisco TMS with the following ports and protocols.
Service
Protocol
Port
Number
Number
Allows Connections
(relative to system)
(relative to system)
HTTP
Or
HTTPS
Or
HTTPS
TCP
TCP
TCP
80
443
443
Inbound
HTTP
TCP
80
Outbound
Note: Network systems that rewrite source addresses will interfere with communications to Cisco TMS
and proxies that require authentication may also hinder communications from systems to Cisco TMS.
and proxies that require authentication may also hinder communications from systems to Cisco TMS.
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
No
Changes to
Requirements
Requirements
This system type is not supported by secure-only mode, so its configuration and network
requirements do not change.
requirements do not change.
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.
TelePresence Servers defined to have their conferences managed by an external server (slave blade)
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.
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.
Due to lack of SNMP support, when adding this type of system into Cisco TMS, you must use the
Discovery Non-SNMP Systems option when adding the system.
Discovery Non-SNMP Systems option when adding the system.