The same issue can occur if you reboot the ATA repeatedly within a short interval.Īs for the initial registration failure (before your ATA kept trying to re-register again every 30 seconds), NAT corruption is a likely cause. If the ATA keeps try to re-register after 30 seconds (after a failed registration attempt), you can end up temporarily IP banned by the ProxyServer the ATA was trying to register with. Thank you very much for updating the thread, and I'm glad your issue is resolved after following Step C (above). Changed SIP server to voip2, retry interval to 120 (previous default was 30) and issues resolved. You can also try rebooting your modem–>router (wait for it to be fully up and transmitting data)–>ATA (in that order).īeeknight80 wrote:Update: Read a previous thread on similar issues. You should only need to do this if you're experiencing a DNS issue.Į. If you don't believe you're IP banned, and if the ATA is completely unable to reach FPL's Proxy Servers, you may want to try specifying alternate DNS servers in your ATA. The purpose of :6060 is to circumvent SIP ALG features in routers.ĭ. If you're temporarily IP banned, you could then try switching ProxyServer to a different FPL server than the one you were previously using (,, or :6060), unless you need to use :6060 because you have SIP ALG forced on in your router. If your ATA makes more than 5 registration attempts in 5 minutes, you may end up being temporarily IP banned by the specific FPL server the ATA was sending registration requests to.Įach time you reboot your ATA, the ATA is attempting to register again. I use 17 for UDP Unreplied Timeout and 117 for UDP Assured Timeout.Ĭ. The SIP Registration Failure Retry Wait Time is 120. Note that I will not be held accountable any damage resulting from failed firmware updates. If your router supports Tomato firmware, that may be another option. However, my understanding is that third party Tomato firmware has these two settings as well. UDP Unreplied Timeout (in your router) Other settings. 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: 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). (Credit goes to Mango for this information). And, then, the ATA keeps the corrupted connection in a persistent state over and over again. Possibly a NAT router connection was never disconnected or never timed out properly. If changing X_UserAgentPort works, you were dealing with a corrupted NAT connection in your router. (If you use to change settings, you will need to use ). Click the “submit” button, and reboot the ATA. Change to a new port number in that range. X_UserAgentPort should be a random port number between 3000. In your Obihai ATA or at, whichever method your normally use (don't use both), navigate to Voice Services->SP(FPL) Service->X_UserAgentPort. If the service status website doesn’t note any issues, then chances are the problem is on your end. FPL SIP reports that my account is still connectedĪnd are you positive you're logging into the exact same FPL account you have provisioned on your ATA?Īre Freephoneline’s SIP servers down? My ATA isn’t registered.ī.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |