[Resolved] Fongo Mobile/ Fongo Works and FPL Services Down

[Liptonbrisk]

https://status.fongo.com/incidents/ItzGHNyOvl3J

"Identified - A networking issue has been identified our ops team is working to restore connectivity
Feb 04, 2023 - 11:34 (EST)"

[Liptonbrisk]

Hmm, incoming calls are working with one FPL number on voip2.freephoneline.ca.

I'll check some other numbers.

[Liptonbrisk]

A different FPL number works for incoming calls on voip.freephoneline.ca

[Liptonbrisk]

I can make outgoing and incoming calls on voip.freephoneline.ca

[mkaye]

freepbx says can't register with voip.freephoneline.ca since 6:25am this morning
both incoming/outgoing calls now working

[Liptonbrisk]

voip4.freephoneline.ca is working for incoming and outgoing calls with a 3rd FPL number.

Basically, all FPL servers are working for incoming and outgoing calls at the moment despite the server status listed at https://status.fongo.com/.

Maybe I should test voicemail?

[Liptonbrisk]

freepbx says can't register with voip.freephoneline.ca since 6:25am this morning

Okay, I just read about the outage on Fongo's status webpage at 11:50 a.m.

Maybe the problem is fixed now.

both incoming/outgoing calls now working

Well you must be registered now then. Otherwise incoming calls wouldn't work.

[Liptonbrisk]

I'm experiencing intermittent issues connecting to Fongo Mobile.

"Fongo Connection Failed - Click to Retry" in red (up at the top).

If I close the app and run it again (multiple attempts), sometimes it works.

[Liptonbrisk]

Voicemail and voicemail notifications are working with Freephoneline.

[Liptonbrisk]

I'm experiencing intermittent issues connecting to Fongo Mobile.

"Fongo Connection Failed - Click to Retry" in red (up at the top).

If I close the app and run it again (multiple attempts), sometimes it works.

Alternate Fongo Connection setting doesn't make a difference. Neither does "Alternate DNS Resolver".

Same problem on 5G.

[Liptonbrisk]

The Freephoneline desktop app isn’t working at the moment.
I can’t register on voip3.freephoneline.ca (used by the desktop app), and outgoing calls won’t work.

[Liptonbrisk]

At 1:20 p.m. EST,

Freephoneline VoIP unlock keys work (all permitted servers).

- FPL desktop app doesn't work (uses voip3.freephoneline.ca)

- Fongo Mobile app doesn't work intermittently (times out while authenticating and fails)

[mkaye]

still getting packet timed out with freepbx

[hanke]

Voip server is down, no registration. Flipped over to voip2 and registration and service works. Will wait til things get corrected. Thanks for finding the fault.

[Liptonbrisk]

I've checked voip.freephoneline.ca with several Freephoneline numbers at different locations within Canada using different ISPs. Incoming calls are working on all of them, which means registration is working fine on that server for those numbers at 3:12 p.m. EST.

If you're continuing to experience issues with voip.freephoneline.ca, for SPA/PAP series ATAs, navigate to Line 1 (or whatever you're using for FPL)-->SIP settings, and change SIP Port to a random number between 30000 and 60000. Do this for security reasons (to help avoid SIP Scanners/hackers). Also, this step may help to temporarily address a corrupted NAT association that's developed between a router and ATA (if you're having registration issues, try selecting a new random port number in this range, and then reboot the ATA. If that works, you were dealing with a corrupted/stale NAT association in your router).

For Obihai ATAs, Navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort. X_UserAgentPort should be a random port number between 30000 and 60000. Just pick a port number in that range.
If you've already chose a random number in that range, choose a different number in that range. Save settings, and reboot the ATA. If that works, you were dealing with a corrupted/stale NAT association in your router.

If you're switching back to voip.freephoneline.ca at this point (from another server), you won't be able to check for NAT corruption. Registration should work at this point unless a temporary IP ban is in place due to too many registration attempts within a short interval when using voip.freephoneline.ca

Regardless, voip.freephonline.ca has been the least reliable proxy server over the past year. You may be happier using voip4.freephoneline.ca:6060 or voip2.freephoneline.ca.

[Liptonbrisk]

At 1:20 p.m. EST,

Freephoneline VoIP unlock keys work (all permitted servers).

- FPL desktop app doesn't work (uses voip3.freephoneline.ca)

- Fongo Mobile app doesn't work intermittently (times out while authenticating and fails)

All FPL servers are working now. That also means FPL's desktop app is working.

Fongo Mobile continues to fail randomly. It's failing less than it did earlier, but it's still failing occasionally.

[hanke]

Flipped back over to voip.freephoneline.ca and registration is there and all working again.

Thanks again Liptonbrisk for you speedy help and up to date reports of the situation.

[Liptonbrisk]

Flipped back over to voip.freephoneline.ca and registration is there and all working again.

Thanks again Liptonbrisk for you speedy help and up to date reports of the situation.

You're welcome. On one hand, if I were you, I wouldn't use voip.freephoneline.ca (due to it being less reliable than the other proxy servers over the past year). On the other hand, I'm grateful when you report voip.freephoneline.ca isn't working because I've switched everyone I know to a different primary server so that I deal with less complaints (I'm not usually aware when voip.freephoneline.ca isn't working anymore), and when registration fails, their Obihai ATAs are configured to try a different FPL proxy server automatically anyway.

[Liptonbrisk]

I just managed to register Fongo Mobile 10 times in a row, so maybe the problem is resolved.

[mkaye]

12:34pm
all circuits busy - outgoing
incoming - not in service

was voip2, switched back to voip, same

[Liptonbrisk]

All FPL servers are working normally on several different FPL numbers I tested for incoming and outgoing calls.

Fongo Mobile is connecting normally.

Issue is marked as resolved: https://status.fongo.com/incidents/ItzGHNyOvl3J.

Thread closed.