2019-07-07, 07:13 AM
(This post was last modified: 2019-07-07, 07:19 AM by Kay Diefenthal.)
i think the current state of Sat>ip is not bad but there should somethings implemented too
in the Rtsp stack is the session timeout ignored
the Session Timeout param can you get from the RTSP Setup Response
and this timeout param need you for an Keepalive thread who send an RTSP Options to the server so knows the Server that there is an client is listen
without this thread means the server there is no one that listen and close the connection
RTCP is very use full to look for connection infos
RTCP APP hold informations for the tuned frequency wich tuner/ frontend , how strong the Signal (Level Quality) values are and is signal present locked
sure RTSP Describe Response hold this infomation too but not all server support ways some use RTCP others use RTSP
RTCP Bye send by the server and the client should than stop all Threads RTP RTCP RTSP
Servers send this RTCP Bye packets if they should reboot
in the Rtsp stack is the session timeout ignored
the Session Timeout param can you get from the RTSP Setup Response
and this timeout param need you for an Keepalive thread who send an RTSP Options to the server so knows the Server that there is an client is listen
without this thread means the server there is no one that listen and close the connection
RTCP is very use full to look for connection infos
RTCP APP hold informations for the tuned frequency wich tuner/ frontend , how strong the Signal (Level Quality) values are and is signal present locked
sure RTSP Describe Response hold this infomation too but not all server support ways some use RTCP others use RTSP
RTCP Bye send by the server and the client should than stop all Threads RTP RTCP RTSP
Servers send this RTCP Bye packets if they should reboot