# TALK setup, documentation is really poor **URL:** \ **Category:** ℹ️ Support\ **Created:** [April 21, 2020, 11:58am UTC](https://help.nextcloud.com/t/talk-setup-documentation-is-really-poor/78697 "2020-04-21T11:58:10Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![h3rb3rt](https://help.nextcloud.com/user_avatar/help.nextcloud.com/h3rb3rt/32/9824_2.png) [@h3rb3rt](https://help.nextcloud.com/u/h3rb3rt)\ **Post date:** [April 21, 2020, 12:33pm UTC](https://help.nextcloud.com/t/talk-setup-documentation-is-really-poor/78697/4 "2020-04-21T12:33:42Z")
I used the official documentation > **[Overview - Nextcloud Talk API documentation](https://nextcloud-talk.readthedocs.io/en/latest/TURN/)** and this worked great, in addition you can get more inside reading this thread > [@HowTo: Setup Nextcloud Talk with TURN server](https://help.nextcloud.com/t/howto-setup-nextcloud-talk-with-turn-server/30794): > > Background The configuration of Nextcloud Talk mainly depends on your desired usage: As long as it shall be used only within one local network, nothing should be needed at all. Just verify that all browsers support the underlying [WebRTC](https://en.wikipedia.org/wiki/WebRTC) protocol (all famous ones do on current versions) and you should be good to go. Talk tries to establish a direct [peer-to-peer (P2P)](https://en.wikipedia.org/wiki/Peer-to-peer) connection, thus on connections throughout the local network (behind a [NAT](https://en.wikipedia.org/wiki/Network_address_translation)/router), clients do not only need to know each others … @mvv_vmd the documentation you are referring to, is not optimal, it misses out on thing to be explained and it uses configuration parameters and combinations which are outdated or need some more information to get them working. --- _[View the full topic](https://help.nextcloud.com/t/talk-setup-documentation-is-really-poor/78697)._