Cisco Cisco TelePresence Management Suite (TMS) Version 15 Document
Conferencing Products
Cisco TelePresence Server
At a glance
TMS version tested
13.2.1
Product status
Active
Product software versions -
tested
tested
2.2(1.54)
2.3(1.50)
2.3(1.50)
Product software versions -
target
target
2.2, 2.3
Cisco TelePresence Server in this section refers to the TelePresence Server 7010 and MSE 8710 series
of MCUs and their model variants.
of MCUs and their model variants.
Configuration Requirements
The following configuration requirements must be met for the device to be managed by Cisco TMS in the
traditional ‘Managed by Cisco TMS’ mode:
traditional ‘Managed by Cisco TMS’ mode:
Cisco TMS must be provided a username and password of an account on the MCU that has
administrator privileges.
administrator privileges.
HTTPS and/or HTTP service must be enabled on their default ports
The following settings are required, but can be configured automatically by Cisco TMS after the device is
added to Cisco TMS if Enforce Management Settings is enabled (recommended)
added to Cisco TMS if Enforce Management Settings is enabled (recommended)
feedback receiver URL - must be set to point to the Cisco TMS server. This setting is not
accessible via the device’s web interface but will be configured automatically when the device is
added to Cisco TMS
accessible via the device’s web interface but will be configured automatically when the device is
added to Cisco TMS
Conference Aliasing
Note: It is important that aliases are configured prior to opening the MCU for scheduling by users. If you
change the aliases used by Cisco TMS for the MCU, existing scheduled meetings that use that MCU will
need to be rebooked by editing the existing conference to update the conference to the new aliases.
change the aliases used by Cisco TMS for the MCU, existing scheduled meetings that use that MCU will
need to be rebooked by editing the existing conference to update the conference to the new aliases.
Aliases used for conferences created by Cisco TMS on the MCU are based on the Meeting ID settings
defined for the MCU in
defined for the MCU in
System Navigator
. One alias is computed for each possible conference the MCU
could host, up to the total number of ports in the MCU.
Meeting IDs are defined per MCU in
System Navigator
under
Extended Settings
for the system. The
First Meeting ID value is used for the first alias, and each additional alias is created by incrementing the
alias by the Meeting ID step value. The computed Meeting IDs are used as the H.323 alias to register for
conferences by Cisco TMS scheduling.
alias by the Meeting ID step value. The computed Meeting IDs are used as the H.323 alias to register for
conferences by Cisco TMS scheduling.
SIP aliases are created using the same Meeting ID settings in Cisco TMS, but the SIP Outbound domain
is suffixed to the Meeting ID to create the aliases
is suffixed to the Meeting ID to create the aliases
. The MCU’s SIP Outbound domain setting is found in
Configuration
>
System Settings
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
.
For dial-in for conferences to function, the Register With Gatekeeper and Conference SIP Registration
settings under
settings under
MCU Settings
must be enabled on scheduled conferences. These are enabled by default
in Cisco TMS, and their default value for new conferences is managed in the
Extended Settings
page for
the device in
System Navigator
.