slimmswitch wrote:Just wondering if there was any changes to freephoneline.ca settings recently
Freephoneline accounts are now being blocked for not using a 3600 second registration interval. Otherwise, not that I've been made aware of, no.
I have multiple VoIP unlock keys registered at multiple locations.
Do you hear an error message when dialing out? If so, what is it?
If your account(s) are blocked, visit
viewtopic.php?f=8&t=20537, and read carefully.
Otherwise, click
viewtopic.php?f=8&t=20532. You can ignore steps 7,8, 10, 11, 22, 23, 24, and 27 until registration has been established.
Some additional considerations follow:
A. Obviously, one of the first things that can happen is ISP related. A DNS issue (where you suddenly can't reach a server using the proxy name, for example) or a routing problem between you and the proxy server being used can develop. Step 26 from
viewtopic.php?f=8&t=20532 shows how to test for those two issues (winmtr test can help pinpoint a routing problem).
B. Have you been trying to use your FPL accounts on SIP apps or other devices? Using the same FPL account on more than one line can drop registration on your ATA when using the same proxy server.
Disconnect your ATAs for at least an hour and login at
https://www.freephoneline.ca/showSipSettingsIf SIP Status shows "Connected" at that point and if you also see a SIP User Agent that you don't recognize, you have a problem. In that case, someone and something else is using your FPL account(s).
C. NAT corruption can develop in users' routers (your hub) without them doing anything differently. That can happen due to using incorrect UDP timeouts in routers as described in point 28 from
viewtopic.php?f=8&t=20532. Testing for that problem (should it arise again when registration fails) is simple enough and described in step 12 from that link.
D. If you were not using a 120 second failed registration timer (and a lot of old FPL guides didn't included that setting), you can be temporarily IP banned by the FPL proxy server that was being used. (If you switched to voip4.freephoneline.ca:6060, on one of the ATA lines, from a different proxy, then the problem wasn't being IP banned.) Also changing to a different proxy should reset NAT associations (point 5 above).
When registration fails, the failed registration timer setting indicates how often the ATA is going to attempt to register again. If that setting is set to 10 seconds, for example, you can be IP banned eventually.
"As May 2013, our servers will rate limit REGISTER requests to a maximum of 10 requests per 5 minutes. Each authentication round usually consumes 2 requests (digest auth), so it is a fair number given our guidelines."
https://community.freepbx.org/t/trunk-s ... ca/22479/8If that rate limit has changed since then, I'm not aware. I've encountered that situation before, and I'm not going to test.
Being temporarily IP banned can also occur when using registration timers with short intervals with Freephoneline. Too many registrations attempts within a short period can lead to an IP ban. Keep in mind that every time you reboot the ATA (or power cycle it), it's attempting to register with Freephoneline proxy server(s) again. The same (typically) happens when you run a SIP app.
E. One FPL account means you can only register one line on one an ATA using it. Don't register the same FPL account on both ATAs.
Your ATA configuration guide is located at
viewtopic.php?f=15&t=16206.