Re: [reTurn-devel] reTurn causes Linksys SPA942 to continuously register
Hi Eric,
One thing to keep in mind is that reTurn implements the latest stun rfc 5389. The SPA942 is likely to be using the older STUN rfc 3489 - however there was effort put into reTurn to provide backwards compatibility with older stun clients, so I would expect it to work if enable properly. To enable rfc3489 back compat support you need to start reTurn with full command line parameters (from reTurnServer /?):
Usage: reTurnServer <address> <turnPort> <tlsPort> <altAddress> <altPort>
IPv4 Example (with RFC3489 support):
reTurnServer 192.168.1.10 3478 5349 192.168.1.11 3479
IPv6 Example (with RFC3489 support):
reTurnServer 3ffe:0501:0008:0000:0260:97ff:fe40:efab 3478
5349 3ffe:0501:0008:0000:0260:97ff:fe40:efac 3479
Note: For RFC3489 legacy support define altPort as non-zero and
ensure you don't use INADDR_ANY for the IP addresses.
Both adresses should terminate on the machine running
reTurn.
Scott
On Fri, Jul 24, 2009 at 7:21 PM, Eric Chamberlain
<eric@xxxxxx> wrote:
Hello,
I have a Linksys SPA942 set up to use STUN with reTurn.
The SPA942 keeps registering over and over, even though the SPA942 receives the external ip and port, puts:
Warning: 399 spa "Full Cone NAT Detected"
in the REGISTER header, and receives the 200 OK back from the SIP server. Oddly, if I use stund (Vodiva), then the SPA942 reports:
Warning: 399 spa "Symmetric NAT Detected"
in the REGISTER header, uses the external IP and port returned from the STUN server, and won't send a new register until the current one expires, the expected behavior.
Has anyone encountered this issue or is successfully using Linksys products with reTurn?
--
Eric Chamberlain, Founder
RF.com - http://RF.com/
_______________________________________________
reTurn-devel mailing list
reTurn-devel@xxxxxxxxxxxxxxx
List Archive: http://resiprocate.org/archive/return-devel/