You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to open srt stream from haivision srt gateway AWS appliance. astits: fetching next packet failed: astits: fetching next packet from buffer failed: astits: reading 188 bytes failed: max buffer size exceeded
#3960
Open
gargolito opened this issue
Nov 15, 2024
· 0 comments
My use case is to read an encrypted stream from a haivision srt gateway appliance on AWS.
start the server
publish with HLS (although I've tried rtsp and just srt with with the same problem)
read with srt.
I am able to read the same feed with ffmpeg and vlc. Unfortunately I cannot change the configuration on the srt gateway - I intended to use mediamtx to monitor srt feeds at lower resolutions with hls. I have changed my mediamtx config to only do srt and hls and turned off all other options trying to isolate the problem I've tried both with and without SourceOnDemand, but same issue reading - I'm guessing that reading is the actual problem. I'm attaching my config here: mediamtx.yml.gz
the gateway is configured as a listener with these parameters:
link: mtu 1496, ttl 64, ToS 0x68
srt: Latency 300, Encryption AES128
A POSSIBLE SEPARATE ISSUE TO MAKE YOU AWARE OF
Although the transcode to hls does not work for me in this use case, the server continues as though the HLS feed is working, I would expect it to fail or at least indicate that there's a problem, so I think there is something in the code that is not catching the error - I would expect something to the effect of "no sources available."
Which version are you using?
1.9.3
Which operating system are you using?
Linux amd64 standard
Describe how to replicate the issue
My use case is to read an encrypted stream from a haivision srt gateway appliance on AWS.
I am able to read the same feed with ffmpeg and vlc. Unfortunately I cannot change the configuration on the srt gateway - I intended to use mediamtx to monitor srt feeds at lower resolutions with hls. I have changed my mediamtx config to only do srt and hls and turned off all other options trying to isolate the problem I've tried both with and without SourceOnDemand, but same issue reading - I'm guessing that reading is the actual problem. I'm attaching my config here: mediamtx.yml.gz
the gateway is configured as a listener with these parameters:
link: mtu 1496, ttl 64, ToS 0x68
srt: Latency 300, Encryption AES128
A POSSIBLE SEPARATE ISSUE TO MAKE YOU AWARE OF
Although the transcode to hls does not work for me in this use case, the server continues as though the HLS feed is working, I would expect it to fail or at least indicate that there's a problem, so I think there is something in the code that is not catching the error - I would expect something to the effect of "no sources available."
Server logs
srt_problem_mediamtx.log
Network dump
srt_problem_mediamtx.pcap.gz
The text was updated successfully, but these errors were encountered: