Remote webRTC connection doesn't worth with Reolink

[mgoh99]

• I can get a webrtc remote feed from my Unifi cameras but not from my Reolink POE Doorbell.
• Reolink webrtc works locally
• Reolink only work MSE remotely
• Even with a wireguard local tunnel, I can't get the reolink webRTC to work.

Here's my config

streams:
    Front_door:
    #reolink POE doorbell
           - rtsp://admin:90kitties@192.168.1.xx:554/h264Preview_01_main
           - "ffmpeg:Front_door#audio=opus"
        Unfi: rtspx://192.168.1.1:7441/xxxxxxxxxx
    #unifi g3 instant

What would cause that difference? I'd understand if webRTC didn't work for any cameras but it seems odd that it's only for the Reolink it's broken.

[AlexxIT]

Well. If "Reolink webrtc works locally" + "Unifi webrtc works remote" = probably Reolink bitrate too high for WebRTC UDP connection. It's known problem for 2K+ and 4K+ streams. WebRTC TCP should work fine, but you needs to setup it properly. It can be not easy task.

I prefer WebRTC UDP for local connection and WebRTC TCP for remote connection. You should have public IP-address, forward WebRTC TCP port on your router and setup webrtc public canditate in the go2rtc config.

[mgoh99]

Thanks. You were right. Switching to lower res sub stream fixed it. Still periodically choppy on RTC vs MSE but it’s a start! Thanks for your amazing work on this software

— Mark Goh

---

From: Alex X @.> Sent: Saturday, July 27, 2024 9:04:09 AM To: AlexxIT/go2rtc @.> Cc: mgoh99 @.>; Author @.> Subject: Re: [AlexxIT/go2rtc] Remote webRTC connection doesn't worth with Reolink (Issue #1281)

Well. If "Reolink webrtc works locally" + "Unifi webrtc works remote" = probably Reolink bitrate too high for WebRTC UDP connection. It's known problem for 2K+ and 4K+ streams. WebRTC TCP should work fine, but you needs to setup it properly. It can be not easy task.

— Reply to this email directly, view it on GitHubhttps://github.com/AlexxIT/go2rtc/issues/1281#issuecomment-2254144230, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOZPVBBNFEPU4WIDT4S7HLZOOLETAVCNFSM6AAAAABLR3LMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGE2DIMRTGA. You are receiving this because you authored the thread.Message ID: @.***>