D-Link Forums

The Graveyard - Products No Longer Supported => D-Link VoIP => DPH-541 => Topic started by: mel2000 on September 26, 2009, 07:02:39 AM

Title: Can't get past "STUN NAT Detect" prompt
Post by: mel2000 on September 26, 2009, 07:02:39 AM

During bootup my DPH-541 stays stuck on "STUN NAT Detect" when it used to quickly detect it and move on to registration. I tried several STUN servers with the same result. Without STUN enabled I cannot hear audio from my callers. Is there a way to troubleshoot this issue?

Title: Re: Can't get past "STUN NAT Detect" prompt
Post by: mel2000 on September 27, 2009, 12:49:55 AM

The problem appears to be solved for now. I tried stun.sipgate.net on my Sipgate account and it was detected. Still don't know why the other two (stunserver.org and stun.xten.com) didn't work.

Title: Re: Can't get past "STUN NAT Detect" prompt
Post by: mel2000 on September 27, 2009, 05:26:59 PM

I just learned that stunserver.org and stun.xten.com are no longer working.

Current free STUN servers:
********************
stun.voipbuster.com
stun01.sipphone.com
stun.ekiga.net
stun.ideasip.com
stun.rnktel.com
stun.sipgate.net
stun.sipgate.net:10000
stun01.sipphone.com
stun.softjoys.com
numb.viagenie.ca
stun.voxalot.com

Title: Re: Can't get past "STUN NAT Detect" prompt
Post by: Mlachake on October 05, 2009, 05:02:01 PM

The STUN server is contacted on UDP port 3478, however the server will hint clients to perform tests on alternate IP and port number too (STUN servers have two IP addresses). The RFC states that this port and IP are arbitrary. That may be the reason why the units is taking too long to contact the server.

Title: Re: Can't get past "STUN NAT Detect" prompt
Post by: WiFi on December 31, 2009, 07:13:09 PM

i found STUN servers unreliable, for me anyway. and also had some STUN servers put the call on a GRAY route, making the call sound really bad, like magicjack, sometimes :-)

Title: Re: Can't get past "STUN NAT Detect" prompt
Post by: mel2000 on January 03, 2010, 03:39:05 AM

Quote from: Mlachake on October 05, 2009, 05:02:01 PM

The RFC states that this port and IP are arbitrary. That may be the reason why the units is taking too long to contact the server.

Sorry for the delayed response. I just want to make it clear that the reason the STUN servers I used seemed stuck was because they were no longer active. So I chose another that worked immediately. I've since found I can use the phone without STUN anyway.