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

[koreyb]

Outgoing calls are no issue...

incoming seems to be the big issue.. I can't even get calls between FPL to go through... they all go to voice mail.

I mean I get FREEPHONELINE isn't with support but this sounds more and more like a system issue. I think a simple update from Fongo would be nice.

Update at 5:15pm:

I tested my FONGO mobile app, and it seems to be working correctly for incoming and out going calls, so it seems to be isolated to either FREEPHONE LINE or just those of us who use voip key/SIP.

[johnny2000]

Well, we paid for those keys, so they should continue supporting those keys.

[sic698]

KoreyB I had the same problems as you today incoming calls were not working, the calls went straight to VM, outgoing calls worked with no problems, I switched the server to voip2.freephonline.ca and incoming calls started working again.

I'm going to leave it on that server, for now, I will monitor the situation.

[SeanO2000]

wow! changing to voip2 totally worked. Man! thanks!

[marcaccioc]

i changed my proxy to voip2.freephoneline.ca and was able to get incoming calls again.

[Hyrules]

Yeah this does seem to be doing it for me as well. Changed the server to voip2.freephoneline.ca and it's working again. Thanks for the tip.

[johnny2000]

Thanks for the tip it works on voip2 server.

[johnny2000]

I just tested it and yes there is inbound call but no audio.

[Venturess]

Thank you everyone. I did change the server and now Fongo works but still not receiving calls from anyone else.

I don't know what else to do.

[nicolas_dh]

Changing "proxy" does NOT work for me...

Same problem:
- Freephoneline (FPL) not receiving incoming calls SINCE TODAY (~noon)
This was working yesterday, no changes to local setup, but obviously there is a problem
although https://status.fongo.com/ is reporting Voice Services (Home Phone & FPL platforms) "Operational".

Tests with a friend also not receiving FPL incoming calls:

• - OK: PBX to FONGO
  - OK: FPL to PBX
  - OK: FPL to FONGO
  - OK: FPL to FPL
  - FAIL: FONGO to FPL
  - FAIL: PBX to FPL

FPL = Freephoneline
PBX = Outisde FPL or Fongo phone provider...(non Fibernetics...)

Changing proxy to "vopi2.freephoneline.ca" the first time enabled Ringing on incoming calls but, when trying to answer an incoming call,

• - on the FPL side we get "busy" signal... (bip,bip,bip) and
  - on the non-FPL caller end, the caller hears nothing, and eventually chooses to hangup...

After "re-powering" the ATA (Linksys PAP), we can still make outboud calls, but now, incoming calls are not even RINGING.

• - On the receiving FPL side, nothing happens.
  - On the Caller side:
  • - If calling from FONGO, the caller hears several rings but the line eventually self-hangs-up (no voice message).
    - If calling from "outside" (PBX), the caller hears several rings and eventually falls to the FPL voice message box...

Switching to voip or voip2.freephoneline.ca back and forth, doesn't change anything anymore...

It looks like behavior has "changed" in the last hour, maybe someone is trying to solve the issue... speculation

[Venturess]

I guess we'll just have to wait and see if there's an update or if things get back to normal soon....maybe tomorrow.

[Liptonbrisk]

Just took a look at the forums right now. I'm exhausted, and I'm surprised to see this thread. I've been registered all day on voip2.freephoneline.ca

All incoming calls to me from either regular mobility numbers and Fongo Mobile have worked fine.

I even got some scam call that my setup didn't block.

Two way audio works fine.

Outgoing calls work fine.

Someone here works from home at the moment, so if there was a problem on voip2.freephoneline.ca, I would have gotten an earful.

[Liptonbrisk]

configuration, despite the fact that nothing has been changed, i.e. Internet providers or touched any configurations.

While I can't guarantee there wasn't a problem with voip.freephoneline.ca today since I wasn't registered on it, NAT corruption can develop in routers without users doing anything.

[Liptonbrisk]

Guess I'll test voip.freephoneline.ca

[Liptonbrisk]

Guess I'll test voip.freephoneline.ca

Works right now for me. Incoming and outgoing work fine. Fongo Mobile to FPL works fine. Mobility calls to FPL work fine.
But I wasn't registered on that server earlier.
I'll remain registered on it to see if anything happens.

One possible cause is server congestion if the issue was intermittent, but right now should be prime time. People are home and more likely to be making calls than earlier today when people were less likely to be home.

[Liptonbrisk]

