My case is the third one: the client video decoder connects to rtsp-simple-server via RTSP/TCP but client causes rtsp-simple-server to kill TCP connection by sending invalid Receiver Report (please check my previous comments for Wireshark frame capture) ![]() Which case are you referring to? i'm willing to transform fatal errors into warnings if we clearly identify the issue. * when a client reads a stream from the server and sends invalid received reports, RTCP decoding errors are fatal `source: publisher`), RTCP decoding errors are fatal * when a camera publishes its stream to the server (i.e. Most media software print warning messages in case of malformed packets, so there's no reason to remove it. ![]() `source: rtsp://camera-url`), RTCP decoding errors are ignored and a warning message is printed. * when a camera is proxied from the server (i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |