[Resolved] voip.freephoneline.ca not working since Sunday, October 5, 2025

[hanke]

This was noticed at 8AM EDST. Server - voip.freephoneline.ca is down for me. I changed to voip2.freephoneline.ca and that is working fine. Maybe its only on my system but I will check later to see if things change.

[Liptonbrisk]

I just woke up.

voip.freephoneline.ca isn't responding to registration requests.

I've tried contacting someone at Fongo.

Thanks for posting.

[Liptonbrisk]

Those who have setup server failover for Obihai and Poly 4xx series ATAs and Obihai IP Phones won't encounter this problem.

(OutboundProxy should be left blank with Freephoneline. There is no separate OutboundProxy server.)



1. Dial ***1. Enter the IP address you hear into a web browser. Login. Default username and password is "admin" (without the quotation marks).

2. Navigate to Router Configuration-->WAN Settings-->Local DNS Records

(For OBi200/300/2182 or Obihai devices without a built-in router, navigate to System Management–-->WAN Settings-->Local DNS Records)

For line 1 (presuming this is a blank line . . . just choose a blank line), enter

"voip2.freephoneline.ca={voip.freephoneline.ca:5060,3},{voip2.freephoneline.ca:5060,1},{voip4.freephoneline.ca:6060,2}" (without the quotation marks)

In this example voip2.freephoneline.ca:5060 (1) is being given priority. If there's no response on voip2.freephoneline.ca:5060 (1), then the Obihai device will attempt to register with voip4.freephoneline.ca:6060 (2), and if there's no response from that server, the OBi202 finally attempts to register with voip.freephoneline.ca:5060 (3).

I'm choosing voip2.freephoneline.ca:5060 as the primary proxy (SIP) server here because voip.freephoneline.ca tends to have the most problems (as evidenced by this thread) over the years. (I'm guessing that's because most users are registering on voip.freephoneline.ca.)

Make the primary server (1) what you're defining (what's before the equal sign on the left). So if you want primary server (1) to be voip4.freephoneline.ca instead, then use "voip4.freephoneline.ca={voip.freephoneline.ca:5060,3},{voip2.freephoneline.ca:5060,2},{voip4.freephoneline.ca:6060,1}" without the quotation marks.


3. Click "Submit".

4. Navigate to Service Providers-->ITSP Profile used for FPL-->SIP->

a) change ProxyServer to voip2.freephoneline.ca (this needs to be what's before the equal sign). If you want the primary server (1) to be voip4.freephoneline.ca, then enter voip4.freephoneline.ca for ProxyServer.
b) change ProxyServerPort to 5060
If you want the primary server (1) to be voip4.freephoneline.ca, then use 6060 for ProxyServerPort. Otherwise, use 5060. That matters in some scenarios where the ATA or IP Phone boots up before the router finishes booting up.



5. Enable/check X_ProxyServerRedundancy (you will have to uncheck the default box). This setting is needed so that server failover works.

6. Set X_CheckPrimaryFallbackInterval to 7200 seconds (ATA will check to see if voip2.freephoneline.ca:5060 will work after 2 hours if it wasn't working; this will allow enough time for a temporary IP ban to clear as well on the primary proxy server, and then the ATA will register on the primary proxy server, voip2.freephoneline.ca:5060, in the first example, again).

7. Click submit.

8. Reboot ATA.

[Liptonbrisk]

For Grandstream HT-8xx series ATA users (other Grandstream ATA users with different models may be able to modify these instructions accordingly),

1) a) Dial ***
b) Then dial 02
c) Enter the IP address you hear into a web browser.
d) Login to your ATA.

Default login password is admin.

2) Navigate to FXS Port tab (for HT-812, navigate to Profile tab) used for Freephoneline.

3) Set Primary SIP server to voip2.freephoneline.ca:5060 (specifying UDP port 5060 isn't necessary, but I wanted to make the distinction between voip4.freephoneline.ca:6060 apparent for people)

4) Set Failover SIP server to "voip4.freephoneline.ca:6060" (without the quotation marks)

(or vice versa . . . you can use voip4.freeephoneline.ca:6060 for the primary sip server and voip2.freephoneline.ca:5060 for the failover sip server if you prefer)

5) Set Prefer Primary SIP server to Yes (for HT-80x)
For HT-812, select "Will register to Primary Server if Primary Server responds, need to enable SIP OPTIONS/NOTIFY
Keep Alive"

6) Set Failback Timer to 120 minutes (this will allow enough time for temporary IP bans to clear)

7) Click "Apply" and "Reboot".

[Liptonbrisk]

I've tried contacting someone at Fongo.

No one has responded to me yet. So this is a waiting game.

Use voip2.freephoneline.ca or voip4.freephoneline.ca:6060 until someone responds.

[bbea4]

I lost connection after a power failure,

Using a Cisco ATA SPA112.

Changed the PROXY on the "Quick setup" page to "voip2.freephoneline.ca" and all is good agian.

It was "voip.freephoneline.ca" for many years.

[Liptonbrisk]

