Table of Contents
- Product Overview
- Technical Specifications
- Hardware and Software Limitations
- Installing the Content Server
- Completing the Initial Configuration
The Cisco TelePresence Content Server (Content Server), allows you to share knowledge and enhance communication by recording video conferences. You can access live and on-demand presentations anywhere, anytime. In addition, you can distribute live or recorded content to any computer, or download to your favorite portable media device.
This release introduces the third-generation Content Server hardware that runs Cisco Content Server Release 6.0 software. The third-generation Content Server is based on the Cisco UCS C220 M3 server. (For more information, see the Cisco UCS C220 Server Installation and Service Guide on Cisco.com.)
KVM1 connector— Use this port for initial configuration
1-Gb Ethernet dedicated management port (also see Figure 3)
LAN1 (Arrow 7, left pointer)— Use this port to connect the Content Server to the network (also see Figure 3)
Four 8-Gb DDR32 low-voltage DIMMs provide a total of 32 GB of memory.
Two Generation 3 PCIe3 expansion slots on risers, occupied by a RAID4 card (LSI MegaRAID SAS9266-8i with SuperCap power module RAID backup unit, configured for RAID 5) and a NIC5 card (Broadcom 5709 quad port 1-Gb Ethernet).
Drives are installed into front-panel drive bays that provide hot-pluggable access. Small Form Factor—The appliance can hold up to eight 2.5 in x .55 in (63.5 mm x 14mm) SAS6 or SATA7 hard drives or solid state drives. The appliance ships with two drives installed.
- The third-generation Content Server ships with Cisco Content Server Release 6.0 pre-installed. This software release supports only new installations on third-generation server hardware. You cannot install Release 6.0 on older hardware or use it to migrate files from older hardware to the new server.
- Third-generation Content Servers in a cluster must all be the same hardware version. You cannot mix older (first- or second-generation) servers in a cluster with third-generation Content Servers.
- The USB media kit is used only for a third-generation Content Server software reimage. You cannot use the USB drive to upgrade the software on first- and second-generation server hardware.
Select and prepare an installation site that meets the requirements that are described in the Cisco UCS C220 Server Installation and Service Guide on Cisco.com.
For specific compliance and safety information, see the Regulatory Compliance and Safety Information for the Cisco UCS C-Series Servers on Cisco.com.
When you receive the server, verify the contents of the shipping carton to ensure that you have all items necessary for installation. Save the packing material in case you need to repack the server. If any item is missing or damaged, contact your Cisco representative or reseller for instructions.
For Content Server rack mounting procedures, see the “Installing the Server” chapter of the Cisco UCS C220 Server Installation and Service Guide .
- USB keyboard, mouse, and VGA monitor
- Windows Server 2008 product activation key—see the product activation key label on the Content Server chassis
- IP address, subnet mask, and gateway for
- Task 1: Connect and power on the Content Server and configure CIMC
- Task 2: Set the local administrator password
- Task 3: Enter the Windows Server 2008 activation key
- Task 4: Configure a static IP address
- Task 5: Set the date and time
- Task 6: Enable Remote Desktop Connection
- Task 7: Install a security certificate
- Task 8: Configure the H.323/SIP registration settings
- Task 9: Make a test recording
Step 1 Attach a supplied power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet. Wait for approximately two minutes to let the server boot in standby power mode during the first bootup. You can verify power status by looking at the Power Status LED (Figure 1):
Step 2 Use the supplied KVM cable to connect a USB keyboard, mouse, and a VGA monitor to the KVM connector on the Content Server front panel (Figure 1).
Alternatively, you can use the VGA and USB ports on the rear panel. However, you cannot use the front panel VGA and the rear panel VGA at the same time. If you do so, the first VGA connector is disabled.
The Windows Server 2008 Physical Key is on the printed label on the Content Server top near the front. You should have an Internet connection to access the Windows Server 2008 online activation service. Follow these steps:
Step 1 Connect the Content Server to your network. Use an Ethernet cable to connect from your LAN to the LAN1 network port, marked with blue in Figure 3, on the rear panel. Use the connector marked with red for your CIMC management connection.
Step 2 Log in to the Content Server Windows Server Manager by using the password that you set in Task 2: Set the local administrator password.
Step 4 Choose IPv4 from the list. In the IPv4 Properties window, click the Use the following IP address radio button. Enter the Content Server IPv4 address , subnet-mask , and default-gateway . Click OK .
Step 1 Log in to the Content Server by using the Administrator password that you set in Task 2: Set the local administrator password.
Step 2 In the Server Manager window, click the time and date box in the lower right corner to open the settings window. Or, go to Start > Control Panel > Clock, Language, and Region > Set the time and date .
Beginning with Cisco Content Server Release 6.0, all Windows Server 2008 administration and configuration is accomplished by using Windows Remote Desktop Connection to access the server administration interface. Follow these steps to enable remote desktop on the Content Server:
Step 1 Log in to the Content Server by using the Administrator password that you set in Task 2: Set the local administrator password.
The Content Server is shipped with a self-signed certificate, which is valid for one year. Because self-signed certificates are not from a trusted Certificate Authority, when users log in, most browsers will display a message that the identity of the site could not be verified.
You can add the server to the Trusted sites list in Internet Explorer, or add an exception in Firefox to avoid error messages at log in. However, we recommend purchasing a security certificate from a certificate issuing authority that has a trusted relationship back to a root authority, such as VeriSign or Comodo. These credentials are most likely to be trusted by browsers, which eliminates the need to add the server to the list of Trusted sites. The certificate should be generated against the Windows machine name or the DNS entry associated with the server IP address.
Step 2 In the Remote Desktop Connection dialog box, enter the IP address that you configured in Task 4: Configure a static IP address.
Step 3 Click Connect . Log in with the administrator password that you set in Task 2: Set the local administrator password. The Server Manager user interface appears.
You can also install the certificate for the Windows Media Administration website to avoid security warnings when administrators log in to that site. When you have installed the certificate on the website, the purchased certificate is then used instead of the self-signed certificate.
If the security certificate expires, (regardless of whether the server uses the purchased security certificate or the original self-signed certificate), browsers will display additional warnings. You can generate a new certificate request by using the IIS Web Server Certificate Wizard. After this request another self-signed certificate may be created by using a third party tool. Or, this request can be forwarded to a certificate issuing authority. Do NOT remove the expired certificate until you have installed a new certificate because this will prevent any log in attempts.
Step 1 On your computer, open a browser and enter the Content Server IP address the you configured in Task 4: Configure a static IP address.
Step 2 Log in to the Content Server web interface by using the password that you configured in Task 2: Set the local administrator password.
- If you are using an H.323 gatekeeper, enter the H.323 ID and the E.164 alias . Click Save .
- If you are using a SIP registrar, enter the SIP address (URI) and SIP display name . Click Save .
Caution Make sure that all E.164 aliases and H.323 IDs are unique in your network and valid for your gatekeeper. The H.323 ID of the default live recording alias is Live<serial_number> and the default on-demand recording alias is OnDemand<serial_number>.
See the online help for an explanation of recording aliases. SIP URIs must be unique in their network and valid for their SIP registrar.
For more information about any of the tasks below, see the online help or the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
We recommend that you change the default API password. For information about the default API settings, see the Cisco TelePresence Content Server API Guide on Cisco.com.
The default authentication option in the Management tab, Configuration > Site settings is Local. We recommend that you change the default authentication method to LDAP/Active Directory mode or Domain mode. See the online help for more information about when to use each mode.
Recording access can be restricted to authenticated users—that is, those who have logged in. If you want to allow unauthenticated users to view conferences, you can enable guest access in the User properties section of Site settings . Users that are not logged in are able to view conferences that have Allow access to all users selected in the conference permissions. RSS feeds are only available if guest access is enabled.
If you want to use an external streaming server or enable multicast streaming you should configure a Media server for live streaming, on demand streaming, or both. In the Management tab, go to Recording Setup > Media servers .
You can make the media server configurations that you created the system defaults in Site settings . The server configurations will display as the defaults when you create a Template or when editing a recording output in the Manage outputs page.
The server is preconfigured with a number of default templates that you can edit, or you can create new templates by using the Media server configurations. In the Management tab, go Recording setup > Templates .
You can assign Recordings a display category to help users find them. For example, the marketing department can have a category for use with all marketing recordings. In the Management tab, go to Recording setup > Categories .
The server is preconfigured with a number of default Recording aliases. Each Recording alias has an H.323 ID, E.164 alias and/or SIP URI that can be dialed to record a call or conference. In the Management tab, go to Recording setup > Recording aliases .
When the system H.323 ID, E.164 alias, SIP URI or server IP address is called, the Default Recording alias is used. You can set the Default Recording alias in the System defaults section of Site settings .
The Cisco TelePresence Management Suite (TMS) can be used to record scheduled one-off or recurrent conferences. See the Cisco TelePresence Content Server Administration and User Guide and all TMS documentation for this release on Cisco.com.
We recommend that you back up the server regularly and also before system upgrades. For more information on backup, see the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
The default location for media files is drive E:. You can change this location to store files on a Network Attached Storage (NAS) device. Using an NAS device ensures that the recording capacity is not limited by the disk space on the server. For more information about NAS, see the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
Up to ten Content Servers can be clustered to increase the total call capacity and improve redundancy and resilience. For more information about system requirements, set up and management of a Content Server cluster, see the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
If you experience any problems when configuring or using the Content Server, consult the online help for an explanation of how individual features and settings work. Also, see the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
- The serial number and product model number of the server
- The software build number, which can be found on the product user interface
- Your contact email address or telephone number
- A full description of the problem
To provide feedback on this document, or to report an error or omission, you can use the online, Embedded Feedback form that appears on the left side of the screen. You can also send feedback to firstname.lastname@example.org .
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .
Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)