Computer Hardware User Manual

27
The name that users will see on auto attendant
screens and on the MCU's web interface.
Conference names must be unique; conferences
cannot share names.
Only scheduled conferences have a configurable
Name; ad hoc conferences do not have one.
Additional information about the conference,
which can assist users joining conferences.
Use the description to provide more detailed
information about the conference than the name
alone conveys.
This is an optional field for scheduled
conferences; ad hoc conferences cannot be given
a description.
The unique identifier used for dialing in to the
conference (as a chairperson participant) using an
auto attendant or through an H.323 gatekeeper or
SIP registrar. This number can also be used to
stream the conference from the Streaming-only
interface. For more information about
chairpersons and guests, refer to Using IDs and
PINs.
When connected to an auto attendant,
participants can join a conference by typing its
numeric identifier.
If you plan to allow audio-only participants, then
you will need to enter either a Numeric ID or a
Guest numeric ID.
If H.323 gatekeeper registration is enabled for a
conference, the MCU attempts to register the
conference with an E.164 telephone number,
which is comprised of the Registration prefix and
the numeric identifier.
If SIP registration is enabled for a conference,
then the Numeric ID is registered with the SIP
registrar.
Conferences that are simultaneously active must
not share a Numeric ID. For example, a conference
on a Tuesday and a conference on a Thursday can
share a Numeric ID, whereas two permanent
conferences cannot share a Numeric ID. The same
number can be used for the Guest numeric ID, if
there are two different PINs. Additionally,
because the numeric identifier is used in
gatekeeper registration, conferences and auto
attendants cannot share a numeric identifier
value.
For more information, refer to Using IDs and
PINs.
For ad hoc conferences created via the auto
attendant, the number allocated by the
conference creator becomes the Numeric ID. If ad
hoc conferences are registered with the
gatekeeper (and for this to work, the Register ad
hoc conferences with gatekeeper control must be