OriginURL Question

[davidlgood]

I've finally configured an Origin/Edge server as well as another Edge server. Got load balancing and redirects seem to be working.

Origin/Edge -- Application "live" is set to "liverepeater-origin-record"
Origin/Edge -- Application "liveedge" is set to "liverepeater-edge"
Edge -- Application "liveedge" is set to "liverepeater-edge"

The plan is for multiple "live" streams to be sent (at the same time) to the Origin/Edge server using FMLE, as so:

FMS URL: rtmp://000.000.000.000/live
Stream: mp4:streamName

I was able to work with the sample Flash modules and can get the least-loaded server. The only problem is that I can't play the stream with a simple name. In other words, if the least loaded server returns a value of the EDGE-only server (let's assume the IP address for the edge-only server is: 111.111.111.111) I have to have the following information in the Wowza "LiveVideoStreaming" sample Flash player as follows:

Server: rtmp://111.111.111.111/liveedge
Stream: rtmp://000.000.000.000/live/_definst_/mp4:streamName

In other words, the Stream name has to point back to the original Origin application/stream. While I usually wouldn't care (as this is all "under the hood" and the end user will never see that) I don't really care for the information that results when I try to look at the connections information (by accessing http://111.111.111.111:8086/connectioncounts?flat). When I look at that information, the streamName is listed as such:

streamName="rtmp%3A%2F%2F000.000.000.000%3A1935%2F live%2F_definst_%2Fmp4%3AstreamName"

I was reading where you could assign the <OriginURL></OriginURL> to the Origin application, which should allow me to use the following:

Server: rtmp://111.111.111.111/liveedge
Stream: mp4:streamName

But this simply has not worked for me. I've tried to change the <OriginURL> as follows:

<Repeater>
<OriginURL>rtmp://000.000.000.000:1935/live</OriginURL)
<QueryString><![CDATA[]]></QueryString>
</Repeater>

I've added that line to the Application.xml in both "liveedge" applications. That didn't seem to do it... so I added it to the Origin "live" application (which is set to "liverepeater-origin-record") but that didn't work either... and I even tried adding it to the Repeater application's Application.xml -- nothing seems to do the trick.

I'm guessing I'm overlooking something simple, but I'm lost on this one. I have a dozen browser windows open trying to find clues here and there and am now starching my head.

Any help would be greatly appreciated. Thanks in advance!

[rrlanham]

Take a look at the the LiveVideoStream/clientFlex example, JW Player. Both of these are setup for the 302 redirect application.

With JW Player if you connect to an application configured to do 302 redirect, it just works, seamlessly, you can't tell by looking at the player, you have to check the ser There is nothing to configure on the player side.

We recommend using .stream files usually instead of the originURL method. If you publish a stream named "myStream" to the origin, you can make a .stream file on the edge in the content folder named origin.stream with this contents:

rtmp://[wowza-origin-address]:1935/liveorigin/myStream

With the Wowza Load Balancer redirect application configured and named "redirect", connect like this with JW Player

Streamer: rtmp://[wowza-loadbalancer-address]:1935/redirect
file: origin.stream

For reference:
http://www.wowza.com/forums/content....er-Quick-Start
http://www.wowza.com/forums/content....ncing-solution

Richard

[davidlgood]

Richard

Many thanks for the reply. I was looking at potentially using the JW Player, but I've been using a custom Flash application only because it allows an easy method to require a simple single password/code that people have to enter before it will advance to the actual video player. JW Player, to my knowledge, doesn't offer any method of simple authentication (without database/programming/etc.). The password/code isn't really intended to be any real "security" measure -- just a way to make it difficult for the random web surfer from viewing the webcast and consuming our limited resources.

Still... if you think it's the best method to get this done, I'll start digging into it.

One more question:

As stated previously, there will be several live streams coming to the Origin at once -- will a .stream file support multiple streams with different stream names?

In other words, if I have four streams, named "mp4:houston", "mp4rlando", "mp4:kansascity", and "mp4:newyork", can I place the following into the single "origin.stream" file and get it to work:

rtmp://[wowza-origin-address]:1935/liveorigin/mp4:houston
rtmp://[wowza-origin-address]:1935/liveorigin/mp4rlando
rtmp://[wowza-origin-address]:1935/liveorigin/mp4:kansascity
rtmp://[wowza-origin-address]:1935/liveorigin/mp4:newyork

?

[rrlanham]

Each .stream file can only have one line. But you can have many .stream files pointing to any number of different origin streams. houston.stream, orlando.stream, etc.

Richard