Hi,
Today I do not know why I am not getting any phone call. I use a phone set instead of the desktop app. Everything used to be working fine until this morning.
I did manage to log in to my account in freephoneline.ca and set up a find me follow up in order to receive the phone calls.
Could someone please have a look what is going wrong, why I am not getting any phone call? My number is: 403444XXXX. Let me know if you need my full number.
Thanks for your help.
Syed
Not receiving any call, please help
-
Bloodsong
- Tried and True
- Posts: 362
- Joined: 09/18/2009
- SIP Device Name: Zoiper| Grandstream GXP2000
- ISP Name: Tek Savvy Internet (DSL)
- Computer OS: CentOS, Arch, Widows 7, AIX, AS/400
- Router: Cisco ASA 5520
- Smartphone Model: Samsung Galaxy Ace Q
- Android Version: 2.3.6
- Location: Simcoe County
Re: Not receiving any call, please help
Syed, I must remind you this is *NOT* an official support channel for Fongo/FPL. It doesn't mean that you won't get help from the admins at Fongo/FPL through here, but it is MUCH faster every time to call into support, keep them on the phone with you while you trouble shoot, and if it's not resolved by the time you're done troubleshooting, have them open a trouble ticket for escalation. If you have a cell-phone or a non-internet based alternative, use that to make the call during troubleshooting as this will allow you to reboot your modem and routing equipment with the troubleshooter on the other end of the phone, rather than risking the need to call in again, and possibly receiving a different operator.
Things to note before you call: Did you have a power-outage last night or a power spike? Did your I.P. change on your modem? (check ipchicken.com occasionally to know what your IP is currently, this will not help you after the fact to find if your IP has changed.) Did the IP on your router or ATA change? Possibly on both?
I always ensure for the purpose of port-forwarding and providing a robust VoIP solution that my ATA has a STATIC IP Address set in it's interface, that way the Ports I forward to it a year ago, are the ones that still point at it today.
If I have a separate modem and router I ensure that my router is handling the PPPoE connection (for DSL) or the DHCP connection (for CABLE) so that there is no need for port and route configuration between the modem and router. Often the modem and router are combined these days, that too is fine, and is essentially the same as having the router handle your internet connection.
I do all of this because black-outs and power-spikes are a fact of modern life. When my network comes back up I want to rest assured that everything I set-up once, is still there later. DHCP is great, but it leaves a lot of room for error and should only be used on guest networks, or networks with a very large number of client computers which can be configured and maintained properly by a knowledgeable administrator.
Things to note before you call: Did you have a power-outage last night or a power spike? Did your I.P. change on your modem? (check ipchicken.com occasionally to know what your IP is currently, this will not help you after the fact to find if your IP has changed.) Did the IP on your router or ATA change? Possibly on both?
I always ensure for the purpose of port-forwarding and providing a robust VoIP solution that my ATA has a STATIC IP Address set in it's interface, that way the Ports I forward to it a year ago, are the ones that still point at it today.
If I have a separate modem and router I ensure that my router is handling the PPPoE connection (for DSL) or the DHCP connection (for CABLE) so that there is no need for port and route configuration between the modem and router. Often the modem and router are combined these days, that too is fine, and is essentially the same as having the router handle your internet connection.
I do all of this because black-outs and power-spikes are a fact of modern life. When my network comes back up I want to rest assured that everything I set-up once, is still there later. DHCP is great, but it leaves a lot of room for error and should only be used on guest networks, or networks with a very large number of client computers which can be configured and maintained properly by a knowledgeable administrator.