[Resolved] No Incoming calls on voip.freephoneline.ca

[Liptonbrisk]

here is a nice article for your modem-router to bypass it's internal router

https://support.shaw.ca/t5/internet-art ... /ta-p/6457

Good idea

Stick the SPA3102 ATA's MAC address in there.

[hanke]

Well in my modem/router I do not have that availability as suggested in the Shaw Support Link. My device only has the 4 tabs on that window, no IP Pass Thru tab. Anyhow, I have played with it more, and whenever I go back to voip.freephoneline.ca setting, no incoming calls. I have now set it to the voip4.freephoneline.ca:6060 server and will leave it at that right now. Just odd that for whatever reason this has become an issue as of today.

Thanks again

[SLS]

I had exactly the same issue today and too was able to resolve it by switching to voip2 server. I started getting "we can't reach you, the call ends in your voicemail" comments from my co-workers three weeks ago when this whole 'working from hom'e began. Evenings and weekends usually no problem, so my guess is that it can be caused by an increased load. Most folks use the first voip server, may be it gets overloaded at peak hours. Today I was able to get through only 1 time out of 10 attempts to call from my cell, tried to reset my obi adapter and my router, then read this forum and switched to voip2. I hope fongo people will be able to fix this. So far I've been using my phone for many years with zero issues.

[amuskiluke]

I have the same problem today. No changes were made at my end, so I am hoping it resolves itself soon. (I did make changes after noticing the problem , but I know what they are.

[Liptonbrisk]

Welp, I'm having the same problem again on voip.freephoneline.ca for incoming calls as of 8:03 p.m. Outgoing is fine.

[hanke]

Further, since I have my SPA3102 on voip4.freephoneline.ca:6060 or even on voip2.freephoneline.ca all is fine on incoming calls. I have 2 family members using a SPA2102 and Obi200, both are not accepting any inbound calls on a regular basis (they go to voicemail). I have changed the Obi200 over to voip2.freephoneline.ca and works no problem. I have to physically attend the SPA2102 location to changed that server but will do at some point. The Obi200 has received the odd inbound call but not always. This is similar to what I had experienced when this issue was discovered earlier today. These two configurations as well as my SPA3102 have been working fine until today when it was discovered.

Just thought I would update that 3 different devices located at 3 different locations are having issues with voip.freephoneline.ca so I would suspect there is a problem.

[Liptonbrisk]

There was an incoming call problem earlier today with voip.freephoneline.ca. Then the problem went away, possibly as server load decreased. Now the issue has returned at the time of this post.
The problem is intermittent.

I've tried reaching out. Unfortunately, due to COVID-19, any response may be delayed: https://twitter.com/Fongo_Support/statu ... 48902?s=20.
I wouldn't normally expect a response anyway, given FPL does not provide free technical support anymore, but this is not an issue on the users' end.

[flob3d]

Hi,

Two days ago I started having problems with the phone ,,freephoneline,, I can call but I cannot be called !
I use LINKSYS PAP2T-NA I reset it and configured it but the same.
I have changed home phones and it is the same.
When someone calls me busy, and they leave a message to voice mail *98.

Any ideas?

[hanke]

Check this topic - http://forum.fongo.com/viewtopic.php?f=8&t=19793

The server " voip.freephoneline.ca " is having problems and several of us have switched to " voip2.freephoneline.ca " till hopefully it gets resolved.

[flob3d]

Thanks!

[stepheny]

Change FPL server to voip2.freephoneline.ca is working now. It should be a solution hopefully. Thanks user jarfgames!

[Liptonbrisk]

Hi folks,

So, I did receive a response.

"Hello,

We apologize for the system issue you are having; we are experiencing higher than normal call volumes, and it has caused issues on our server. We have resolved the issue, and it should be working as usual now.
Note: You may need to reboot your ATA device."




I'm hoping the problem is resolved now.

For anyone experiencing this problem, I recommend following these steps, step by step:

1. Use a high random SIP port. Each time you change local sip port, you help to reset corrupted/stale NAT associations that may develop between your router and ATA (it's also good practice to use a high, non-standard local sip port for security reasons).

a) For Obihai users, if you used the Obitalk web portal (http://www.obitalk.com) to configure your ATA, keep in mind that you must continue using it to configure your ATA. Otherwise whatever settings you change will eventually be overwritten by what you previously entered at obitalk.com anyway. If you wish to disable this behaviour, dial ***1. Enter that IP address into a web browser. Navigate to System Management-->OBiTalk Provisioning-->select Disabled for the method. Save. Reboot ATA. Now obitalk.com won't overwrite whatever changes you make via the device's interface (via IP address).

Pick one method (obitalk.com) or the other (IP address of device) for changing device settings. But do not use both methods.

(In Obitalk.com, you will need to enable and enter expert settings to do the following, if you want to use Obitalk.com. You do this by selecting Edit Profile-->Advanced Options-->check Enable OBi Expert Entry from Dashboard-->submit))

Keep in mind too, that if you're using the Obitalk.com web portal, after you submit a new setting, it take several minutes before Obitalk.com pushes the changes you've made to your ATA. Your ATA should reboot automatically after the changes are submitted.

In your Obihai ATA or at Obitalk.com, (whichever method you originally used; don't use both methods), navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort
X_UserAgentPort should be a random port number between 30000 and 60000. Just pick a new port number in that range.
Click save.


b) If you have an Linksys/Cisco PAP2, for example, or something similar, log into your ATA, navigate to Line 1 (or whatever you're using for FPL)-->SIP settings, and change SIP Port to a new random number between 30000 and 60000.
Save settings.


c) If you have a Grandstream device, you should already have your device configured to use a random SIP port anyway if you've been following the PDF guides on these forums.


2. Reboot your a)modem-->b) router (wait for it to be fully up and running first with Wi-Fi SSIDs populated)-->c) ATA/IP Phones in that order

