Cisco Cisco TelePresence Management Suite (TMS) Version 15 Document
Conferencing Products
of
MCU’s prefix registration settings should be set based on your desired dial plan. The prefixes are
optional, but it is recommended that Prefix for MCU registrations be used. Alternatively, the MCU
Service prefix may be defined, or both prefixes may be defined; but if both prefixes are enabled they both
must be set to the same value.
Service prefix may be defined, or both prefixes may be defined; but if both prefixes are enabled they both
must be set to the same value.
If Prefix for MCU registrations is used, and MCU Service Prefix is not, the MCU setting Allow numeric
ID registration for conferences
ID registration for conferences
must be enabled in the MCU’s H.323 configuration. (
Settings
>
H.323
).
If using SIP, the MCU setting Allow numeric ID registration for conferences must be enabled in the
MCU’s SIP configuration. (
MCU’s SIP configuration. (
Settings
>
SIP
).
SIP aliases are created using the same Meeting ID settings in Cisco TMS, but the SIP registrar domain is
suffixed to the M
suffixed to the M
eeting ID to create the aliases rather than using the MCU’s prefix settings. The MCU’s
SIP registar domain setting is found in
Settings
>
SIP
of the MCU’s web interface.
The resulting computed aliases to be used by Cisco TMS are listed in the
View Settings
page for the
MCU in
System Navigator
.
ISDN Calling
An MCU can be accessible for ISDN dial in and out if a gateway is configured for the IP Zone assigned to
the MCU. Call routes will be via the gateway’s call prefixes and DID number. If the setting Enable ISDN
Gateway DID Mapping under
the MCU. Call routes will be via the gateway’s call prefixes and DID number. If the setting Enable ISDN
Gateway DID Mapping under
Extended Settings
for the MCU in
System Navigator
is enabled, dial in
ISDN call routes for the MCU will use those ISDN numbers rather than the gateway’s DID number. Which
ISDN numbers to use
ISDN numbers to use
should be based on your network’s dial plan and translations. Handling of routing
or translation of those ISDN numbers to the actual conference aliases must be provisioned in your
network’s dial plan and is not configured by enabling this setting.
network’s dial plan and is not configured by enabling this setting.
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 tr
aditional ‘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
Or
HTTPS*
Or
HTTPS*
TCP
TCP
TCP
80
443
443
Outbound
SNMP (optional)
UDP
161
Inbound
* Only used when Secure-Only Management is enabled, otherwise provisioning/feedback/phonebooks
must use HTTP for connections to Cisco TMS and HTTP must not be blocked on the network.
must use HTTP for connections to Cisco TMS and HTTP must not be blocked on the network.
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.