Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lorex 2k doorbell wrong response on DESCRIBE #1594

Open
esand opened this issue Feb 12, 2025 · 0 comments
Open

Lorex 2k doorbell wrong response on DESCRIBE #1594

esand opened this issue Feb 12, 2025 · 0 comments
Assignees
@AlexxIT
Labels
bug Something isn't working

Comments

@esand
Copy link

esand commented Feb 12, 2025

I have a Lorex 2k doorbell (not on the latest firmware - that seems to block the http API) that I have configured for regular streaming, as well as backchannel audio. The wifi isn't 100%, so it was suggested I pass it through ffmpeg which has significantly reduced the errors go2rtc logs, however the backchannel stream cannot be passed through ffmpeg otherwise it consumes it and that blocks the call button from working (this doorbell is the same as the Amcrest 410 and Dahua doorbells).

What I notice is that whenever my Frigate card in Home Assistant tries to open the backchannel stream, it causes an error to log about a wrong response on DESCRIBE. If it matters, the stream is h.265 encoded, and I do have an HTTPS domain I access Home Assistant from (for WebRTC if it matters), and the domain is listed in the webrtc candidates, but I removed it for privacy.

This is pieces of my go2rtc config (removing other cameras):

ffmpeg:
  myfix: -fflags +igndts+genpts+discardcorrupt -i {input}
  myvol: -af "volume=2"
  bin: /usr/lib/ffmpeg/7.0/bin/ffmpeg
streams:
  Front_doorbell:
      # 2560x1920 @15fps
  - ffmpeg:rtsp://XXXX:[email protected]:554/cam/realmonitor?channel=1&subtype=0#backchannel=0
  - ffmpeg:Front_doorbell#audio=myvol#audio=opus
  Front_doorbell_detect:
      # 720x576 @15fps
  - ffmpeg:rtsp://XXXX:[email protected]:554/cam/realmonitor?channel=1&subtype=1#backchannel=0
  Front_doorbell_2way:
  - rtsp://XXXX:[email protected]:554/cam/realmonitor?channel=1&subtype=0
webrtc:
  candidates:
  - 192.168.3.2:8555
  - stun:8555

  listen: :8555
api:
  origin: '*'
hass:
  config: /config
log:
  format: text
rtsp:
  default_query: mp4

This is a trace log of the error happening:

4:12:51.447 p.m.	trace	[rtsp] client response:
RTSP/1.0 200 OK
Cseq: 6
Session: 12961780151629
Rtp-Info: url=trackID=0;seq=53423;rtptime=269976246,url=trackID=1;seq=53151;rtptime=218331146,url=trackID=5;seq=0;rtptime=0

4:12:51.354 p.m.	trace	[rtsp] client request:
PLAY rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/ RTSP/1.0
CSeq: 6
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/", response="34b1243f0b91e556dfc25c9cc3609087"
Session: 12961780151629

4:12:51.354 p.m.	trace	[rtsp] client request:
TEARDOWN rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0
CSeq: 3
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="fa50be72fc916f068bfaae67f9e76f28", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0", response="9e5d746cae243e1aba3530420c1932fc"

4:12:51.354 p.m.	trace	[rtsp] client response:
RTSP/1.0 200 OK
Cseq: 5
Session: 12961780151629;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=10-11;ssrc=6EEB125A
X-Dynamic-Rate: 1

4:12:51.332 p.m.	trace	[rtsp] client request:
SETUP rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=5 RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=4-5
CSeq: 5
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=5", response="57a9d2d443d48743da3107a65b4c0d59"
Session: 12961780151629

4:12:51.332 p.m.	trace	[rtsp] client response:
RTSP/1.0 200 OK
X-Dynamic-Rate: 1
Cseq: 4
Session: 12961780151629;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;ssrc=38C0A268

4:12:51.305 p.m.	trace	[rtsp] client request:
SETUP rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=1 RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
CSeq: 4
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=1", response="ec291aac8a28603ae3281266f6fa100d"
Session: 12961780151629

4:12:51.305 p.m.	trace	[rtsp] client response:
RTSP/1.0 200 OK
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=0CB6921A
X-Dynamic-Rate: 1
Cseq: 3
Session: 12961780151629;timeout=60

4:12:51.275 p.m.	trace	[rtsp] client request:
SETUP rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=0 RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
CSeq: 3
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/trackID=0", response="adda41a18fa4bec80f0a5409c255ec59"