That's always the proper device reboot order.


3. Login at https://www.freephoneline.ca/showSipSettings
a) Ensure SIP Status indicates "connected" and that
b) SIP User Agent is something you recognize.

4. Then test again with an incoming call.

Good luck!

[Liptonbrisk]

Change FPL server to voip2.freephoneline.ca is working now. It should be a solution hopefully. Thanks user jarfgames!

Hello,

You originally replied in a thread that's over a year old, when all servers were working perfectly fine. Your issue was unrelated to anything in the thread you originally posted in (and all users in that thread eventually resolved their problems). I'll move your post to the appropriate thread.
Please refer to http://forum.fongo.com/viewtopic.php?f= ... =25#p77370 for this current issue.

Thank you

[Liptonbrisk]

Hi folks,

So, I did receive a response.

"Hello,

We apologize for the system issue you are having; we are experiencing higher than normal call volumes, and it has caused issues on our server. We have resolved the issue, and it should be working as usual now.
Note: You may need to reboot your ATA device."




I'm hoping the problem is resolved now.

For anyone experiencing this problem, I recommend following these steps, step by step:

1. Use a high random SIP port. Each time you change local sip port, you help to reset corrupted/stale NAT associations that may develop between your router and ATA (it's also good practice to use a high, non-standard local sip port for security reasons).

a) For Obihai users, if you used the Obitalk web portal (http://www.obitalk.com) to configure your ATA, keep in mind that you must continue using it to configure your ATA. Otherwise whatever settings you change will eventually be overwritten by what you previously entered at obitalk.com anyway. If you wish to disable this behaviour, dial ***1. Enter that IP address into a web browser. Navigate to System Management-->OBiTalk Provisioning-->select Disabled for the method. Save. Reboot ATA. Now obitalk.com won't overwrite whatever changes you make via the device's interface (via IP address).

Pick one method (obitalk.com) or the other (IP address of device) for changing device settings. But do not use both methods.

(In Obitalk.com, you will need to enable and enter expert settings to do the following, if you want to use Obitalk.com. You do this by selecting Edit Profile-->Advanced Options-->check Enable OBi Expert Entry from Dashboard-->submit))

Keep in mind too, that if you're using the Obitalk.com web portal, after you submit a new setting, it take several minutes before Obitalk.com pushes the changes you've made to your ATA. Your ATA should reboot automatically after the changes are submitted.


