> Unless you know that you will be streaming to multiple receivers, and have
> always multicast routing enabled between the sender and (all of) the
> receivers, you should use unicast streaming, using the
> “testOnDemandRTSPServer” code (i.e., with “OnDemandServerMediaSubsession”
> objects) as
Unless you know that you will be streaming to multiple receivers, and have
always multicast routing enabled between the sender and (all of) the receivers,
you should use unicast streaming, using the “testOnDemandRTSPServer” code
(i.e., with “OnDemandServerMediaSubsession” objects) as your model.
Thank you Ross Finlayson,
I changed
destinationAddress.s_addr = chooseRandomIPv4SSMAddress(*env);
to
destinationAddress.s_addr = our_inet_addr("192.168.31.1");
for testing and now it works, so missing multicast support really is the
problem here.
What is the right way to go on allowing both: m
> Now I tried to run testH264VideoStreamer with a test.264 file and using
> openRTSP tool to receive the stream.
[…]
> but the created openRTSP output file is empty.
>
>
> Using testOnDemandRTSPServer, openRTSP does receive packets, so I guess it's
> not a problem of firewall settings?
>
>
>
Hi,
I'm working on an embedded Live streaming platform.
I've cross-compiled live555 with a SoC toolchain, using -DLOCALE_NOT_USED and
adjusting compiler name (these are the only changes I made).
Now I tried to run testH264VideoStreamer with a test.264 file and using
openRTSP tool to receive th
