Cisco_Systems_Server

Logging in to the web interface

What you see when the Cisco TelePresence Content Server web interface opens depends on whether guest access is enabled:

???If guest access is enabled, you see the list of recorded conferences that guest users have permission to see. As the guest user you can play some or all of these conferences.

???If guest access is not enabled, you are prompted to log in (also called authenticating). After you have logged in, the list of recorded conferences is displayed.

To do more than watch conferences you need to log in, and what you can then do depends on your role . The local administrator and other users who are also site managers have full privileges. For more about roles, see Understanding users and groups.

To log in:

1.Using a web browser, enter the host name or IP address of the Content Server.

2.Click Log in in the top right of the window.

3.Enter your user name and password. Contact your local site manager for more information.

The Recorded conferences list opens and the appropriate menus for your role are displayed at the top of the page.

Supported browsers, plugins & platforms

Cisco recommends that you use software mentioned on this page to ensure that you can watch/stream conferences successfully.

Supported browsers

Ensure that you have JavaScript, ActiveX and media plugins enabled in your browser.

The Conference play properties check determines the conference formats that you can watch on your

computer and displays this information in your Preferences . If you have installed/uninstalled a plugin, but the Content Server has not been automatically updated, go to Preferences and click Recheck

properties.

* (i) Microsoft Silverlight plugin for MacOS is available as a free download at the time of publishing from http://silverlight.net/

(ii) The Content Editor is not available on Apple Macintosh computers using Silverlight for conferences in Windows Media format.

** The following Microsoft Windows Media Player is required to display movies in Windows Media ?? WMV format in Mozilla Firefox, and is available as a free download at the time of publishing from http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx

Recommended player versions

Windows Media Windows: Windows Media Player 9.x or higher

Understanding the conference lists

Conferences (recorded calls) are displayed in three lists. Your access to each of the lists depends on whether you have logged in, and if you have, your user role . Which conferences you see in the lists

depends on the permissions set on the conference. (Permissions determine who can view or edit the conference.) To display the Conference lists, go to View Conferences.

Live conferences list

This list shows calls that are currently being recorded. When the call completes, the resulting conference is transferred to the Recorded list. If there are outputs to transcode, the conference also appears in the Pending queue. This page refreshes automatically every 10 seconds.

Pending queue

The Pending queue shows conferences for which the Content Server is currently processing (transcoding) the outputs. The number and types of output depend on the Recording alias used for the conference, or what outputs have been selected in the Manage Outputs page. (Also see Understanding recording configurations.) This page refreshes automatically every 10 seconds.

Recorded conferences list

The Recorded conferences list shows conferences for which the call has completed. If the Content Server is still processing (transcoding) the outputs for a conference, then the conference is listed even

though it cannot be watched or downloaded, and the icon is displayed beside it. When processing is complete, the appropriate links are displayed - see below. This page does not refresh automatically.

Common features

These pages have a number of common features:

???Category:

Select a Category from the drop-down list to only see conferences belonging to that Category. Selecting All displays all the conferences that you have access to. The number of conferences that you can view in each Category is displayed in brackets after the name in the drop-down list.

???Search:

Enter a conference name, description, speaker, location or keyword to search for a particular conference. (These are part of the conference information entered from the Recording alias used during the call, and can be edited by the conference editors at any time.)

???Sort by (Not available for Pending conferences):

Select a sort to rearrange the conferences in the list. By default, conferences are sorted by date, with the most recent one at the top. (The Pending list shows the order in which conferences will be processed and their outputs produced. Conferences that are currently being processed are highlighted.)

???Page: If the number of conferences is such that there is more than one page in the list, the Page links allow you to move between pages.

???Show only conferences that I can edit: Displayed for conference editors only. This check box

allows you to display the list showing only conferences that you can edit, rather than including those that you can only play, download and share.

In addition, if the following links are displayed for a conference, you can:

???Play/Play options: see Watching a conference in the Content Server web interface . Click Play

to have the Content Viewer choose the best stream for you to view based on your bandwidth. To manually choose a conference size or bit rate to play, choose a link under Play options.

o If these links do not appear, streaming outputs have not been created for the conference.

o If you see a icon beside the Play button and Play is disabled, you do not have the appropriate media players installed on your computer to watch the conference. Click on the icon to find out which players you are missing and see your preferences for more information. If you see the icon but you can still play the conference, then your

Understanding the conference lists

bandwidth has been determined to be at a lower rate than the bandwidth of the conference. You can still play the conference, but you may experience playback problems. For more information about your bandwidth, see your preferences .

???Download: see Watching a conference on your computer and Watching a conference on a portable device (iPod or Zune). The download link only appears if the appropriate download output formats have been produced for a conference.

???Share: see Sending a link so others can watch a conference . The Share link only appears for conferences with streaming outputs because the link opens the Content Viewer (see Watching

a conference in the Content Server web interface ). The link provided can be copied and pasted in to your email application or you can click Email to open a new email in your email application with the link to the conference included. If the conference requires a password for security, a prompt is displayed when the link is used.

???Edit: see Editing conferences - overview.

Watching a conference in the Content Server web interface

The Content Viewer is opened when you ask to stream/play a conference.

Watching a conference

To stream a conference using the Content Viewer: go to the appropriate View Conferences page and click the thumbnail, the conference name or the Play button. The conference is displayed at the best quality for your connection, as determined automatically or entered manually in Preferences . The conference indexes are displayed, if there are any. For information about the controls, see the appropriate section below.

The availability of the Content Viewer depends on:

???Whether the conference has outputs suitable for streaming. If no outputs are available, the Play button does not appear in the Conference list and the conference thumbnail and title are not links. Conference editors can change a conference's outputs using the Manage Outputs page.

???The format of the conference outputs (Windows Media, MPEG-4 for QuickTime, MPEG-4 for Flash or Real Media) and the correct player being installed on your computer. If you are missing the correct players, the Play button is disabled and appears beside it. Click on the exclamation mark icon to find out which players are missing. For more information about your available players, see your Preferences .

???Your bandwidth (internet speed) and the bandwidth of the conference. If your bandwidth has

been determined to be at a lower rate than the bandwidth of the conference, then appears beside the Play button. You can still play the conference, but you may experience playback problems. For more information about your bandwidth, see your Preferences .

Notes:

Output formats depend on the Template used for the conference, and can be changed by conference editors in the Manage Outputs page. PC users are able to view outputs in the following formats: Windows Media, MPEG-4 for QuickTime, MPEG-4 for Flash and Real Media. On an Apple Mac, Windows Media is supported with the Silverlight plugin, and MPEG-4 for QuickTime and MPEG-4 for Flash are also supported. See Supported browsers, plugins & platforms to check the supported formats for different browsers and platforms.

The Template allows a maximum of two bit rate/resolution combinations per format so that you can choose the bit rate to watch rather than having the Content Server chose it for you. Click Play options

and choose a conference bit rate to play in the Content Viewer. This may be useful for example if the same conference is watched by users on a fast network and as well as users with only a dial-up

connection.

Using the Content Viewer

If the conference includes a Dual video stream, the editor of the conference can choose how the main and dual video is displayed: as switching (main video steam then the dual video steam when it is activated), joined (main and dual video steams side by side as one stream), two videos (main and dual video steams separately) or picture-in-picture (big dual video steam with the main video steam in a corner). Otherwise, you just see the main video stream.

Watching a conference in the Content Server web interface

The Content Viewer playing an example conference with only main video:

The Content Viewer playing an example conference with main and dual videos and an index:

???The Next layout button changes where the Content Viewer shows the main and dual videos (if a separate dual video is available), and the index (if a conference editor has added one). This button is not displayed if it is not possible to switch layouts.

???The Slide list button displays the still images taken of the dual stream for conferences with Audio-only or Small outputs. Clicking on a slide in the list advances the conference to that point in the conference. Clicking the slide list icon again removes the slide list.

Watching a conference in the Content Server web interface

Note: Check Port information to make sure that the correct ports for streaming are not blocked; otherwise, the streaming media will fail to load.

Using the Content Viewer with Silverlight

The Content Viewer initially displays a Play button in the center: click this to watch the conference. The controls at the bottom of the window fade after a few seconds but placing the mouse in the control area redisplays them.

If the conference includes a dual video stream, the editor of the conference can choose how the main and dual video is displayed: as switching (main video steam then the dual video steam when it is activated), joined (main and dual video steams side by side as one stream), two videos (main and dual video steams separately) or picture-in-picture (big dual video steam with the main video steam in a corner). Otherwise, you just see the main video stream.

???Conference indexes are displayed by clicking on the Index button displayed to the right of the conference duration. Clicking on an index advances to that point in the conference.

The Slide list icon displays the still images taken of the dual stream for conferences with audio- only or Small outputs. Clicking on a slide advances the conference to that point in the conference. Clicking the Slide list icon again removes the slide list.

Note: Microsoft Silverlight uses port 8080 for streaming from the Content Server. If that port is blocked, streaming media will fail to load. For more information, see Port information .

Watching a conference on your computer

If a conference has downloadable outputs, you can download the conference to your computer. This may be better than streaming the conference, especially if you have a maximum download limit on your internet connection. After the conference has been saved on your computer, you can watch it as often as you like.

Site managers can specify that downloadable outputs should be created in the Template used for a

conference before the conference is created. After the conference has been recorded, site managers or conference editors can add outputs by clicking Edit and then Manage Outputs for the conference.

See Managing conference outputs.

Conferences without downloadable outputs do not have the Download link in the View Conferences > Recorded page.

To download the conference:

1.Go to View Conferences > Recorded page and click Download for the conference.

2.Select the required format and size of conference.

3.Click Save and browse to the directory in which you want to save the conference. Click Save.

4.On your computer, go to the directory used in the previous step and double-click on the conference to watch it.

The conference is displayed in the appropriate viewer for its format; that is, in the program that is the default to play that type of media file on your computer. For example, if QuickTime is set up to always play .mp4 files and you download an MPEG-4 for Flash file, then it will play in QuickTime if you double-click on the file.

Watching a conference on a portable device (iPod or Zune)

