[SOLVED] FPL line not registering

[neptune]

Hi all,

I have a Grandstream HT-702 with single FPL line. Its been working fine for many months. Just last night, it failed to register.
Literally nothing changed in my network - all other devices and connections work fine. I can login to the HT702 and it shows Not Registered for line 1. FPL web console shows Disconnected.
I've rebooted the HT several times. Also unplugged it for few minutes. Nothing has worked.

Your help is much appreciated!

Thanks

[Liptonbrisk]

A. Latest ATA firmware is here: http://www.grandstream.com/sites/defaul ... .0.8.2.zip

i. "Once the new firmware is installed, set SIP REGISTER Contact Header Uses to WAN address."--Mango

ii. "Set "Enable SIP Options Keep-Alive" to "Yes."-- Fongo Support

http://forum.fongo.com/viewtopic.php?f= ... 910#p73907
iii. SIP registration failure retry wait time (the first one) should be 120.

B. Never port forward unless you have no other choice. Doing so is a security risk. I note that you were port forwarding before. That's a great way to allow SIP Scanners/crackers access to your devices and services.




from http://forum.fongo.com/viewtopic.php?f= ... =50#p73760


"These are just a few general points:

1. It doesn't matter if you never changed settings and suddenly have a failed registration state or are suddenly getting dead air. It doesn't matter if the service worked fine for years. Unless FPL servers are down, the problem is likely to be on your end. http://status.fongo.com/

The problem may be related to a user not properly changing registration timers: http://support.freephoneline.ca/hc/en-u ... redentials
Registration Interval: 3600 seconds (1 hour or 60 minutes), Registration Expiry: 3600 seconds (1 hour or 60 minutes), Failed Registration Re-Try Interval: 120 seconds
If your timers are wrong, you can end up with a temporary IP ban with the specific FPL SIP server you're attempting to register with.
If your ATA makes more than 5 registration attempts within 5 minutes, you'll be temporarily IP banned from the Freephoneline server you were attempting to register with.

There's three FPL SIP servers that you can try: voip.freephoneline.ca, voip2.freephoneline.ca, and voip4.freephoneline.ca:6060


The problem can also include a user not understanding that there may be a corrupted NAT connection that has developed in his or her router to the ATA that needs to be reset.
In some cases, changing local SIP port or X_UserAgentPort is the most effective way of, temporarily, fixing this.The problem can arise due to the router's UDP timeout being in excess of the ATA's Failure Retry timer.


2. If changing local SIP Port (in SPAxxx, PAP ATAs, etc.) or X_UserAgentPort in Obihai ATAs works, that means you are dealing with a corrupted NAT connection in your router. Typically, it's best to choose a random value between 30000 and 60000 to help thwart SIP scanners and circumvent faulty/buggy SIP ALG features in routers.

3. voip4.freephoneline.ca:6060 is used for dealing with SIP ALG issues. Rogers Hitron router and modem combos have SIP ALG enabled by default with no way for user to disable that feature without getting a Rogers tech to do it for you. Other modem/router combos that are issued by ISPs can also have SIP ALG stuck on. Typically, it's best to have your own router with SIP ALG/SPI disabled in it and stick the ISP's router/modem in bridge mode.

To better understand why SIP ALG is horrible visit http://www.voip-info.org/wiki/view/Routers+SIP+ALG and read. Although SIP ALG is not broken in all routers (for example, the SIP Passthrough function in Asus routers doesn't seem to affect FPL), it is broken in a lot of them.

4. Proper device reboot order is always modem-->router (wait for it and your modem to be fully up, running, and passing data before turning on your ATA; you may need to wait 10 minutes, depending on the router)-->ATA"

[neptune]

Hi, thanks for the detailed reply!
Have made the changes you suggested. And did couple of reboots of routers as well.
I believe it was an issue with one of the public DNS servers I'm using. It was was slow or timing out in some cases, which may have caused an issue with FPL registration.

A. Latest ATA firmware is here: http://www.grandstream.com/sites/defaul ... .0.8.2.zip

i. "Once the new firmware is installed, set SIP REGISTER Contact Header Uses to WAN address."--Mango

ii. "Set "Enable SIP Options Keep-Alive" to "Yes."-- Fongo Support

