<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Dear Ross,</p>
<p>..thats it, sorry for my bad explanation.</p>
<p>Unicast/one-client is suitable, so I'll follow the <font size="2"><span style="font-size:10pt;">testOnDemandRTSPServer</span></font> model.<br>
</p>
<p>Thanks for your help</p>
<p>Edward<br>
</p>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> live-devel <live-devel-bounces@ns.live555.com> on behalf of Ross Finlayson <finlayson@live555.com><br>
<b>Sent:</b> 12 September 2016 16:00<br>
<b>To:</b> LIVE555 Streaming Media - development & use<br>
<b>Subject:</b> Re: [Live-devel] Listen for reuest to stream live video</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">OK, thinking about this some more - now I think I understand.<br>
<br>
You’re streaming from your camera via IP multicast (because you're using the ‘Elphel’ code as a model). In this case, each RTSP session - from a client - asks to receive the (existing) IP multicast stream, but does not start a new stream (or stop the existing
multicast stream).<br>
<br>
So you want to know how to stop the IP multicast stream (independently of RTSP clients). There’s no way within the RTSP protocol to do this, so - if you really want to do this - you’d have to come up with your own protocol/mechanism to do this, and implement
it yourself. (The actual code inside your server would be straightforward: simply call<br>
yourSink->stopPlaying();<br>
<br>
But perhaps you should ask yourself if you *really* want to stream via IP multicast. If you’re streaming to only one client - or to multiple clients located on non-IP-multicast routed networks - then you would be better off streaming via IP *unicast* instead.
If you were to do this, then the RTSP server would send out a stream only when requested by a RTSP client. This can be done easily using our “testOnDemandRTSPServer” code as a model; see<br>
<a id="LPlnk434241" href="http://live555.com/liveMedia/faq.html#liveInput-unicast">
http://live555.com/liveMedia/faq.html#liveInput-unicast</a><br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/">http://www.live555.com/</a><br>
<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
</div>
</span></font></div>
</div>
</body>
</html>