service down or just me :)?

Mango · Post by **Mango** » 02/09/2015

I'm glad to hear your hardware is operating properly. When you get the chance, try my suggestions and let us know if that changes the symptoms.

barbus · Post by **barbus** » 02/09/2015

After switching from voip.freephoneline.ca to voip2.freephoneline.ca i got the signal and all lights on my Linksys PAP2 device are on. Desktop app is showing 'SIP Status: connected'. Everything seems to be back to normal. Why voip.freephoneline.ca is not working any more that is a mystery to me.
Mango, you are a lifesaver.

Mango · Post by **Mango** » 02/09/2015

I'm glad it's working. Did you check your settings against the official guide I posted earlier? In particular, be sure Register Expires is set to 3600.

barbus · Post by **barbus** » 02/10/2015

Register Expires was already set to 3600.
Do you have any explanation why voip.freephoneline.ca is not working any more? And... How come more people are not complaining about this?

Post by **Fongo Support** » 02/10/2015

barbus wrote:Register Expires was already set to 3600.
Do you have any explanation why voip.freephoneline.ca is not working any more? And... How come more people are not complaining about this?

Hi there,

The explanation is on Acanac status page.

https://www.acanac.com/contactus.php

Regards,

Mango · Post by **Mango** » 02/10/2015

barbus wrote:Do you have any explanation why voip.freephoneline.ca is not working any more?

voip.freephoneline.ca is working, but it seems to be not working for you.

Since you already tried to change your SIP port and that did not solve the problem, that tends to rule out a corrupted NAT connection in your router. Perhaps Acanac's issues caused your internet connection to go up and down, which caused your ATA to register over and over again, which in turn caused you to be banned for registrations that are too frequent.

If you can switch back to voip.freephoneline.ca after not using it for some time (and letting the ban expire), that confirms my guess. If it still doesn't work, it could be that Acanac's route to voip is temporarily down. It seems as if voip and voip2 are in different datacentres. You can confirm this guess with ping.

barbus · Post by **barbus** » 02/10/2015

Thanks Mango and FongoSupport.
Hoping Acanac cable issue will be resolved soon so I can try switching back to voip.freephoneline.ca.

kevindonovan79 · Post by **kevindonovan79** » 02/12/2015

I am running a freephoneline and fongo service through an lg e973 phone. The freephoneline account uses sipdroid and goes through pbxes as it is shared with my home phone. The fongo account is using the fongo app. On both services all incoming calls have an incoming voice delay of 3 to 4 seconds when answered, the caller can hear me answer immediately. This problem happens on both wifi networks and through 4g. Is this the norm or is there a setting to change to speed up the incoming voice. I should mention that the incoming voice is not really delayed in the sense that the entire 3 to 4 seconds is not all received at once, I just don't receive it at all and pick up halfway through their conversation.

barbus · Post by **barbus** » 02/13/2015

Acanac fixed their cable issue yesterday. I tested voip.freephoneline.ca. It was working just fine.
I can confirm that my service down issue was Acanac related.

kevindonovan79 · Post by **kevindonovan79** » 02/13/2015

Thanks barbus for the update. However, I am still getting a 3 second delay on incoming voice when receiving a call, out going calls are fine. I have tried on Acanac, Bell wifi at work and Bell lte.

temptemp · Post by **temptemp** » 02/20/2015

I've been having this issue for a while. When there's an international incoming call, it always got forwarded to my forwarded number. The Disconnect Reason showing in the call log is 'Internetworking, unspecified'. When the incoming call is from US or Canada, it's fine, the call is able to reach my FPL number/device. Can you advise what went wrong?

catmitelton · Post by **catmitelton** » 03/09/2015

My phone didn't work all of a sudden this morning.
?????

Mango · Post by **Mango** » 03/09/2015

Please try to change the SIP Port on your fdfsdfd to a random number between 20000 and 65535.

If that works, this indicates a corrupted NAT connection on your fsdfsdfsdfdsfd. In that case, you should investigate your fsdfsdfsdfdsfd's UDP timeout settings as a possible cause of the problem. If the fsdfsdfsdfdsfd does not have configurable UDP timeouts, you can increase the fdfsdfd's failed registration timeout to compensate for the problem.

If that does not solve the problem, change your fdfsdfd's SIP server from voip.freephoneline.ca to voip2.freephoneline.ca, or vice versa.

If that works, you may have been accidentally banned. In that case, you should ensure your fdfsdfd's registration timeout is set to 3600.

I can troubleshoot ANYTHING.

adamm · Post by **adamm** » 03/11/2015

barbus wrote:Register Expires was already set to 3600.
Do you have any explanation why voip.freephoneline.ca is not working any more? And... How come more people are not complaining about this?

