Configuring site settings
Cisco TelePresence Content Server 4.1 printable online
address. Changes to this page are not
saved if a connection cannot be made to
the specified address or it is not that of this
Content Server.
conferences page and the conference
URL displayed on the Edit conference
page. Otherwise links to conferences
use the address that you typed in the
browser URL to log in to the Content
Server.
settings
status
Displays the status of Content Server
registration with the gatekeeper (registered
or not registered).
Click View all gatekeeper
registrations
to display a page showing
all the system and Recording alias
registration details. See
Displaying
gatekeeper registrations.
enabled
Select to register with the gatekeeper.
Enter the Gatekeeper address, an
H.323 ID and/or an E.164 alias and
choose the Registration mode.
The gatekeeper must be enabled for a
cluster – it is not possible to disable the
gatekeeper functionality.
discovery
Manual gatekeeper discovery means
that the Content Server registers with
one specific gatekeeper, identified by its
IP address or fully qualified domain
name.
The IP address or DNS name of the
gatekeeper.
Other systems can call the Content Server
using the H.323 ID if the Content Server is
registered to the gatekeeper. The
Recording alias specified in the Default
Recording aliases below is used for the
If the Content Server is in a cluster, its
H.323 ID is not set here but in the
server overview page.
Other systems can call the Content Server
using the E.164 alias if the Content Server
is registered to the gatekeeper. The
Recording alias specified in the Default
Recording aliases below is used for the
call.
If the Content Server is in a cluster, its
E.164 alias is not set here but in the
server overview page.
Choose to register the Content Server as a
Terminal or as a Gateway.
If you select Gateway enter the H.323
gateway prefix and the
prefix. The registration mode for a
cluster must be Gateway.
prefix
If registered as a gateway, this prefix must
be entered before the H.323 ID of a
Recording alias when calling the Content
For a cluster, enter non-live and live
H.323 and E.164 gateway prefixes. The
prefixes you enter cannot be subsets of
each other; make sure they are unique
and that they follow the dialing plan set
up on your VCS. The non-live gateway
prefix will be used for Recording aliases
with no live streaming outputs; the live
gateway prefix will be used for
Recording aliases with live streaming
prefix
If registered as a gateway, this prefix must
be entered before the E.164 alias of a
Recording alias when calling the Content
Server.