4:12:51.275 p.m.	trace	[rtsp] client response:
RTSP/1.0 200 OK
Cseq: 2
X-Accept-Dynamic-Rate: 1
Content-Base: rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/
Cache-Control: must-revalidate
Content-Length: 587
Content-Type: application/sdp

v=0
o=- 2264899322 2264899322 IN IP4 0.0.0.0
s=Media Server
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
m=video 0 RTP/AVP 98
a=control:trackID=0
a=framerate:15.000000
a=rtpmap:98 H265/90000
a=fmtp:98 profile-id=1;sprop-sps=QgEBAWAAAAMAAAMAAAMAAAMAlqABQCAHgWNrkkya5ZwCAAAH0gAAdU4Q;sprop-pps=RAHgdrAmQA==;sprop-vps=QAEMAf//AWAAAAMAAAMAAAMAAAMAlqwJ
a=recvonly
m=audio 0 RTP/AVP 8
a=control:trackID=1
a=rtpmap:8 PCMA/8000
a=recvonly
m=audio 0 RTP/AVP 8
a=control:trackID=5
a=rtpmap:8 PCMA/8000
a=sendonly
4:12:51.265 p.m.	trace	[rtsp] server response:
RTSP/1.0 200 OK
Cseq: 26
Session: 18842770

4:12:51.265 p.m.	trace	[rtsp] server request:
OPTIONS rtsp://127.0.0.1:8554/Front_door_detect RTSP/1.0
Cseq: 26
User-Agent: FFmpeg Frigate/0.15.0-cea210d
Session: 24334208

4:12:51.189 p.m.	trace	[rtsp] client request:
DESCRIBE rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.9.8
CSeq: 2
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0", response="a3c5ff0f37214828596adbfb61a28d87"
Accept: application/sdp

4:12:51.189 p.m.	trace	[rtsp] client response:
RTSP/1.0 401 Unauthorized
Cseq: 1
Www-Authenticate: Digest realm="Login to ND032206020280", nonce="59f4ad51acdb0868f7a168649bbf7608"

4:12:51.162 p.m.	trace	[rtsp] client request:
DESCRIBE rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.9.8
CSeq: 1

4:12:51.154 p.m.	warn	undefined error=start from CONN state url=rtsp://XXXX:[email protected]:554/cam/realmonitor?channel=1&subtype=0 caller=github.com/AlexxIT/go2rtc/internal/streams/producer.go:170
4:12:51.154 p.m.	info	[streams] can't add track error=wrong response on DESCRIBE
4:12:51.154 p.m.	trace	[rtsp] client response:
RTSP/1.0 404 Not Found
Cseq: 2
Www-Authenticate: Digest realm="Login to ND032206020280", nonce="fa50be72fc916f068bfaae67f9e76f28"

4:12:51.114 p.m.	trace	[rtsp] client request:
DESCRIBE rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0
CSeq: 2
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="fa50be72fc916f068bfaae67f9e76f28", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0", response="ccf07ed8bea9c3c55de93703144aee88"
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.9.8

4:12:51.114 p.m.	trace	[rtsp] client response:
RTSP/1.0 401 Unauthorized
Cseq: 1
Www-Authenticate: Digest realm="Login to ND032206020280", nonce="fa50be72fc916f068bfaae67f9e76f28"

4:12:51.086 p.m.	trace	[rtsp] client request:
DESCRIBE rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0
CSeq: 1
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.9.8

4:12:51.082 p.m.	trace	[rtsp] client request:
TEARDOWN rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/ RTSP/1.0
CSeq: 7
Authorization: Digest username="XXXX", realm="Login to ND032206020280", nonce="c2bcdbe24d9665472c8a3a7bfb20f5c4", uri="rtsp://192.168.4.11:554/cam/realmonitor?channel=1&subtype=0/", response="af99868c26b5ce798425dafa1a06a126"
Session: 12961772330541

I'm uncertain if this is go2rtc related, but I've also noticed that the Frigate card has an infrequent chance of actually displaying/opening the 2-way audio connection. It seems more often than not, my mic button isn't displayed... but I'm thinking that may be a Frigate card issue.

Is this error because the camera isn't standards compliant, or is there something that can be done to go2rtc to eliminate this (I don't even know if this error is causing me problems other than just being logged).
@AlexxIT AlexxIT added the bug Something isn't working label Feb 13, 2025
@AlexxIT AlexxIT self-assigned this Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexxIT AlexxIT

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexxIT @esand