1) If anyone is using a Linksys/Cisco ATA, ensure that you've not accidentally enabled Caller ID block on your ATA. Dial *68 to remove caller ID blocking on all outbound calls.
Don't use "Anonymous" for display name in your ATA. Don't use or accidentally dial *67.In your ATA under look for, under Voice-->Line (whichever one you're using for FPL)-->Supplementary Service Subscription-->Supplementary Service Subscription-->Block CID Serv: change to no, and click "submit".



2) Login to your ATA. Specify a high random SIP port in your ATA between 30000 and 60000.
Navigate to Line 1 (or whatever you're using for FPL)-->SIP settings, change SIP Port to a random number between 30000 and 60000.
Do not use the same random SIP port for any other Line. Always choose a different random local SIP port for each Line you're using.

Using a high random SIP port may help to bypass SIP ALG, and it also helps to avoid SIP Scanners (or hackers).
Also, changing local SIP port will reset a potential corrupted NAT association that developed between your router and ATA due to UDP timeouts.

If this step works, you were dealing with a corrupted NAT association that developed between your router and ATA.

3) In the ATA, navigate to Voice-->SIP tab-->NAT Support Parameters, and make sure that the following settings are enabled:

a)Handle VIA received-->yes
b)Handle VIA rport-->yes
c)Substitute VIA Addr-->yes
d) NAT Keep Alive Interval--> 20 seconds

d) click "Save Settings" button

This helps to ensure the RTP audio stream is being sent to your WAN IP as opposed to your LAN IP.

4. Navigate to Voice-->Line (whichever you use for FPL)-->NAT settings
a) NAT Mapping Enable should be yes
b) NAT Keep Alive Enable should be yes
c) NAT Keep Alive Msg should be $NOTIFY

d) click "Save Settings" button if changes were made

5) Log in your ATA, navigate to Voice-->Line-->Proxy and Registration-->Register Expires needs to be 3600 seconds (it probably already is set to 3600)

6) Navigate to Voice-->SIP-->SIP Timer Values (sec)
Reg Retry Intvl should be 120 seconds

Click "Save Settings" button if changes were made

Many older guides for FPL don't include this setting.

7) Proper device reboot order is always modem (wait for it to be fully up before turning on your)-->router (ensure Wi-Fi SSIDs are populated first on your devices)-->ATA (wait for router to be fully up and running before turning on ATA). That's always proper device reboot order.

You might also want to give "voip4.freephonline.ca:6060" (without the quotation marks) a shot. Remember 6060 is the proxy server port--and not the local sip port.


Lastly, ensure, after logging in at https://www.freephoneline.ca/showSipSettings that

i) SIP Status shows "connected", and
ii) SIP User Agent reflects a device that own and recognize. If you don't recognize the SIP User Agent, chances are you've been hacked.

Note that only one registration per FPL account is allowed at any time. When there are multiple devices/softphones using the same account, only the most recent registration is valid. The previous device will lose registration, and, consequently, incoming calls will not work on it. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at https://www.freephoneline.ca/showSipSettings or if you're trying to register your FPL account with a smartphone SIP app or with another device. Registration is required for incoming calls. It is not required for outgoing calls. A more significant concern, though, is that multiple registration attempts can lead to temporary IP bans. The more devices being used can make the temporary ban happen more quickly. Note that each time you reboot or restart your ATA or SIP app, it's attempting to register with Freephoneline again. Multiple registration attempts within a short period can result in temporary IP ban. Each time you reboot your ATA it's attempting to register with FPL's proxy server.

[Liptonbrisk]

Grandstream Users

i) For Primary sip server try "voip4.freephoneline.ca:6060" without the quotation marks.
6060 here has nothing to do with local sip port.

ii) Choose a random number between 30000 and 60000 for the local sip port.

Local SIP port is separate from the primary sip server port.

iii)Use random sip port should be set to yes.



Ensure

iv) Random RTP Port: Yes

v) SIP REGISTER Contact Header Uses is set to WAN address (if the setting is available)

vi) Register Expiration is 60 minutes

vii) SIP Registration Failure Retry Wait Time: 120 seconds

viii) Enable SIP Options Keep Alive: Yes

ix) SIP OPTIONS Keep Alive Interval: 20

x) Proper device reboot order is always modem (wait for it to be fully up before turning on your)-->router (ensure Wi-Fi SSIDs are populated first on your devices)-->ATA (wait for router to be fully up and running before turning on ATA). That's always proper device reboot order.

Lastly, ensure, after logging in at https://www.freephoneline.ca/showSipSettings that

i) SIP Status shows "connected", and
ii) SIP User Agent reflects a device that own and recognize. If you don't recognize the SIP User Agent, chances are you've been hacked.

Note that only one registration per FPL account is allowed at any time. When there are multiple devices/softphones using the same account, only the most recent registration is valid. The previous device will lose registration, and, consequently, incoming calls will not work on it. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at https://www.freephoneline.ca/showSipSettings or if you're trying to register your FPL account with a smartphone SIP app or with another device. Registration is required for incoming calls. It is not required for outgoing calls. A more significant concern, though, is that multiple registration attempts can lead to temporary IP bans. The more devices being used can make the temporary ban happen more quickly. Note that each time you reboot or restart your ATA or SIP app, it's attempting to register with Freephoneline again. Multiple registration attempts within a short period can result in temporary IP ban. Each time you reboot your ATA it's attempting to register with FPL's proxy server.

[Liptonbrisk]

OBi200/202 users should be using http://forum.fongo.com/download/file.php?id=2065

Follow the steps from pages 42 to 44, under the heading,
"Are you getting one way audio issues with an OBi200/202 and Freephoneline? Are incoming calls not ringing? Can you not hear one side of the conversation (you can hear the caller, but the caller can't hear you or vice versa)?"

[Liptonbrisk]

And moments ago, while I've been typing all this stuff and approving posts, an incoming call to me from a cellular mobility number while I'm registered on voip.freephoneline.ca worked fine. I'm not saying it has been working fine (I have no clue since I wasn't using voip.freephoneline.ca until now). Anyway, I'll keep monitoring for the next couple hours, but I might fall asleep. Pretty tired

[SeanO2000]

nearly 190 views and 25 comments on a thread created today. i'd say we werent the only ones with calls going to VM today.

[Liptonbrisk]

nearly 190 views and 25 comments on a thread created today. i'd say we werent the only ones with calls going to VM today.

Unique comments from different users do matter more than views.
I'm not saying there wasn't an issue with voip.freephoneline.ca
I am saying that right now I can't reproduce it.

[koreyb]

I've tried switching the proxy and no luck. To have my parents on a different internet provider/router than I'm on and we both are having the same issue (even at this hour) there is clearly something up on the server end. This is a case I think fongo needs to provide some support as most of us have paid for sip/VoIP keys. This is clearly a major issue based on how many are reporting it. My hope is someone echos it up to the powers to look into this ASAP.

[Liptonbrisk]

I've tried switching the proxy and no luck. To have my parents on a different internet provider/router than I'm on and we both are having the same issue (even at this hour) there is clearly something up on the server end. This is a case I think fongo needs to provide some support as most of us have paid for sip/VoIP keys. This is clearly a major issue based on how many are reporting it. My hope is someone echos it up to the powers to look into this ASAP.

I'm doubtful it would make any difference if I submitted a ticket instead of you doing it.

1) I, myself, now have to submit tickets, which have been, depending on my request, closed without a response: http://forum.fongo.com/viewtopic.php?f= ... 651#p77651.

2) It's late (here) for me to be calling other people I've installed this service for, but based on the fact my parents haven't called me on their cells or emailed me to complain, they aren't having issues either.

3) I sincerely can't reproduce this issue on any of my FPL accounts. I also can't reproduce it using the desktop app. I just tried.

What am I supposed to write? "Hey, this has nothing to do with any of my accounts, and I can't reproduce the issue; but some folks online are having problems."
Sorry if I sound glib, but I'm exhausted.

416xxxxxx 1xxxxxxxxxx 05:08 Sep 03, 2020 10:54:33 PM Sep 03, 2020 10:59:41 PM Normal call clearing $ 0.00

[Liptonbrisk]

2) It's late (here) for me to be calling other people I've installed this service for, but based on the fact my parents haven't called me on their cells or emailed me to complain, they aren't having issues either.

Okay, I called them, and my mom picked up. I configured their ATA (shipped it to them years ago) and router for them. Their service is working. We don't live in the same province. They use a different ISP.

[koreyb]

I have opened tickets but as normal get the response they don't offer support for freephoneline. That said the ticket hasn't been closed yet

You are a volunteer mod... I don't expect you to have all answers but would be nice if the company would have someone comment on the issue. They also should allow you to have a line of communication we don't as a mod.

My parents like myself can make outgoing calls without issue. Infact had no clue incoming was an issue until I called them. I have been able to forward incoming calls to their cell for now. But they just changed to fpl, so it's not exactly a great welcome.

Sadly at this hour, nothing will be done, but surely someone can dig into this Friday.