I've tried contacting someone at Fongo.

No one has responded to me yet. So this is a waiting game.

Use voip2.freephoneline.ca or voip4.freephoneline.ca:6060 until someone responds.

To update, I've sent several emails about this issue since Sunday. I have not received any response.
So, there's nothing further I can do.

I've looked at syslogs. I see “SP:REG:NoResp” and “REG:CRLF timeout”, which indicate no SIP responses from 162.213.111.25 (voip.freephoneline.ca).
All SIP clients (including SIP apps) show no response from 162.213.111.25.

I see this:

REGISTER (retransmission, same branch/CSeq) --------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->
REGISTER (retransmission) --------------------------------------->

Transaction timeout -> SP:REG:NoResp (REGISTER failed due to no response)



voip.freephoneline.ca is simply not responding to registration requests (although pinging it works). This was the same problem that was reported at viewtopic.php?t=20947. Fongo restarting the service worked.





So, everyone is forced to use voip2.freephoneline.ca:5060 or voip4.freephoneline.ca:6060 for now.

If voip.freephoneline.ca not working properly bothers you, you can submit a ticket: https://support.fongo.com/hc/requests/new.
Choose "My Account Inquiry" for the issue type.


You can check your ticket status by logging in at
https://support.fongo.com/hc/requests. That's an account for tickets
(zendesk) only and is completely separate from your Freephoneline account or
any other Fongo account you may have. If you don't have a zendesk account yet, click "Sign Up" after visiting the link.
Use the same email address that you use to submit tickets. Do not use the same password as your Freephoneline
account. Again, these accounts are unrelated.

If your ticket is closed, you can submit another ticket: https://support.fongo.com/hc/requests/new (Choose "My Account Inquiry" for the final issue type.)

This is the escalation process: https://support.fongo.com/hc/articles/2 ... -Complaint.




Support staff does not respond to tickets on weekends or Canadian holidays.
Support hours are 9 a.m. until 4 p.m. EST.

Fongo does have https://twitter.com/Fongo_Support. I'm not sure if anyone
there responds to direct messages.

Similarly, they appear to be on Facebook:
https://www.facebook.com/FongoMobile/. I don't know whether they'll respond to you there.

[jimmy]

I also experienced the same issue. Currently I have switched to Use voip2.freephoneline.ca. I don't know when they are going to bring voip.freephoneline.ca up.

[Liptonbrisk]

I also experienced the same issue.

Everyone using voip.freephoneline.ca is.

I don't know when they are going to bring voip.freephoneline.ca up.

No one except Fongo does.

For now, use voip2.freephoneline.ca or voip4.freephoneline.ca:6060. Both of those servers are working.



If voip.freephoneline.ca not working properly bothers you, you can submit a ticket: https://support.fongo.com/hc/requests/new.
Choose "My Account Inquiry" for the issue type.


You can check your ticket status by logging in at
https://support.fongo.com/hc/requests. That's an account for tickets
(zendesk) only and is completely separate from your Freephoneline account or
any other Fongo account you may have. If you don't have a zendesk account yet, click "Sign Up" after visiting the link.
Use the same email address that you use to submit tickets. Do not use the same password as your Freephoneline
account. Again, these accounts are unrelated.

If your ticket is closed, you can submit another ticket: https://support.fongo.com/hc/requests/new (Choose "My Account Inquiry" for the final issue type.)

This is the escalation process: https://support.fongo.com/hc/articles/2 ... -Complaint.




Support staff does not respond to tickets on weekends or Canadian holidays.
Support hours are 9 a.m. until 4 p.m. EST.

Fongo does have https://twitter.com/Fongo_Support. I'm not sure if anyone
there responds to direct messages.

Similarly, they appear to be on Facebook:
https://www.facebook.com/FongoMobile/. I don't know whether they'll respond to you there.

[tanny]

This was noticed at 8AM EDST. Server - voip.freephoneline.ca is down for me. I changed to voip2.freephoneline.ca and that is working fine. Maybe its only on my system but I will check later to see if things change.

Cisco/Linksys SPA2102
Product Name: SPA-2102
Software Version: 5.2.12 Hardware Version: 1.2.5(a)

(Had no working phone/registration since Sunday, Oct.05, 2025)
Thanks for the post, and for this freephoneline community support forum
My old Cisco/Linksys SPA2102 doesn't have a (failover) PROXY option, so I changed the PROXY from voip.freephoneline.ca to voip2.freephoneline.ca and all is fine again.
I've had this SPA-2102 since 2008(new), and it's "Still Alive and Well": https://www.youtube.com/watch?v=NdIGrNcXcs4

[Liptonbrisk]

My old Cisco/Linksys SPA2102 doesn't have a (failover) PROXY option

Correct. PAP2Ts and the SPA ATA series can't support server failover without the service provider (Fongo) offering DNS SRV records with multiple (or without you having a router or device that allows you to edit/create DNS records) server entries listed. That's why I can't provide failover configuration steps for those devices.

[Liptonbrisk]

Do not use voip3.freephoneline.ca, which can lead to account suspension.

