Table of Contents
Configuring Live Streaming on the
Cisco TelePresence Content Server with
Cisco TelePresence MCU Series
1. Review the Live Streaming Guidelines.
- Cisco TelePresence Content Server
- Cisco TelePresence MCU 4500 Series
- Cisco TelePresence MCU 5300 Series
- Cisco TelePresence System Codec C90
- Cisco TelePresence System EX60/EX90 Series
- The Content Server should join the conference at precisely the rate that you intend to stream. For example, connect at 768 kbps to achieve a live streaming resolution of 576p. This setting provides good resolution with moderate bandwidth usage.
- For best live streaming results, the Content Server negotiated video resolution should not exceed 720p when connected to the MCU, or directly to an endpoint.
- The bit rate for endpoints dialing in or out of the MCU should be from 768 kbps to 1.2 mbps. This will provide a negotiated resolution that is 720p, 576p, or 448p in the main video channel.
- For the content channel, it is extremely important that the connected device (PC/laptop/DVI) resolution is set to 720p or XGA (768x1024) before joining the conference. If the content source resolution is higher or lower than the recommended setting, text and graphics displayed on all endpoints will be significantly degraded.
- You should confirm these settings on the MCU conference template and global defaults, the Content Server recording template, and on all endpoints:
- When configuring the Content Server recording template, only use the size Large streaming profile. This ensures that the target bit rate is always the call speed of the call when the recording is created and will avoid additional transcoding overhead.
- Pay attention to participant environmental lighting for live streaming calls. You can learn more about studio lighting and technical requirements for Cisco Telepresence endpoints here:
Although there are several ways that you can connect the appliances, we recommend that you configure the MCU to dial out to the Content Server. This provides better control and forces the Content Server to dial in to the conference at the optimum live streaming speed. In the example configuration we are using 768 kbps to achieve a good balance between bit rate and quality on the Content Server. You can choose other speeds that meet your specific requirements.
- Motion / sharpness tradeoff: Favor motion
- Preferred bandwidth from MCU: 768 kbps
- Preferred bandwidth to MCU: 768 kbps
To maintain high-quality video for all participants, we recommend configuring the MCU to force the C90 endpoint to dial in and stream out of the conference at a specific speed (2 mbps). In contrast to the Content Server 768 mbps setting, we recommend that all endpoints join the conference at 2 mbps for the best possible experience for all participants.
- Motion / sharpness tradeoff: Favor motion
- Preferred bandwidth from MCU: 2 mbps
- Preferred bandwidth to MCU: 2 mbps
In our example we use a Flash distribution profile and a Wowza media server. We recommend this configuration to achieve the best live streaming experience. For more information about using a Wowza server, see the Configuring the Cisco Content Server for Streaming Flash from a Wowza Media Server in the Related Documentation section.
To configure the Content Server to join the conference at the optimum live streaming speed, go to Management > Recording setup > Templates . Create a new template, or edit an existing template. Enter the following:
- On demand format: MPEG-4 for Flash
- Sizes: Large
- MPEG-4 for Flash drop down menu: Wowza (or your media server)
- Optimize for motion check box: Click to enable
- Live stream check box: Click to enable
- Format drop down menu: MPEG-4 for Flash
- Size drop down menu: Large
- Media server configuration drop down menu: Wowza (media server where the Content Server publishes the live stream)
To configure the C90 endpoint main video channel and content channel to join the conference at the optimum live streaming speed, go to Configuration > Peripherals . Enter the conference parameters along with these specific live streaming settings:
Note CONTENT SHARING DEVICE: For any device that plugs into the VGA cable to share content during a live stream, make certain that the device will send 720p or XGA (768x1024). It is extremely important that the connected device resolution is set to 720p or XGA before joining the conference. If the content source resolution is higher or lower than the recommended setting, text and graphics displayed on all endpoints will be significantly degraded.
Figure 5 shows the Content Server stream from the MCU (top arrow) and the endpoint stream to the MCU (bottom arrow).
Figure 6 shows that the Content Server is sending 768 kbps in the main video channel and streaming 720p in the dual video stream (content) channel. The content channel is sending and receiving 720p.
Figure 7 shows that the C90 endpoint is sending and receiving 2 mbps to the MCU. The main video channel resolution is 576p and the content channel resolution is 720p.
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.This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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)
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.