does turnserver support the older "classic" STUN RFC3489 messages ? about rfc5766-turn-server HOT 6 CLOSED

You are talking about the obsolete STUN specs in RFC 3489. We support only the 
current STUN specs is RFC 5389. I may mark it as "enhancement" but I really do 
not know when I can work on it, supporting the obsolete specs has never been 
much of priority. Can you find a softphone that supports the new STUN specs 
(RFC5389 and RFC5780) ?

Thanks a lot for your confirmation. I'll find another softphone to try with the 
turn server.

About 6 months ago I checked this for the other two open source TURN servers.  
reTurn (from reSIProcate) does appear to support legacy STUN clients, while 
TurnServer.org does not appear to support the legacy STUN clients.  I used the 
command line client (/usr/bin/stun) from the stun package on Debian to test 
them all:

http://packages.debian.org/sid/stun

Adding this functionality is possible because we can separate obsolete incoming 
client packets from the "new" packets. It would definitely create a mess in the 
code because the old RFC was mostly split into two new RFCs (5389 and 5780) 
which we support. But if this is really important for some users, then it can 
be done.

This backward compatibility will be added to the upcoming 1.8.7.0 build. the 
build will be tested and issued in a few days.

Fixed in v1.8.7.0