"Use of Fongo SIP Servers that are not listed in this document will result in your account being suspended."

Visit https://support.freephoneline.ca/hc/art ... redentials.

voip4.freephoneline.ca:6060 will work for everyone (doesn't just apply to Rogers customers).

[freephonefan]

I'm on the old HT-286 ATA from GrandStream. FreePhone service went down. Switched to voip2.freephoneline.ca on both the SIP and Outbound. Don't forget to re-enter your SIP password. Reboot and then you're back in business. I have no idea what happenned to voip.freephoneline.ca or if it's coming back. I tried the voip4 address with 6060 port, but I don't think it works oh an HT-286.

[Liptonbrisk]

Switched to voip2.freephoneline.ca on both the SIP and Outbound.

There is no need to enter outbound proxy for Freephoneline. There is no separate outbound proxy server for Freephoneline. Entering one is redundant. Erase Outbound Proxy, and keep it blank, as shown in the configuration guide that should be used for the HT-286: viewtopic.php?p=64434#p64434.

I have no idea what happenned to voip.freephoneline.ca or if it's coming back

The same issue involving voip.freephoneline.ca has occurred periodically over the years requiring Fongo to typically restart the server (the temporary fix is simple until the problem occurs again). Consequently, it's been the least reliable proxy/SIP server to use.

I still haven't received any response from Fongo.

I tried the voip4 address with 6060 port, but I don't think it works oh an HT-286.

It does. Enter "voip4.freephoneline.ca:6060" without the quotation marks for SIP server as noted in the PDF configuration guide (page 3) over here: viewtopic.php?p=64434#p64434.

[vincent_zalzal]

Thanks Liptonbrisk for the detailed explanations, it is greatly appreciated (and it worked).

[Liptonbrisk]

Thanks Liptonbrisk for the detailed explanations, it is greatly appreciated (and it worked).

You’re welcome!

Fongo hasn't responded to me or noted the problem with voip.freephoneline.ca at https://status.fongo.com/. I have received no communication from Fongo concerning this issue.

They have posted that the forum will be down for system maintenance: https://status.fongo.com/maintenances/eIsip8MeB56n.
"Scheduled for Oct 07, 21:00 - Oct 07, 23:00 (EDT)"

[hanke]

This was noticed at 8AM EDST. Server - voip.freephoneline.ca is down for me. I changed to voip2.freephoneline.ca and that is working fine. Maybe its only on my system but I will check later to see if things change.

Good morning....as of 0830AM EDST the " voip.freephoneline.ca " server is up and running again.

[hanke]

This was noticed at 8AM EDST. Server - voip.freephoneline.ca is down for me. I changed to voip2.freephoneline.ca and that is working fine. Maybe its only on my system but I will check later to see if things change.

Good morning....as of 0830AM EDST the " voip.freephoneline.ca " server is up and running again.

I perhaps spoke too soon....it seems calls go to Voicemail...or making a call sometimes goes to fast busy. So I have switched back to voip2 server.

[Liptonbrisk]

I perhaps spoke too soon....it seems calls go to Voicemail...or making a call sometimes goes to fast busy. So I have switched back to voip2 server.

One of my lines works. Another one doesn't.

Hmm. And now the one that wasn't working suddenly is.

Testing other lines . . .

[Liptonbrisk]

One of my lines works. Another one doesn't.

Hmm. And now the one that wasn't working suddenly is.

Testing other lines . . .

Now no incoming calls are working on voip.freephoneline.ca

And now an incoming call works on another line.

Intermittent.

Yeah, no good . . .

I've tried contacting Fongo again.

[Liptonbrisk]

I've tried contacting Fongo again.

Okay, I've been told they're looking into it.

[Liptonbrisk]

I'm seeing "Temporary Failure" in call logs when using voip.freephoneline.ca after logging in at https://www.freephoneline.ca/callLogs.




ISUP error code 41 temporary failure = SIP error code 503 (Service unavailable)

[Liptonbrisk]

For what it's worth, incoming calls are working (repeatedly) on 3 lines using voip.freephoneline.ca:5060 right now (no temporary failures in logs). I'll hold off testing more lines.

I'll need to wait to hear from Fongo again before marking this thread as being resolved, I think (particularly if the problem could return for the reason I think it started).

[Liptonbrisk]

This was noticed at 8AM EDST. Server - voip.freephoneline.ca is down for me. I changed to voip2.freephoneline.ca and that is working fine. Maybe its only on my system but I will check later to see if things change.

Good morning....as of 0830AM EDST the " voip.freephoneline.ca " server is up and running again.

I perhaps spoke too soon....it seems calls go to Voicemail...or making a call sometimes goes to fast busy. So I have switched back to voip2 server.

Thank you for letting us know.

[Liptonbrisk]

Incoming calls are continuing to work on the lines I'm testing using voip.freephoneline.ca

A Fongo representative replied to me and indicated all services are working normally at this time (and recognizes that a problem existed), so I'm going to mark this thread as being resolved. Fongo is continuing to monitor the situation for now.