does turnserver support the older "classic" STUN RFC3489 messages ?

phanimahesh / rfc5766-turn-server

Automatically exported from code.google.com/p/rfc5766-turn-server

0 stars 0 forks source link

does turnserver support the older "classic" STUN RFC3489 messages ? #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?

I deployed turnserver in one of my machine(192.168.11.53). When I tried with 
the buildin tool 
   turnutils_stunclient 192.168.11.53
I can get the response successfully. (see the No.3 message in the attached file)
I setup a softphone(xlite) in another machine(192.168.11.188) with stun 
configuration.
When the turnserve received the request, no response will be send back. (See 
the No.13 message in the attached file)
Is that means turnserver doesn't support the classic stun message.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by zhangjun...@gmail.com on 17 May 2013 at 3:28

Attachments:

jjz.cap

GoogleCodeExporter commented 9 years ago

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) ?

Original comment by mom040...@gmail.com on 17 May 2013 at 4:06

Changed title: does turnserver support the obsolete RFC3489 stun messages ?
Changed state: Accepted
Added labels: Priority-Low, Type-Enhancement
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

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

Original comment by zhangjun...@gmail.com on 18 May 2013 at 1:02

GoogleCodeExporter commented 9 years ago

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

Original comment by dan...@pocock.pro on 6 Jun 2013 at 2:18

GoogleCodeExporter commented 9 years ago

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.

Original comment by mom040...@gmail.com on 6 Jun 2013 at 2:56

GoogleCodeExporter commented 9 years ago

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.

Original comment by mom040...@gmail.com on 21 Jun 2013 at 12:01

Changed title: does turnserver support the older "classic" STUN RFC3489 messages ?

GoogleCodeExporter commented 9 years ago

Fixed in v1.8.7.0

Original comment by mom040...@gmail.com on 23 Jun 2013 at 5:54

Changed state: Fixed