AlexxIT
commented
5 months ago I think you using Safari. Because I can't see TCP remote candidates. So you can use only UDP candidates. But default UDP port for go2rtc is random. And you using Frigate docker with closed network. So all your random ports closed in the container. So you can:
- change network for Frigate to host (better option)
- change go2rtc settings to static webrtc port for TCP and UDP https://github.com/AlexxIT/go2rtc#module-webrtc
PS. The go2rtc docs has an error about the static port for UDP by default
lorenzomartini1
Hi, I'm using the go2rtc module inside Frigate. I've some problem when I'm using the two-way-audio functionality for a Tapo C212 camera.
go2rtc config inside Frigate:
The first doubt is about
candidates: I've seen lot of different config on the web but i'm not sure what is the best for my env. Frigate container is behinghostnetwork mode. The server IP which runs docker is192.168.1.130. My current client IP is192.168.1.21. My home network extenal IP address is93.56.x.x. I'm using Fastweb as ISP and I'm behind a normal NAT. On the modem I've forwarded 8555 port both TCP/UDP to the docker server.Main problem is: from the LAN and outside the network I can't see WebRTC:
webrtc-cameracard and via "WebRTC Magic: video+audio+microphone link " I got infinite loading for the video but two-way-audio (client > camera) is working well:With this card config I can stream correctly audio and video from
cam_gatto_subcamera, but when I switch toMIC ONstream (socam_gatto_twaone) I got always loading video but two way audio instantly working.