In your Obihai ATA or at Obitalk.com, (whichever method you originally used; don't use both methods), navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort
X_UserAgentPort should be a random port number between 30000 and 60000. Just pick a new port number in that range.
Click save.

b) If you have an Linksys/Cisco PAP2 or something similar, log into your ATA, navigate to Line 1 (or whatever you're using for FPL)-->SIP settings, and change SIP Port to a new random number between 30000 and 60000.
Save settings.

c) If you have a Grandstream device, you should already have your device configured to use a random SIP port anyway if you've been following the PDF guides on these forums.


2. Reboot your a)modem-->b) router (wait for it to be fully up and running first with Wi-Fi SSIDs populated)-->c) ATA/IP Phones in that order

That's always the proper device reboot order.


3. Login at https://www.freephoneline.ca/showSipSettings
a) Ensure SIP Status indicates "connected" and that
b) SIP User Agent is something you recognize.

4. Then test again with an incoming call.

Good luck!

Currently, voip.freephoneline.ca is working for me for incoming calls. I'm going to continue testing incoming calls periodically over the course of this evening.
Then I'm going to switch permanently away from voip.freephoneline.ca to hopefully help do my part with server load balance. However, I am a little paranoid that we're all going to switch to voip2.freephoneline.ca and congest that server as well.

[hanke]

All seems to be working for my device and 3 others that I help with, all sitting on the "voip.freephoneline.ca" again. Lets hope it holds out.

[Liptonbrisk]

All servers are still working fine.

I'm going to switch away from voip.freephoneline.ca now to help reduce load.

[jenom]

I switched and remained on voip2 server since I started this thread
my device is a former Vonage VDV21, and changing server is done via a local webserver provisioning.....PITA
As long as voip2 does works, no point to switch.

[koreyb]

Is anyone else having an issue with incoming calls all going direct to voicemail?

My parents and I who both use freephoneline VOIP key both have no incoming calls. They go direct to voice mail... I can assume everyone else is having the same issue?

[speedbump]

Same problem here.

[SeanO2000]

hi. i have two phone numbers with FPL and they both stopped receiving incoming calls today. I noticed a similiar post a month ago and tweaked my SIP setting based on that post, but same thing -- no incoming calls. Glad to hear its just not me. This issue started today / this morning. Sept 3 2020. If you find out anything, pls let me know too.

[Gmass]

I'm having the same issue. I can call out, but not receive any calls. It was working fine yesterday, but noticed it wasn't receiving calls this morning. It shows "Temporary Failure" when I look at the call logs.

[MrDr]

I have the same problem, since this morning(I think).
outgoing is ok, but incoming calls went directly to voice main.

CarryTel cable internet
Obi2020
voip.freephoneline.ca :5060

[Venturess]

I am having the same issue today. I have rebooted, but no sucess. Family members also have been experiencing this problem for the past few weeks and all they get is that they need to check their configuration, despite the fact that nothing has been changed, i.e. Internet providers or touched any configurations.

Perhaps there is a problem that is ongoing or this service is slowly being phased out. If so, it would be appreciated if users are informed of this. Support tickets are answered briefly after several weeks with no satisfactory solution as Freephoneline is no longer supported, although this service has been exceptional for the past seven years of use with no problems until today. Support in this forum by volunteers is exceptional though!

An update would be helpful please.

Thank you.

Taz

[MrDr]

I have the same problem since this morning,
nothing has changed in my router& VOIP adpt. for years,
just reboot my VOIP adpt., and problem seems solved.
##########

Oop, I said it too early, it worked for a few calls, then not work again,
Reboot it, and worked for another call, then not working again.
##########

Changed to
voip4.freephoneline.ca:6060
And problem seems fix.

[Hyrules]

Similar issue here. But in my case some numbers can call and other cannot.

EDIT : Outgoing call works fine. Incoming not so. I sure hope we get some answer from Fongo otherwise i'll be moving to another voip provider. It's nice to have a free phone line but when you don't get any support that's a problem.