Thanks for the note. I’ll be including this change in the next release of the
software. (However, I won’t be including the “UsageEnvironment&” parameter,
for consistency with “makeSocketNonBlocking()”, and to avoid having to change
any existing code that calls “makeSocketBlocking()”.)
Ross F
I have tested for over 100 hours with instrumentation to confirm the code
is being used.
This happens during rtsp-over-http and appears to be where the device is
not expecting Receiver Reports back on the GET connection.
RTPInterface calls the following function in GroupsockHelper.cpp with 500
mil
