Hi,
at first glance its hard to say why the connection isn't successful, however setting up the RTSP stream fails on the very first step - getting the stream description.

It is expected that no hls files are generated as no media has been sent.

Are you sure that the RTSP camera is available?
You might try connecting to it using VLC media player or OBS

First, really nice project this - thanks! Trying it out by making a Membrane time lapse application, intention is to grab one image an hour or so from the same camera that kruskakli uses. For starters I also try the rtsp_to_hls demo with an URL that works perfectly with VLC and get similar issues:

> mix run --no-halt
> Compiling 1 file (.ex)
> warning: Membrane.Pipeline.play/1 is deprecated. use pipeline's :playback action instead
>   lib/application.ex:26: Membrane.Demo.RtspToHls.Application.start/2
> 
> Generated hls_proxy_api app
> [debug] Application is starting
> [debug] Pipeline start link: module: Membrane.Demo.RtspToHls.Pipeline,
> pipeline options: %{output_path: "hls_output", port: 20000, stream_url: "rtsp://arnold:arnold@192.168.0.155:554/stream1"},
> process options: []
> 
> [debug] Source handle_init options: %{output_path: "hls_output", port: 20000, stream_url: "rtsp://arnold:arnold@192.168.0.155:554/stream1"}
> [debug] ConnectionManager: start_link, args: [stream_url: "rtsp://arnold:arnold@192.168.0.155:554/stream1", port: 20000, pipeline: #PID<0.395.0>]
> [debug] ConnectionManager: Initializing
> [debug] ConnectionManager: Connecting
> [debug] [pipeline@<0.395.0>] Changing playback state from stopped to prepared
> [debug] [pipeline@<0.395.0>] Playback state changed from stopped to prepared
> [debug] [pipeline@<0.395.0>] Changing playback state from prepared to playing
> [debug] [pipeline@<0.395.0>] Playback state changed from prepared to playing
> [debug] ConnectionManager: Setting up RTSP description
> [warning] ConnectionManager: Connection failed: :getting_rtsp_description_failed
> [debug] ConnectionManager: Connecting
> [debug] ConnectionManager: Setting up RTSP description
> [warning] ConnectionManager: Connection failed: :getting_rtsp_description_failed

kruskakli pajso 
As I can see it failed on DESCRIBE so it's not about auth or unable to connect cam at all.
Firstly, try to change 
`membrane_rtsp` in mix.exs to `0.3.2`  or `0.3.3` there are some rtsp servers that we are having issues with as they tend to send response for DESCRIBE in parts and our client fails while parsing it.
We fixed it in in `0.3.2` but with that fix rtsp sometimes hits timeout, so we fixed it differently in `0.3.3`  but some time after we noticed that it's still failing in some cases.
I still haven't debug it but maybe it's time to do it 🙂

blazpie thanks for feedback; with 0.3.2, now I get this:

`[debug] ConnectionManager: Setting up RTSP description
[error] GenServer #PID<0.409.0> terminating
** (MatchError) no match of right hand side value: [""]
    (membrane_rtsp 0.3.2) lib/membrane_rtsp/response.ex:28: Membrane.RTSP.Response.parse/1
    (membrane_rtsp 0.3.2) lib/membrane_rtsp/rtsp.ex:76: Membrane.RTSP.handle_call/3
    (stdlib 4.3) gen_server.erl:1149: :gen_server.try_handle_call/4
    (stdlib 4.3) gen_server.erl:1178: :gen_server.handle_msg/6
    (stdlib 4.3) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message (from ConnectionManager): {:execute, %Membrane.RTSP.Request{method: "DESCRIBE", path: nil, headers: [], body: ""}}
State: %Membrane.RTSP.Logic.State{transport: #Port<0.5>, uri: %URI{scheme: "rtsp", authority: "arnold:arnold@192.168.0.155:554", userinfo: "arnold:arnold", host: "192.168.0.155", port: 554, path: "/stream1", query: nil, fragment: nil}, transport_module: Membrane.RTSP.Transport.TCPSocket, session_id: nil, cseq: 0, execution_options: [], auth: :basic}
Client ConnectionManager is alive

    (stdlib 4.3) gen.erl:256: :gen.do_call/4
    (elixir 1.14.4) lib/gen_server.ex:1035: GenServer.call/3
    (hls_proxy_api 0.1.0) lib/connection_manager.ex:183: Membrane.Demo.RtspToHls.ConnectionManager.get_rtsp_description/1
    (hls_proxy_api 0.1.0) lib/connection_manager.ex:69: Membrane.Demo.RtspToHls.ConnectionManager.connect/2
    (connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
    (stdlib 4.3) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
[error] GenServer ConnectionManager terminating
** (stop) exited in: GenServer.call(#PID<0.409.0>, {:execute, %Membrane.RTSP.Request{method: "DESCRIBE", path: nil, headers: [], body: ""}}, 5000)
    ** (EXIT) an exception was raised:
        ** (MatchError) no match of right hand side value: [""]`

`[debug] ConnectionManager: Setting up RTSP description
[error] GenServer #PID<0.413.0> terminating
** (MatchError) no match of right hand side value: [""]
    (membrane_rtsp 0.3.3) lib/membrane_rtsp/response.ex:28: Membrane.RTSP.Response.parse/1
    (membrane_rtsp 0.3.3) lib/membrane_rtsp/rtsp.ex:76: Membrane.RTSP.handle_call/3
    (stdlib 4.3) gen_server.erl:1149: :gen_server.try_handle_call/4
    (stdlib 4.3) gen_server.erl:1178: :gen_server.handle_msg/6
    (stdlib 4.3) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message (from ConnectionManager): {:execute, %Membrane.RTSP.Request{method: "DESCRIBE", path: nil, headers: [], body: ""}}
State: %Membrane.RTSP.Logic.State{transport: #Port<0.6>, uri: %URI{scheme: "rtsp", authority: "arnold:arnold@192.168.0.155:554", userinfo: "arnold:arnold", host: "192.168.0.155", port: 554, path: "/stream1", query: nil, fragment: nil}, transport_module: Membrane.RTSP.Transport.TCPSocket, session_id: nil, cseq: 0, execution_options: [], auth: :basic}
Client ConnectionManager is alive

    (stdlib 4.3) gen.erl:256: :gen.do_call/4
    (elixir 1.14.4) lib/gen_server.ex:1035: GenServer.call/3
    (hls_proxy_api 0.1.0) lib/connection_manager.ex:183: Membrane.Demo.RtspToHls.ConnectionManager.get_rtsp_description/1
    (hls_proxy_api 0.1.0) lib/connection_manager.ex:69: Membrane.Demo.RtspToHls.ConnectionManager.connect/2
    (connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
    (stdlib 4.3) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
[error] GenServer ConnectionManager terminating
** (stop) exited in: GenServer.call(#PID<0.413.0>, {:execute, %Membrane.RTSP.Request{method: "DESCRIBE", path: nil, headers: [], body: ""}}, 5000)
    ** (EXIT) an exception was raised:
        ** (MatchError) no match of right hand side value: [""]
            (membrane_rtsp 0.3.3) lib/membrane_rtsp/response.ex:28: Membrane.RTSP.Response.parse/1

blazpie got [debug] [pipeline@<0.390.0>] Playback state changed from prepared to playing
[debug] ConnectionManager: Setting up RTSP description
[warning] ConnectionManager: Connection failed: :getting_rtsp_description_failed

Opened the TAPO camera up, if you like to try connecting: rtsp://arnold:arnold@81.225.49.228:554/stream1

I have no idea what the meaning of this is: `o=- 14665860 31787219 1 IN IP4 192.168.0.155`

after some tracing with `edbg` I found this

ExSDP.Address.parse_addrtype/1 doesn't like "IN" , not sure what to do about this...

where is this 'o=' field described? can't seem to find it in RFC-2326?

that '1' in the 'o=' string seem to break the RFC: https://datatracker.ietf.org/doc/html/rfc8866#name-origin-o

o=<username> <sess-id> <sess-version> <nettype> <addrtype> <unicast-address>

and the code expects exactly 6 parts (ExSDP/origin.ex)

I did a very ugly workaround in the code and got past the problem...

Thanks kruskakli - problem identified, so I'm closing the port.

I created a diff of my ugly fix in case someone want to look at it: https://github.com/etnt/ex_sdp/commit/c127b2063e03c38f43616f61e644c931a233a705

perhaps we should wait and see if I get any response from the TP-link support people

The cameras not following the specification are unfortunately quite a common problem :/ We have discussed the problem you are facing and decided that we could add an option switch to the ExSDP that would make the SDP parser "greedily" read only the fields that were correct (even though some of these fields might be marked as "necessary" in the RFC) instead of failing. Then the ExSDP could be launched with such an option for parsing the RTSP response and it simply wouldn't read the `origin` field in case its parsing fails (we don't use the value of that field anywhere). We have inspected that FFmpeg does a similar thing - it parsers different fields of the SDP for different protocols, independent from what the RFC marks as "necessary". It's not the cleanest solution, and surely it would be best if TP-link's cameras followed the specification, but still I think it will be more convenient for you than maintaining a forked repository.

fyi: I got a second reply from the TP-support

RTSP demo with Tapo C320WS

kruskakli

31 responses

Join out Discord Community