Results 1 to 8 of 8

Thread: WOWZ reconnect

  1. #1

    Default WOWZ reconnect

    We're running a master server and several edge servers. Master server PublishingType is rtp-live, edge servers are liverepeater-edge.

    We're using this platform for IP cameras streaming. Some types of IP cameras disconnect randomly for various reasons. Wowza master server simply reconnects and viewers in flash players don't see any huge interruption - the stream is not stopped.

    Of course it's not a good idea to stream from master server so we route viewers to the edge servers. When IP camera disconnects from master server, flash players connected to edge servers are disconnected - the stream simply stops and they need to click to Play again.

    How can we avoid this? It works fine on master server.


  2. #2


    So really no idea?

  3. #3
    Join Date
    Dec 2007


    Try making the origin Application.xml /StreamType "live" or "liverepeater-origin", and start streams in StreamManager or /conf/StartUpStreams.xml with MediaCaster type "rtp". On the edge servers, start the origin streams in /conf/StartUpStreams.xml with MediaCaster type "liverepeater".

    On the origin, you might try using ModuleMediaCasterStreamMonitorAdvanced to monitor and reset the cameras if necessary:

    There is a trouble-shooting section of the IP camera/RTSP restreaming guide, and some Property settings that might help for some of these cameras:

    But what you might find really interesting in your case of various cameras is this new method of adding settings to a .stream file. This way you can handle different cameras as needed:


  4. #4


    Thanks. Using live PP type is not an option for us - we have to use rtp-live and connect to cameras on demand.

  5. #5


    Hi Rob,

    What is happening is that the mediaCaster between the origin and edge is detecting the unPublished event from the camera stream when it resets and is sending a `NetStream.Play.UnpublishNotify` message to the players. It does this because it doesn't know if the camera is going to reconnect or not.

    When you are connected directly to the origin, the mediacaster that connects to the cameras doesn't fire off an unPublished message when a reset happens.

    The only way around it is to have the player ignore the NetStream.Play.UnpublishNotify message but this may cause problems when the stream is really unpublished.


  6. #6


    Is the any way to avoid this behavior? Override with module?

  7. #7
    Join Date
    Dec 2007


    If you test your configuration (origin=rtp-live, edge=liverepeater-edge, no pre-starts on either side) with the Wowza /example/LiveVideoStreaming/FlashRTMPPlayer/player.html, you will not have the problem, because that player ignores the NetStatusEvent "NetStream.Play.onUnPublish" notification Roger mentions. The affect is that the MediaCaster system on the edge starts re-connect cycle, which tickles the origin and keeps it trying to re-connect. Otherwise, if there are no clients, after a few reconnect attempts and unpublish event on the origin, the origin app stops.

    JW player has a live stream reconnect plugin that will handle this, but it is only supported in JW Player 4 and 5, not 6

    Otherwise, if you have control of the player source, you can suss-out the handling of the NetStatusEvent notification "NetStream.Play.onUnPublish", and just don't handle it, comment out whatever it is doing in that case.


  8. #8


    Yes, livestream plugin is an option. But not a good one - we need to solve it for mobile devices as well so we prefer some Wowza-side solution.

Similar Threads

  1. how is wowz protocol deffirrent rtmp
    By hehe37 in forum General Forum
    Replies: 3
    Last Post: 07-28-2014, 10:22 AM
  2. WOWZ™ protocol triggered by upgrade to all v3.5
    By rainman in forum General Forum
    Replies: 12
    Last Post: 01-04-2013, 01:12 PM
  3. how to use vlc to provide rtsp stream to wowz server?
    By shadowlin in forum Live Streaming and Encoder Discussion
    Replies: 8
    Last Post: 07-08-2012, 01:32 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts