[Live-devel] Detecting network failure

Jeremy Noring jnoring at logitech.com
Wed Mar 24 15:08:26 PDT 2010


On Wed, Mar 24, 2010 at 2:45 PM, Ross Finlayson <finlayson at live555.com>
wrote:
> I should warn you that I consider the "DarwinInjector" stuff to be
> deprecated technology, and although I'll probably be upgrading it to do an
> asynchronous "ANNOUNCE", there's no guarantee that it will continue to be
> supported in the future.  We have our own RTSP server implementation, and
> people should really be using this, rather than using this hack along with
> some other implementation.

Well, let me explain a few things to you (you seem confused about why I'm
doing this), and maybe you can recommend something better.

We have a device that streams audio/video.  This device will run on our
customer's private networks (think SOHO type network at your house--dumpy
linksys/dlink/netgear/whatever router hooked up to cable/DSL/etc.).  To view
AV remotely, we have to traverse NAT somehow (customers cannot directly
connect to the device behind their NAT router without configuration).  We
don't want people to have to configure their router (i.e. port forwarding)
because the vast majority of people A) do not know how to do this and B)
haven't the foggiest clue what port forwarding/networking involves.
Furthermore, doing it with multiple devices behind the same NAT is extra
cumbersome/complicated/error prone, particularly when you throw DHCP into
the mix on their internal network.

So, we relay video through a central server that we support and maintain.  I
use the DarwinInjector to push video to Wowza (http://www.wowzamedia.com/),
and that relays the video onto some client elsewhere (note that wowza can
also transcode, so it can deliver over rtmp, rtsp, etc).  Even when we do
get a more sophisticated NAT traversal method, like STUN/ICE/whatever, we're
still going to need this relay for the remaining customers for whom
STUN/ICE/whatever doesn't work.

What alternate options to the DarwinInjector do I have that would accomplish
this with Live555?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20100324/54949811/attachment.html>


More information about the live-devel mailing list