stun servers?????
-
- One Hit Wonder
- Posts: 1
- Joined: 01/06/2015
- SIP Device Name: grandstream ht502n
- ISP Name: bell
- Router: bell fibe router
stun servers?????
our phone stopped working after 2 yrs and cannot get it working now. we have a grandstream ht502n we can get everything to work and register but in status where it say nat we cannot get it to say port restricted cone nat. all it says is unknown nat. hopefully someone can point us in the right direction. right now im using stun.stunprotocol.org tried all the other we could find but no luck yet.. we can get it to work but only the person calling can hear us. thanks
-
- Tried and True
- Posts: 411
- Joined: 08/14/2014
- SIP Device Name: OBi110
- Firmware Version: 1.3.0 (Build: 2824)
- ISP Name: Telus
- Computer OS: Windows 7
- Router: Toastman Tomato
Re: stun servers?????
Please set the following:
NAT Traversal (STUN): No, but send keep-alive
Primary SIP Server: voip3.freephoneline.ca
Let us know if that works. If not, we will continue to troubleshoot.
NAT Traversal (STUN): No, but send keep-alive
Primary SIP Server: voip3.freephoneline.ca
Let us know if that works. If not, we will continue to troubleshoot.
-
- Just Passing Thru
- Posts: 4
- Joined: 09/08/2011
- SIP Device Name: SPA2102
- ISP Name: Rogers
- Computer OS: MacOS X 10.10.2
- Router: Fortigate
Re: stun servers?????
Mind if I ask what changed on voip3.freephoneline.ca? I was having an issue where it's worked for years and suddenly it didn't. I changed my server to voip3 and everything is working again.
-
- Tried and True
- Posts: 411
- Joined: 08/14/2014
- SIP Device Name: OBi110
- Firmware Version: 1.3.0 (Build: 2824)
- ISP Name: Telus
- Computer OS: Windows 7
- Router: Toastman Tomato
Re: stun servers?????
Are you able to change back to your original server now? If so, the problem was likely either:
a) you were banned for registering too frequently.
b) your router had a corrupted NAT connection.
Next time the problem happens, change your SPA2102's SIP Port to a random number between 20000 and 65535. If that solves the problem, it indicates b).
As usual, you should make sure your device is configured as per the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16198
a) you were banned for registering too frequently.
b) your router had a corrupted NAT connection.
Next time the problem happens, change your SPA2102's SIP Port to a random number between 20000 and 65535. If that solves the problem, it indicates b).
As usual, you should make sure your device is configured as per the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16198