Is it Possible to Configure TURNServer to Operate "only" in TURN or ICE mode ...

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Currently testing with Counterpath X-Lite Vers. 3.0 build 56125
2.
3.

What is the expected output? What do you see instead?
Is there a way to configure the turnserver to NOT operate in Classic STUN mode 
and only in TURN and/or ICE usage mode? The X-Lite version I'm using
has a selection for ICE use, but if it can traverse the NAT only using classic 
STUN, doesn't help me evaluate the TURN and/or ICE functionality of the server 
with a free and/or commercial SIP client.  Also trying Bria 3 for Android and 
tried Jitsi but can't get those to even operate in classic STUN mode.

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 dhreamch...@gmail.com on 4 Nov 2013 at 6:33

[GoogleCodeExporter]

There are three protocols supported:

1) "classic" STUN (RFC 3489)
2) STUN (RFC 5389)
3) TURN (RFC 5766)

Which ones you want to be able to turn off ? Both STUNs together, right ?

Original comment by mom040...@gmail.com on 4 Nov 2013 at 7:14

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yes sir, both STUNs together...

Original comment by dhreamch...@gmail.com on 4 Nov 2013 at 7:38

[GoogleCodeExporter]

That functionality will be added to the upcoming 2.6.7.0 release. There will be 
a new option like "--no-stun".

Original comment by mom040...@gmail.com on 4 Nov 2013 at 8:14

[GoogleCodeExporter]

Original comment by mom040...@gmail.com on 4 Nov 2013 at 8:15

[GoogleCodeExporter]

Fixed in 2.6.7.0, see the new option --no-stun

Original comment by mom040...@gmail.com on 6 Nov 2013 at 7:57

• Changed state: Fixed