Hi Ross,
Many thanks for your support and your quick development!!!
I will integrate your work and test it in the next few days.
PS : sorry for my last erroneously “reply all” on the mailing list.
Regards
Denis.
___
live-devel mailing list
live-devel@l
cembre 2018 06:26
À : live-devel@lists.live555.com
Objet : [Live-devel] Add a "reason for leaving" in RTCP Bye packet
Thanks to Denis Genestier for this suggestion. I have now installed a new
version (2018.12.14) of the “LIVE555 Streaming Media” code that implements this
(for both send
Thanks to Denis Genestier for this suggestion. I have now installed a new
version (2018.12.14) of the “LIVE555 Streaming Media” code that implements this
(for both sending and receiving RTCP “BYE” packets). There has been a change
to the API. This API change is backwards compatible; however,
> I think we’d have to change “setByeHandler()” to take, instead, a
> “ByeHandlerFunc*” as parameter, where we define “ByeHandlerFunc” to be
> something like:
> typedef void ByeHandlerFunc(void* clientData, char const* byeReason =
> NULL);
> Note that “byeReason” is an optional parameter.
> For our project we would have the requirements to make a distinction between
> different use cases of RTSP server closures from the client’s side: session
> shutdown for load balancing, priority management on stream access, …
> For that I was thinking about using the “reason for leaving” of the
Hi Ross,
I hope everything is fine for you.
For our project we would have the requirements to make a distinction between
different use cases of RTSP server closures from the client's side: session
shutdown for load balancing, priority management on stream access, ...
For that I was thinking abou