If a conference has downloadable outputs suitable for portable devices, you can download the conference and then watch it on your iPod or Microsoft Zune device. You need to use a computer as an intermediary device and then load the conference to the iPod/Zune as you would any other file. After the conference has been loaded on the device, you can watch it as often as you like.

Site managers can specify that downloadable outputs should be created in the Template used for a

conference before the conference is created. After the conference has been recorded, site managers or conference editors can add outputs by clicking Edit and then Manage Outputs for the conference.

See Managing conference outputs.

To watch the conference:

1.Go to View Conferences > Recorded and click Download for the conference.

2.Select the required format: - one of iPod video, iPod audio, Zune video or Zune audio.

3.Browse to the directory on your computer in which you want to save the conference temporarily. Click Save.

4.From your computer, load the conference on to your portable device.

5.Play the conference on your portable device as you would any other file.

Sending a link so others can watch a conference

Click Share and then Email in the Recorded conferences page to share conferences with others. The Share link only appears for conferences with streaming outputs. (Note that the fact that you can watch the conference does not automatically mean that the person you send the conference link to will be able to watch it: this depends on the conference permissions.)

If the conference requires a password for security, a prompt is displayed when the link is used.

Note: The link uses the Frontend address specified in Site settings , or if it was not defined, the URL you typed in to your browser to log in to the Content Server.

Calling out to record

If your login account has creator privileges you can dial out to an endpoint and record the endpoint's camera view for the duration of the call as an ad hoc conference.

Scheduled - as opposed to ad hoc - conferences can be recorded using the Cisco TelePresence Management Suite (TMS) - see Using TMS to schedule conferences to be recorded on the Content Server and the TMS online help for more information. A maximum of five calls can be recorded (either scheduled or ad hoc) simultaneously and two of these can be streamed live.

To dial out and record a call:

1.Go to Conference setup > Create conference.

2.Complete the fields using the table below .

3.Click Place call.

4.To end the call, either hang up from the remote endpoint or system, or click End call.

Calling out to record

Conference permissions

One of:

???Allow access to all users, including guests: If Allow guest access is selected in Site settings , this field is displayed. If selected, all users including guests can view the conference.

???Allow access to all authenticated users: If Allow guest access is not selected in Site settings , this field is displayed. If selected, all authenticated (logged in) users can view the conference.

???Allow access to only these authenticated groups and users: If selected then only groups or users entered in the field below can view the conference. Enter all or part of the name or display name of the group or user - either one per line or separated by a semicolon. If only

part of a group or user name has been entered, then clicking Check access list or Place call adds all matching groups and

users to the list.

Note: After clicking Check access lists or

Place call , the users entered will have the following formats:

oLocal authentication mode: MACHINENAME\user.name

oDomain authentication mode:

DOMAINNAME (optional)\user.name

oLDAP authentication mode: user.name

All groups will be in the format group.name where the group name is expanded to the full LDAP name (for example, ???CN=group.name, OU=staff, DC=company, DC=com???).

Using TMS to schedule conferences to be recorded on the Content Server

Cisco recommends that you use the Cisco TelePresence Management System (TMS) for scheduled calls that you want to record with the Content Server. This is because TMS is aware of the Content Server's capabilities so that resource conflicts are resolved at the time of the booking. This is in contrast to ad hoc calls, either calling out to an endpoint or calls in to the Content Server: there is no guarantee that those calls will be connected; it depends on the number and type of calls happening when you place the call. Therefore, Cisco recommends that a Content Server which is managed by TMS should not be used for ad hoc calls.

To add the Content Server to TMS:

These steps only need to be performed once for each Content Server that you add to TMS.

1.Enable the Content Server API:

a.Go to Management settings > Site settings.

b.In the API section select API enabled.

c.Cisco recommends that you change the API password from the default to a strong password.

2.Configure the Content Server:

oIf 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 Recording aliases and their Personal Recording aliases. No further special configuration is necessary on the Content Server side for standalone Content servers.

a.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 conferences generated by TMS may not work.

oIf the Content Server is registered to a gatekeeper in Terminal mode, only System aliases and dedicated Personal Recording aliases (with the owner set to api-admin) are available for recording conferences. On the Content Server:

a.Go to Management settings > Add 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 the owner set to api-admin.

c.Create two live and three non-live dedicated TMS-only Recording aliases . Only those aliases will be available for booking by TMS.

3.Add the Content Server/Content Server cluster to TMS. For more information, read the TMS online help.

To use TMS to book conferences on the Content Server:

1.Go to Booking > New Conference.

2.In the Advanced settings section select a Recording alias .

3.Save the booking. TMS will provide a link to view the conference. For more information, read the TMS online help.

Editing conferences - overview

After a conference has been recorded, conference editors can update the conference as follows:

???Editing conference information and permissions: conference information is used to search for the conference in the Recorded conferences list. Conference permissions define who can view the conference and who can edit it.

???Managing conference outputs: how the conference is made available to users - the format and size of outputs and whether it is viewable in the Content Server interface, downloadable or distributed to Podcast Producer or iTunes U.

???Indexing, cropping & concatenating conferences in the Content Editor: delete unwanted portions of a conference or join two conferences together.

Site managers can edit all conferences.

Managing conference outputs

Site managers and editors of the conference can:

???Add new on demand outputs for that conference. The conference outputs will be added into the Offline Transcoding Queue for processing and transcoding will start when all the conferences higher in the queue have been processed. Note that the total number of outputs can now exceed the six permitted when a conference is created; however, adding outputs puts an added transcoding load on the Content Server and uses more disk space.

???Delete outputs that are no longer needed by deselecting them and clicking Save. Note that files sent to external servers, for example, Podcast Producer or QuickTime Streaming Server, are not deleted off those servers but this can be done manually, if required.

???Change previously chosen layouts, formats and sizes.

To manage outputs:

1.Go to View Conferences > Recorded conferences.

2.Click Edit and then select Manage outputs.

3.Update how you want to make the conference available by selecting the appropriate check boxes. Selecting a check box opens a section of the page:

o Outputs to view in the Content Server web interface o Outputs to download for portable devices

o Outputs to download for general purpose

o Outputs for distribution to Podcast Producer or iTunes U

4.Edit the fields for each opened section using the table below .

5.Click Save.

Indexing, cropping & concatenating conferences in the Content Editor

You can use the Content Editor to edit conferences that you are an editor of. Site managers can edit any conference. The Content Editor can:

???Add indexes and manage index points.

???Crop the conference by changing its start (in point) and/or end (out point).

???Concatenate conferences : that is, join another conference to the one already open in the editor. One example use of this is to remove a section in the middle of a conference by opening the same conference twice.

All changes are non-destructive; therefore you can change the in and out points for a conference, for

example, many times. Viewing the conference in the Content Viewer reflects the changes straight away. However, downloads need to be re-transcoded: click Save and close. This removes existing

downloadable outputs and replaces them with new ones when they have been transcoded.

Notes:

To open a conference in the Content Editor, the conference must have outputs that can be viewed in the Content Viewer.

You can use the Content Editor on an Apple Mac using MPEG-4 for QuickTime or MPEG-4 for Flash. The Content Editor is not available on the Mac for Windows Media conferences using Silverlight.

The Content Editor window

Open the Content Editor by going to View conferences > Recorded, clicking Edit for the appropriate conference and selecting Open content editor.

The top section displays the movies on the left and the Index options on the right with previously created Indexes displayed. Indexes are used to progress the conference to a specific point in the conference, making it easier for users to find where they want to watch in the conference. By clicking an item in the Index, the conference will start playing at that reference point.

Note: Indexes can only be added, deleted or renamed in the Content Editor, but they are displayed and can be used in the Content Viewer when watching the conference.

Indexing, cropping & concatenating conferences in the Content Editor

change the start and end points.

??? a Join recording

button to append another conference to this one.

Indexing a conference

Play the conference and pause it where you want an index, or click on the seek bar to jump to a point in the video, then click Add index. Type in a name and click Save and close.

Cropping a conference

To crop a conference, move the sliders to where you want the conference to start and stop and click

Save and close.

Removing a section in the middle of a conference

You may have recorded a conference that you are an editor of that has a break in the middle that you want to remove. This is how it is done:

1.Open the conference in the Content Editor as described above.

2.Click Join recording to show the list of conferences that can be joined to this one. Add the same conference again by clicking Join recording next to the conference name.

3.Click on the first thumbnail and then adjust the Out point of the original conference to the beginning of the section you want to remove.

When you join a recording, the conference thumbnails appear next to the conference controls. In the example image, the highlighted thumbnail is the original conference and the thumbnail of the joined conference is beside it.

4.Click on the second thumbnail and then adjust the In point of the 'joined' copy of the conference to the end of the section that you want to remove.

5.If required, add indexes to each conference and click Save and close.

6.Check the result in the Content Viewer .

7.If necessary, repeat the steps to make any final adjustments.

Indexing, cropping & concatenating conferences in the Content Editor

Concatenating conferences

To be able to join conferences, you must have edit access to both conferences (or have the site manager role ) and the conferences must have streaming outputs in the same format and size (for example, Windows Media, Medium) and the same dual video status: it is not possible to join two conferences if only one of them has a dual video stream.

To join two conferences:

1.Open the conference in the Content Editor as described above.

2.Click Join recording to show the list of conferences that can be joined to this one. Add a different conference by clicking Join recording next to the required conference.

3.If required, crop each conference.

4.If required, add indexes to each conference.

5.Click Save and close.

6.Check the result in the Content Viewer .

7.If necessary, repeat the steps to make any final adjustments.

Understanding recording configurations

The Content Server records calls and can produce the resulting conferences in a range of formats and sizes for users to watch or download. Conferences can be made available to all or selected users, and given information to make them easier for users to find. All this is controlled by a configuration called a Recording alias . See Displaying the Recording alias list .

If the system defaults are not suitable, then you can configure the following.

Recording aliases are created by the site manager. There are two types of Recording alias:

???System Recording aliases, which can be used by any user with a creator or site manager role .

???Personal Recording aliases, which have an owner. Recording alias owners must have a creator role and can edit certain parts of their Recording alias.

Cisco recommends that site managers create one or more Personal Recording aliases for each group or user with the creator role . See Adding & editing Recording aliases .

To record a call, users can:

