You can use this module along with ModuleMediaCasterStreamMonitorAdvanced module to monitor streams through a set of configuration properties. If any of the streams become unhealthy all the streams in a given MediaStreamNameGroup will be re-started.
Note: Wowza 2.2.4 or later is required.
- Create a SMIL file that includes all the streams that you wished to be considered part of a MediaStreamNameGroup. A single application can have several MediaStreamNameGroups. The SMIL file does not need to be used for stream playback. Be sure to include all streams in the group that you wish to keep synchronized. For example, if you have 3 streams associated with a Silverlight smooth stream and 3 streams associated with an iPhone multi-bitrate stream and 1 of the streams are associated with both the Silverlight and iPhone stream (total of 5 unique streams) then create a SMIL file that includes all 5 unique streams.
Here is an example SMIL file (for this example the SMIL file is located at [install-dir]/content/stream.smil):
<smil> <head> </head> <body> <switch> <video src="stream_hi.stream" system-bitrate="628000"/> <video src="stream_lo.stream" system-bitrate="478000"/> </switch> </body> </smil>
- Using either the Stream Manager, /conf/StartupStreams.xml, or MediaCaster with the Java API, start the stream with MediaCaster type rtp using the stream name smil:[smil-file-name]. For example, to start the stream group above use the stream name smil:stream.smil. After starting, you can double check to be sure the stream is started as a group by viewing the streams in the Stream Manager. Stream groups will be listed under each of the individual streams.
If you're having problems or want to discuss this article, post in our forum.