No. FPL is up and running.
Follow the steps in the order listed below, carefully:
A. Visit
http://status.fongo.com/ to check server status.
B. Double check your Registration timers.
https://support.freephoneline.ca/hc/en- ... redentialsa) Registration Interval: 3600 seconds (1 hour)
b) Registration Expiry: 3600 seconds (1 hour)
c) Failed Registration Re-Try Interval: 120 seconds
In your PAP2T, navigate to LINE 1-->Proxy and Registration -->Register Expires should be 3600.
In your PAP2T, navigate to SIP-->SIP Timer Values-->Reg Retry Intvl: should be 120.
If your ATA or IP Phone makes more than 5 registration attempts in 5 minutes, you will end up being temporarily IP banned by the specific FPL server the ATA or IP phone was sending registration requests to. If you're temporarily IP banned, you could then try switching proxy to a different FPL server than the one you were previously using (voip.freephoneline.ca, voip2.freephoneline.ca, or voip4.freephoneline.ca:6060), unless you need to use voip4.freephoneline.ca:6060 because you have SIP ALG forced on in your router or modem/router combo. The purpose of voip4.freephoneline.ca:6060 is to circumvent SIP ALG features in routers.
C. If the service status website doesn’t note any issues, then chances are the problem is on your end. In your PAP2T, Navigate to Line 1 (or whatever you're using for FPL)-->SIP settings. Change SIP Port to a random port number between 30000 and 65535. Just pick a port number in that range. Click the “save settings” button, and reboot the ATA.
If changing SIP Port works, you were dealing with a corrupted NAT connection in your router.
Possibly a NAT router connection was never disconnected or never timed out properly. And, then, the ATA keeps the corrupted connection in a persistent state over and over again. (Credit goes to Mango for this information). Possibly, this problem is due to the router's UDP timeout being in excess of the ATA's Failure Retry timer (RegisterRetryInterval with Obihai ATAs). With FPL, that's 120 seconds.
Thanks to Mango, many of us now understand that in order for ATAs to remain registered and working properly with a VoIP SIP provider like Freephoneline, in particular after power failures, the following conditions must be met:
UDP Unreplied Timeout (in your router) < NAT Keep-alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires) < UDP Assured Timeout (in your router) < SIP Registration Failure Retry Wait Time (or RegisterRetryInterval in Obihai ATAs)
“<“ means less than.
When a modem leases a new IP address, a problem can arise where prior associations using the old IP address are maintained in the router. When the ATA attempts to communicate using the old IP address, the response is unreplied, and then if the UDP Unreplied timeout is greater than the Keep Alive Interval (and UDP Unreplied timeout is often set to 30 by default in consumer routers) a problem arises where the corrupted connection persists. If UDP Unreplied timeout is, for example, 10, and the NAT Keep Alive Interval is 20, then the corrupted connection will timeout or close. A new connection will be created, and everything will work fine.
Another problem can occur when the Keep-Alive interval is greater than UDP Assured Timeout (often 180 by default in consumer routers): the NAT hole will close due to the ATA not communicating frequently enough with the SIP server. In turn, incoming calls may, intermittently, not reach the ATA. Again, NAT Keep-alive Interval is supposed to be 20 with FPL.
Getting access to both UDP Unreplied Timeout and UDP Assured Timeout settings in consumer routers may be difficult, if not impossible. Asuswrt-Merlin, third party firmware for Asus routers, does offer easy access to these two settings, which are found under Tools-->Other settings. In part, for this reason, I tend to use Asus routers that work with Asuswrt-Merlin. However, my understanding is that third party Tomato firmware has these two settings as well. So if your router supports Tomato firmware, that may be another option.
The keep alive interval for FPL is 20. The SIP Registration Failure Retry Wait Time is 120. I use 10 for UDP Unreplied Timeout and 117 for UDP Assured Timeout.
D. You can also try rebooting your modem–>router (wait for it to be fully up and transmitting data)–>ATA (in that order).