• Sample map file entries for Stream Target destinations (push publishing)

    The Stream Targets feature in Wowza Streaming Engine™ live streaming software (version 4.2.0 and later) allows you to send live streams from Wowza Streaming Engine to widely distributed destinations over a variety of protocols. The easiest way to send live streams to distributed destinations is to use the Stream Targets graphical user interface in Wowza Streaming Engine Manager. You can, however, also edit the PushPublishMap.txt map file to manually instruct Wowza Streaming Engine to send a source stream to a target destination.

    This article provides sample map file entries and playback testing instructions for the target destinations supported by Wowza Streaming Engine software versions 4.2 and earlier and by Wowza Media Server™ 3.6.4.

    Note: The PushPublishMap.txt file supports quotation (") marks around the keys and value strings, in compliance with the JSON specification.

    Contents


    Wowza Streaming Engine
    Wowza Streaming Cloud
    Adobe Media Server
    Akamai HTTP (Adobe HDS and Apple HLS)
    Akamai RTMP
    BitGravity
    EdgeCast
    Icecast 2
    Justin.tv
    Level 3
    Limelight
    Livestream
    Mirror Image Internet
    MPEG-2 Transport Stream (MPEG-TS)
    Real-time Transport Protocol (RTP), unicast or multicast
    Shoutcast 1
    Shoutcast 2
    Ustream.tv
    YouTube Live

    Wowza Streaming Engine


    To send a stream to another server that's running Streaming Engine, use the rtmp profile. The UserName and Password items are only needed if RTMP authentication is enabled on the destination Wowza server.

    Following is an example entry to send the stream myStream to a remote server that's running Streaming Engine at the domain name wowza.myserver.com, assuming RTMP authentication is enabled and the following credentials are valid:

    • Application: live
    • User Name: myUser
    • Password: myPassword

    Example map entry:

    myStream={"profile":"rtmp", "streamName":"myStream", "host":"wowza.myserver.com", "application":"live", "userName":"myUser", "password":"myPassword"}

    For adaptive bitrate delivery, the map entry is a bit more complicated to ensure that keyframes in the streams are properly aligned. For example, for the following three adaptive bitrate streams:

    • myStream_480p: 500Kbps
    • myStream_360p: 750Kbps
    • myStream_720p: 1000Kbps

    The map entries to properly send these streams to Wowza Streaming Engine and maintain alignment are:

    myStream_480p={"profile":"rtmp", "streamName":"myStream_480p", "host":"wowza.myserver.com", "application":"live", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true"}
    myStream_360p={"profile":"rtmp", "streamName":"myStream_360p", "host":"wowza.myserver.com", "application":"live", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true"}
    myStream_720p={"profile":"rtmp", "streamName":"myStream_720p", "host":"wowza.myserver.com", "application":"live", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true"}

    You must create a Synchronized Multimedia Integration Language (SMIL) file in the [install-dir]/content folder on the remote server that's running Streaming Engine to properly playback the adaptive bitrate set of streams. (See our live streaming Tutorials for more detailed information.) For example, the SMIL file for the above set of streams might look like this:
    <smil>
        <head>
        </head>
        <body>
            <switch>
                <video src="myStream_480p" video-bitrate=400000  audio-bitrate=96000  width=320 height=180>
                    <param name="videoCodecId" value="avc1.66.12" valuetype="data"/>
                    <param name="audioCodecId" value="mp4a.40.2" valuetype="data"/>
                </video>
                <video src="myStream_360p" video-bitrate=650000  audio-bitrate=96000  width=476 height=268>
                    <param name="videoCodecId" value="avc1.66.21" valuetype="data"/>
                    <param name="audioCodecId" value="mp4a.40.2" valuetype="data"/>
                </video>
                <video src="myStream_720p" video-bitrate=900000  audio-bitrate=96000  width=640 height=360>
                    <param name="videoCodecId" value="avc1.66.31" valuetype="data"/>
                    <param name="audioCodecId" value="mp4a.40.2" valuetype="data"/>
                </video>
            </switch>
        </body>
    </smil>
    To playback the stream:

    1. Open [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html.

    2. Enter the address of the server that's running Wowza Streaming Engine software and the application name in the Server box as rtmp://[wowza-ip-address]/[application]/.

    3. Enter the stream name in the Stream box.

    4. Click Connect.

    Note: See How to stream to another Wowza Streaming Engine instance for instructions on how to send a live stream from one Streaming Engine instance to another using Stream Targets in Wowza Streaming Engine 4.2.

    Wowza Streaming Cloud


    To send a stream to Wowza Streaming Cloud, use the wowza-streaming-cloud profile. The connectionCode is the only item needed.

    Example map entry:

    myStream={"entryName":"My cloud target", "profile":"wowza-streaming-cloud", "connectionCode":"123abc", "destinationName":"wowzastreamingcloud"}

    Note: Sending a stream to Wowza Streaming Cloud requires Wowza Streaming Engine 4.1.2 or later. See How to stream to Wowza Streaming Cloud for instructions on how to send a live stream from Streaming Engine to Streaming Cloud using Stream Targets in Wowza Streaming Engine 4.2.

    Adobe Media Server


    To send a stream to Adobe Media Server, use the rtmp profile. The UserName and Password items are only needed if RTMP authentication is enabled on the destination Adobe Media Server.

    Following is an example entry to send the stream myStream to a remote Adobe Media Server, assuming RTMP authentication is enabled and the following credentials are valid:

    • User Name: myUser
    • Password: myPassword

    Example map entry:

    myStream={"profile":"rtmp", "streamName":"myStream", "userName":"myUser", "password":"myPassword", "originalTimecodeThreshold":"0x100000"}

    To playback the stream:

    1. Open [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html.

    2. Enter the address of the Adobe Media Server and the application name in the Server box as rtmp://[adobe-address]/[application]/.

    3. Enter the stream name in the Stream box.

    4. Click Connect.

    Akamai HTTP (Adobe HDS and Apple HLS)


    To send a stream to Akamai using Apple HLS or Adobe HDS, use the cupertino-akamai or sanjose-akamai profile, respectively. These profiles are configured to send streams to the Akamai HD Network. For proper operation, the Wowza media server application must be set up as a live application and the cupertinolivestreampacketizer or sanjoselivestreampacketizer must be enabled in the <Stream>/LiveStreamPacketizers container. If the appropriate packetizer isn't set, a warning message is logged when the live stream is sent to Akamai.

    Streams sent to Akamai must be provisioned through the Luna Control Center. Be sure to use the appropriate configuration type for each stream. For example, Apple HLS streams must be configured as HD iPhone/iPad Live. You must also provision a stream with the following information:

    • StreamId
    • HostId

    The StreamId is the number after the "at-sign" (@) symbol in the Stream Name and the HostId is in the Host Name / Status column. Entering a value for the HostId isn't required. If not specified, the HostId value will default to example-i. For this example, we'll use an Apple HLS stream that's already provisioned for testing, supplied with the following values:

    • StreamId: 215930
    • HostId: wowzadevapple-i

    This is the only information that's required. The remaining map entry components only control the full playback URL.

    Example cupertino-akamai map entry:

    myStream={"profile":"cupertino-akamai", "streamName":"myStreamHLS", "cupertino.renditions":"audiovideo", "akamai.streamId":"215930", "akamai.hostId":"wowzadevapple-i", "akamai.eventName":"test", "adaptiveGroups":"group2", "debugLog":"false"}

    Example sanjose-akamai map entry:

    myStream={"profile":"sanjose-akamai", "streamName":"myStreamHDS", "sanjose.representationId":"myRep", "akamai.streamId":"123456", "akamai.hostId":"wowzadevhds-i", "akamai.eventName":"test", "adaptiveGroups":"group1", "debugLog":"true"}

    See About map profiles for the definitions of these fields.

    About adaptive groups


    The adaptiveGroups parameter allows Wowza Streaming Engine to create an adaptive bitrate stream from a group of individual streams. The group contains the streams you specify and uses a unique, adaptive bitrate playback URL. See Akamai HTTP protocol playback URL formats to see how the URL formats are enumerated. A stream can belong to multiple adaptive bitrate groups. All streams in an adaptive bitrate group must have the same akamai.streamId, akamai.hostId, akamai.eventName, and akamai.sendToBackupServer (if defined), but each stream must have unique streamName. To ensure unique streamName values, we recommend including the bitrate or vertical resolution of the stream, such as myStream_720p. It's sufficient to set the streamName to the same value as the source stream name. The following example shows how three Apple HLS streams (myStream1, myStream2, and myStream3) are used two adaptive bitrate groups (group1 and group2):

    myStream1={"profile":"cupertino-akamai", "streamName":"myStream1", "cupertino.renditions":"audiovideo", "akamai.streamId":"215930", "akamai.hostId":"wowzadevapple-i", "akamai.eventName":"test", "adaptiveGroups":"group1", "debugLog":"false"}
    myStream2={"profile":"cupertino-akamai", "streamName":"myStream2", "cupertino.renditions":"audiovideo", "akamai.streamId":"215930", "akamai.hostId":"wowzadevapple-i", "akamai.eventName":"test", "adaptiveGroups":"group1|group2", "debugLog":"false"}
    myStream3={"profile":"cupertino-akamai", "streamName":"myStream3", "cupertino.renditions":"audiovideo", "akamai.streamId":"215930", "akamai.hostId":"wowzadevapple-i", "akamai.eventName":"test", "adaptiveGroups":"group2", "debugLog":"false"}

    In this example, group1 includes myStream1 and myStream2, and group2 includes myStream2 and myStream3.

    You can also control how many items are maintained in a stream's playlist by using the http.playlistCount settings. By default, the value of http.playlistCount is set to 0, which maintains a sliding window live stream that has three segments. Set the playlist count to a higher value to maintain a longer DVR playlist on Akamai for DVR functionality. You can also set http.playlistAcrossSessions to true to instruct Wowza Streaming Engine to try to maintain a playlist across streaming sessions. The http.playlistTimeout is used to control the time limit for how long non-running playlists are maintained.

    Example cupertino-akamai map entry that uses many of the configuration options:

    myStream={"profile":"cupertino-akamai", "streamName":"myStream", "cupertino.renditions":"audiovideo|audioonly", "akamai.streamId":"215930", "akamai.hostId":"wowzadevapple-i", "akamai.destinationServer":"redundant", "akamai.eventName":"test", "http.playlistCount":"10", "http.playlistAcrossSessions":"true", "adaptiveGroups":"group1|group2", "debugLog":"true"}

    Note: See How to stream to the Akamai HD network for instructions on how to send a live stream to Akamai over HTTP using Stream Targets in Wowza Streaming Engine 4.2.

    Akamai RTMP


    To send a stream to Akamai using RTMP, use the rtmp-akamai profile. The rtmp-akamai profile is configured to send to the Akamai HD Network. When sending streams to Akamai, the following account information is required:

    • StreamId
    • User Name
    • Password

    Following is an example entry to send the stream myStream to Akamai, assuming these credentials:

    • StreamId: 12345
    • User Name: myUser
    • Password: myPassword

    Example map entry:

    myStream={"profile":"rtmp-akamai", "streamName":"myStream_1_500", "akamai.streamId":"12345", "userName":"myUser", "password":"myPassword"}

    The stream is sent to the Akamai entry point p.ep[stream-id].i.akamaientrypoint.net/EntryPoint/ with a stream name of myStream_1_500@[stream-id]. For the example entry above, the entry point is p.ep12345.i.akamaientrypoint.net/EntryPoint/ and the stream name is myStream_1_500@12345. The optional akamai.sendToBackupServer parameter would change the entry point to b.ep12345.i.akamaientrypoint.net/EntryPoint/ if set to true.

    To configure a backup/failover endpoint, add the optional akamai.sendToBackupServer:true parameter to the map entries on the backup Streaming Engine instance. This parameter is only required on the backup instance and will continue to send the stream to Akamai should the primary server that's running Wowza Streaming Engine fail.

    Example map entry:

    myStream={"profile":"rtmp-akamai", "streamName":"myStream_1_500", "akamai.streamId":"12345", "userName":"myUser", "password":"myPassword", "akamai.sendToBackupServer":"true"}

    Note: When sending RTMP streams to the Akamai HD Network, destination stream names must be in the form [name]_[angle]_[bitrate].

    • The [name] value can be any string, but must be identical for all of your event's streams or else the Akamai HD Network will treat them as different events.

    • The [angle] value can be any string, but is intended to be a string that identifies the camera angle.

    • The [bitrate] value should be the total bitrate of the video in kilobits per second (kbps).

    • The underscore (_) character is the only allowed field separator.

    Fields after the third field (bitrate) in the destination stream name are truncated. Streams that aren't delivered in this format can't be played.

    If sending streams to the original AMS network, set the akamai.hdNetwork parameter to false to allow simple stream names without the above syntax requirements.
    For adaptive bitrate delivery, the map entry is a bit more complicated to ensure that the key frames in the streams are properly aligned. For example, for the following three adaptive bitrate streams:

    • myStream_480p: 500Kbps
    • myStream_360p: 750Kbps
    • myStream_720p: 1000Kbps

    The map entries to properly send these streams to Akamai to maintain alignment are:

    myStream_480p={"profile":"rtmp-akamai", "streamName":"myStream_1_500", "akamai.streamId":"12345", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true", "sendOriginalTimecodes":"true", "originalTimecodeThreshold":"0x100000"}
    myStream_360p={"profile":"rtmp-akamai", "streamName":"myStream_1_750", "akamai.streamId":"12345", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true", "sendOriginalTimecodes":"true", "originalTimecodeThreshold":"0x100000"}
    myStream_720p={"profile":"rtmp-akamai", "streamName":"myStream_1_1000", "akamai.streamId":"12345", "userName":"myUser", "password":"myPassword", "adaptiveStreaming":"true", "sendOriginalTimecodes":"true", "originalTimecodeThreshold":"0x100000"}

    To playback the RTMP stream through the Akamai network over RTMP, you can use the following Akamai players:

    • For the new HD network:

      • Flash Entry Point Debug Player. You must log in to your account to use this player. You must select the desired stream from the provided dropdown menu.

      • Akamai RTMP Test Player. You must create the stream URL from the streamName and streamID specified in your map file and from the hostname found in the Akamai configuration screens, in the following form:

        http://<HostName>.akamaihd.net/<streamName>@<streamID>

        Note: Assumes you have HD Flash 1.0 delivery enabled in the associated Akamai configuration.
    • For the legacy Flash network:

      • Akamai Flash Support Player. You must create the stream URL from the streamName and streamID specified in your map file and from the hostname found in the Akamai configuration screens, in the following form:

        rtmp://<HostName>/<streamName>@<streamID>

    To playback the stream through the Akamai network via Adobe HDS (HD network only), you can use the Akamai HDS Test Player. You must create the stream URL from the streamID and the [name] and [angle] parts of the streamName specified in your map file, and from the hostname found in the Akamai configuration screens, in the following form:

    http://<HostName>.akamaihd.net/z/[name]_[angle]@<streamID>/manifest.f4m

    Note: Assumes you have HDS delivery enabled in the associated Akamai configuration.
    To playback the stream through the Akamai network via Apple HLS (HD network only), you can use any HLS player, such as the stock iOS media player or Safari. Create the stream URL from the streamID and the [name] and [angle] parts of the streamName in your map file, and from the hostname found in the Akamai configuration screens, in the following form:

    http://<HostName>.akamaihd.net/i/[name]_[angle]@[streamID]/master.m3u8

    Note: Assumes you have HLS delivery enabled in the associated Akamai configuration.
    Note: See How to stream to the Akamai HD network for instructions on how to send a live stream to Akamai over RTMP using Stream Targets in Wowza Streaming Engine 4.2.

    BitGravity


    To send streams to BitGravity, use the rtmp profile. First, use the BitGravity Dashboard to provision a live stream.

    Following is an example entry to send the stream myStream to BitGravity, assuming the destination live stream has been provisioned through the dashboard:

    • Server: rtmp://rtpdev1.iad1.bitgravity.com/rtmp/push
    • Stream: test@test.com/71d73d4cfd1e2f2fed77238021a2cbbe/test/live/feed01

    The Server URL breaks down to:

    • Host: rtpdev1.iad1.bitgravity.com
    • Application: rtmp
    • AppInstance: push

    Example map entry:

    myStream={"profile":"rtmp", "streamName":"test@test.com/71d73d4cfd1e2f2fed77238021a2cbbe/test/live/feed01", "host":"rtpdev1.iad1.bitgravity.com", "application":"rtmp", "appInstance":"push"}

    Note: See How to stream to BitGravity for instructions on how to send a live stream to BitGravity using Stream Targets in Wowza Streaming Engine 4.2.

    EdgeCast


    To send a stream to EdgeCast, use the rtmp profile. The rtmp profile is configured to send to an RTMP CDN. When sending to EdgeCast, the following account information is required:

    • Host
    • ApplicationID
    • StreamName
    • Live Authentication Key

    Following is an example entry to send the stream myStream to EdgeCast, assuming these credentials:

    • Host: fso.lax.0001.edgecastcdn.net
    • ApplicationID: 200001
    • StreamName: myStream
    • Live Authentication Key: 0123456

    Example map entry:

    myStream={"profile":"rtmp", "host":"fso.lax.0001.edgecastcdn.net", "application":"200001", "streamName":"myStream?0123456", "originalTimecodeThreshold":"0x100000"}

    To playback the stream:

    1. Open [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html.

    2. Enter the address in the Server box as rtmp://fml.0001.edgecastcdn.net:1935/ApplicationId/.

    3. Enter the stream name in the Stream box.

    4. Click Connect.

    Icecast 2 Server


    To send to an Icecast 2 server, use the icecast2 profile. When sending to an Icecast 2 server , the following account information is required:

    • Host
    • Port
    • Username
    • Password
    • StreamName

    The following information is optional:

    • Public
    • URL
    • Name
    • Genre
    • ICQ ID
    • AIM ID
    • IRC ID

    Following is an example entry to send the stream myStream to a Icecast 2 server, assuming the following credentials:

    • Host: 192.168.1.10
    • Port: 8000
    • Username: source
    • Password: broadcast
    • StreamName: mountpoint.aac
    • Public: true
    • URL: http://www.wowza.com
    • Name: Wowza Server
    • Genre: Wowza Music
    • ICQ ID: icqme
    • AIM ID: aimem
    • IRC ID: ircme

    Example map entry:

    myStream={"entryName":"Icecast2Target", "profile":"icecast2", "port":"8000", "host":"192.168.1.10", "icecast2.irc":"ircme", "icecast2.icq":"icqme", "icecast2.description":"Wowza Audio Stream", "icecast2.genre":"Wowza Music", "destinationName":"icecast2", "password":"broadcast", "icecast2.name":"Wowza Server", "streamName":"mountpoint.aac", "icecast2.public":"true", "icecast2.aim":"aimem", "icecast2.url":"http://www.wowza.com", "userName":"source"}

    Note: See How to stream to SHOUTcast and Icecast for instructions on how to send a live audio stream to an Icecast2 server using Stream Targets in Wowza Streaming Engine 4.5.

    Justin.tv


    To send to Justin.tv, use the rtmp profile. On the channel Setup page, find the Stream Key link and use it as the stream name.

    • StreamName: ExampleStringKeyKFMpfXrssJhbq

    Example map entry:

    myStream={"profile":"rtmp", "host":"live.justin.tv", "application":"app", "streamName":"ExampleStringKeyKFMpfXrssJhbq"}

    To playback the stream, log in to your Justin.tv account and go to the Channel page. After an advertisement, the live video should start to play.

    Level 3


    To send to Level 3, use the rtmp profile. When sending to Level 3, the following account information is required:

    • User Name
    • Password
    • Host
    • Application

    Following is an example entry to send the stream myStream to Level 3, assuming these credentials:

    • User Name: myUser
    • Password: myPassword
    • Host: level3entry.com
    • Application: myaccount

    Example map entry:

    myStream={"profile":"rtmp", "streamName":"myStream", "host":"level3entry.com", "application":"myaccount", "userName":"myUser", "password":"myPassword", "originalTimecodeThreshold":"0x100000"}

    Limelight


    To send to Limelight, use the rtmp-limelight profile. The rtmp-limelight profile is configured to send to the Limelight CDN. When sending to Limelight, the following account information is required:

    • User Name
    • Password

    Following is an example entry to send the stream myStream to Limelight, assuming these credentials:

    • User Name: myUser
    • Password: myPassword

    Example map entry:

    myStream={"profile":"rtmp-limelight", "streamName":"myStream", "userName":"myUser", "password":"myPassword", "originalTimecodeThreshold":"0x100000"}

    To playback the stream:

    1. Open [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html.

    2. Enter the server address in the Server box as rtmp://[username].fc.llnwd.net/[username].

    3. Enter the stream name in the Stream box.

    4. Click the Connect.

    Note: See How to stream to Limelight for instructions on how to send a live stream to Limelight using Stream Targets in Wowza Streaming Engine 4.2.

    Livestream


    Note: Wowza Streaming Engine only supports the original Livestream platform (host: publish.livestream.com). New versions of LiveStream platform (host: livestream.com) aren't supported.
    To send to the original Livestream platform, use the rtmp profile and the following map file entry information:

    • Host: publish.livestream.com
    • Application: mogulus
    • appInstance: myChannel/username=myUser/password=myPassword/isAutoLive=true

    Note: Other options can be added to this, such as /aspectWidth=4, aspectHeight=3, and so on.
    Example map entry:

    myStream={"profile":"rtmp", "host":"publish.livestream.com", "application":"mogulus", "appInstance":"myChannel/username=myUser/password=myPassword/isAutoLive=true"}

    To playback the stream, log in to your Livestream account and go to the Channel page.

    Mirror Image Internet


    To send to Mirror Image, use the rtmp profile. When sending to Mirror Image, the following account information is required:

    • User Name
    • Password
    • Host
    • Application

    Following is an example entry to send the stream myStream to Mirror Image, assuming the following credentials:

    • User Name: myUser
    • Password: myPassword
    • Host: origin address provided during provisioning
    • Application: channel

    Example map entry:

    myStream={"profile":"rtmp", "host":"Origin Address", "application":"channel", "appInstance":"_definst_/doPublish=myPassword"}

    To playback the stream:

    1. Open [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html.

    2. Enter the address in the Server box as rtmp://[CNAME created during provisioning]:1935/channel/.

    3. Enter the stream name in the Stream box.

    4. Click Connect.

    Note: See How to stream to Mirror Image for instructions on how to send a live stream to Mirror Image using Stream Targets in Wowza Streaming Engine 4.2.

    MPEG-2 Transport Stream (MPEG-TS)


    To send an MPEG-TS stream to the multicast address 239.1.1.1:10000, use the following map entry:

    myStream={"profile":"mpegts", "streamName":"myStreamMPEGTS", "host":"239.1.1.1", "port":"10000", "rtpWrap":"false"}

    Note: See How to use MPEG-TS to distribute live streams for instructions on how to send a live stream to an MPEG-TS destination using Stream Targets in Wowza Streaming Engine 4.2.

    Real-time Transport Protocol (RTP), unicast or multicast


    To send a native RTP stream to the multicast address 239.1.1.1, ports 10002-10005, use the following map entry:

    myStream={"profile":"rtp", "streamName":"myStreamRTP", "host":"239.1.1.1", "videoPort":"10002", "audioPort":"10004"}

    Notes:
    • When you use native RTP to send a stream to a destination, the video and the audio each use a UDP port. Make sure that the VideoPort and AudioPort values are even numbers. This will allow room for the second port.

    • When you use MPEG-TS or native RTP to send a live stream to a destination, an SDP file is automatically generated in the [install-dir]/applications/[application]/sdp folder. The name of the SDP file is the StreamName value that's specified in the map entry with a .sdp file name extension. Media players that support multicast playback can use this file to play the stream.

    • When you use MPEG-TS or native RTP to send a live stream to a destination, both protocols use a similar configuration to send a stream to a unicast and multicast address. The only difference is that the Host item in the map configuration must point to the proper address range. Multicast address ranges are described in the following Wikipedia article Multicast address.

    • When streaming multicast on a Linux computer that has multiple network interfaces, there may be issues under certain kernel versions where the multicast stream isn't available on both interfaces. For more information, see CentOS 6 - Problems with Multicast.

    • See How to use RTP to distribute live streams for instructions on how to send a live stream to an RTP destination using Stream Targets in Wowza Streaming Engine 4.2.

    Shoutcast 1 Server


    To send to a Shoutcast 1 server, use the shoutcast1 profile. When sending to a Shoutcast 1 server, the following account information is required:

    • Host
    • Port
    • Password

    The following information is optional:
    • Public
    • URL
    • Name
    • Genre
    • ICQ ID
    • AIM ID
    • IRC ID

    Following is an example entry to send the stream myStream to a SHOUTcast 1 server, assuming the following credentials:

    • Host: 192.168.1.10
    • Port: 8000
    • Password: broadcast
    • Public: true
    • URL: http://www.wowza.com
    • Name: Wowza Server
    • Genre: Wowza Music
    • ICQ ID: icqme
    • AIM ID: aimem
    • IRC ID: ircme


    Example map entry:

    myStream={"entryName":"Shoutcast1Target", "profile":"shoutcast1", "port":"8000", "host":"192.168.1.10", "shoutcast.public":"true", "shoutcast.url":"http://www.wowza.com", "shoutcast.name":"Wowza Server", "destinationName":"shoutcast", "password":"broadcast", "shoutcast.genre":"Wowza Music", "shoutcast.icq":"icqme", "shoutcast.aim":"aimem", "shoutcast.irc":"ircme"}

    Note: See How to stream to SHOUTcast and Icecast for instructions on how to send a live audio stream to a Shoutcast 1 server using Stream Targets in Wowza Streaming Engine 4.5.

    Shoutcast 2 Server


    To send to a Shoutcast 2 server, use the shoutcast2 profile. When sending to a Shoutcast 2 server , the following account information is required:

    • Host
    • Port
    • Username
    • Password
    • StreamName

    The following information is optional:

    • Public
    • URL
    • Name
    • Genre
    • ICQ ID
    • AIM ID
    • IRC ID

    Following is an example entry to send the stream myStream to a SHOUTcast 2 server, assuming the following credentials:

    • Host: 192.168.1.10
    • Port: 8000
    • Username: authenticationHash
    • Password: broadcast
    • StreamName: 1
    • Public: true
    • URL: http://www.wowza.com
    • Name: Wowza Server
    • Genre: Wowza Music
    • ICQ ID: icqme
    • AIM ID: aimem
    • IRC ID: ircme

    Example map entry:

    myStream={"entryName":"Shoutcast2Target", "profile":"shoutcast2", "port":"8000", "host":"192.168.1.10", "shoutcast.icq":"icqme", "destinationName":"shoutcast", "password":"broadcast", "shoutcast.genre":"Wowza Music", "streamName":"1", "shoutcast.public":"true", "shoutcast.url":"http://www.wowza.com", "shoutcast.irc":"ircme", "userName":"authenticationHash", "shoutcast.name":"Wowza Server", "shoutcast.aim":"aimem"}

    Note: See How to stream to SHOUTcast and Icecast for instructions on how to send a live audio stream to a Shoutcast1 server using Stream Targets in Wowza Streaming Engine 4.5.

    UStream.tv


    To send to UStream.tv, use the rtmp profile. On the UStream Dashboard for your channel, find the Remote tab and get the URL and Stream Key. They will look something like this:

    • URL: rtmp://1.2345.fme.ustream.tv/ustreamVideo/67890
    • StreamName: ExampleStringKeyKFMpfXrssJhbq

    The streaming URL is broken into the following components in the map data:

    • Host: 1.2345.fme.ustream.tv
    • Application: ustreamVideo
    • AppInstance: 67890

    Example map entry:

    myStream={"profile":"rtmp", "host": "1.2345.fme.ustream.tv", "application":"ustreamVideo", "appInstance": "67890", "streamName":"ExampleStringKeyKFMpfXrssJhbq", "originalTimecodeThreshold":"0x100000"}

    To playback the stream, log in to your Ustream account and go to the Channel page. After an advertisement, the live video should start to play.

    YouTube Live


    To send to YouTube Live, use the rtmp profile. After your account is created, you'll receive a Stream Name and two URLs. They will look something like this:

    • URL: rtmp://a.rtmp.youtube.com/live2
    • Backup URL: rtmp://b.rtmp.youtube.com/live2?backup=1
    • StreamName: myaccount.u8w0-z0pr-c4qx-7jt1

    The streaming URLs are broken into the following components in the map data:

    • Host: a.rtmp.youtube.com
    • Application: live2

    Example map entry:

    myStream={"profile":"rtmp, "host":"a.rtmp.youtube.com", "application":"live2", "streamName":"myaccount.u8w0-z0pr-c4qx-7jt1"}

    Note: See How to stream to YouTube for instructions on how to send a live stream to YouTube using Stream Targets in Wowza Streaming Engine 4.2.

    Originally Published: 10-02-2010.
    Updated: For Wowza Streaming Engine 4.5.0 on 06-23-2016.

    If you're having problems or want to discuss this article, post in our forum.