Not getting incoming calls

Have a question or problem with your Fongo Home Phone service? This forum is the place to get help from both staff and fellow community members.
Visit The Fongo Home Phone Support Knowledge-base for more.
jester
Just Passing Thru
Posts: 19
Joined: 06/15/2011

Not getting incoming calls

Post by jester »

My phone is not getting any incoming calls. When I call the number with my cell, there is a long pause and then it goes to voicemail. Usually when my internet is down, a call goes directly to voicemail without the pause.

I tried setting my call rings before voicemail to a different number and then back to 5, no effect.

I unplugged my router and my ATA device for one hour. During this time, when I logged into my FPL account, the SIP status said that I was still connected.

I checked the call forward and the DND are not activated.

I am able to make outgoing calls. When I called someone, I tried to call myself using my cell to see if the call waiting would work. It did not work either.

Can anyone offer any help?

Thanks.
jester
Just Passing Thru
Posts: 19
Joined: 06/15/2011

Re: Not getting incoming calls

Post by jester »

The problem seems to have resolved itself. Thanks if you had anything to do with it.
s.ouellette
Just Passing Thru
Posts: 4
Joined: 10/18/2012
ISP Name: TekSavvy (Cable)
Computer OS: Windows 7

Re: Not getting incoming calls

Post by s.ouellette »

I am having the same issue but the problem did not "resolve" itself. What should I be trying? What proxy server should I be using to configure my ATA device? The emails says sip.fongo.com but the online SIP says voip.freephoneline.ca?
Bing Kol
Active Poster
Posts: 117
Joined: 07/23/2010
SIP Device Name: PAP2T
Firmware Version: 5.1.6 (LS)
ISP Name: CarryTel 25/10 DSL
Router: pfSense i5-3470
Location: GTA

Re: Not getting incoming calls

Post by Bing Kol »

s.ouellette wrote:... What proxy server should I be using to configure my ATA device? The emails says sip.fongo.com but the online SIP says voip.freephoneline.ca?
Use one or the other. Both resolve to the same ip address.
dibsmft
*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: Not getting incoming calls

Post by dibsmft »

s.ouellette wrote:I am having the same issue but the problem did not "resolve" itself. What should I be trying? What proxy server should I be using to configure my ATA device? The emails says sip.fongo.com but the online SIP says voip.freephoneline.ca?
The PAP2 seems to present this problem fairly often. You may find that if your run STUN and possibly NAT mapping enable and NAT keep alive may cure the problem. However, check your port forwarding carefully to make sure that it is working as it should.
jester
Just Passing Thru
Posts: 19
Joined: 06/15/2011

Re: Not getting incoming calls

Post by jester »

Problem happened again yesterday. I logged into my FPL account, changed the number of rings before going to voicemail to a different number, clicked on save, and then changed it back to 5, and clicked on save. This resolved the problem immediately. I tested the phone right before I did this and it was not working. Works after doing the action.
colesy
Quiet One
Posts: 37
Joined: 12/11/2012
ISP Name: Bell DSL 2mbps
Computer OS: Windows 7
Router: 2Wire

Re: Not getting incoming calls

Post by colesy »

This happened to me as well and seemed to caused by the system thinking I had a new voice mail when I didn't. jesters last post seemed to work for me. I wonder if there is a way to stop it from going straight to voice mail if there are new messages.
User avatar
bridonca
Technical Support
Posts: 1225
Joined: 11/16/2009
SIP Device Name: Netgear WGR615V
Firmware Version: latest
ISP Name: Eastlink
Computer OS: XP

Re: Not getting incoming calls

Post by bridonca »

The root of the problem is a flaky router, on that does not do a good job of routing incoming packets, of which is the sole purpose of a router. Might look into getting something better than what you have now. Something that is DD-WRT capable is a huge plus.

The PAP2 is one of the most unforgiving ATA devices out there, if there is a port misconfiguration, the PAP2 with do little to nothing to work around the problem.

To permanently fix your problem, your best option is to manually forward RTP ports the PAP2 uses. I think by default, the PAP2 use ports 16384 onward, so get the router to forward those to the pap2.

STUN only works when the ports are properly configured, so it is kind of useless. proxy server settings probably will be of no help in this situation, especailly when the router is too stupid to know where to send the incoming traffic, let alone remember where to send it the next call.