Using tms to schedule calls, About tms scheduling, Creating a dedicated tms alias – TANDBERG 1D13898.07 User Manual
Page 97: Scheduling calls with tms, Using, Tms to schedule calls, Section
97
D13898.07
NOVEMBER 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.
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.
For more information on TMS integration, refer to the
TANDBERG Management Suite Administrator Guide or contact
your TANDBERG representative or authorized reseller.
Scheduling Calls with TMS
TMS 11.8 and above offers full support for
Recurrent meetings. The Screenshot 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 dropdown menu.
The screenshot shows the Recording
dropdown menu in TMS 12.0, with aliases
arranged by Content Server. .
About TMS Scheduling
Creating a Dedicated TMS Alias
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.
From the Add Users page on the Content Server, add a
1.
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
2.
owner set to
: api-admin
. Do NOT check the System
Alias checkbox—the TMS alias must be a Personal
alias.
You need to create two live and three non-live
3.
dedicated TMS-only Recording Aliases. Only those
aliases will be available for booking by TMS.
Content Server v.3.x 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.