Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Feature Support
Personal
Multiparty Basic
Multiparty Basic
Personal Multiparty Advanced
Collaboration Meeting Rooms
provisioned by Cisco
TMSPE/Rendezvous conferences in
TelePresence Conductor
provisioned by Cisco
TMSPE/Rendezvous conferences in
TelePresence Conductor
Yes
Yes
Ad hoc escalated conferences
Yes
Yes
TelePresence Conductor scheduling
in Cisco TMS
in Cisco TMS
Not currently supported
Maximum conference size
Up to 4
participants
participants
Limited by the conference bridge capacity, concurrent
usage, and the deployment's total number of Screen
licenses included in Personal Multiparty Advanced
license packs.
usage, and the deployment's total number of Screen
licenses included in Personal Multiparty Advanced
license packs.
Number of concurrent conferences
per named host
per named host
1
1
Requirement that host is present in
the conference
the conference
Yes
Yes
Maximum video resolution
HD (720p 30fps)
Limited only by conference bridge capabilities
Maximum content quality
1280 x 720p 5fps Limited only by conference bridge capabilities
Multiscreen support
Only one screen
of multiscreen
endpoints is
displayed
of multiscreen
endpoints is
displayed
Yes
Table 2 Differences between Personal Multiparty Basic and Personal Multiparty Advanced
The restrictions listed in the table above are not enforced automatically, but must be configured on TelePresence
Conductor and in the CMR template.
Conductor and in the CMR template.
■
Instructions for configuring CMR templates in Cisco TMSPE are provided below.
■
To configure TelePresence Conductor ad hoc conferences to work with either license, see
Applying License Restrictions to CMR Templates
for instructions on configuring Cisco TMSPE for use with
TelePresence Conductor and Collaboration Meeting Rooms.
Replace the task
template that complies with Personal Multiparty Basic or Personal Multiparty Advanced:
1.
In Cisco TMS, go to Systems > Provisioning > Users.
2.
Under Collaboration Meeting Room Templates, click New Template.
3.
Give the template a name, and select the appropriate TelePresence Conductor.
4.
Select a Service Preference that contains conference bridges of type TelePresence Server.
5.
Create a SIP alias pattern. We strongly recom mend basing the pattern on username, which is always unique, to
avoid alias conflicts.
avoid alias conflicts.
49
Cisco TelePresence Management Suite Provisioning Extension with Cisco Unified CM Deployment Guide