Incoming calls not working
-
- One Hit Wonder
- Posts: 1
- Joined: 07/30/2012
- SIP Device Name: Grandstream
- ISP Name: Videotron Cable
- Computer OS: Windows XP
- Router: Dir-615
Incoming calls not working
Hi,
Im a new Fongo home phone customer and ive been having problems with incoming calls. About every second call goes directly to my voice mail instead of ringing.
My router is a dir 615 and im using the grandstream ATA provided by fongo. Ive tried opening the ports ( 5060-6061, 10000-20000) on my router but it doesnt seem to be working. Ive called D-LINK and the said those ports could not be open because they were being used by someone else. Im quite confused.
If anybody can help it would be very much appreciated.
Im a new Fongo home phone customer and ive been having problems with incoming calls. About every second call goes directly to my voice mail instead of ringing.
My router is a dir 615 and im using the grandstream ATA provided by fongo. Ive tried opening the ports ( 5060-6061, 10000-20000) on my router but it doesnt seem to be working. Ive called D-LINK and the said those ports could not be open because they were being used by someone else. Im quite confused.
If anybody can help it would be very much appreciated.
-
- ***Übergod***
- Posts: 1632
- Joined: 08/13/2011
- SIP Device Name: FPL PC softphone (buggy)
- Firmware Version: 3.0.3.0
- ISP Name: Telus Optik
- Computer OS: Win7
- Router: Actiontec V1000H
- Smartphone Model: none
- Location: Surrey, BC
Re: Incoming calls not working
We have a discussion going about the Dlink DIR-615 in another thread ... check your firmware, disable ALG once you have updated, and if possible, see if you can flash the DD-WRT patch ...G_Loz wrote:Hi,
Im a new Fongo home phone customer and ive been having problems with incoming calls. About every second call goes directly to my voice mail instead of ringing.
My router is a dir 615 and im using the grandstream ATA provided by fongo. Ive tried opening the ports ( 5060-6061, 10000-20000) on my router but it doesnt seem to be working. Ive called D-LINK and the said those ports could not be open because they were being used by someone else. Im quite confused.
If anybody can help it would be very much appreciated.
one or both of these may help!
Try reading this link: http://forums.dlink.com/index.php?topic=13599.0
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
-
- Active Poster
- Posts: 77
- Joined: 07/28/2012
- SIP Device Name: GrandStream ATA
- Firmware Version: Fongo shipped
- ISP Name: 295.ca
- Computer OS: WIN 7
- Router: NETGEAR DB WNDR4000
- Smartphone Model: Nexus4
- Android Version: 4.3
Re: Incoming calls not working
I am also a new user - 6 days!
After I connected the ATA to my router everything worked instantly as promised by Fongo. No fooling around with router settings - nothing. I was a happy customer!
This morning I decied to try the system again and guess what! Incoming calls from, my Bell phone did not go through. When I called my Fongo home number from my cell, I get recording that "the number you have called is not in service". Really? Than how come my outgoing calls to my Bell line and my cell both work fine?
Tried to reset the system by powering off my setup and back on but no luck so far. When the system comes back to life so is the problem.
Environment:
I use the Grandstream ATA shipped to me by Fongo folks and a TP-Link G Router, running Windows & OS.
Now I am not happy !
My hunch is that others must have had this problem before? Any comments? Suggestions?
After I connected the ATA to my router everything worked instantly as promised by Fongo. No fooling around with router settings - nothing. I was a happy customer!

This morning I decied to try the system again and guess what! Incoming calls from, my Bell phone did not go through. When I called my Fongo home number from my cell, I get recording that "the number you have called is not in service". Really? Than how come my outgoing calls to my Bell line and my cell both work fine?
Tried to reset the system by powering off my setup and back on but no luck so far. When the system comes back to life so is the problem.
Environment:
I use the Grandstream ATA shipped to me by Fongo folks and a TP-Link G Router, running Windows & OS.
Now I am not happy !