???Use the Cisco TelePresence Management Suite (TMS), specifying a Recording alias to use to record a scheduled conference.

???Dial an address (H.323 ID, E.164 alias or SIP URI) of a Recording alias from an endpoint or remote system to create an ad hoc conference.

???Go to Conference setup > Create conference, select a Recording alias and dial out to create an ad hoc conference. See Calling out to record .

A Recording alias is used to create a conference: it defines several properties (see the diagram below):

???The Recording alias name that can be selected when scheduling a conference in TMS, or dialing out from the Content Server web interface.

???An owner. The owner must have a creator role and be added to the Groups & users list first. Owners can edit certain parts of their Recording alias. See Adding & editing Recording aliases for details of the properties that can be edited.

???Dialing addresses (H.323 ID, E.164 alias or SIP URI depending on how the gatekeeper and SIP settings are configured in Site settings ) used to call to Content Server and record using this Recording alias.

???A Template which determines output sizes and formats. Recording alias owners can select which Template they want to use in a Recording alias. Only site managers can add, edit or delete Templates. Templates may also contain Media server configurations which contain settings for where conference media is stored, and how it is streamed or distributed.

???A Call configuration that specifies call settings such as dual video stream support, supported call speeds, maximum call length, encryption, and advertised video and audio codecs. Only site managers can select a Call configuration for a Recording alias.

???Default conference information and a Category that is copied to conferences created with this Recording alias. The Category must be added to the Categories list first. Site managers and Recording alias owners should add as much default conference information as possible to make conferences created with this Recording alias easy to find.

Understanding recording configurations

???Default conference permissions that specify who can view and edit conferences created with this Recording alias. The groups and users specified must be added to the Groups & users list first.

When a conference is created, the following properties are copied from the Recording alias used to create it to the new conference:

???Live and on demand outputs from the Template. On demand outputs can be changed by conference editors or site managers in Manage Outputs after the conference has finished recording.

???Conference information and a Category that users can use to search and sort conferences. Conference editors or site managers can change the conference information at any time. The Category must be added to the Categories list first.

???Permissions that specify who can view and edit the conference. Conference editors or site managers can change the conference permissions at any time. The groups and users specified must be added to the Groups and users list first.

Storing recordings

The default location for media files is drive E:. You can change this to store files on a Network Attached Storage device (NAS), so that the recording capacity is not limited by the disk space on the Content Server. Then media will be recorded to a temporary directory on the Content Server before automatically being moved to the NAS. The Content Server streams the media from the NAS.

Cisco recommends using a NAS device built on the Windows Storage server that is also Windows Hardware Quality Lab certified. The file sharing protocol used by the Content Server to the NAS is Microsoft SMB.

Notes: For best performance, Cisco recommends that the NAS used is a device dedicated to media storage. Running applications such as domain controllers, databases or external streaming servers on the same device may result in errors.

The Content Server must be added to the same domain as the NAS.

Changing the storage location to use Network Attached Storage

Ensure you have enough time to complete the operation. The TCS Wizard copies all media files referenced by the Content Server database from the local E: drive to the external storage location. This takes several minutes, depending on how much media is recorded.

To change the media storage location from the default E: drive to a NAS

WARNING: Using the wizard to move media from the local E: drive to the external storage location does not move any media files which are not associated with the Content Server???s database. That

includes orphaned temporary files not used in any conferences, .tcb import or export files, and files placed in the data folder by users. These files will not be moved and will be deleted. However when

you use the TCS Wizard to move media between one NAS location and another, or from the NAS back to a local Content Server disk drive, these files will not be moved, and the TCS Wizard will not

delete them from the NAS.

1.Back up the Content Server.

2.Add the Content Server to the same domain as the NAS. If you add the Content Server to an existing domain, you need to define a separate security policy for the Content Server, otherwise the existing security policies may prevent the server from functioning correctly. Please contact your authorized Cisco reseller for details of the recommended security policy settings.

3.Choose or create an account in the domain that IIS (Microsoft's Internet Information Server) on the Content Server will use to access the share on the NAS. This domain account needs to have both administrative rights on the Content Server and permissions over the NAS share. It can have any name - in this topic we use MYDOMAIN\TCSNASUSER.

Note: The TCS Wizard can run under the following user accounts:

???a domain administrator account

???the special domain account, MYDOMAIN\TCSNASUSER

???the local administrator account

Storing recordings

4.Configure the NAS, if you have not already done so.

a.Log on to your NAS using Windows Remote Desktop Connection .

b.Set up a shared folder.

c.Set permissions on the share to allow the Content Server and the shared account (MYDOMAIN\TCSNASUSER in this example) full control over the share. Right-click on the share and select Sharing and Security... Click Permissions. Click Add.

d.Click Object Types. Select Computers and click OK.

e.Enter <Content Server Server Name> (as registered in the domain). Click Check Names and OK.

f.Enter the shared account name (MYDOMAIN\TCSNASUSER). Click Check Names and OK.

g.Give the Content Server and the shared account (MYDOMAIN\TCSNASUSER) full control over the share.

h.Click the Security tab. Click Add. Repeat steps d to g to give the Content Server and MYDOMAIN\TCSNASUSER full control of the NAS share.

5.Log in to the Content Server using Windows Remote Desktop Connection .

6.Run the TCS Wizard.

7.Click Alternate Storage [NAS] Wizard.

If there are live calls, the wizard prompts you to end all calls. It also puts the Content Server in Idle mode, so that no new calls or transcoding jobs are accepted while the wizard is running. The wizard must complete (or be cancelled) in order to return the Content Server to normal operation (Online mode). This happens automatically.

8.Follow the on-screen instructions.

a.Enter the remote server information for the new NAS location in the format: \\ServerName\ShareName\. ServerName must be entered as the DNS name, not IP address, otherwise the wizard will fail.

b.At the Content Server Checks step, confirm that the Content Server has been backed up and that anti-virus software has been stopped (if any has been installed). If this is not the case, cancel the wizard and complete those actions, then run the wizard again. Your system will not have changed if you cancel.

c.The NAS: Test Result step displays information about your intended setup. If all the tests have been successful, click Configure to configure the Content Server and move existing

media files from the NAS back to the E: drive. This may take several minutes depending on how much media has to be moved. You may also click Finish to exit the wizard without making any changes at this step. If any tests failed, you cannot continue. Check the external NAS configuration and the information you entered and try again.

9.When the process is complete, click Finish. No server restart is necessary. TCS Wizard logs are available in E:\logs\SetupUtility. To check your new media location, go to Management Settings > Server Overview.

Note: If the password for the domain account that the Content Server uses to access the NAS share changes subsequently, complete step 4 below. If you want to use another domain account, complete all the steps:

1.Add the new domain account to the Administrators group first: go to Start> Administrative

Tools> Computer Management.

2.Select System Tools > Local Users and Groups > Groups.

3.Double-click Administrators and add the new domain account to the Administrators group (see step 3 above).

4.In the TCS wizard select the NAS wizard and then use the Update user account option to update the Content Server. Follow the on-screen instructions.

Storing recordings

Changing the storage location back to the default storage location

You will not be able to complete this process if the media size on the NAS is larger than the space available on the E: drive. Check the data folder size on the NAS first and, if you want to proceed, delete some conferences using the Content Server web interface if your NAS data folder is larger than space available on the E: drive.

Follow the steps in the previous section (Changing the storage location to use a Network Attached Storage) from step 5 onwards but select Return media to local storage in the wizard and enter the

new location in which to store media.

Changing the storage location from one NAS location to another

You will not be able to complete this process if the media size on the original NAS location is larger than the space available on the destination drive. Check the data folder size on the NAS first and delete some conferences if necessary.

Follow the steps in the previous section (Changing the storage location to use Network Attached Storage) from step 5 onwards but select Move media to a different network location in the wizard and enter the new location in which to store media.

Displaying the Categories list

A conference can be assigned a Category to make searching for conferences faster. Six Categories come with the Content Server: Announcements, Education, General, Meetings, News and Training. Each Category has a name and can have a description.

Site managers can display the Categories list: go to Management settings > Categories. From the Categories list, they can:

???Edit existing Categories : click Edit for the Category that you want to change.

???Delete Categories: select the Category and click Delete selected. (If you delete a Category that is in use in a conference or Recording alias, the conference or Recording alias then has no Category.)

???Add new Categories : click Add category. There is no limit on the number of Categories that can be added.

Recording aliases can be assigned a Category so that any conference created using the Recording alias is assigned that Category.

Note: In the View Conferences pages, guests (unauthenticated users) and users with the viewer or creator role who have logged in only see a Category in the drop-down list if there is a conference in that Category that they have permissions to see. The number of conferences in each Category is

displayed in brackets. All Categories are displayed to site managers.

Adding & editing Categories

Administrators can add and edit Categories. A conference can be assigned a Category to make searching for conferences faster in the View conferences pages.

To add a new Category:

1.Go to Management settings > Categories.

2.Click Add category.

3.Enter a Name and, if required, a Description. (Descriptions are optional and are displayed only in the Categories list.)

4.Click Save.

To update a Category:

1.Go to Management settings > Categories.

2.Click Edit for the Category that you want to update.

3.Update the Name and/or the Description.

4.Click Save.

Displaying the Recording alias list

Recording aliases are used to record calls and contain all the information about how the new conference is created. The Content Server is delivered with a number of default Recording aliases called:

???Default Live and OnDemand: conferences created using this Recording alias can be streamed while the call is ongoing, and also watched after the conference completes and has been transcoded.

???Default OnDemand only: conferences created using this Recording alias can be watched after the conference completes and has been transcoded.

The Recording alias determines:

???What to dial to record using this Recording alias.

???How the Content Server communicates with the remote endpoint or system while recording, based on the Call configuration specified.

???How conferences created with this Recoding alias are streamed or played back, and whether they can be played live (while recording is in progress) or only on demand. This is specified by the Template .

???What conference information will be copied to conferences created with this Recording alias.

???Who has access to view or edit conferences created with this Recording alias and whether they have a password which must be entered before users can watch or download them.

For more information see Understanding recording configurations .

Conference information (such as the name, description, speaker, location, copyright and Category), conference permissions and outputs specified in the Recording alias are automatically copied to a conference that is created using that Recording alias. This information can be edited before the call is placed, during the call and also after the call has finished.

Only site managers can add new Recording aliases. Site managers can see and edit all the properties of all Recording aliases, deciding whether a Recording alias is a System or Personal Recording alias. Creators who own a personal Recording alias can only see and edit selected properties.

Note: Conferences made with the same Recording alias have the same default settings but different conference URLs.

Displaying the Recording alias list

To display the list of current Recording aliases, go to Conference setup > Recording aliases. From the Recording alias list you can:

???Edit a Recording alias : click the appropriate Edit button.

???Add new Recording aliases : click Add Recording alias. Site managers can also use an existing Recording alias, change its name and dialing properties, and then click Save as.

???Select a Recording alias and then click Delete selected to delete it. If you cannot delete a Recording alias, its check box is grayed. Only site managers can delete Recording aliases.

Adding & editing Recording aliases

Site managers can create and update Recording aliases which define several recording properties . One of these is the Recording alias type which determines whether it is a System Recording alias or a Personal Recording alias. Personal Recording aliases have an Owner other than the local administrator and the Owner of a Personal Recording alias can edit some of the properties of that Recording alias - as explained in the table below .

A Recording alias is selected when selecting to record scheduled conferences using the Cisco TelePresence Management Suite (TMS), by dialing an address of a Recording alias or when creating an ad hoc conference by calling out . For more information about using the Content Server with TMS, see Using TMS to schedule conferences to be recorded on the Content Server and the TMS online help.

When using:

???A gatekeeper, up to twenty four Recording aliases can be created when the Content Server is registered to the gatekeeper in Terminal mode. There is no limit on the number of Recording aliases when the Content Server is registered to the gatekeeper in Gateway mode

???A SIP registrar, up to twenty four SIP registrations can be used.

???Neither a gatekeeper or SIP registrar, only IP dialing is supported.

To add a new Recording alias:

1.Go to Conference Setup > Recording aliases.

2.Click Add Recording alias.

3.Complete the fields using the table below .

4.Click Save.

You can also use an existing Recording alias, change its fields (see below) and then click Save as.

To edit an existing Recording alias:

1.Go to Conference Setup > Recording aliases.

2.Click Edit for the Recording alias that you want to update.

3.Change any fields as appropriate using the table below .

4.Click Save.

Displaying the Template list

A Template determines how a conference is recorded, streamed and played back:

???Whether the conference can be streamed live or only on demand or both.

???Formats supported: for example, Windows Media, MPEG-4 for QuickTime, MPEG-4 for Flash or Real Media.

???The sizes for the outputs.

???Outputs for playback in portable devices (iPod or Zune).

???Outputs for uploading to your iTunes U account or your Podcast Producer server.

???Outputs for downloading to your computer.

The Template forms part of the definition of a Recording alias - see Understanding recording configurations .

There are a number of pre-defined Templates. Equally, site managers can create Templates and these can be updated, saved as a new Template and deleted if they are not being used in a Recording alias (when their check box is grayed). When deciding whether to edit an existing Template as the basis for a new one, or start again, look at how close the settings you require are to those in an existing Template.

Displaying the Template list

To display the list of current Templates, go to Management settings > Templates. From the list site managers can:

???Edit a Template by clicking Edit, either to update it or save it as a new Template. See Adding & editing Templates. Note that any changes will not be used in current calls but only for new calls.

???Delete Templates that are not in use: select the Template and click Delete selected.

???Create a new Template by clicking Add template. See Adding & editing Templates. You can also use an existing Template, change its settings and then click Save as.

Adding & editing Templates

Site managers can add new Templates and update existing ones:

???To edit a Template, go to Management settings > Templates and click Edit for the appropriate Template. Then update the fields as required using the table below and click Save.

???To create a new Template either:

oGo to Management settings > Templates and click Add Template. Then complete the fields using the table below and click Save.

oGo to Management settings > Templates, click Edit for the Template that is to be the

basis of the new one. Then update the fields as required using the table below and click

Save as.

Note: There is a maximum of six outputs per Template to reduce the processing time and disk space used by each conference when it is first created. If you exceed this, a message is displayed and you must reduce the number of outputs before you can save the Template. If no outputs are selected, conferences using this Template are recorded but cannot be watched or downloaded (see

Understanding recording configurations). Site managers and the editors of a conference can create additional outputs after the conference has been recorded by going to View conferences > Recorded, and clicking Edit and then Manage Outputs for the conference. See Managing

conference outputs.

Outputs to view in the Content Server web interface

Displaying the Media server configurations list

Media server configurations tell the Content Server where the media for a conference is stored and how it is streamed. Media server configurations can also be used to automate the process of uploading recorded content to Apple???s Podcast Producer server for completion and publishing using a Podcast Producer workflow or to Apple's iTunes U for content distribution.

By default, the Content Server can stream Windows Media live and on demand using the local Windows Media Streaming Server. MPEG-4 for QuickTime, MPEG-4 for Flash and Real Media can be delivered on demand as a progressive download (HTTP streaming) using the local web server (IIS). This is specified by the two preconfigured Media server configurations which cannot be deleted:

???Local IIS Web Server: can be used to deliver MPEG-4 for QuickTime, MPEG-4 for Flash and Real Media for on demand playback as a progressive download (HTTP or pseudo-streaming). It also delivers still images, if available.

???Local Windows Media Streaming Server: can be used for streaming Windows Media live and on demand.

External streaming servers for Windows Media, MPEG-4 for QuickTime, MPEG-4 for Flash and Real Media can also be used to stream conferences. Site managers set up the streaming server, and then add a Media server configuration to the Content Server that specifies how the Content Server puts the media files on the external streaming server and how the media is streamed. These Media server configurations can then be selected in a Template, or when creating outputs using the Manage outputs page. If this Media server configuration is used often, it can be set as a default in Site settings so that it will appear at the top of Media server configurations lists in the Templates and Manage outputs pages.

To display the list of Media server configurations, go to Management settings > Media servers. From the list, site managers can:

???Edit the Media server configurations by clicking Edit for the appropriate entry. See Adding & editing Media server configurations .

???Delete a Media server configuration that was added previously: select the entry and click Delete selected. Note that you cannot delete a Media server configuration that is used by a Template or conference???s Manage outputs page.

???Add new Media server configurations. Click the appropriate link for the type of server and see Adding & editing Media server configurations .

Adding & editing Media server configurations

Site managers can add new Media server configurations and update existing ones:

???To edit a Media server, go to Management settings > Media servers and click Edit for the

appropriate entry. Then update the fields as required using the table in the appropriate section below and click Save.

Note: If you have existing conferences that use a Media server configuration and you edit that Media server configuration, the streaming URLs for the outputs viewable in the Content Server web interface may also be updated. For example, if the server address of an external streaming server has changed, update the address in the Media server configuration; then conferences that use that Media

server configuration will still be playable.

???To create a new Media server configuration either:

o Go to Management settings > Media servers and click the appropriate link for the type of

server that you want to add. Then complete the fields using the table in the appropriate section below and click Save.

o Go to Management settings > Media servers, click Edit for the Media server

configuration that is to be the basis of the new one. Then update the fields as required using the table in the appropriate section below and click Save as.

See the appropriate section for the type of Media server configuration that you are updating or adding:

???Windows Media Streaming Server

???QuickTime or Darwin Streaming Server

???Wowza Media Server for Flash

???Real Media Streaming Server

???Podcast Producer Server

???iTunes U Server

Media server configuration: Windows Media Streaming Server

Only Windows Media Streaming Servers are supported for streaming Windows Media content. Saving the Media server configuration checks that the server is available at the specified server address and displays the server type if the information is available.

You can set up a Media server configuration for a Windows Media Streaming Server to do live and/or on demand streaming. Live streams can be sent to the Windows Media player using either a unicast or a multicast connection. Note that unicast streaming can be configured for either the local or an external Windows Media Streaming Server, but multicast streaming can only be configured with the local Windows Media Streaming Server.

Note: Before you start delivering your live content as a multicast stream, check with your network administrator that the network is multicast enabled.

Media server configuration: QuickTime or Darwin Streaming Server

The Content Server default installation supports only HTTP-based on demand streaming of MPEG-4 for QuickTime from its local IIS web server. An external server must be set up for live unicast and true (RTSP) on-demand streaming of MPEG-4 for QuickTime. Only QuickTime and Darwin Streaming Servers are supported for streaming MPEG-4 for QuickTime content.

Saving the Media server configuration checks that the server is available at the specified server address and displays the server type, if the information is available. Unicast live streaming from QuickTime or Darwin servers (RTSP announce) is also tested when the Media server configuration is saved.

You can set up a Media server configuration for a QuickTime or Darwin Streaming Server to do live and/or on demand streaming. There are two options for configuring the Media server for live MPEG-4 for QuickTime streaming:

???Live unicast streaming: This requires an external QuickTime or Darwin Streaming Server to relay streams to clients.

Media server configuration: Wowza Media Server for Flash

The Content Server default installation supports only HTTP-based on demand streaming of MPEG-4 for Flash from its local IIS web server. An external media server must be set up for live unicast and true (RTMP) on-demand streaming of MPEG-4 for Flash. Only the Wowza Media Server for Flash is supported for streaming MPEG-4 for Flash content.

Saving the Media server configuration checks that the server is available at the specified server address and displays the server type, if the information is available. Unicast live streaming from the Wowza Media Server for Flash (RTSP announce) is also tested when the Media server configuration is saved.

You can set up a Media server configuration for a Wowza Media Server for Flash to do live and/or on demand streaming.

Displaying the Call configurations list

To display the Call configurations list, go to Management settings > Call configurations. The Content Server is delivered with a default System Call configuration. It is used in the pre-installed Recording aliases - Default OnDemand Only and Default Live and OnDemand.

From the list, site managers can:

???Add new Call configurations : click Add Call configuration. These Call configurations can then

be selected in a Recording alias . You can also edit an existing Call configuration, change its fields and then click Save or Save as.

???Edit a Call configuration : click the appropriate Edit button.

???Delete a Call configuration: select it and then click Delete selected. You cannot delete a Call

configuration that is used by a Recording alias: its check box is grayed.

The Call configuration determines:

???Dual video support and resolutions

???Supported call speeds

???Maximum call length

???Encryption support

???Supported video and audio codecs

Adding and editing Call configurations

Site managers can add and edit Call configurations. The Call configuration is used by a Recording alias. See Understanding recording configurations .

To add a new Call configuration:

1.Go to Management settings > Call configurations.

2.Click Add Call configuration.

3.Complete the fields using the table below .

4.Click Save.

You can also use an existing Call configuration, change its fields (see below) and then click Save as.

To edit an existing Call configuration

1.Go to Management settings > Call configurations.

2.Click Edit for the Call configuration that you want to update.

3.Change any fields as appropriate using the table below .

4.Click Save.

Understanding groups & users

Access to view conferences

Who can view conferences can be configured:

???Content Server wide with the Allow Guest Access field in Site settings .

o When guest access is selected, entering the Content Server???s address in a web browser displays the View conferences menu: you do not need to authenticate (log in).

o If guest access is not selected in Site settings, then every user has to log in.

???For individual conferences:

o All users can be allowed access to a conference. If guest access is enabled in Site settings , the option in Conference permissions is Allow access to all users, including guests and this means that all users, including guests, can view the conference. If guest access is not enabled, then the option in Conference permissions is Allow access to all authenticated users. This means that all authenticated users can view the conference after they have logged in.

o Only certain groups and users can be given access by selecting Allow access to only these authenticated groups and users in Conference permissions and entering which groups or users can view the conference after they have logged in.

Group & user roles

A group or user with access to the Content Server can have one of three roles. See Adding and updating groups & users for a full explanation but briefly:

???Viewer: groups/users who can view the conferences they have been given access to.

???Creator: groups/users who can create conferences.

???Site manager: groups/users who can use all the Content Server's functionality.

The role also determines which menus are displayed when you log in.

Site managers can give individual users in a group a higher role than that inherited from the group. For example, to have most members of a group be viewers or creators, but have some members be site managers, set the group role to be viewer or creator, then individually add the users you want to be a site manager (see Adding and updating groups & users ) and set their Role to Site manager. The

higher role (group role or individual user role) is applied. A user can find out their role when they have logged in by going to their Preferences. See Editing user preferences .

Understanding groups & users

Who can view or edit a conference

A conference specifies who can view it and who can edit it. Users who can view a conference see the conference in the listing and are able to watch and download it. Editors of a conference can edit conference permissions and metadata, use the Content Editor to change the conference, add further outputs to a completed conference using the Manage outputs page, and delete the conference.

Group & user accounts and adding groups & users to the Content Server

Groups and users have to be Windows group or user accounts before they can be added to the Content Server. Adding users to the Content Server may happen automatically: it depends whether guest access is enabled in Site settings . You also need to consider the authentication mode set in Site settings (LDAP, Domain or Local): the correct authentication mode depends on how user accounts are organized within your company:

???You use Active Directory but your Content Server is not on a domain, or is on a different domain from that containing your groups and users.

???You use Active Directory and your Content Server is in the same domain as your groups and users. This is the recommended option for a cluster .

???You do not use Active Directory. This is the least preferred option because it is more time consuming to configure and maintain. This option is not recommended for a cluster.

Each of these options is detailed below.

Active Directory but your Content Server is not on a domain, or is on a different domain from that containing your groups and users

1.Go to Management settings > Site settings. See Configuring site settings .

2.For Authentication mode select LDAP - but see the note below.

3.Enter the details of your LDAP server or servers.

4.Go to Management settings > Groups and users. See Adding and updating groups & users .

5.Add the LDAP groups or users to the Content Server in the format group.name or user.name, and assign the correct Role (Viewer, Creator or Site manager).

o If Allow Guest Access is enabled in Site settings , you need to manually add all the groups and users who you want to log in. If a user does not exist on the Content Server before they attempt to log in for the first time, but a group to which they belong does, their account will be created automatically and they will be given the role of viewer. When the user logs in, their role will be whichever is higher of their group role or their individual user role.

o If Allow Guest Access is turned off in Site settings , you only need to add the groups and users who need a role higher than viewer (that is, creators or site managers). If a user does not exist on the Content Server before they attempt to log in for the first time (regardless of whether there is a group added to the Content Server that they are a member of), their account will be created automatically and they will be given the role of viewer. When the user logs in, their role will be whichever is higher of their group role or their individual user role.

6.All users and all members of the added groups now automatically have access to the Content Server using their normal Active Directory username and password. Groups and users who

have been added to the Content Server are listed in the Displaying the Groups & users list: go to Management settings > Groups and users. Their role is displayed next to the name. Note

that users may have inherited a higher role from their group membership than the one displayed but they can find out their role after they have logged in by going to their Preferences. See Editing user preferences .

Understanding groups & users

Note: Before changing authentication mode to LDAP, a site manager must add at least one LDAP group or user with the site manager role to the Content Server. Under LDAP authentication, local users (that is user accounts set up through the web interface for Windows Server administration on

the Content Server machine) including the local administrator cannot log in using the login dialog. However, the local administrator can log in by adding #page:login&rescue:true to the end of the

Content Server URL in the browser: http://<ContentServerIPaddress>/tcs/#page:login&rescue:true.

Active Directory and your Content Server is in the same domain as your groups and users

1.Go to Management settings > Site settings. See Configuring site settings .

2.For Authentication mode select Domain.

3.So that the Content Server can obtain group information, enter the details of your LDAP server or servers.

4.Go to Management settings > Groups and users. See Adding and updating groups & users .

5.Add the domain groups or users to the Content Server in the format group.name or DOMAINNAME (optional)\user.name: Display Name(optional)>, and assign the correct Role

(Viewer, Creator or Site manager).

6.All users and all members of the added groups now automatically have access to the Content Server using their normal Active Directory username and password. Groups and users who have been added to the Content Server are listed in the Displaying the Groups & users list: go to Management settings > Groups and users. Their role is displayed next to the name. Note

You do not use Active Directory

1.Create local user accounts on the Content Server for every user individually: go to Management settings >Windows server and create the accounts in the normal way.

2.Go to Management settings > Site settings. See Configuring site settings .

3.For Authentication mode select Local.

4.Go to Management settings > Groups and users. See Adding and updating groups & users .

5.Add every user individually to the Content Server in the Add groups or users page with the correct role (viewer, creator or site manager). See Adding and updating groups & users . Local users must be entered in the format: MACHINENAME\user.name:Display Name (optional). Note that local authentication does not support groups.

6.All users now have access to the Content Server using the username and password of their local account. Their role is the one assigned to them individually.

Users who have been added to the Content Server are listed in the Displaying the Groups &

Displaying the Groups & users list

The Content Server has one predefined user - the local administrator with the default password TANDBERG. We strongly recommend that you change this password - see Changing the local administrator account password . Users can access the Content Server either as a guest - without the need to log in (if this is allowed in Site settings) or by logging in (authenticating). To understand more about groups and users, see Understanding groups & users.

Displaying the Groups & users list

To display the list of current groups and users, go to Management settings > Groups and users. When the list opens, it shows both groups and users alphabetically by name. The icon for an entry

tells you whether it is a group or a user . You can display only groups or only users with the Show drop-down list.

From the Groups & users list a site manager can:

???Edit a group or user by clicking Edit. See Adding & updating groups & users .

???Delete groups and users: select the group or user and click Delete selected. You cannot delete the local administrator or the user you are logged in as.

???Add a new group or user by clicking Add groups or users. Whether you need to do this

manually depends on a number of factors - see Understanding groups & users. Then for instructions, see Adding & updating groups & users .

Adding & updating groups and users

Site managers can add new groups or users to give them a role (see below), and update existing ones. Cisco recommends working with groups where possible and then users can be added automatically: if you have not already done so, read the topic Understanding groups & users before continuing:

???To add a new group or user, go to Management settings > Groups and users and click Add Groups or Users. Then complete the fields using the table below, if necessary, and the naming format displayed in the web interface, then click Add Groups or Users.

???To edit a group or user, go to Management settings > Groups and users and click Edit for the appropriate entry in the Groups & users list. You are taken to the Edit group or user page. Change the fields using the table below, if necessary.

Table for adding groups and users

Table for editing groups and users

Configuring site settings

Site settings must be configured before using the Content Server. To open Site settings, go to

Management Settings > Site settings.

Most settings in the Site settings page can be applied while the Content Server is in a call without affecting current calls; however, if you change a setting that requires all calls to have ended before it takes effect, the Content Server automatically enters Configuration Reload mode and will not accept new incoming calls or make outgoing calls. When the call or calls currently in progress are completed, the new settings are applied and the Content Server is then able to receive and make calls. In Configuration Reload mode:

???The Site settings page displays: "The Content Engine is currently in X calls. The Cisco TelePresence Content Server is in configuration reload mode and will not accept any further calls or apply the new settings until all current calls have ended. To apply new settings now, click End all calls."

???The Create conference page displays ???There are no resources available to make a call, please try again later???.

???The Server overview page and the LCD panel displays: ???Reloading configurations???.

Site managers can override Configuration Reload mode and apply changes immediately by clicking End All Calls in the Site settings page, which terminates calls on the Content Server and applies the new settings.

The settings that trigger Configuration Reload mode are: System name, Cluster name (if in a cluster), Gatekeeper settings, Advanced H.323 settings, SIP settings and Email settings.

(The Site settings page automatically refreshes every 10 seconds.)

Exporting and importing conferences

Conferences can be copied from one Content Server to other Content Servers by site managers, one at a time. To do this, use the export/import functionality. Copying a conference involves:

1.Exporting the conference as a .tcb file.

2.Downloading this file to an external directory.

The outputs served by the default Media server configurations (Local IIS Web Server and Local Windows Media Streaming Server) and the conference information and permissions are copied and packaged in a signed proprietary format .tcb file.

3.Uploading the .tcb file to another Content Server.

Files under 2GB in size can be uploaded using the web interface. Larger files must be uploaded using Windows Remote Desktop Connection.

4.Importing the conference.

Uploaded .tcb files are listed on the Import conference page. Importing unpacks the .tcb file and displays the conference in Recorded conferences.

These steps are described in more detail below.

Notes:

???You must be logged in as a site manager to export conferences.

???Conferences with pending outputs cannot be exported.

???Distribution outputs (for example, for Podcast Producer), and files stored on external streaming servers, are not exported.

???Unicode characters in conference names are replaced with underscores when uploaded through the web interface. When a file with unicode characters in the conference name is

placed directly in the Imports shortcut on the Content Server desktop using Remote Desktop , the Import Conference page will not display it.

???The maximum period of time allowed for a file to be uploaded through the web interface is fifteen minutes. If the upload process is incomplete after this time, for example due to poor network conditions, the upload fails.

???You cannot export or import when the Content Server is in Error mode. The Content Server mode is shown in the server overview .

???Exported conferences can be imported to a Content Server of the same or higher software

version as the Content Server that the conference was exported from. To check the software version, go to Management Settings > Server overview. The export/import functionality is available from software release S3.3.

Exporting and downloading a conference

To export a conference

1.Log in as a site manager.

2.Go to View Conferences > Recorded conferences.

3.Click Edit > Edit conference for the conference you want to export.

4.In the Export conference section, click Export conference. (If the conference cannot be exported - due to it having pending outputs for example - then this section does not appear. Try again later.)

The conference is exported: how long this takes depends on the duration of the conference and the number of outputs. When complete, the page displays links that allow you to update the exported conference and download the .tcb file.

Exporting and importing conferences

5.Click Download exported conference and save the exported .tcb file to an external network location.

The .tcb file remains on the source Content Server for a week from the date of exporting before being

automatically deleted. During this time you can update the information and outputs for this conference and export it again by clicking Update exported conference. This replaces the original .tcb file with

an updated one.

Importing a conference

The Content Server web interface upload functionality checks the files inside the .tcb bundle, their structure and the signature of the bundle, and rejects invalid or corrupted files. Files with incorrect

extensions (an extension other than .tcb) uploaded through Remote Desktop to the Content Server's Imports shortcut are not displayed on the Import Conference page.

To import a file

1.Upload the .tcb file by one of the following methods:

a.Through the web interface:

???Go to Management settings > Import conference and click Upload File.

???Browse to the .tcb file of the conference you want to import and click Upload.

Automatically import conferences after upload is selected by default and then step 2

is then unnecessary. If you deselect this check box, the conference file will be uploaded and displayed on the Import conference page with the status Not Imported - go on to step 2.

b.Through Remote Desktop , for example if the file is larger than 2GB or is taking too long to upload through the web interface:

???Copy the exported .tcb file to the Imports shortcut on the desktop.

The conference is displayed on the Import conference page with the status Not Imported.

2.In Management settings > Import conference select the file and click Import to start unpacking the .tcb file. This may take a while. After all the conference outputs have been

unpacked and conference state has changed to Imported, the conference is displayed in

Recorded conferences.

3.The import file can be deleted from the Import Conference page. This deletes the .tcb file but does not affect the imported conference in Recorded Conferences.

Displaying the cluster overview

Up to ten Content Servers can be clustered to increase the total call capacity and improve redundancy and resilience. Such a cluster uses scalable external storage, an external Microsoft SQL Server database, and provides one web interface for viewing and managing the cluster. Video conferencing calls are balanced across the cluster by the VCS. The use of a network load balancer ensures that incoming HTTP user requests are spread evenly across the servers in the cluster. All configurations and conference information are global across the cluster.

For more information about the main features, system requirements, setup and management of a Content Server cluster, download the deployment guide, Creating and managing a TCS cluster, from the Documentation section of the Cisco web site.

The Cluster overview page provides information about cluster status, as well as the number of calls and offline transcoding jobs in progress. It is automatically updated every ten seconds.

Displaying the cluster overview

To display the Cluster overview page, go to Management settings > Cluster Overview. The Cluster overview page:

???Lists the System names and IP addresses of all the Content Servers in the cluster.

???Displays a link to the Server overview page for each Content Server. In addition to the "standard" server overview information, a Content Server???s system name, H.323 ID and E.164 alias are set in the Server overview page when in a cluster.

???Reports the total number of current calls for the cluster and for each Content Server.

???Reports the total number of offline transcoding jobs in progress for the cluster and for each Content Server.

???Reports the server mode for each Content Server.

???Reports the status for each Content Server. If the Content Server's mode is Online, then the Status displays a green tick, meaning that the Content server is running correctly. If the Content Server's mode is not Online, then the Status displays a red exclamation mark. Go to the Server overview for this Content Server to see more details.

???Displays links to each Content Server???s server logs and web interface for Windows Server administration.

???Allows you to End all calls on the whole cluster. If you want to end calls on a particular Content Server only, do this from the Server overview page for that Content Server.

???Allows you to put a Content Server in Maintenance mode. In this mode, no new calls or offline transcoding jobs are accepted on that server but current calls and jobs continue until completed. The other Content Servers in the cluster continue working as usual.

Maintenance mode should be used to ensure that no new calls are made to a Content Server; for example, if you want to defragment its drive, run a Windows security update installer or update antivirus software on that Content Server. You should also put a Content Server in Maintenance mode (after ending its current calls) if you need to shut it down and move it to

another location.

To put a Content Server in Maintenance mode, click Enter maintenance mode. The button changes to Rejoin cluster, and the Server mode displays Maintenance. After you have completed maintenance, click Rejoin cluster. The button changes back to Enter maintenance mode and Server mode displays Online. This means that the Content Server is now ready to receive calls and offline transcoding jobs.

Working with the logs

To view the Content Server logs go to Management settings > Server logs. The logs from the Content Engine are displayed by default: to view other logs, select from the drop-down list.

???To view a log, click the name of the log file and select to open it or save it.

???If the list is long, there may be more than one page: click on a page number to display the logs.

???To delete a log, select it and click Delete selected. (The current log is displayed at the top of the list. Except for Content Library logs, the current log cannot be deleted.)

All server logs can also be accessed from the E:\logs directory on the Content Server. Service event logs for the Content Engine, Transcode Engine, and Helper services can be found in the Windows Event Viewer when you Remote Desktop into the Content Server. These events show service starting and stopping information.

Content Engine logs

Content Engine logs include information generated by the Content Engine service about:

???Incoming and outgoing calls

???Codecs in call, call speed

???Dual video start/stop during a call

???Gatekeeper and SIP registrations

???Information about the generation of live streaming and live transcoded outputs

???Reasons for disconnected and rejected calls

A new log is created every time the Content Engine service restarts, or if the current log exceeds 10 MB.

Transcode Engine logs

The Transcode Engine logs include information about offline transcoded outputs including the output size and format, and how long the output took to transcode.

A new log is created every time the Offline Transcode Engine service is restarted, or if the current log exceeds 10 MB.

Helper logs

The Helper logs show information from the Helper service, including:

???The transfer of transcoded and dump files from temporary to final storage location

???Exporting and importing of .tcb files

???FTP transfer

???Hinting for MPEG-4 for QuickTime outputs

???When conference outputs have been deleted

A new log is created every time the Helper service is restarted, or if the current log exceeds 10 MB.

Content Library logs

The Content Library logs include information reported by the web interface. Most log entries can be ignored unless something unexpected has occurred while using the interface.

Backing up and restoring the Content Server

Cisco recommends that you back up the Content Server regularly and also before you upgrade it or install a security update. This topic explains how to do both scheduled and ad hoc backups. It also provides instructions for restoring the Content Server, if required. It is very important to follow the procedure as described here; otherwise future upgrades may not work.

Important: To ensure that you do not lose data, Cisco recommends that you back up the Content Server regularly.

Backing up

Note: If your media is located on a Network Attached Storage device (NAS), or on an external media server, this procedure will not back up these files. Ensure that you back up your media at the same time as the Content Server. If you restore from backup, you must restore the media backup taken at the same time as your Content Server backup; otherwise you may not be able to play some

conferences.

Before backing up

You either need a USB drive with enough disk space for all the files to be backed up or you can back up to a network drive. Check the size of the data to be backed up by logging in to the Content Server using Remote Desktop and opening My Computer to calculate the used size of the local C: and E: drives.

Making an ad hoc backup

Follow these steps to make a one-off backup.

1.If you are not backing up to a network location but using a USB hard drive:

a.Connect the USB hard drive to a USB port on the Content Server.

b.Log in to the Content Server using Remote Desktop and make sure that the USB hard drive appears in My Computer. If it does not, go to Start > Administrative Tasks > Computer Management and map a drive to a letter that does not conflict with those already in use. If necessary use the Windows help.

2.Open the Backup and restore wizard:

oThrough the web interface : using Internet Explorer go to Management settings > Windows server > Maintenance > Backup.

Note that Internet Explorer's security settings may prevent the necessary Active X scripts from running so that you cannot access the web interface for Windows Server

administration or some of its tools. To overcome this issue, add the URL of the Content Server to the trusted sites in your browser: go to Tools > Internet Options. Then select the Security tab and click Trusted sites. Click Sites, enter the Content Server's URL and click Add. Click Close and OK.

oUsing Remote Desktop: Log in to the Content Server using Remote Desktop and go to

Start > All Programs > Accessories > System Tools > Backup.

3.In the welcome dialog, click Next.

4.Select Back up files and settings and click Next.

5.In What to back up, select Let me choose what to back up and click Next.

6.In Items to back up, expand My computer, select Local Disk [C:], Local Disk [E:] and System State and click Next.

Backing up and restoring the Content Server

7.In Backup type, destination and name, browse to the network location or USB drive that you want to back up to, type a name for the backup and then click Next.

8.In Completing the backup or restore wizard, check the summary of your choices and click

Finish.

The backup process takes approximately 10 minutes per 5 GB of data. Progress is displayed and a detailed report is provided when the backup completes.

Configuring a scheduled backup

Follow these steps to set up a routine/repeated backup.

1.If you are not backing up to a network location but using a USB hard drive:

a.Connect the USB hard drive to a USB port on the Content Server.

2.Open the Backup and restore wizard:

oThrough the web interface: using Internet Explorer go to Management settings > Windows server > Maintenance > Backup.

Note that Internet Explorer's security settings may prevent the necessary Active X scripts from running so that you cannot access the Windows Server administration interface or

some of its tools. To overcome this issue, add the URL of the Content Server to the trusted sites in your browser: go to Tools > Internet Options. Then select the Security tab and click Trusted sites. Click Sites, enter the Content Server's URL and click Add. Click

Close and OK.

oUsing Remote Desktop: Log in to the Content Server using Remote Desktop and go to

Start > All Programs > Accessories > System Tools > Backup.

3.Select Advanced mode.

4.Open the Scheduled jobs tab and then click Add job and Next.

5.In What to back up, select Back up selected files, drive, or network data and click Next.

6.In Items to back up, expand My computer, select Local Disk [C:], Local Disk [E:] and System State and click Next.

7.In Backup type, destination and name, browse to the network location or USB drive that you want to back up to, type a name for the backup and then click Next.

8.In Type of backup, select the type of backup from the drop-down list using the explanations displayed and then click Next.

9.In How to back up, select Verify data after backup and click Next.

10.In Backup options, select Append this backup to the existing backups and click Next.

11.In When to backup, select Later and click Set Schedule. Enter your scheduling options and click OK.

12.Enter a name for the backup job and then click Next.

13.Enter an account that has administrative privileges on the Content Server (this could be the

local administrator account, or if the Content Server is on a domain, a domain administrator account). Enter the administrator account password twice and click OK.

14.In Completing the backup or restore wizard, check the summary of your choices and click Finish to schedule the backup.

The backup process will run according to the schedule that you set up.

Backing up and restoring the Content Server

Restoring from a backup

Make sure that you are using a backup taken from the same Content Server that you are restoring. If you want to restore to a different Content Server, contact your Cisco reseller.

Note: If your media is located on a Network Attached Storage device (NAS), or on an external media server, this procedure will not restore these files. You must have a media backup taken at the same time as the Content Server backup and you must restore this media backup as well; otherwise, you

may not be able to play some conferences.

Follow these steps to restore the Content Server from a backup.

1.End any calls in progress.

2.Log on to the Content Server using Remote Desktop .

3.Uninstall the Cisco TelePresence Content Server software:

a.Go to Start > Control Panel > Add or Remove Programs.

b.Select Content Server and click Change.

c.Select the Remove option and click Next. Continue until the installer has finished uninstalling.

d.Select Microsoft SQL Server 2005 and click Remove.

e.In Component selection, select TCS database engine and click Next. Continue until the installer has finished uninstalling.

f.Select Microsoft SQL Server VSSWriter and click Remove. Continue until the installer has finished uninstalling.

g.Select Microsoft SQL Server Setup Support Files and click Remove. Continue until the installer has finished uninstalling.

4.Browse to C:\Windows\Security and look for files called edb*.log. (There is edb.log and at least one more file often called edbtmp.log or edb0000*.log). DO NOT delete edb.log, but delete the other files. Not removing these files could result in future upgrades failing following a restore.

5.Start the Backup and restore wizard: go to Start > All Programs> Accessories > System Tools > Backup.

6.Select Restore files and settings and click Next.

7.In What to restore, select Local Disk [C:], Local Disk [E:] and System State and click Next.

8.In the Completing the Backup or Restore Wizard, click Advanced.

9.From Where to restore, leave the default setting ??? Original location. Click Next and OK to acknowledge the warning.

10.In How to restore, select Replace existing files and click Next.

11.Leave the default options selected in Advanced restore options and click Next.

12.Check the choices and click Finish.

13.The restore process starts and progress is displayed. When it completes you can display a detailed report by clicking Report.

14.You must restart the Content Server after the restore process.

Shutting down and restarting the Content Server

On Content Servers equipped with an LCD panel, this can be used to shut down or restart. On Content Servers which do not have a LCD panel, you should use a PC connected to the Content Server serial port via a serial cable. Cisco recommends that you end all calls on the Content Server before you shut down; otherwise the conferences may fail.

Note: If calls are in progress when the shut down occurs, the recorded conferences appear in the Recorded conferences list but may be unusable. They can be deleted in the normal way.

LCD panel operations

Restarting the Content Server using the LCD panel

1.Make sure that the Content Server is not recording or transcoding; that is, the LCD displays 'online'.

2.Press to display the main menu.

3.Go to Commands > Restart.

4.Select Yes to confirm.

You will see the message 'Restarting' on the LCD panel.

Shutting down the Content Server using the LCD panel

1.Make sure that the Content Server is not recording or transcoding; that is, the LCD displays 'online'.

2.Press to display the main menu.

3.Go to Commands > Shutdown.

4.Select Yes to confirm.

5.The Content Server shuts down. When you see the message 'Power off' on the LCD or when the LAN1 and HDD LEDs stop blinking, you can turn off the power using the switch at the back of the unit.

LCD status display and button functions

Terminal emulator program operations

Restarting the Content Server using a PC connected to the serial port

1.Connect the supplied serial cable from the serial port on the back of the Content Server to the serial port on a PC.

2.Start a terminal emulator program on the PC by going to All Programs > Accessories > Communications > HyperTerminal. (If HyperTerminal is not installed, download a terminal emulator program from the Internet; for example, puTTY.)

3.Open a new connection and enter a name for the connection.

4.Configure the connection to use the PC???s serial port as follows:

a.Set Baud rate to 115200 bps.

b.Set Data bits to 8.

c.Set Parity to None.

d.Set Stop bits to 1.

e.Set Flow control (hardware and software) to None.

5.Click OK.

6.Press Enter to display the main menu.

Shutting down and restarting the Content Server

7.Make sure that the Content Server is not recording or transcoding. Then press Esc to display Cisco TelePresence Content Server version, IP address and recording/transcoding status.

8.Use the Up or Down arrows to navigate to Commands and press Enter to select.

9.Use the Up or Down arrows to navigate to Restart and press Enter to select.

10.Close the terminal emulator session and disconnect the serial cable.

WARNING: Do not leave a terminal emulator session open after it is no longer in use. An open session may cause issues for system operation and when restarting.

Shutting down the Content Server using a PC connected to the serial port

1.Follow steps 1-8 in the previous section.

2.Use the Up or Down arrows to navigate to Shutdown and press Enter.

3.Close the terminal emulator session and disconnect the serial cable.

Warning: Do not leave a terminal emulator session open after it is no longer in use. An open session may cause issues for system operation and restart.

Terminal emulator session keys

Upgrading the Content Server

It is a good idea to regularly check for upgrades to the Content Server software on the Cisco web site. To upgrade the Content Server, read the Release notes for the release that you are upgrading to and then follow the instructions below. Note that you will need a release key to upgrade to S4 (but not if you subsequently upgrade to a minor release, for example S4.1), and this depends on the Content Server's serial number: contact your Cisco reseller.

Downloading Content Server software releases

1.Log in to the Content Server web interface as a site manager and go to Management settings > Server overview.

2.Make a note of the software version that is currently installed.

3.Go to the support section of the web site and check whether a more recent release is available for the Content Server.

4.Download the installer from the http://ftp.tandberg.com/ site to a directory on your computer.

Upgrading the Content Server software

1.Make sure there are no ongoing calls.

2.Log into the Content Server using Windows Remote Desktop Connection .

3.Back up your Content Server and turn off any anti-virus programs, if any.

4.Transfer the installer that you downloaded in step 4 above to the Content Server (do not run the installer from a mapped or network drive).

5.Verify the MD5 hash (checksum) of the file.

A unique MD5 file is provided which can be used to verify that a file has not become corrupted as a result of file transfer, disk error or tampering. Any MD5 program can be used for verifying the installer using the provided MD5 file. A list of links to popular programs is available at: http://en.wikipedia.org/wiki/Md5sum . You need to follow instructions for the MD5 program you have downloaded.

For example, a program such as md5sum.exe requires you to run a command in this format: md5sum -c <installerFileName>.md5

If the installer file successfully passes the integrity check, it returns:

<installerFileName>.exe: OK

If the installer file does not pass the check, you see the following indicating that the file has

been corrupted and the installer should not be run:

<installerFileName>: FAILED

md5sum: WARNING: 1 of 1 computed checksum did NOT match

6.If the file passed, run the executable by double-clicking on it and follow the on-screen instructions.

7.If prompted to do so, restart the Content Server. Otherwise, terminate your Remote Desktop session by logging off. Do not choose Shutdown, because it will shut down the Content Server.

Applying security updates

Cisco recommends that you check the http://ftp.tandberg.com/pub/software/device_security/ FTP site regularly for new security updates and apply them to ensure that your Content Server is protected with the most up-to-date security patches released by Microsoft. Go to http://ftp.tandberg.com/pub/ software/device_security/ rather than to the Microsoft web site because these updates have been tested for compatibility with the Cisco TelePresence Content Server.

To apply security updates

1.End all calls because you must restart the Content Server when the installer finishes.

2.Go to http://ftp.tandberg.com/pub/software/device_security/ and download the update installer to a temporary directory.

3.Use Windows Remote Desktop Connection to copy the update installer to a directory on the Content Server.

4.Using My Computer navigate to the directory into which you copied the installer.

5.Verify the MD5 hash (checksum) of the file.

For example, a program such as md5sum.exe requires you to run a command in this format: md5sum -c <installerFileName>.md5

If the installer file successfully passes the integrity check, it returns:

<installerFileName>.exe: OK

If the installer file does not pass the check, you see the following indicating that the file has

been corrupted and the installer should not be run:

<installerFileName>.exe: FAILED

md5sum: WARNING: 1 of 1 computed checksum did NOT match

6.If the installer passed the integrity check, double-click on it to install the security update.

7.When prompted, restart the Content Server. Otherwise, terminate your Remote Desktop session by logging off. Do not choose Shutdown because it will shut down the Content Server.

Using the web interface for Windows Server administration

Open the web interface for Windows Server administration in a new window by going to Management settings > Windows server. This page can also be accessed by typing https://<ContentServerIPAddress>:8098 in the Web browser URL field. You need to use Internet Explorer (IE) to use this menu item.

The Windows Server page is used to:

???Change the local administrator account password

???Update the date and time settings

???Create local user accounts

???Set up scheduled or ad hoc backups and restore the Content Server from a backup

Note: Some IE security settings may prevent the necessary ActiveX controls from running so that you cannot access the Windows Server administration interface or some of its tools. To overcome this

issue, add the URL of the Content Server to the trusted sites in your browser. (To do this, in your browser go to Tools > Internet Options. Select the Security tab and click Trusted sites. Click

Sites, enter the Content Server's URL and click Add. Click Close and OK.)

Using Windows Remote Desktop Connection

Windows Remote Desktop Connection is used for a number of administrative tasks:

???Upgrading the Content Server

???Using the TCS wizard to store recordings externally

???Backing up and restoring

???Applying security updates

???Importing & exporting conferences

Using Remote Desktop

1.On your computer, go to Start > All programs > Accessories > Communications > Remote desktop connection. (On some computers this may be Start > All programs > Accessories > Remote desktop connection.)

2.Type in the IP address or DNS name of the Content Server.

3.If you are upgrading, applying security updates or manually copying a conference import file to the Content Server, you need to share your disk drives:

a.In the connect dialog click Options.

b.Select the LocalResources tab and select Disk Drives from Local devices and resources (you may need to click More to see this option).

4.Click Connect.

5.Log in with an administrator account username and password. This can be the local administrator account, or if the Content Server is on a domain, a domain administrator account.

Using Remote Desktop via the Content Server web interface

WARNING: Do not use this method for installing software upgrades to the Content Server or applying Windows security updates.

1.Open the web interface for Windows Server administration in a new window by going to Management settings > Windows server. You need to use Internet Explorer (IE) to use this menu item. (This page can also be accessed by typing https://<ContentServerIPAddress>:8098 in the web browser URL field.)

2.Go to Maintenance and select Remote Desktop.

Note: Some IE security settings may prevent the necessary ActiveX controls from running so that you cannot access the web interface for Windows Server administration or some of its tools. To overcome

this issue, add the URL of the Content Server to the trusted sites in your browser. (To do this, in your browser go to Tools > Internet Options. Select the Security tab and click Trusted sites. Click

Sites, enter the Content Server's URL and click Add. Click Close and OK.)

* These ports are configurable in Site settings when in a cluster.

Note: This does not include any ports used in Site settings , or manually configured Media server configurations for streaming to external streaming servers. For example:

???Port range in Advanced H.323 Settings in Site settings .

???Network pull port(s) for Windows Media streaming servers. For more information, see the Windows Media Services help topics.

???Streaming port range start specified for unicast streaming on QuickTime or Darwin streaming servers , or Wowza Media Servers for Flash , or for multicast streaming in Windows Media streaming servers or QuickTime or Darwin streaming servers .

???Port used for a Real Media Streaming Server .

Port information

Ports for streaming from the Content Server

Streaming Windows Media from the Content Server uses the following ports:

Note: The Windows Media player will automatically use protocol rollover if necessary. The default streaming protocol for the Windows Media player is RTSP on port 554. If the player cannot obtain the stream using RTSP (because the port is blocked on a firewall, for example), then it will automatically rollover to MMS. MMS (port 1755) is a deprecated streaming protocol and is not used as a streaming transport for Windows Media Player version 9 and above. The player will then try HTTP on port 80. The Content Server will redirect any requests for Windows Media streams on port 80 to the correct

HTTP port used by the Windows Media Streaming Server on the Content Server (port 8080).

Streaming Windows Media from the Content Server to the Silverlight player uses the following port:

Note: The Silverlight player will request the stream on port 80 because this is the default HTTP port. The Content Server will redirect any requests for Windows Media streams on port 80 to the correct

HTTP port used by the Windows Media Streaming Server on the Content Server (port 8080).

Serving MPEG-4 for QuickTime, MPEG-4 for Flash or Real Media from Content Server using the default "Local IIS Web Server" Media server configuration uses the following port:

Ports for streaming from external streaming servers

The default setup for a Windows Media Streaming Server uses the following ports:

Port information

transport for Windows Media Player version 9 and above. The player will then try HTTP on port 80.

The default setup for a QuickTime or Darwin streaming server uses the following port:

The default setup for a Wowza Media Server for Flash uses the following ports:

The default setup for a Real Media (Helix) streaming server uses the following port:

Changing the local administrator account password

The local administrator account is a built-in Windows account that has complete access to the local system. It has been added to the Content Server???s Groups and users list as <machine- name>\Administrator with a site manager role and cannot be deleted from the list.

This account can be used to log into the Content Server web interface, the Windows Server administration interface and Remote Desktop.

Because this account has complete access to the Content Server, Cisco recommends that you change the local administrator password regularly. You may want to record the new password in a safe location.

Note: Do not change the local administrator account name.

Changing the local administrator account password

1.Go to Management settings > Windows server.

2.Click Set administrator password.

3.Enter the current password, then the new password twice and click OK.

Restoring to Content Server defaults

You can restore the Content Server to its default settings, partially or fully, using the LCD and the buttons on the front panel:

???A partial restore (using ConfigRestore) deletes all user-created Recording aliases, Media server configurations, Call configurations and Templates, and restores the default configuration for the current software release, but does NOT affect the conferences stored on the server.

???A full restore (using FullRestore) deletes all conferences, media files and logs, in addition to

deleting all user-created Recording aliases, Media server configurations, Call configurations and Templates, and restoring the default configuration for the current release. If the data location has been changed to an external storage location (NAS), it also changes the default storage location back to the Content Server. Media files on the NAS are not deleted.

WARNING: Restoring to defaults (either a partial or full restore) must not be interrupted! Logs of the restore are available in E:\logs\SetupUtility directory.

Notes:

???Restoring to defaults cleans up the Content Server???s database and/or media. It does not revert the Content Server back to the state it was in when delivered (that is, the restore does not affect the operating system in any way).

???A partial restore (ConfigRestore) is not available for Content Servers in a cluster .

???A full restore (using FullRestore) run on a Content Server which has been clustered will revert that Content Server to a standalone Content Server with the default configuration files for the current software release, and no media. However, the cluster database will still report that this Content Server is part of a cluster: Cisco recommends removing a clustered Content Server from the cluster by running the TCS Wizard before restoring it to its default settings.

Restoring the Content Server to default settings can be done using the LCD panel on Content Servers equipped with the LCD panel. On Content Servers which do not have a LCD panel, you should use a PC connected to the serial port.

Restoring the default settings

1.Make sure that the Content Server is not recording or transcoding; that is, the LCD displays online.

2.Press to display the LCD's main menu.

3.Go to Commands > RestoreDefaults and then select either FullRestore or ConfigRestore. See the notes below.

4.Select Yes to confirm.

LCD status display and button functions

Restoring default settings using a PC connected to the Content Server serial port

1.Connect the supplied serial cable from the serial port on the back of the Content Server to the serial port on a PC.

3.Open a new connection and enter a name for the connection.

4.Configure the connection to use the PC???s serial port as follows:

a.Set Baud rate to 115200 bps.

b.Set Data bits to 8.

c.Set Parity to None.

d.Set Stop bits to 1.

e.Set Flow control (hardware and software) to None.

5.Click OK.

6.Press Enter to display the main menu.

7.Make sure that the Content Server is not recording or transcoding. Then press Esc to display Cisco TelePresence Content Server version, IP address and recording/transcoding status.

License, copyright and trademark information

TANDBERG copyright

TANDBERG is a registered trademark of TANDBERG in the United States and/or other countries. TANDBERG is now part of Cisco Systems, Inc.

Third party licenses information

Amended / expanded copyright notices for third-party software on the Cisco TelePresence Content Server systems are listed below:

The non-commercial third party code is distributed in binary form under the terms of open source licenses such as BSD.

In accordance with section (6) of the GNU Lesser General Public License and section 3.6 of the Mozilla Public License, copies of such code will be provided upon request by contacting TANDBERG. Please contact us by using the Online Support section at www.tandberg.com. Please provide USD 10.00 for media and shipping.

License for OpenSSL

THE OpenSSL SOFTWARE IS PROVIDED BY THE Open SSL PROJECT ???AS IS??? AND ANY

EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING ,BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT( INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

Mozilla Public License (???MPL???)

Software distributed under the MPL (http://www.mozilla.org/MPL/MPL-1.0.html): MPEG4IP, JS FLV Player.

License for Ogg

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of the Xiph.org Foundation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS??????

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS BE LIABLE

FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

License, copyright and trademark information

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,

OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE

OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

License for JSON:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

THIS SOFTWARE IS PROVIDED ``AS IS?????? AND ANY EXPRESS OR IMPLIED WARRANTIES,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

ROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

OF THE POSSIBILITY OF SUCH DAMAGE.

License for Prototype:

Prototype is Copyright ?? 2005-2007 Sam Stephenson. It is freely distributable under the terms of an MIT-style license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ???Software???), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED ???AS IS???, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN

THE SOFTWARE.

License for scriptaculous:

script.aculo.us is licensed under the terms of the MIT License.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

License, copyright and trademark information

copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN

THE SOFTWARE.

Third party trademark and copyright notices

RealNetworks?? technology is provided under license from RealNetworks, Inc., copyright ?? 1995???2003 RealNetworks, Inc. and/or its suppliers. P.O. Box 91123, Seattle Washington 98111???9223, U.S.A. Patents Pending. All rights reserved. RealNetworks is a registered trademark of RealNetworks, Inc.

Wowza Media Server?? Disclaimer: Wowza Media Systems, Wowza Media Server and related logos are either registered trademarks or trademarks of Wowza Media Systems, Inc. in the United States and/or other countries.

QuickTime is a trademark of Apple Computer, Inc.

Adobe and Flash are registered trademarks of Adobe Systems Incorporated, and may be registered in the United States or in other jurisdictions including internationally.

TANDBERG patents

This TANDBERG product is covered by one or more of the following patents: US7,136,577

US6,590,603

US7,283,588 US7,619,645 B2 EP01953201 GB1338127

Other patents pending: go to http://www.tandberg.com/tandberg_pm.jsp for an updated list.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE

WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO

BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST

TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE

INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS

REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR

CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB???s public domain version of the UNIX operating system. All rights reserved. Copyright ?? 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE

SUPPLIERS ARE PROVIDED ???AS IS??? WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL

WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS

FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR

TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR

INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING

OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF

THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks . Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.