[Live-devel] Need advice on best way to proceed.

[Frederik De Ruyck]

Q: Is this supported by the Live555 media server libraries?
A: There is no support, you have to build it in yourself

One of your streams will indeed return a=sendonly, check on that string 
to detect the backchannel MediaSubsession.
Instead of creating a FramedSource in your MediaSubsession you have to 
create an RTPSink.
Eventually you will call startPlaying on the sink and then you can start 
sending data into the sink.

You should read the onvif specs first to see how the communication must be.
There is a backchannel section.
http://www.onvif.org/specs/stream/ONVIF-Streaming-Spec-v210.pdf


Op 02-Jun-16 om 8:42 PM schreef Ben Rush:
> Fredrick,
>
> Great, thanks for the info, at least. So, as far as the ONVIF 
> backchannel stuff is concerned:
>
> I noticed that, per the specification, it requires that one of the 
> streams be a=sendonly (for the "backchannel" stream). What I'm 
> confused about is this in particular. Is this supported by the Live555 
> media server libraries? To me this means the server itself should be 
> receiving streaming content from the client (right?), but I don't see 
> anything in the server libraries for *receiving* content.
>
> We've had a pretty basic use case up until now, and so some of these 
> more advanced server features may have escaped me. But, I'm unable to 
> find any way for the server to receive media content from a client in 
> the API.
>
> Thanks again.
>
> On Thu, Jun 2, 2016 at 4:08 AM Frederik De Ruyck 
> <frederik.deruyck at vsk.be <mailto:frederik.deruyck at vsk.be>> wrote:
>
>     No there's no support in LiveMedia yet.
>
>     We have to do the same so I'm implementing it myself atm. You can
>     use the RTSP require tag (which is optional) and Onvif backchannel
>     (which uses RTSP require).
>
>     I hacked it into someone else his startings:
>     https://github.com/alb423/live555_20140206
>
>     I won't post my modifications to this github project because the
>     project is quite sloppy and it got worse because I hard coded a
>     lot of things.
>
>     I had to add RTSP require fields everywhere it was still missing
>     in the project (take a look at RTSPClient::setRequestFields,
>     modify every command if it's backchannel related, add require to it)
>
>     The project uses UDP btw, I don't have it working with tcp yet.
>
>     You will have to learn how LiveMedia works to get it done anyhow.
>
>
>     Op 01-Jun-16 om 9:09 PM schreef Ben Rush:
>>     We have built a RTSP streaming server using Live555's server
>>     libraries:
>>
>>     ....
>>     RTSPServer* rtspServer = RTSPServer::createNew(*usageEnvironment,
>>     StreamingOptions::PortNumber, NULL);
>>     ....
>>
>>     And so on. Works like a charm and we're very happy with it. What
>>     we're needing now is a solution for two-way audio, meaning we
>>     have a camera viewing a room and we'd like a person in the room
>>     and the person viewing the room to be able to talk with one
>>     another. To reduce overhead we'd like to enable the audio to be
>>     duplex, so it shares the same channel (much like VOIP). I'm quite
>>     certain but I thought I'd ask: there's no support for this in
>>     RTSP and therefore no support for duplex audio in Live555's
>>     server libraries, correct?
>>
>>
>>
>>
>>     _______________________________________________
>>     live-devel mailing list
>>     live-devel at lists.live555.com <mailto:live-devel at lists.live555.com>
>>     http://lists.live555.com/mailman/listinfo/live-devel
>
>     _______________________________________________
>     live-devel mailing list
>     live-devel at lists.live555.com <mailto:live-devel at lists.live555.com>
>     http://lists.live555.com/mailman/listinfo/live-devel
>
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20160603/7ddf398f/attachment.html>