Yes.
Something like this:
1) ~ProxyServerMediaSession
2) ~ServerMediaSession //(at this point fProxyRTSPClient is already deleted)
3) deleteAllSubsessions()
4) Medium::close(fSubsessionsHead)
...
5) delete medium
6) ~ProxyServerMediaSubsession
7) envir() << *this << "::~ProxyServerMediaSubsession(
Andrey,
Thank you for the bug report.
I agree that there is probably a bug here, but I don’t like your proposed
solution.
If a “ProxyServerMediaSession” has been deleted, then nobody should be calling
“url()” on it.
I.e., the problem is not that code is trying to access an already-deleted
“P
No, I don’t want to make this change, because it would be a fairly large change
to the code, with limited benefit.
In particular, “RTPReceptionStats” was intended primarily to be used as a
database of statistics to be used when generating RTCP Reception Report (“RR”)
packets that get transmitte
Hello. I tried live555ProxyServer.cpp example and found that if:
1) we start program with -V option
2) there are active proxy streams (not clients, but just get descriptions
from rtsp streams);
3) we EXIT from event loop and delete server with *Medium::close()*
then it will crash due to access to
--- Begin Message ---
Classified as: {OPEN}
Hello Ross,
live555 does not provide any means to detect SRTP errors.
>From the user point of view, SRTP errors, mostly SRTP authentication issues,
>are considered as packet losses.
Here is a patch which adds to RTPReceptionStats some statistics abou