My hunch is that others must have had this problem before? Any comments? Suggestions?
-
- Active Poster
- Posts: 118
- Joined: 06/22/2010
- SIP Device Name: Cisco PAP2T
- Firmware Version: 5.1.6
- ISP Name: Fibrestream
- Router: D-Link DIR-601 N 150
Re: Incoming calls not working
I'm having issues with incoming calls as well. I get no rings, everything goes straight to voicemail. My ata doesn't even ring, so forwarding a cell # to fpl at home is useless right now.
Is there a network issue? Or does this stuff just break on me without any real reason?
Is there a network issue? Or does this stuff just break on me without any real reason?
-
- *Go-To Guy*
- Posts: 651
- Joined: 05/11/2011
- SIP Device Name: Yealink T22 (SPA3102 GS286)
- Firmware Version: 7.60.0.110
- ISP Name: Bell-Aliant DSL
- Computer OS: Linux Mint
- Router: Speedstream 6520
- Smartphone Model: Google Nexus 5
- Android Version: 3.2.1
- Location: St. John's NL
Re: Incoming calls not working
Some people get this problem but guessing how to help you is difficult as you have given no information about your set up other than you have an ATA. You need to tell us your service provider and type of service, your modem, your router and your ATA and which of the Fongo phone services that you are using as well as any other information that you may think useful.pete_fpl wrote:I'm having issues with incoming calls as well. I get no rings, everything goes straight to voicemail. My ata doesn't even ring, so forwarding a cell # to fpl at home is useless right now.
Is there a network issue? Or does this stuff just break on me without any real reason?
-
- Just Passing Thru
- Posts: 2
- Joined: 07/26/2012
- SIP Device Name: Cisci SPA122
- ISP Name: Cable
- Router: TP-LINK
Re: Incoming calls not working
Just lost all incoming calls too. Everything goes into voicemail.
I have an SPA122 (router/ATAx2lines) and a freephoneline.ca number (hereinafter FONGO 1). This setup worked all right for a couple weeks, so today I got brave (my wife would say careless+greedy) enough to port my Bell home number to FONGO. Wanted to keep FONGO 1 number too (I got a 2 line ATA after all). Customer service told me I should register FONGO 2 account because FONGO 1 will be assigned the Bell number they are porting for me and then call back to port FONGO 1 to FONGO 2. Again: FONGO 1 will get Bell No., and FONGO 2 will get the FONGO 1 number. OK, I go and register another account, get a better number than I already have and decide that I may not need to keep FONGO 1 after all. Next, I tried FONGO 2 for calling/setting up voicemail on PC. As soon as I logged in the app as FONGO 2 and tried to call my FONGO 1 line, all the incoming calls on the ATA (FONGO 1) got lost. What the ...?!
1 more symptom - I get 8 short beeps before I get the dial tone for the outgoing calls.
I have an SPA122 (router/ATAx2lines) and a freephoneline.ca number (hereinafter FONGO 1). This setup worked all right for a couple weeks, so today I got brave (my wife would say careless+greedy) enough to port my Bell home number to FONGO. Wanted to keep FONGO 1 number too (I got a 2 line ATA after all). Customer service told me I should register FONGO 2 account because FONGO 1 will be assigned the Bell number they are porting for me and then call back to port FONGO 1 to FONGO 2. Again: FONGO 1 will get Bell No., and FONGO 2 will get the FONGO 1 number. OK, I go and register another account, get a better number than I already have and decide that I may not need to keep FONGO 1 after all. Next, I tried FONGO 2 for calling/setting up voicemail on PC. As soon as I logged in the app as FONGO 2 and tried to call my FONGO 1 line, all the incoming calls on the ATA (FONGO 1) got lost. What the ...?!
1 more symptom - I get 8 short beeps before I get the dial tone for the outgoing calls.
-
- Active Poster
- Posts: 77
- Joined: 07/28/2012
- SIP Device Name: GrandStream ATA
- Firmware Version: Fongo shipped
- ISP Name: 295.ca
- Computer OS: WIN 7
- Router: NETGEAR DB WNDR4000
- Smartphone Model: Nexus4
- Android Version: 4.3
Re: Incoming calls not working
After reading your note and many others I think FONGO is still having growing pains. I suggest step back a bit, get one thing working and once you are happy request the next change.
As for your wife -
- ditto here. I still have my Bell number any will keep it for until I am happy. Just ordered UPS from Amazon to avoid problems with power outages.
As for your wife -

