Google provides an example of WEBRTC using Turnserver way

Google's Turnserver download method:svn checkout http://rfc5766-turn-server.googlecode.com/svn/branches/v3.2/ Rfc5766-turn-server-read-only

About the application of WEBRTC Google gives an example:

https://apprtc.appspot.com/(need FQ, sometimes fq may not be able to land, it is estimated that the use of too many people)

I was always curious about the way he used turn, and then finally figured out what was going on. Take a look at the following characters:

1, client: normal WEBRTC terminal, Android, browser, Windows application, MAC program, etc.

2, signaling server: Here is the apprtc.appspot.com this server

3, Turnserver:turn Server, Nat cross-use, help to make holes (relay)

4, Turnclient account Management Server, and signaling server use the same first-level domain name and port number (must be so, not detailed here)

5, the client side of Turnclient:turn is generally integrated in the client.

Work in the following ways:

A. Client gets the URL of the Turnclient account Management Server from the signaling server

b, client use URL to access turnclient account Management Server, get access to Turnserver's account and password

C, the client will inform the account and password turnclient

D, turnclient visit turnserver

See here is a problem: the whole process of Turnclient account Management Server and turnserver how no interaction process?

There is really no interaction here, please listen to me slowly:

Here Turnserver work mode is "Restapi" (Do not know what is RESTAPI please go to see the turn protocol), the way is as follows:

This way only need Turnclient know Turnserver key is good, turnclient only need to use key, try to use key to generate account and password just fine. The creation of the user name and password is done by the Turnclient account Management Server .

Please leave a message about the detailed workflow.

Google provides an example of WEBRTC using Turnserver way