# How to use own Intranet penetration solution without the default configured stun server

**URL:** <https://help.nextcloud.com/t/how-to-use-own-intranet-penetration-solution-without-the-default-configured-stun-server/158363>\
**Category:** 💬 Talk (spreed)\
**Tags:** talk-app\
**Created:** [March 23, 2023, 6:20am UTC](https://help.nextcloud.com/t/how-to-use-own-intranet-penetration-solution-without-the-default-configured-stun-server/158363 "2023-03-23T06:20:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [March 23, 2023, 7:48am UTC](https://help.nextcloud.com/t/how-to-use-own-intranet-penetration-solution-without-the-default-configured-stun-server/158363/3 "2023-03-23T07:48:48Z")

</div>

@blxw987_bao  
I found this for you [here](https://help.nextcloud.com/t/howto-setup-nextcloud-talk-with-turn-server/30794):

- **Configure Nextcloud Talk to use your TURN server**  
Go to Nextcloud admin panel \> Talk settings. Btw. if you already have your own TURN server, you can and may want to use it as STUN server as well:

```auto
STUN servers: your.domain.org:<yourChosenPortNumber>
TURN server: your.domain.org:<yourChosenPortNumber>
TURN secret: <yourChosen/GeneratedSecret>
UDP and TCP

```

Do not add `http(s)://` here, this causes errors, the protocol is simply a different one. Also `turn:` or something as prefix is not needed. Just enter the bare `domain:port`.

[…]

> Nextcloud Talk is still based on the Spreed video calls app (just got renamed) and thus the [Spreed.ME](http://Spreed.ME) WebRTC solution. For this reason all guides about how to configure coturn for one of them, applies to all of them.

---

_[View the full topic](https://help.nextcloud.com/t/how-to-use-own-intranet-penetration-solution-without-the-default-configured-stun-server/158363)._