Table of Contents
This deployment guide is designed to provide guidelines for configuring the TelePresence Content Server and the external QuickTime Streaming Server for live unicast and on demand streaming. These guidelines are for a Content Server running release 5.0.
The Content Server default installation supports only HTTP-based on demand streaming (also known as progressive download) of MPEG-4 from its local IIS Web Server. An external streaming media server, such as QuickTime or Darwin, must be set up for live unicast and true (RTSP) on-demand streaming of MPEG-4 content.
Live multicast streaming of MPEG-4 content does not require an external QuickTime server, as the multicast stream is sent directly from the Content Server. See the Cisco TelePresence Content Server Release 5.0 Administration and User Guide for more information.
The information required to set up your QuickTime Streaming Server can be found in the QuickTime Streaming Server Administration manual and the streamingserver.xml-sample file available within the QuickTime Streaming Server application folder.
While this document makes specific mention of QuickTime Streaming Server throughout, all the information is also directly relevant to the Darwin Streaming Server. The settings detailed in the sections “Configuring QTSS for live unicast streaming” and “Configuring QTSS for on demand streaming” are the same for both QuickTime Streaming Server and Darwin Streaming Server.
Note When specifying ports for a new media server from the Content Server, the starting point must be an even number. The Content Server will use up to 30 ports for two simultaneous live calls. Ensure that the port range specified in this module is large enough to support the maximum number of live calls supported by your Content Server configuration.
Step 6 Give the newly created user privileges to push media to the QuickTime Streaming Server by creating a qtaccess file at the root level of the Movies folder of QuickTime Streaming Server. By default this path is /Library/QuickTimeStreaming/Movies/.
The contents of the new qtaccess file is structured in two sections, the first being write (push) privileges and the second being the view permissions. The following example allows any authenticated user account to be used for pushing content to the QuickTime Streaming Server and allows any user (unauthenticated) to view content streamed from the QuickTime Streaming Server:
While there are no further changes required to the QuickTime streaming service setup to have it stream media generated by the Content Server on-demand, there needs to be some way for the Content Server to get the media to the QuickTime Streaming Server. The standard method for this is FTP.
Ensure that you have an FTP service running on same server as your QuickTime Streaming Server and that the FTP service has access to write into the Movies folder of your QuickTime Streaming Service. Please refer to the administration manual of your FTP service for details on how to accomplish this.
The following steps will create a new media server on the Content Server with support for live and on demand streaming through QuickTime Streaming Server. If you only require support for one type of streaming, follow the steps as applicable to create a live streaming-only or on demand-only media server.
Step 3 Enter a name for your new media server, and check the type of streaming you want to support. You can check Support live unicast streaming, Support live multicast streaming , Support on Demand, or all three.
b. Enter a Streaming port range start value that is within the range set in Step 3 of “Configure for live unicast streaming”. This value must be an even number. The Content Server will use a range of 30 ports beginning with this port for streaming of up to two live simultaneous calls.
Note You should choose to use alternate live URLs only if you know the live streaming URLs for the QuickTime Streaming Server require different path or filename information to that generated by the Content Server (for example, when live streaming to a CDN).
a. In the Multicast IP address field, enter the destination multicast IP address that the Content Server streams to. Your chosen multicast IP address must not conflict with any other multicast address in use in your network. Further considerations apply if you want to multicast over the public Internet. Contact your network administrator for more information.
This value tells the network how far multicast packets should be allowed to travel across the network. The default threshold is LAN (TTL=32). The value "Subnet" (TTL=1) means that packets do not pass the first network router and should mean a multicast stream is viewable on any network, even those not enabled for multicast, where the client is on the same subnet as the Content Server.
Step 6 If you checked Support on demand , media needs to be moved from the Content Server to the QuickTime Streaming Server. The standard method for this is File Transfer Protocol (FTP). In the On demand settings section, click FTP movies to location and enter the required FTP server information:
Now that you have created a media server that supports streaming from a QuickTime Streaming Server, you need to use this media server in a Content Server template. Multiple templates can use the same media server.
Now that you have a template for streaming from a QuickTime Streaming Server, you need to create a recording alias on the Content Server that uses this template. Multiple recording aliases can use the same template.
The objective of this Guide is to provide readers with assistance in using and configuring their Content Server. Product capabilities of Cisco and other manufacturers’ products change over time and so the required configuration may be different from that indicated here. If you have any suggestions for changes to this document, please feed them back to Cisco through your Cisco Authorized Service Representative.
Every effort has been made to supply complete and accurate information in this Guide; however, Cisco assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Except for the limited exception set forth in the previous sentence, no part of this Guide may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronically, mechanically, by photocopying, or otherwise, without the prior written permission of Cisco. Requests for such permission should be addressed to firstname.lastname@example.org.
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
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.
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.