Closed hanyuwei70 closed 1 year ago
It's stumbling over this third stream description:
m=application/TP-LINK 0 RTP/AVP smart/1/90000\r
a=rtpmap:95 TP-LINK/90000\r
a=control:track3\r
which doesn't follow the rules of RFC 8866 section 5.14. In particular, the smart/1/90000
makes no sense. The RFC says:
m=<media> <port> <proto> <fmt> ... If the <proto> subfield is RTP/AVP or RTP/SAVP, the <fmt> subfields contain RTP payload type numbers.
It should probably be 95
as described by the following line.
The application/TP-LINK
also probably should be just application
; this is supposed to be just the type not the subtype, and there are only a few values defined in the registry.
It looks like ffmpeg ignores this stream because the media type application/TP-LINK
isn't one of ffmpeg's few understood/allowed ones (video
, audio
, application
, text
). I can change Retina (Moonfire's RTSP library) to also ignore this stream based on the media type and/or the parsing problem, rather than producing an error.
I have no idea what information is contained in this stream. application/TP-LINK
doesn't tell me anything. Not video or audio anyway.
Thanks for your time investigating this issue. Maybe it's TP-LINK's private usage for motion detection? you can safely ignore it (or produce a warning).
Describe the bug Unable to parse onvif data.
To Reproduce connect to this IPC.
Expected behavior it will connect to stream normally
Server (please complete the following information): Running
scottlamb/moonfire-nvr:v0.7.5
logCamera (please complete the following information): TP-LINK TL-IPC44AW-COLOR 4.0 FW: 1.0.10 Build 220330 Rel.35741n
Desktop (please complete the following information): Unrelated