Cisco Cisco TelePresence MCU 4510 Maintenance Manual
settings of each template to the requirements of a particular conference. A template can be moved by
selecting a new parent template in the
selecting a new parent template in the
Template configuration page
.
Templates can also be deleted. The parent of a deleted template becomes the parent of any child template
below the deleted template.
below the deleted template.
The MCU supports up to 100 templates in total.
When you add a new scheduled conference from the
Conference list
page, you select the template that you
want the conference to use from a drop down list. The selected template provides the settings that appear on
the
the
Add conference
page which you can then change if required.
The ad hoc conference template provides the configuration for all ad hoc conferences. You can alter any of
the conference settings during the conference.
the conference settings during the conference.
For information about the conference configuration settings, refer to
which
lists all conference configuration settings.
Related topics
n
n
Conference ownership
Each scheduled conference (i.e. conferences that are configured via the web interface with a start time and,
optionally, a duration and repetition) has an associated owner. This owner is the ID of a configured user, and
normally corresponds to the user who scheduled the conference.
optionally, a duration and repetition) has an associated owner. This owner is the ID of a configured user, and
normally corresponds to the user who scheduled the conference.
Scope of conference ownership
Conference ownership affects only web interface control of conferences - in particular, it plays no part in
validating video conferencing endpoints' attempts to join conferences when they connect to the MCU via
H.323 or SIP. Restricting conference entry in this situation is accomplished via conference (or auto
attendant) PINs, as before.
validating video conferencing endpoints' attempts to join conferences when they connect to the MCU via
H.323 or SIP. Restricting conference entry in this situation is accomplished via conference (or auto
attendant) PINs, as before.
User privileges
The actual implications of conference ownership depend on the privilege of the user; specifically:
Privilege level
Effects of conference ownership
n
administrator
n
conference
creation and full
control
creation and full
control
Users with these privilege levels are able to create and own conferences, and are able to
exercise full control of all conferences.
exercise full control of all conferences.
n
conference
creation and
limited control
creation and
limited control
Users with these privilege levels are able to create and own conferences. They have full
control of conferences they own, and limited control of conferences owned by other users.
control of conferences they own, and limited control of conferences owned by other users.
Cisco TelePresence MCU Series 4.5 Online Printable Help
Page 58 of 278
Managing conferences
Adding and updating conferences