Menu
▾
▴
#23 No RTSP Keep Alive and Teardown request sent
Hi,
For any rtsp session started (by clicking on "live video", "Video Streaming", etc), no rtsp keep alive packets are sent. So after the session timeout, the video freezes. Simple rtsp request like GET_PARAMETER can be sent every minute to keep the session alive. Also none of the opened rtsp sessions are closed by moving to other view(say "Network settings"). So even though user is not viewing the video the video streaming will continue(until session timeout) and load the NVT. This can be solved by sending a rtsp TEARDOWN request on moving away from the video view.
Regards,
Rakshith
Hi,
the bug related to TEARDOWN will be fixed in few nearest releases. As concerning rtsp keep-alive, i need to do some investigations, if you know any documentation where it is described, please provide me with links to it.
thanks for your report,
Sincerely yours,
Andrei
Hi,
In the latest release of odm(v1.7.5202), RTSP TEARDOWN seems to be supported and I have verfied it against our NVT. However the keep-alive packets are not sent causing the video to freeze after the session timeout. The following link
http://tools.ietf.org/html/rfc2326#page-37
gives information as to how to keep the rtsp client-server session alive. As per the rtsp rfc GET_PARAMETER, PLAY and SET_PARAMETER can be used to keep the session alive. Our NVT implementation supports all these to keep the session alive. In our testing we have seen that VLC uses GET_PARAMETER to keep the session alive while the official onvif test tool uses SET_PARAMETER to keep the session alive.
Regards,
Rakshith
Hi.
Did anybody resolve this problem ?
I have the same and I don't how to write the code in WinFormSample project
Thanks
I've just got the latest, and the problem definitely remains. One work-around may be to use TCP or HTTP instead of UDP for the transport. The RTCP messages over the TCP connection appear to be enough for some servers to treat this as a keep-alive.