Coturn / frigate config

[jsapede]

Does anyone have a fully functionnal coturn docker setting and config for frigate and would mind sharing it ?
quite unexperienced in this and would be of great help

[jsapede]

Hi folks,
as no-one seems to have investigated this here are first tests and observations inspired from this https://github.com/AlexxIT/WebRTC/wiki/Coturn-Example

docker run command :

docker run -d --name coturn --restart unless-stopped --mount type=tmpfs,destination=/var/lib/coturn -e DETECT_EXTERNAL_IP=yes --network=host -v /opt/coturn/turnserver.conf:/etc/coturn/turnserver.conf coturn/coturn:latest

not sure all options are necessary !

turnserver.conf : 

realm=myrealm.com
server-name=Coturn
fingerprint
listening-ip=0.0.0.0
external-ip=IP_OF_THE_ROUTER
listening-port=3478
min-port=49160
max-port=49200
log-file=stdout
verbose
user=frigate:frigate1234
lt-cred-mech`

and finally frigate settings :

webrtc:
    listen: :8555
    candidates:
      - 192.168.0.112:8555
      - EXTERNAL_IP:8555
    ice_servers:
      - urls: [turn:EXTERNAL_IP:3478]
        username: frigate
        credential: frigate1234

seems to work as i got some logs when connecting to cameras streams :

341: (33): INFO: IPv4. Local relay addr: 192.168.0.146:49173
341: (33): INFO: session 000000000000000001: new, realm=<myrealm.com>, username=<frigate>, lifetime=600
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet ALLOCATE processed, success
341: (33): INFO: session 000000000000000001: peer 192.0.0.4 lifetime updated: 300
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CREATE_PERMISSION processed, success
341: (33): INFO: session 000000000000000001: peer 192.0.0.4 lifetime updated: 600
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CHANNEL_BIND processed, success
341: (33): INFO: session 000000000000000001: peer 192.0.0.4 lifetime updated: 600
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CHANNEL_BIND processed, success
341: (33): INFO: session 000000000000000001: peer 80.215.102.217 lifetime updated: 300
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CREATE_PERMISSION processed, success
341: (33): INFO: session 000000000000000001: peer 80.215.102.217 lifetime updated: 600
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CHANNEL_BIND processed, success
341: (33): INFO: session 000000000000000001: peer 80.215.102.217 lifetime updated: 600
341: (33): INFO: session 000000000000000001: realm <myrealm.com> user <frigate>: incoming packet CHANNEL_BIND processed, success

I'm not quite sure of the frigate config !