diff options
| author | Ivan Sein <ivan@nextcloud.com> | 2020-04-01 12:58:16 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-01 12:58:16 +0300 |
| commit | 865f396233563f2ff121d9ca569caac9ab4a88d7 (patch) | |
| tree | f81275bb0cc3e4e2b20749a6093b5cc753b5f2af /docs | |
| parent | 38734148979e0a5b3465d14df41f2b815a415a92 (diff) | |
| parent | 2d5e55725be12e3f20fcd373e04fedcea808e0e3 (diff) | |
Merge pull request #3221 from nextcloud/bugfix/noid/reflect-NAT-in-turn-docs
Reflect the NAT situation a bit better in the TURN docs
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/TURN.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/TURN.md b/docs/TURN.md index 20047ead7..8b8480ae7 100644 --- a/docs/TURN.md +++ b/docs/TURN.md @@ -98,7 +98,7 @@ simple-log #### 5. Port opening/forwarding -- The TURN server on `<yourChosenPortNumber>` needs to be accessible for all Talk participants, so you need to open it to the web and if your TURN server is running **behind a NAT**, forward it to the related machine. +- The TURN server on `<yourChosenPortNumber>` needs to be accessible for all Talk participants, so you need to open it to the web and if your TURN server is running **behind a NAT**, forward it to the related machine. Also make sure to set the [`--external-ip` option](https://github.com/coturn/coturn/wiki/turnserver#options) when your TURN server is in a private networt. ### What else Nextcloud Talk´s WebRTC handling is still mostly based on the one from the [Spreed.ME](https://www.spreed.me/) WebRTC solution. For this reason, all guides about how to configure coTURN for it, applies to Nextcloud Talk too. |