aler9
commented
3 months ago Hello,
Regarding the fact that the connection is closed after GET_PARAMETER requests, it seems to me that the server is responding indeed, and that the connection gets closed after some seconds, for unknown reasons (you cut the log):
2024/01/14 23:56:42 DEB [RTSP] [conn 192.168.10.50:49578] [c->s] GET_PARAMETER rtsp://192.168.7.252:8554/mystream RTSP/1.0
mediamtx-rtsp | CSeq: 1106
mediamtx-rtsp | Session: 27b216cb2e9e4c738328c6974932f6b3
mediamtx-rtsp | User-Agent: HIP 2.42.1.55.3
mediamtx-rtsp |
mediamtx-rtsp |
mediamtx-rtsp | 2024/01/14 23:56:42 DEB [RTSP] [conn 192.168.10.50:49578] [s->c] RTSP/1.0 200 OK
mediamtx-rtsp | CSeq: 1106
mediamtx-rtsp | Content-Type: text/parameters
mediamtx-rtsp | Server: gortsplib
mediamtx-rtsp | Session: 27b216cb2e9e4c738328c6974932f6b3;timeout=60
mediamtx-rtsp |
2024/01/14 23:56:47 INF [RTSP] [conn 192.168.10.50:49578] closed: Keep in mind that the player has to send GET_PARAMETER requests BEFORE the timeout, not after, even though i don't think the error is related to GET_PARAMETER.
Regarding error "UDP ports 4709 and 4710 are already assigned to another reader with the same IP", it's a limitation of your player, since it should pick random port (or at least free ports) instead of using fixed ones.
Therefore, both issues seem player-related.
Luis-Sarabando
Which version are you using?
Docker -> latest-ffmpeg
Which operating system are you using?
Describe the issue
Im using a video feed from Camera "A" and converting it into a feed that Video Door bell "B" can handle. The video is accepted and working but after the initial 60seconds it will stop working.
Describe how to replicate the issue
Did you attach the server logs?
yes, see below
Did you attach a network dump?
yes HIPexternalVideo.zip
Logs from the docker container,
Looking at these logs it suggests, this starts a steam which has a 60 second timeout, after this timeout equipment "B" video doorbell tries to extend the feed as per RFC2326 Medixmtx doesnt seem to answer so it closes the stream?
It will then try and reconnect every 10 seconds, but the ports are in use
1st attempt:
2nd attempt:
3rd attempt:
4th attempt:
5th attempt:
After the 5th attempt it will timeout
2024/01/15 00:11:50 INF [RTSP] [session 08a882ab] destroyed: session timedSo a new session can be made again, So it will work again for 60 seconds.