This TURN server does not work with Stuntman clients

John Selbie reported:

=====================================

I am contributing a patch to the 1.8.3.4 source tree that will allow the client 
program from the Stuntman source to make STUN binding requests to your server.

Here's the gist of the change. Stuntman comes with a STUN client library and 
client program. The client program displays the mapped IP address and port if 
it gets back a successful binding response.  It also interops with JSTUN, a 
Java implementation of STUN. However, the JSTUN server refuses to respond to 
any binding request that doesn't have a CHANGE-REQUEST attribute in it.  I had 
previous contacted the developer of that code base about the issue, but he 
didn't respond back.  So the only workaround is for the client to make a 
request with an empty CHANGE-REQUEST attribute (neither the ip or port bit are 
set).

I can see in the code you don't explicitly support the CHANGE-REQUEST attribute 
unless RFC 5780 mode is turned on.  Otherwise, an error response is sent back. 
And it doesn't appear that is an option for the user to enable this yet.  So 
the patch I'm providing allows the code to reasonably accept an EMPTY 
CHANGE-REQUEST attributes, while rejecting anything else.

======================================================

Original issue reported on code.google.com by mom040...@gmail.com on 1 May 2013 at 5:39

Attachments:

rfc5766-turn-server.patch

lxdyy / rfc5766-turn-server

This TURN server does not work with Stuntman clients #19