Besides, there may be other clients out there that would benefit
from this patch.
For the last time: I won't be adding a patch to have the server set
the "timeout=" parameter, because this would - incorrectly - be
telling cliente that they need to send periodic RTSP commands to
indicate 'live
Ross Finlayson wrote:
if you're using our software to develop your client,
I can see how you might have gotten the impression that I was writing
the client myself. When I said I had a client here, I meant it was
sitting on the table over there to my right. :) It's a set-top box,
much lik
Later, in section 6.2: "Turning off RTCP reception reports is NOT
RECOMMENDED... However, doing so may be appropriate for systems...
that don't require feedback on the quality of reception or liveness
of receivers and that have other means to avoid congestion."
That definitely applies to my s
Ross Finlayson wrote:
I have a client here that doesn't send RTCP RR packets to the server.
Your client is broken, because RTCP is a required part of the RTP/RTCP
standard. It is not optional functionality.
RFC 3550, section 6.0: "[RTCP] SHOULD be used in all environments, but
particularl
Ross Finlayson wrote:
Our server impelmentation uses both RTSP commands *and* RTCP ("RR")
packets from clients to indicate liveness. Therefore, the
"timeout" parameter in a "Session:" header is not needed, because
periodic RTSP commands (e.g., "GET_PARAMETER") from the client are
not needed i
Ross Finlayson wrote:
Our server impelmentation uses both RTSP commands *and* RTCP ("RR")
packets from clients to indicate liveness. Therefore, the "timeout"
parameter in a "Session:" header is not needed, because periodic RTSP
commands (e.g., "GET_PARAMETER") from the client are not needed in
Our server impelmentation uses both RTSP commands *and* RTCP ("RR")
packets from clients to indicate liveness. Therefore, the "timeout"
parameter in a "Session:" header is not needed, because periodic RTSP
commands (e.g., "GET_PARAMETER") from the client are not needed in
order to tell the ser
live555MediaServer has a hard-coded 45-second timeout in it for
detecting clients that go away without telling the server. The timer
gets reset when a client sends another RTSP command, which a conforming
client does periodically to convince the server that it is still alive.
RFC 2326 (RTSP)
