Configure liverepeater reconnect behavior

Wowza Streaming Engine
1

Hi Everyone,

I’d like to modify the reconnect behavior on my liverepeater-edge. Is there a way I can listen for the disconnect event so I can programatically determine whether to reconnect or not?

Thanks,

Jay

2

What player are you using, Jay?

Richard

3

Jay,

You can send RTMP notifications from a Wowza origin to its edges. Let me look around for an example of that

Richard

4

Jay,

Try setting edge Application.xml StreamValidator /Enable to “false” and add /MediaCaster /streamTimeout Property set to “0”

<Property>
	<Name>streamTimeout</Name>
	<Value>0</Value>
	<Type>Integer</Type>
</Property>

Richard

5

Jay,

That is actually just the built-in Advanced MediaCaster Monitor in Wowza 4. In Wowza 3, if you have enabled the Advanced MediaCaster Monitor then you will want to disable that.

Richard

6

Jay,

You can turn off re-connection attempts by adding the streamTimeout Property set to “0” to Application.xml /MediaCaster Properties container:

<Property>
	<Name>streamTimeout</Name>
	<Value>0</Value>
	<Type>Integer</Type>
</Property>

Richard

7

Hi Richard,

I’m using a number of different players and STB’s. Really, I just want to prevent the liverepeater-edge from trying to reconnect to an origin I know to be unavailable. I have a multi origin network, and encoders can move between origins from time to time.

I’m using a class that implements IMediaStreamNameAliasProvider2 to locate my origin when a stream is first requested, but if the origin application shuts down while the edge is connected, I want to be able to locate the origin again instead of having the liverepeater try to reconnect on its own.

This needs to be entirely server side, and have no player dependency.

8

Thanks Richard.

I’m wondering though, is there nothing I can do at the edge to simply tell the repeater to not automatically reconnect?

9

Thanks Richard.

Is the StreamValidator config available in 3.5.x? I haven’t come across that one before

10

Great. Thanks again Richard.

11

Hmm… seems the streamTimeout property didn’t have an effect. Are there other properties available? Perhaps one that sets the number of reconnect attempts to zero?

12

Any ideas on other configs?