This article is about how I setup a STUN/TURN service server on my domain meetme.id, so I do not forget how to do it again later 🙂 You can then use the STUN and/or TURN server on meetme.id from anywhere, any application that requires one or both of them.
meetme.id is a service server that I setup to test and learn the current IP communication technologies such as WebRTC, SIP and XMPP/Jabber. I also try to seriously setup and maintain it so that it can actually be useful to anyone for actual usages on a long-term.
UPDATE:
Actual deployment of STUN/TURN server on meetme.id is different than this manual. Current implementation the STUN/TURN server on meetme.id are using different port than the default setup.
[code lang=text]
Public STUN server address : stun.meetme.id:443
Public TURN server address : turn.meetme.id:443 (UDP/TCP)
Public TURN credential : public
Public TURN username : public
[/code]
This article is divided into three parts:
- Part 1: Installation
- Part 2: Basic Configuration
- Part 3: The Test
The server is using Ubuntu Server 14.04 and the STUN/TURN server software is Coturn.
Just in case you’re wondering why you should need to even use a STUN and/or TURN service server, here are some pages to start with:
- http://blog.tadhack.com/2015/06/08/turn-to-turn-streamstack/
- http://piratefsh.github.io/projects/2015/08/27/webrtc-stun-turn-servers.html
- https://www.webrtc-experiment.com/docs/STUN-or-TURN.html
- http://www.html5rocks.com/en/tutorials/webrtc/infrastructure/#after-signaling-using-ice-to-cope-with-nats-and-firewalls
- http://www.avaya.com/blogs/archives/2014/08/understanding-webrtc-media-connections-ice-stun-and-turn.html
- https://www.youtube.com/watch?v=p2HzZkd2A40
Ready ? Let’s begin.