Table of Contents
Configuring Cisco Show and Share for Streaming Flash from a Wowza Media Server
Configuring Wowza Media Server for Video On-Demand
Configuring Wowza Media Server for Live Streaming
Configuring Show and Share for Video On-Demand
Configuring Show and Share for Live Streaming
Notes on Configuring Wowza 4.x on Content Server
Obtaining Documentation and Submitting a Service Request
Contents
- Introduction
- Flash Streaming Prerequisites
- Configuring Wowza Media Server for Video On-Demand
- Configuring Wowza Media Server for Live Streaming
- Configuring Show and Share for Video On-Demand
- Configuring Show and Share for Live Streaming
- Notes on Configuring Wowza 4.x on Content Server
- Related Documentation
- Disclaimers and Notices
- Obtaining Documentation and Submitting a Service Request
Introduction
This configuration guide provides guidelines for configuring Cisco Show and Share and an external web server running Wowza Media Server for on-demand and live Flash media streaming (Figure 1). These guidelines are for Cisco Show and Share running release 5.3 or later and Wowza Media Server Pro 1.7.2. or later.
Show and Share with Wowza supports on-demand streaming via RTMP for desktop playback of H.264 encoded video in the MP4 file format. For MP4 playback on IOS mobile devices, Show and Share with an Apache or IIS server (or other third-party web server) supports on-demand streaming via HTTP progressive download.
Figure 1 Overview of Show and Share Streaming Flash from a Wowza Media Server
![]()
Flash Streaming Prerequisites
Before you begin, confirm that your network is configured for on-demand and live media streaming.
1.
Define a Media Server with the following applications installed:
2.
Define three storage locations on the Media Server:
a.
[storage drive]:\content\rtmp
b.
[storage drive]:\content\http
c.
[storage drive]:\content\fileupload
3.
Make sure that the (S)FTP server has access to the [storage drive]:\content and that the associated user permissions have read/write privileges.
4.
Confirm that the HTTP server root URL is [storage drive]:\content and that it has access to the sub-folders.
5.
Verify that the HTTP server has MIME type enabled for .mp4 video.
6.
Confirm that the Wowza Media Server is installed and licensed as described in the http://www.wowzamedia.com installation instructions.
Configuring Wowza Media Server for Video On-Demand
Follow these steps to configure the Wowza Media Server for on-demand media streaming.
Step 1
Install the Wowza Example applications in this directory:
[install-dir]\examples\installall.bat
Step 2
Configure the Wowza VOD Application:
a.
Save a copy of the original Application configuration file [install-dir]\conf\vod\Application.xml to Application_Original.xml.
b.
Configure the Application.xml file to point to your RTMP storage location by modifying the <StorageDir> parameter:
![]()
Next, configure Cisco Show and Share for VOD as described in the “Configuring Show and Share for Video On-Demand” section.
Configuring Wowza Media Server for Live Streaming
Follow these steps to configure the Wowza Media Server for live media streaming.
Step 1
Confirm that you have installed the Wowza Example applications as described in the “Configuring Wowza Media Server for Video On-Demand” section.
Step 2
Create the folder: [install-dir]\applications\_defapp_
Step 3
Edit the file [install-dir]\conf\publish.password and add a username and password.
Next, configure Cisco Show and Share for a live event as described in the “Configuring Show and Share for Live Streaming” section.
Configuring Show and Share for Video On-Demand
The following steps will enable Show and Share to store on-demand content on a Wowza server and direct client players to the Wowza Media Server when the video thumbnail is selected.
For more information about enabling Cisco Show and Share and Cisco Digital Media Manager with a Cisco Media Experience Engine (MXE) 3500, see the integration notes on Cisco.com:
http://www.cisco.com/en/US/products/ps12130/products_installation_and_configuration_guides_list.html
![]()
Note To avoid duplicate file errors, you must specify a unique URL directory location for RTMP and HTTP, they cannot be the same directory.
Follow these steps to create three external file hosting locations.
Step 1
Log in to Cisco Show and Share with an account that has the Administrator role or as superuser.
Step 2
Choose Administration from the global navigation drop-down menu in the top right corner of the page.
![]()
Step 3
Choose Setup > Show and Share. The File Hosting Location page appears. By default, the check box labeled “Publish locally to <Show_and_Share_appliance_FQDN>” is checked.
![]()
Step 4
Uncheck the Publish locally to check box. The File Hosting Location selection window appears.
![]()
Step 5
Create an RTMP File Hosting Locations with these parameters:
a.
File Hosting Location Name: RTMP MP4
b.
Accepts Files with extensions: *.mp4, *.m4v, and *.mpv4
c.
File Upload Protocol: FTP or SFTP
d.
Host Address: The DNS-resolvable FQDN or routable IP address of the remote server where you will deploy files of the relevant file type. Using an FQDN is recommended.
e.
Login Name and Login Password: A user account with sufficient privileges to use the remote server. The assigned password for the login name that you specified.
f.
Directory root location: The relative directory path to files that you will deploy. Example: /content/rtmp
g.
Directory root URL path: The URL where Cisco Show and Share will reference your files. For example: rtmp://media_server:1935/vod/mp4:
Step 6
Create an HTTP File Hosting Location with these parameters:
a.
File Hosting Location Name: HTTP MP4
b.
Accepts Files with extensions: *.mp4, *.m4v, and *.mpv4
c.
File Upload Protocol: FTP or SFTP
d.
Host Address: The DNS-resolvable FQDN or routable IP address of the remote server where you will deploy files of the relevant file type. Using an FQDN is recommended.
e.
Login Name and Login Password: A user account with sufficient privileges to use the remote server. The assigned password for the login name that you specified.
f.
Directory root location: The relative directory path to files that you will deploy. For example: /content/http
g.
Directory root URL path: The URL where Cisco Show and Share will reference your files. For example: http://media_server/http
Step 7
Create a new File Hosting Location with these parameters:
a.
File Hosting Location Name: Generic File Upload
b.
Accepts Files with extensions: *.*
c.
File Upload Protocol: FTP or SFTP
d.
Host Address: The DNS-resolvable FQDN or routable IP address of the remote server where you will deploy files of the relevant file type. Using an FQDN is recommended.
e.
Login Name and Login Password: A user account with sufficient privileges to use the remote server. The assigned password for the login name that you specified.
f.
Directory root location: The relative directory path to files that you will deploy. For example: /content/fileupload
g.
Directory root URL path: The URL where Cisco Show and Share will reference your files. For example: http://media_server/fileupload
You have now configured Show and Share for streaming MP4 videos from a Wowza Media Server to desktop and mobile devices. You should upload an MP4 video and verify that the video appears on the Wowza content directories.
Configuring Show and Share for Live Streaming
The following steps will enable Show and Share to stream live content from a Wowza server.
Step 1
Log in to Cisco Show and Share with an account that has Live Event User role privileges.
Step 2
Click My Account , and then click Create a Live Event . The Create a Live Event window opens.
![]()
Step 3
In the Choose a Live Event Type field, click non-DME Live Event if the live stream is not originating from a Cisco Digital Media Encoder. In addition to the Wowza Media Server, this includes the Cisco TCS or MXE 3500 encoders.
Step 4
Enter information about the video in the Live Event Basic Setup window.
Step 5
Enter the Video URL of the Wowza Media Server using this format: rtmp://servername/application/codecID:streamname.extension
Step 7
In the Videos area on the My Account page, click the Live Events tab to view the event. Select the live event, and then do the following:
a.
Click Publish to publish the listing of the live event to Show and Share.
b.
Click Administer and then click Start in the Main administrative controls area when you want to start the broadcast.
Step 8
View the Live Event in Show and Share.
You can also test the live stream URL by entering it directly into an RTMP MP4 media player such as a VLC.
You have now configured Show and Share to stream live content from a Wowza Media Server. You should create and test a live event stream.
Notes on Configuring Wowza 4.x on Content Server
When you configure a Wowza 4.x media server in the Content Server Management > Recording Setup > Media server configurations > + Add Wowza server screen, you might see the following error when you click Save.
Step 1
Log in to the Wowza streaming manager. Navigate to the Applications page.
Step 2
Choose Add Application .
Step 3
Choose Live: Single Server or Origin .
Step 4
Name the application _defapp_ and click Save .
Step 5
Restart the Wowza server. Add the Wowza media server in the Content Server UI.
Related Documentation
For additional product integration procedures, see these resources on Cisco.com.
http://www.cisco.com/en/US/products/ps6682/products_installation_and_configuration_guides_list.html
http://www.cisco.com/en/US/products/ps6682/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps12130/products_installation_and_configuration_guides_list.html
http://www.cisco.com/en/US/products/ps12130/tsd_products_support_series_home.html
Disclaimers and Notices
The objective of this guide is to provide the reader with assistance in using and configuring this product. 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.
If you need technical support, please contact your Cisco Authorized Service Representative.
The specifications for the product and the information in this Guide are subject to change at any time, without notice, by Cisco. 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.
Cisco® is a registered trademark belonging to Cisco ASA. Other trademarks used in this document are the property of their respective holders.
This Guide may be reproduced in its entirety, including all copyright and intellectual property notices, in limited quantities in connection with the use of this product. 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.
Obtaining Documentation and Submitting a Service Request
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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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.
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.