>
>
> Hello everyone
>
>
>
> My name is Hernan and I am working with the FFMPEG SRT protocol. I'm
> having trouble connecting to an encrypted SRT stream. My test gateway is a
> VITEC Channel Link.
>
>
>
> The command line I'm using is the following
>
>
>
> ffmpeg -i Srt://
> 158.69.134.168:30000?connect_timeout=1500?latency=2000?mode=caller?listen_timeout=1000?passphrase=1234567890?pkt_size=188?pbkeylen=16?rcvbuf=800
> -c:v copy -c:a copy -f mpegts -metadata service_name="SRT  TEST" -metadata
> service_provider="TEST" udp://192.168.50.172:2002?pkt_size=188
>
>
>
> If the SRT stream is not encrypted, the connection is established without
> problems using the same command mentioned above.
>
>
>
>
>
> The error I get when connecting to the gateway when the SRT flow is
> encrypted is the following
>
>
>
> 10:03:55.279000/!W:SRT.cn: @939236380: processConnectResponse: rejecting
> per reception of a rejection HS response: ERROR:UNSECURE
>
> 10:03:55.279000/!W:SRT.cn: @939236380: processAsyncConnectRequest: REJECT
> reported from HS processing: Password required or unexpected - not
> processing further
>
> [srt @ 000001d8741b46c0] Connection to srt://
> 158.69.134.168:30000?connect_timeout=1500?latency=2000?mode=caller?listen_timeout=1000?passphrase=1234567890?pkt_size=188?pbkeylen=16?rcvbuf=800
> failed: I/O error
>
> [in#0 @ 000001d8741b3cc0] Error opening input: I/O error
>
> Error opening input file srt://
> 158.69.134.168:30000?connect_timeout=1500?latency=2000?mode=caller?listen_timeout=1000?passphrase=1234567890?pkt_size=188?pbkeylen=16?rcvbuf=800
> .
>
> Error opening input files: I/O error
>
>
>
> Does anyone know the reason for this error? Am I overlooking something and
> not realizing it?
>
>
>
   I am using ffmpeg version
2025-06-26-git-09cd38e9d5-essentials_build-www.gyan.dev.
   The Vitec Gateway is in mode listener. The FFMPEG is in mode caller

   Thank you in advance.
   Hernan Loisi
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to