title: Easy way to test TURN server
body: <p>I'm looking at this site, which is supposed to be table to test a TURN server (<a href="https://stackoverflow.com/a/28775122/5378216">according this this answer</a>).</p>
  
  <p>plugin.temasys.com.sg/demo/samples/web/content/peerconnection/trickle-ice/index.html</p>
  
  <p>I put in my server info, but couldn't find anything to determine if the server is working. The ice candidates section looks the same even its there's no server chosen.</p>
  
  <p>My TURN server is installed on Amazon EC2. I followed the install instructions from the coturn repository here: </p>
  
  <p>github.com/coturn/coturn/blob/master/INSTALL</p>
  
  <p>The following is what I get in my server when I do the command to start the TURN server, from <a href="http://blog.knoldus.com/2013/10/24/configure-turn-server-for-webrtc-on-amazon-ec2/" rel="noreferrer">here</a>: </p>
  
  <pre><code>RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
  Version Coturn-4.2.1.2 'Monza'
  0:
  Max number of open files/sockets allowed for this process: 4096
  0:
  Due to the open files/sockets limitation,
  max supported number of TURN Sessions possible is: 2000 (approximately)
  0:
  
  ==== Show him the instruments, Practical Frost: ====
  
  0: TLS supported
  0: DTLS supported
  0: AEAD supported
  0: Redis supported
  0: PostgreSQL supported
  0: MySQL supported
  0: MongoDB is not supported
  0: OpenSSL compile-time version 0x1000106f: fresh enough
  0: Default Net Engine version: 3 (UDP thread per CPU core)
  
  =====================================================
  
  0: Config file found: /usr/local/etc/turnserver.conf
  0: Listener address to use: 172.31.43.176
  0: Relay address to use: 172.31.43.176
  0: Config file found: /usr/local/etc/turnserver.conf
  0: Domain name:
  0: Default realm: realm
  0: Config file found: /usr/local/etc/turnuserdb.conf
  0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
  0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
  0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
  0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
  0: pid file created: /var/run/turnserver.pid
  0: IO method (main listener thread): epoll (with changelist)
  0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided
  0: Wait for relay ports initialization...
  0:   relay 172.31.43.176 initialization...
  0:   relay 172.31.43.176 initialization done
  0: Relay ports initialization done
  0: IO method (general relay thread): epoll (with changelist)
  0: IPv4. UDP listener opened on: 172.31.43.176:3478
  0: Total UDP servers: 0
  0: Total General servers: 1
  0: turn server id=0 created
  0: IPv4. TCP listener opened on : 172.31.43.176:3478
  0: IO method (cli thread): epoll (with changelist)
  0: IPv4. CLI listener opened on : 127.0.0.1:5766
  0: IO method (auth thread): epoll (with changelist)
  </code></pre>
  
  <p>It appears to be working, but how do I know? I apologize for my ignorance, I've been reading so many docs on this I can't keep track of it all.</p>
  
  <p>EDIT: Well something is happening :)</p>
  
  <p>I'm receiving these on my turn server now whenever use the site mentioned above:</p>
  
  <pre><code>64: ERROR: check_stun_auth: Cannot find credentials of user &lt;ubuntu&gt;
  64: session 000000000000000004: realm &lt;realm&gt; user &lt;ubuntu&gt;: incoming packet message processed, error 401: Unauthorised
  </code></pre>
  
  <p>EDIT 2: I removed the ubuntu portion, and am now receiving what appears to be successful responses. Still don't really know what it means, but it's a start :)</p>
  
  <pre><code>274: handle_udp_packet: New UDP endpoint: local addr 172.31.43.176:3478, remote addr 12.123.123.123:64064
  274: session 000000000000000007: realm &lt;realm&gt; user &lt;&gt;: incoming packet BINDING processed, success
  274: handle_udp_packet: New UDP endpoint: local addr 172.31.43.176:3478, remote addr 12.123.123.123:64068
  274: session 000000000000000008: realm &lt;realm&gt; user &lt;&gt;: incoming packet BINDING processed, success
  274: session 000000000000000007: realm &lt;realm&gt; user &lt;&gt;: incoming packet message processed, error 401: Unauthorised
  274: session 000000000000000008: realm &lt;realm&gt; user &lt;&gt;: incoming packet message processed, error 401: Unauthorised
  274: IPv4. Local relay addr: 172.31.43.176:56767
  274: session 000000000000000007: new, realm=&lt;realm&gt;, username=&lt;turnadm&gt;, lifetime=600
  274: session 000000000000000007: realm &lt;realm&gt; user &lt;turnadm&gt;: incoming packet ALLOCATE processed, success
  274: IPv4. Local relay addr: 172.31.43.176:54363
  274: session 000000000000000008: new, realm=&lt;realm&gt;, username=&lt;turnadm&gt;, lifetime=600
  274: session 000000000000000008: realm &lt;realm&gt; user &lt;turnadm&gt;: incoming packet ALLOCATE processed, success
  274: session 000000000000000007: realm &lt;realm&gt; user &lt;turnadm&gt;: incoming packet ALLOCATE processed, success
  274: session 000000000000000008: realm &lt;realm&gt; user &lt;turnadm&gt;: incoming packet ALLOCATE processed, success
  </code></pre>