my fpl also stopped working a couple of days ago. I was using voip.freephoneline.ca for a while with no problems. I rebooted the router and ATA which usually clears most problems, but it still failed to register. My timeout was already set to 3600.

Changing to voip2 fixed the problem for me as well.

I'm not with Acanac, I'm with Teksavvy cable, so it can't be a problem specifically with Acanac. I think it's a problem either with the Rogers cable that both Acanac and Teksavvy resell, or not ISP related at all and instead a problem with freephoneline

Mango · Post by **Mango** » 03/11/2015

Are you able to switch back to voip.freephoneline.ca, after using voip2 for a couple of hours? If yes, that might indicate a NAT issue with your router which we can troubleshoot.

If not, can you post a tracert? If the tracert shows problems, that indicates a routing issue with your ISP.

The server does work for me.

zagzaggy · Post by **zagzaggy** » 03/11/2015

My Linksys PAP2T has worked perfectly for years. My internet connection is perfectly good. I made no recent changes but suddenly today it will not accept inbound calls. When I try to call out, I get the following response:

"This account is already in use. if you believe you receive this recording in error please contact your system administrator."

What do I need to do to fix this?

Thanks,

Z

zagzaggy · Post by **zagzaggy** » 03/11/2015

My Linksys PAP2T has worked perfectly for years. My internet connection is perfectly good. I made no recent changes but suddenly today it will not accept inbound calls. When I try to call out, I get the following response:

"This account is already in use. if you believe you receive this recording in error please contact your system administrator."

What do I need to do to fix this?

Thanks,

Z

staspmr · Post by **staspmr** » 03/11/2015

Hi, I signed up for fongo a while ago, just got my number ported and just signed up for the texting package in canada.

When I go to the store, it shows that I have 31 days remaining.

However when I try to text someone it says "The text messaging service is not currently available, or you are not currently subscribed to text messaging..."

adamm · Post by **adamm** » 03/11/2015

Mango wrote:Are you able to switch back to voip.freephoneline.ca, after using voip2 for a couple of hours? If yes, that might indicate a NAT issue with your router which we can troubleshoot.

If not, can you post a tracert? If the tracert shows problems, that indicates a routing issue with your ISP.

The server does work for me.

I just switched back to voip.freephoneline.ca and it registers fine now. It's hard to tell if it was a NAT issue or if the problem really was with the ISP or FPL since I didn't switch back a couple hours after switching to voip2. Not possible to correlate the two at this point in time.

Mango · Post by **Mango** » 03/11/2015

Next time the problem happens, try to change your ATA's SIP Port to a random number between 20000 and 65535. If that works, that indicates the router was the problem.

redgee34 · Post by **redgee34** » 03/12/2015

Hi there, currently I'm having an issue with area code with 905.There is no problem with 416,289,514,800.888. Any help?Thanks

cgitej · Post by **cgitej** » 03/12/2015

Having the same issue, and your correct this has started recently. I don't know if it's a firmware issue of the HT502 or something that changed on freephone-lines end.

Mango · Post by **Mango** » 03/12/2015

Next time the problem happens, first try to change your ATA's Local SIP Port to a random number between 20000 and 65535.

If that doesn't work, change your Primary SIP Server from voip.freephoneline.ca to voip2.freephoneline.ca, or vice versa.

Let us know if either of these solves the problem. When you post back, also include the model number of the router you use.

Post by **Fongo Support** » 03/13/2015

redgee34 wrote:Hi there, currently I'm having an issue with area code with 905.There is no problem with 416,289,514,800.888. Any help?Thanks

Hi,

You mean you can call any number Canada or International with no issues.

As soon as you call 905-xxx-xxxx you will get an error?

Please let me know.

Regards,

newinvestor23 · Post by **newinvestor23** » 03/16/2015

Hey,
Everything working fine for a while, no problems. Tried to call out from my Obi100, I have dial tone, call a number, just dead air. So i checked the status and it says it was not registered to voip.freephoneline.ca, so I reboot, still would not. So I read voip3.freephoneline.ca and tried that one and it says registered?
So is this something on my part or theirs? or just a hiccup?
And can I keep using voip3.freephoneline.ca?
Thanks

Fongo Community Forums

service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

Incoming calls have incoming voice delay

Re: service down or just me :)?

Re: service down or just me :)?

FPL incoming call issue

Re: Taking over an account

Re: service down or just me :)?

Re: service down or just me :)?

Re: service down or just me :)?

This account is already in use

This account is already in use

Texting not working

Re: service down or just me :)?

Re: service down or just me :)?

Re: forward to an internal/extension number

Re: call disconnects when I receive another call

Re: service down or just me :)?

Re: forward to an internal/extension number

Any problems on the server?