The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco recommends that you use the Cisco TelePresence Management System (TMS) for scheduled calls that you want to record with the Content Server. The TMS is aware of Content Server capabilities so that resource conflicts are resolved at the time of the scheduling. TMS 12.2 or higher can be used to schedule recording calls on a version 3.3 or higher Content Server.
There is no guarantee that ad hoc recording calls (unscheduled calls) can connect. Successful connection depends on the number and type of other recording calls that are active when users make their calls. We recommend that a Content Server that is managed by TMS should not be used for ad hoc recording calls.
You only need to perform this procedure once for each Content Server that you add to TMS. To add the Content Server to TMS, do the following:
Step 1 In the Content Server administrative web interface, enable the Content Server API:
a. From the Management tab, go to Configuration > Site settings .
b. In the API section, check API enabled .
Note If you have not already, change the API password from the default to a strong password.
Step 2 Staying in the Content Server administrative web interface, configure the Content Server:
Note If you use a group-owned recording alias (AD or LDAP), users will not be able to choose the recording alias in the TMS interface.
If the Content Server is part of a cluster, ensure that the frontend address in Site settings is set to the network load balanced address for the cluster; otherwise, links to recordings that are generated by TMS might not work.
a. From the Management tab, go to Configuration > Groups and users . Add a user with a site manager role and with the username api-admin.
b. Create a personal recording alias—for example, with the name TMS Alias—and set the owner to api-admin.
c. Create two live and three non-live dedicated TMS-only recording aliases. Only those aliases are available to TMS for scheduling.
Step 3 Add the Content Server (or Content Server cluster) to TMS. For more information, read the TMS online help.
To use TMS to schedule recording sessions on the Content Server, do the following:
Step 1 In the TMS web interface, go to Booking > New Conference .
Step 2 In the advanced settings section, choose a recording alias.
Step 3 Save the scheduled session. TMS will provide a link to view the recording.