
19
D13898.08
MAY 2009
TANDBERG
CONTENT SERVER
ADMINISTRATOR GUIDE
Table of
Contents
Introduction
Installation
Quick Setup
TCS
Administration
Backing up and
Restoring
Administrator
Settings
Conference
Setup
View
Conferences
Appendices
Select
Gatekeeper Enabled
and enter the
Gatekeeper address
. You can choose to
register the Content Server as a Terminal
or a Gateway. If you select
Gateway
registration
, you will need to enter H.323
and E.164 Gateway prefixes.
Go to the
Administrator Settings
>
Site
Settings
to set the
System Name
for the
Content Server.
Note:
The System Name is used by TMS
to identify the Content Server.
Basic H.323 Services Setup
Step 1 - Initial Setup
About Basic H.323 Services
A quick basic setup of your TANDBERG Content
Server includes:
1.
Setting up H.323 services via the Content
Server interface.
2.
Making a test call recording.
3.
Changing the administrator password and
setting up server date and time on the
Windows Server.
Start a Web browser and enter the IP
address of the Content Server. You can
use either HTTP or HTTPS. HTTPS is
recommended for administrative access.
When prompted for login, enter the
username
administrator
and
password
TANDBERG
Go to
Conference Setup
>
Recording
Alias Options
. Edit the E.164 aliases
and H.323 IDs for the default Recording
Aliases and save.
Save
Site Settings
. Stay on the page to
verify if gatekeeper registration has been
successful.
For more on setting the administrative
properties and user configuration, see
the
Administrator Settings
section.
For security reasons it is important to
change the password for the default local
administrator account as described in
the
Windows Server Setup
section, as well as the
password for the API (if the API is enabled).
You can register the Content Server with
either gatekeeper or border controller.
For simplicity in this document we’ll use
gatekeeper to refer to either device.
Make sure that the E.164 aliases and H.323
IDs unique on your network are valid for
your gatekeeper or border controller.
By default, the Content Server’s H.323
ID is set to the machine name, eg.
TANDBERG-<random number>. The H.323 ID of
a live Recording Alias is set to
Live
<
machine_
name
> and the H.323 ID of an on demand
Recording Alias is set to
OnDemand
<
machine_
name
>. If upgrading from S2, the machine
name will be replaced by the serial number.
!