search

bluenviron / mediamtx

Ready-to-use SRT / WebRTC / RTSP / RTMP / LL-HLS media server and media proxy that allows to read, publish, proxy, record and playback video and audio streams.
MIT License
11.41k stars 1.45k forks source link

EOF while proxying #1153

Closed pantera329 closed 1 year ago

pantera329 commented 1 year ago

Which version are you using?

v0.20.0

Which operating system are you using?

Describe the issue

Error returned: RTSP source: fix EOF error that happens when using TCP with some cameras (https://github.com/aler9/rtsp-simple-server/issues/548)

*Works correctly from 0.17.10 to version 0.17.14 inclusive, from version 0.17.15 to 0.20.0 results in a permanent error

Sep 15 09:45:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:45:54 INF [RTSP] [conn x.x.x.x:50674] opened Sep 15 09:45:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:45:54 INF [RTSP] [session 848144299] created by x.x.x.x:50674 Sep 15 09:45:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:45:54 INF [RTSP] [session 848144299] is reading from path 'cam240', with UDP, 2 tracks (H264, PCMA) Sep 15 09:46:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:46:54 INF [path cam240] [rtsp source] stopped Sep 15 09:46:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:46:54 INF [path cam240] [rtsp source] ERR: EOF Sep 15 09:46:54 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:46:54 INF [RTSP] [session 848144299] destroyed (terminated) Sep 15 09:47:00 vm-bd11e44c rtsp-simple-server: 2022/09/15 09:47:00 INF [RTSP] [conn x.x.x.x:50674] closed (session not found)

Describe how to replicate the issue

  1. start the server
  2. publish with api
  3. read with player, connection drops after ~132 seconds

Did you attach the server logs?

yes

Did you attach a network dump?

no

aler9 commented 1 year ago

Please provide a network dump as clearly stated in the issue tutorial, otherwise it's impossible to replicate the issue.

aler9 commented 1 year ago

This can't be solved without the author help.

github-actions[bot] commented 8 months ago

This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.