-
- 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: Incoming calls not working
I want to wrap customer support over the fingers with a very sturdy ruler for this.
So you PAID for them to port Bell to Fongo 1, and I imagine you PAID once more, for Fongo 1 to Fongo 2?
But what is the point in the extra transfer?
Sign-up a secondary Fongo account (Fongo 2), port Bell to Fongo 2, thus you will not have any service interuptions on Fongo 1 line, and when the port is complete Fongo 2 line will take over the Bell number relatively seamlessly.
Next the trouble with calling your own Fongo line 1 from line 2 is more about the structure of the internet, and has many possible points of failure. It is unlikely to have any effect when calling to numbers outside of the house, or with proper network management, even to numbers handled by other devices within the house that have their own static IP and routes (Caveat: some providers do not allow for a direct connection back into the same IP it came out of which could break a potential call from line 1 to line 2 at either the SIP or the RTP stages of the call)
In any event, ensure the ATA has a static IP, Portforwarding for both lines etc.
I'm not certain as to the beeps, Voice Mail waiting?
So you PAID for them to port Bell to Fongo 1, and I imagine you PAID once more, for Fongo 1 to Fongo 2?
But what is the point in the extra transfer?
Sign-up a secondary Fongo account (Fongo 2), port Bell to Fongo 2, thus you will not have any service interuptions on Fongo 1 line, and when the port is complete Fongo 2 line will take over the Bell number relatively seamlessly.
Next the trouble with calling your own Fongo line 1 from line 2 is more about the structure of the internet, and has many possible points of failure. It is unlikely to have any effect when calling to numbers outside of the house, or with proper network management, even to numbers handled by other devices within the house that have their own static IP and routes (Caveat: some providers do not allow for a direct connection back into the same IP it came out of which could break a potential call from line 1 to line 2 at either the SIP or the RTP stages of the call)
In any event, ensure the ATA has a static IP, Portforwarding for both lines etc.
I'm not certain as to the beeps, Voice Mail waiting?
-
- *Go-To Guy*
- Posts: 651
- Joined: 05/11/2011
- SIP Device Name: Yealink T22 (SPA3102 GS286)
- Firmware Version: 7.60.0.110
- ISP Name: Bell-Aliant DSL
- Computer OS: Linux Mint
- Router: Speedstream 6520
- Smartphone Model: Google Nexus 5
- Android Version: 3.2.1
- Location: St. John's NL
Re: Incoming calls not working
Well, if you wish to call one line from the other on the same network then you have to be pretty careful with configuration and the SPA122 can be pretty fussy. This is what I would do........dyp wrote:Just lost all incoming calls too. Everything goes into voicemail.
I have an SPA122 (router/ATAx2lines) and a freephoneline.ca number (hereinafter FONGO 1). This setup worked all right for a couple weeks, so today I got brave (my wife would say careless+greedy) enough to port my Bell home number to FONGO. Wanted to keep FONGO 1 number too (I got a 2 line ATA after all). Customer service told me I should register FONGO 2 account because FONGO 1 will be assigned the Bell number they are porting for me and then call back to port FONGO 1 to FONGO 2. Again: FONGO 1 will get Bell No., and FONGO 2 will get the FONGO 1 number. OK, I go and register another account, get a better number than I already have and decide that I may not need to keep FONGO 1 after all. Next, I tried FONGO 2 for calling/setting up voicemail on PC. As soon as I logged in the app as FONGO 2 and tried to call my FONGO 1 line, all the incoming calls on the ATA (FONGO 1) got lost. What the ...?!
1 more symptom - I get 8 short beeps before I get the dial tone for the outgoing calls.
assuming the username and passwords are already in the ATA.
ATA only..
1. Set the router to give the ATA a fixed IP and set the ATA with the IP as static IP. How exactly to do this depends on your router.
2. Forward ports 5061 UDP line 1 and 5062 UDP line 2 from the router to the ATA
3. Forward ports 8000 - 8030 UDP from the router to the ATA
4. Configure the router to use 5061 UDP line 1 and 5062 UDP line 2 for internal SIP and 5060 for external. Set the ATA to use 8000 - 8030 UDP as the RTP port range.
Depending on the model of your router and the behaviour of the ATA that may be enough.
Test it and find out

