Reply to thread

Message

<blockquote data-quote="georgius" data-source="post: 1112240" data-attributes="member: 107951">[USER=82144]@mm1352000[/USER] it seems that you found problem very fast. I don't think that RTSP OPTIONS request is trigger for that, at least because of almost 20 seconds between error and last RTSP OPTIONS request. Dumped data came on RTSP data track, where have to be only valid RTP packets. Due to internal filter reasons are data packed into interleaved packet and processed, so real data are without 4 byte header. Anyway, remote server is sending invalid data on RTSP data track - text 'i'm not dead yet' is surely invalid RTP packet.[USER=133193]@Sigpi007[/USER], I need few days for finishing TV server plugin to be able to set filter to dump incoming data for further analysis.I don't see reason why it stops playback. I see that connection is closed, it is opened new open and data are surely received. It need further analysis (maybe culprit is in MPEG2 TS parsers).</blockquote>

[QUOTE="georgius, post: 1112240, member: 107951"] [USER=82144]@mm1352000[/USER] it seems that you found problem very fast. I don't think that RTSP OPTIONS request is trigger for that, at least because of almost 20 seconds between error and last RTSP OPTIONS request. Dumped data came on RTSP data track, where have to be only valid RTP packets. Due to internal filter reasons are data packed into interleaved packet and processed, so real data are without 4 byte header. Anyway, remote server is sending invalid data on RTSP data track - text '[FONT=Courier New]i'm not dead yet[/FONT]' is surely invalid RTP packet. [USER=133193]@Sigpi007[/USER], I need few days for finishing TV server plugin to be able to set filter to dump incoming data for further analysis. I don't see reason why it stops playback. I see that connection is closed, it is opened new open and data are surely received. It need further analysis (maybe culprit is in MPEG2 TS parsers). [/QUOTE]

Verification