Only Wowza Media Server 2 lets you simultaneously stream your H.264/AAC content to a variety of media clients and devices. [PERFECT FOR WORKING WITH KALTURA AND KALTURA CE]. With Wowza Server 2 you don’t have to use client-specific encoders and servers, or pre-process files for consumption by specific clients – it works with a wide range of conventional RTMP, RTSP/RTP or MPEG-TS H.264 encoders for live streaming, and for on-demand content, with standard file container formats. Now you can take your content to multiple player destinations with just a single encode.
You can use Wowza 2 for EC2 to stream media directly from Amazon Simple Storage Service (S3). Wowza Media Server 2 employs a read through local disk cache to improve the performance of streaming media from S3. The configuration of the caching mechanism is done automatically and is adjusted based on the AMI instance type being used (m1-small, m1-large, m1-xlarge). This feature requires that you use “Wowza Pro DevPay AMI ID v EC2 1.1.9” or greater. See the Wowza Media Server 2 for Amazon EC2 User’s Guide (below) for more information.
This document describes how to install and configure Wowza Media Server 2 on Amazon EC2. The document assumes you have signed up for Amazon EC2 and have installed the Java based command line tools. You can obtain more information about Amazon EC2 and download the command line tools and documentation by going to:
For additional information and documentation,
see Wowza for Amazon EC2 Support.
For information on the new features in Wowza Media Server 2 please refer to the User Guide:
Wowza Media Server 2
Specifications
Multi-Protocol, Multi-Client Streaming |
|||
Adobe RTMP
(RTMPE, RTMPT, RTMPTE, RTMPS) |
Flash player
Flash Lite 3 AIR |
||
Apple HTTP Streaming | iPhone, iPod touch (iPhone OS 3.0 or later)
iPad QuickTime player (10.0 or later) Safari (4.0 or later on Snow Leopard) |
||
Microsoft Smooth Streaming | Silverlight 3 or later | ||
RTSP/RTP | QuickTime player
VideoLAN VLC player Mobile devices (3GPP) Other compliant players |
||
MPEG2 Transport Protocol
(MPEG-TS) |
IPTV set-top boxes |
Compatible Live Encoding |
|||
RTMP | Video: H.264, VP6, Sorenson Spark, Screen Shared codec
Audio: AAC, AAC-LC, HE-AAC, MP3, Speex, NellyMoser ASAO |
||
RTSP/RTP | Video: H.264
Audio: AAC, AAC-LC, HE-AAC, MP3, Speex |
||
MPEG-TS | Video: H.264
Audio: AAC, AAC-LC, HE-AAC, MP3 |
||
ICY (SHOUTcast/icecast) | Audio: AAC, AAC-LC, HE-AAC (aacPlus), MP3 |
Applicable Transport Protocol and Payload Specifications |
|||
RTSP | IETF RFC2326 | ||
RTP: H.264 | IETF RFC3984, QuickTime Generic RTP Payload Format | ||
RTP: ACC | IETF RFC3640
IETF RFC3016 ISO/IEC 14496-3 |
||
RTP: MP3 | IETF RFC2250 | ||
RTP: Speex | IETF RFC5574 | ||
MPEG-TS | ISO/IEC 13818-1 | ||
MPEG-TS over RTP | IETF RFC2038 |
Supported File Formats |
|||
Video and audio | FLV (Flash Video – .flv)
MP4 (QuickTime container – .mp4, .f4v, .mov, .m4v, .mp4a, .3gp, and .3g2) MP3 (.mp3) |
System Requirements |
|||
Minimum recommended production hardware | CPU: Single Dual Core, 3.00 GHz or better
RAM: 2GB Disk: 2 or more in RAID 0 (striping) Network: 1Gb Ethernet |
||
Supported operating systems | Windows (XP, Vista, 7, Server 2003 & 2008)
Linux (all distributions) Solaris Mac OS Unix |
||
Java (required) | Java Runtime Environment (JRE) 6 or greater
or Java Development Kit (JDK) 6 or greater |
*Specifications are subject to change. Please refer to the latest Wowza Media Server 2 User’s Guide and the Wowza forums for the most up to date information.
Hiii there,
Thanks for the information. I was trying to use KCE4 with wowza media server.Earlier tried with red5 and rtmp,live streaming was great.I wanted to give wowza a try as I have heard that its faster than red5, thats good! But I had an issue.I installed it, was ok! but then I tried to do rtmp streaming and was not successful. I also created symlinks to content but that was not helpful. Can you help me with a proper guide or do you have any ref link ?
Thanks in advance
89n3ur0n
Appreciate you sharing, great post.Really looking forward to read more.
Great, thanks for sharing this blog post. Keep writing.