If you want to use a PC on the same network it should be able to manage its ports if you are using Win7.
-
- 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: Incoming calls not working
+1 (Side note: RTP selections are essentially arbitrary, as long as they match in router and ata)dibsmft wrote:Well, if you wish to call one line from the other on the same network then you have to be pretty careful with configuration and the SPA122 can be pretty fussy. This is what I would do........dyp wrote:Just lost all incoming calls too. Everything goes into voicemail.
I have an SPA122 (router/ATAx2lines) and a freephoneline.ca number (hereinafter FONGO 1). This setup worked all right for a couple weeks, so today I got brave (my wife would say careless+greedy) enough to port my Bell home number to FONGO. Wanted to keep FONGO 1 number too (I got a 2 line ATA after all). Customer service told me I should register FONGO 2 account because FONGO 1 will be assigned the Bell number they are porting for me and then call back to port FONGO 1 to FONGO 2. Again: FONGO 1 will get Bell No., and FONGO 2 will get the FONGO 1 number. OK, I go and register another account, get a better number than I already have and decide that I may not need to keep FONGO 1 after all. Next, I tried FONGO 2 for calling/setting up voicemail on PC. As soon as I logged in the app as FONGO 2 and tried to call my FONGO 1 line, all the incoming calls on the ATA (FONGO 1) got lost. What the ...?!
1 more symptom - I get 8 short beeps before I get the dial tone for the outgoing calls.
assuming the username and passwords are already in the ATA.
ATA only..
1. Set the router to give the ATA a fixed IP and set the ATA with the IP as static IP. How exactly to do this depends on your router.
2. Forward ports 5061 UDP line 1 and 5062 UDP line 2 from the router to the ATA
3. Forward ports 8000 - 8030 UDP from the router to the ATA
4. Configure the router to use 5061 UDP line 1 and 5062 UDP line 2 for internal SIP and 5060 for external. Set the ATA to use 8000 - 8030 UDP as the RTP port range.
Depending on the model of your router and the behaviour of the ATA that may be enough.
Test it and find out. If it works then OK as it is always best to keep things a simple as possible but if not there may be more to do. Of course, if you have already done all this then there is not much point in doing it again.
If you want to use a PC on the same network it should be able to manage its ports if you are using Win7.
-
- Just Passing Thru
- Posts: 2
- Joined: 07/26/2012
- SIP Device Name: Cisci SPA122
- ISP Name: Cable
- Router: TP-LINK
Re: Incoming calls not working
Thanks everyone! I appreciate the advice and will keep it for the next failure inevitably looming ahead. In the meantime after a couple reboots during 2 hours spent on the phone with my sysadmin buddy, who explained why IP being dynamic should not be the culprit (and a few other things I didn't need to know as a consumer), a few curses, prayers and some ritual dancing with cables, everything went back to normal by itself. As for the sequence of steps with opening accounts and porting, it's easy to be smart in hindsight once you've "stepped on the rake" and learned there were limitations on system design that make no sense from consumer's point of view, e.g. requirement to set up two separate accounts with two different email addresses even though you're just one person with the same billing address etc. Remember the Hispanic lady on the phone helping you navigate through the setup?
Thanks again, community support makes miracles.
Thanks again, community support makes miracles.
