Using tms to schedule calls, About tms scheduling, Creating a dedicated tms alias – TANDBERG S3.1 User Manual
Page 93: Scheduling calls with tms, Using, Tms to schedule calls, Section
93
D13898.06
MAY 2008
TANDBERG
CONTENT SERVER
ADMINISTRATOR GUIDE
Creating a Dedicated TMS Alias
Using TMS to Schedule Calls
Creating Conferences (continued)
It is possible to schedule calls to be recorded by the
Content Server through TMS (TANDBERG Management
Suite).
In order to use TMS to book recordings on the Content
Server, you need to:
Enable the API in
1.
Content Server Site Settings
>
API
Add the Content Server to TMS
2.
If the Content Server is registered to a gatekeeper in
Gateway mode, users booking a conference in TMS 11.8
and above can choose from a range of System Aliases
and their Personal Recording Aliases. No further special
configuration is necessary on the Content Server side.
If the Content Server is registered to a gatekeeper in
Terminal mode, only System Aliases and dedicated
Personal Aliases (with the owner set to api-admin) will
be available for recording conferences. See below for
configuration notes.
Scheduling Calls with TMS
Graphic shows the user booking a series of
recurrent meetings through TMS.
Current meetings that are recorded with the
TANDBERG Content Server will be displayed
in the Live Conferences List when they
are occurring and when completed will be
available from the Recorded Conferences
List.
A user who logs in to TMS 11.8 or above
with their user name will see their own
Personal Recording Aliases and any System
Aliases in the Recording List of Aliases.
This graphic displays the Personal
Recording Alias Ross and the two System
Aliases, 102 Default Live and OnDemand
and 102 Default OnDemand only.
TMS 11.8 and above offers full support for
Recurrent meetings.
About TMS Scheduling
Creating a Dedicated TMS Alias
1
From the Add Users page on the Content Server, add a new
user with the username
api-admin.
The user needs to have
Administrator privileges.
Create a new recording alias e.g. TMS Alias, with the owner
set to
: api-admin
Do NOT check the System Alias checkbox—the TMS alias
must be a Personal alias.
You need to create 2 live and 3 non-live dedicated TMS-only
Recording Aliases. Only those aliases will be available for
booking by TMS.
For more information on TMS integration, refer to the
TANDBERG Management Suite Administrator Guide or contact
your TANDBERG representative or authorized reseller.
1) When the Content Server is in Terminal mode
Content Server v.3.0 is backwards
compatible with TMS 11.7 for
booking a Transcoding call, using
a dedicated TMS-only Recording
Alias. Archiving call support is not
available.