> I have implemented a multicast out component using SimpleRTPSink and
> RTCPInstance, and a multicast in component using SimpleRTPSource and
> RTCPInstance. When the multicast in component is receiving from a multicast
> out component on the same device, I have them share Groupsocks for RTP and
Hello,
I have implemented a multicast out component using SimpleRTPSink and
RTCPInstance, and a multicast in component using SimpleRTPSource and
RTCPInstance. When the multicast in component is receiving from a multicast
out component on the same device, I have them share Groupsocks for RTP and
RT
Thank you very much for your prompt and helpful response Ross.
> You should definitely upgrade. Not only do we not support old versions of the
> code, but (most importantly) newer versions fix several, often-important bugs,
> including security vulnerabilities. You are putting your system at g
> We rely on a now-ancient version (2009-09-04) of LIVE555 Streaming Media
> library as the basis for the RTSP streaming server in our [open source]
> product. I'm trying to assess how feasible it would be to upgrade to the
> latest version of LIVE555 in the near future.
You should definitely u
Hello
We rely on a now-ancient version (2009-09-04) of LIVE555 Streaming Media library
as the basis for the RTSP streaming server in our [open source] product. I'm
trying to assess how feasible it would be to upgrade to the latest version of
LIVE555 in the near future. Obviously there are challen
> On Aug 4, 2015, at 5:47 AM, Sree Venkedesh wrote:
>
> Hi ,
> i would like to know the streamname from the rtspURL requested by client .
First, you didn’t way for sure, but I assume that you are developing a RTSP
server.
Each RTSP server passes the ‘stream name’ as a parameter to the
“loo