http://forum.fongo.com/viewtopic.php?f= ... 910#p73907
iii. SIP registration failure retry wait time (the first one) should be 120.

A. Check, already at latest
i. Changed to WAN address
ii. Changed to Yes
iii. Changed to 120

B. Never port forward unless you have no other choice. Doing so is a security risk. I note that you were port forwarding before. That's a great way to allow SIP Scanners/crackers access to your devices and services.




from http://forum.fongo.com/viewtopic.php?f= ... =50#p73760


"These are just a few general points:

1. It doesn't matter if you never changed settings and suddenly have a failed registration state or are suddenly getting dead air. It doesn't matter if the service worked fine for years. Unless FPL servers are down, the problem is likely to be on your end. http://status.fongo.com/

The problem may be related to a user not properly changing registration timers: http://support.freephoneline.ca/hc/en-u ... redentials
Registration Interval: 3600 seconds (1 hour or 60 minutes), Registration Expiry: 3600 seconds (1 hour or 60 minutes), Failed Registration Re-Try Interval: 120 seconds
If your timers are wrong, you can end up with a temporary IP ban with the specific FPL SIP server you're attempting to register with.
If your ATA makes more than 5 registration attempts within 5 minutes, you'll be temporarily IP banned from the Freephoneline server you were attempting to register with.

There's three FPL SIP servers that you can try: voip.freephoneline.ca, voip2.freephoneline.ca, and voip4.freephoneline.ca:6060

No port forwarding enabled.
1. I'm using voip. Have tried voip2 as well.

The problem can also include a user not understanding that there may be a corrupted NAT connection that has developed in his or her router to the ATA that needs to be reset.
In some cases, changing local SIP port or X_UserAgentPort is the most effective way of, temporarily, fixing this.The problem can arise due to the router's UDP timeout being in excess of the ATA's Failure Retry timer.


2. If changing local SIP Port (in SPAxxx, PAP ATAs, etc.) or X_UserAgentPort in Obihai ATAs works, that means you are dealing with a corrupted NAT connection in your router. Typically, it's best to choose a random value between 30000 and 60000 to help thwart SIP scanners and circumvent faulty/buggy SIP ALG features in routers.

3. voip4.freephoneline.ca:6060 is used for dealing with SIP ALG issues. Rogers Hitron router and modem combos have SIP ALG enabled by default with no way for user to disable that feature without getting a Rogers tech to do it for you. Other modem/router combos that are issued by ISPs can also have SIP ALG stuck on. Typically, it's best to have your own router with SIP ALG/SPI disabled in it and stick the ISP's router/modem in bridge mode.

To better understand why SIP ALG is horrible visit http://www.voip-info.org/wiki/view/Routers+SIP+ALG and read. Although SIP ALG is not broken in all routers (for example, the SIP Passthrough function in Asus routers doesn't seem to affect FPL), it is broken in a lot of them.

4. Proper device reboot order is always modem-->router (wait for it and your modem to be fully up, running, and passing data before turning on your ATA; you may need to wait 10 minutes, depending on the router)-->ATA"

2. Change local SIP port to 30100
3. Not on Rogers, so I'll stick with voip and voip2
4. Have rebooted a few times, including disconnecting power to ATA for few minutes as well

[Liptonbrisk]

Hi, thanks for the detailed reply!
Have made the changes you suggested. And did couple of reboots of routers as well.
I believe it was an issue with one of the public DNS servers I'm using. It was was slow or timing out in some cases, which may have caused an issue with FPL registration.

Quite possibly

Maybe just use your ISP's DNS servers for your ATA.
In my case, they're faster than Open and Google DNS anyway.

By the way, even if you don't have Rogers, voip4.freephoneline.ca:6060 will work.
But its intended use is for people with SIP ALG issues.

[mh1983]

A. Latest ATA firmware is here: http://www.grandstream.com/sites/defaul ... .0.8.2.zip

i. "Once the new firmware is installed, set SIP REGISTER Contact Header Uses to WAN address."--Mango

ii. "Set "Enable SIP Options Keep-Alive" to "Yes."-- Fongo Support

http://forum.fongo.com/viewtopic.php?f=15&t=18839