Fongo powers free calling solutions for a number of brands. This forum includes information and tips on all of those offerings. Note that your specific services may vary based on the specific Fongo product that you're using.
Have a question or problem with your Fongo application? This forum is the place to get help from both staff and fellow community members.
Fongo recommends Fongo Home Phone for a fully supported Home Phone system for only $4.95/mo
I've been having this issue since I switched to Fongo in February. I've reported this to Tech Support who, instead of doing anything, asked me to wait for 48 hrs during which it would be resolved. I also posted the problem in the Configuration Setting section of this forum in which "dibsmft" suggested me to use STUN server which didn't change anything. I thank dibsmft for his effort to help me out which I couldn't get from the tech support agent. I'm explaining again the problem & uploading the ATA setting for my SPA2102 in the hope that some tech support person will be able to help me.
I've been using voip phone for more than 3 yrs with the same SPA2102 ATA with another provider & never had any issues. Now, the phone doesn't ring for some of the incoming calls randomly & the call log in my DellVoice online account shows "No answer from user". The caller can hear the phone ring but it actually doesn't ring. After a preset number of rings, the caller is forwarded to voice mail. My internet connection is Fibe16 from Bell which works seamlessly & the ATA is connected to the the router. I would appreciate it very much if someone could take a look into the configuration file pics that I've uploaded & suggest a solution for that. I've given up on Fongo tech support over the phone
You do not have the required permissions to view the files attached to this post.
To be fair to Fongo, I think they make it clear that it isn't their role to give support for 3rd party equipment. That being said, I hope someone can find a solution for you.
Do you know if your ATA looses registration at any point? Does the ATA show as registered when the people are saying that they call but your phones don't ring?
I wondered how you had got on with the changes that you were making.
First thing to know is that when you call someone with modern ATA/phone you don't actually hear the phone ringing. The ringing tone is generated locally based on the progress of the call. You may hear 5 rings in your phone but that does not mean that the phone on the other end has made 5 rings, 2 rings or possibly any rings. Sometimes you may not hear any rings before the phone rings at the other end and the called person picks up (when I call relatives in the UK this seems to happen sometimes).
Looking at your configuration I see that you are not running STUN now try running it again as this time also activate under "NAT Settings"
NAT Mapping Enable yes and NAT Mapping keep alive yes
I have the same issue with bell / 2wire and pap2t ata. I ve also tried many diffrent things with absolouly mo effect (including enabling the NAT Keep alive, putting ata in DMZ etc). The only work around I found is to change the proxy port daily. When i do this the phone rings fine for a day or so then stops ringing on incoming calls until i change the port again. Outgoing calls always work fine. I am suspecting the 2 wire router somehow forgets my port forwarding after a while (i've forwarded udp ports 5060 to 6062) to the ata. Any help is much appreciated.
Thanks guys! I have made changes to my ATA as per the link jimbo posted & set NAT Mapping to Yes as dibsmft said. I'll test it for a couple of days to see how it works & will report back. Thanks again!
I've got a few ideas, but I can't see what the link above has you trying as I'm at work and for some reason Websense believes this site to be sexual oriented???
STRANGE.
Anyway, before anyone tries to tell me how to get around Websense, 1) I'm in a secure facility. 2) I'm a network security specialist and I've tried all of the innocuous stay out of trouble methods of avoiding it, my network admin, at least when it comes to locking down the internet, knows his $&(% and let's leave it at that.
I will say in regards to Macmak's mentioned about a 2wire issue. Check for firmware upgrades, I used to run a phone server from behind a junky bell 2wire, using a mikrotik router to handle QOS on the internal network as more than just VoIP was on it. We had 40 remote lines and 11 internal with no issues.
Good to find this thread - so I am not the only one with this problem). The phone randomly doesn't ring with incoming calls. My ISP is Telus (modem router: Actiontec V1000H, the ports are forwarded), the ATA has been purchased from Freephoneline with built-in settings.
This issue has been active since April 22nd, if I go by FPL logs.
It's happening in TWO different locations, different branded routers.
All incoming calls are not coming through, but going to voicemail straight.
Sometimes there is a blip (ie the light flashes ) as if there was a call, but when you pick up it's not there, but the caller ID may show up.
FPL has not returned email to support via the form that was filled out.
At this point I believe the issue is at fongo/fpl's end -- since the exact same configuration worked fine until now at both locations. Perhaps signing on all these dell voip has screwed up their incoming system somehow, or they have introduced a config change affecting certain configs.
I had the same issue in the past and thought it has been fixed by setting the router config to "All day - 24h" in addition to "All week". The problem was apparently resolved but reappeared 1 week later. I then connected the ATA to an ethernet switch and it's working fine since the last 4 days.
I will keep checking this recurrent issue in the next few days and will report any issues.
This problem is NOT on Fongo's end, I promise you that. Let me stress this again, THIS PROBLEM IS NOT ON FONGO'S END!
Let's get to the meat of the problem, you got crap for a router! And combination DSL routers can be the worst pile of junk you can get. It does not help that you have a SPA2102, one of the more problematic ATA devices when not configured properly! You got duff gear. Own up to it!
I shutter to think how awful your router is when it comes to forwarding ports, but if the router is half way competent, you should be able to forward RTP ports 16384 to 16482 from the router to the SPA2102 ATA device. Your incoming call issue should disappear because your Fongo calls will be now be hard routed to where the calls are supposed to go, instead of relying on that crap fest you have for a router.
Now if your router is a real piece of work, it will also have a feature called SIP ALG. It has potential of hijacking port 5060, and routing it to the internal ATA, which likely does not exist on your model of router. Half baked router firmware at work!
There is a fix for that. Use a port other than 5060, like 5062. You have to set 5062 on the ATA, and for good measure, forward 5062 from the router to the ATA device.
Now lets discuss STUN. It is unbelievably useless! If you do not have a proper route forwarded, STUN will not help.
What is good gear? Any router that can be flashed with DD WRT or other open source firmware is a good router. Stable, tested firmware makes life easier. As for an ATA, I prefer Grandstream products because they tend to be more resistant to crappy NAT devices. Saying that, I have found few ATA devices that did not work if hooked up to a good router.
And for a 3rd time, FLAKY INCOMING CALL ISSUES ARE NOT THE FAULT OF FONGO, IT IS YOUR CRAPPY ROUTER THAT IS TO BLAME!
wow there.. that was a serious blamefest over very little info provided from my side.
the two routers are two different brands, and have been working fine with fongo/fpl for over a year without hiccups ( aside from the bandwidth issue, reducing to g729 by force fixes echos/distortions )
anyway, i apologise for jumping to conclusions, but it appears the resolution was very very wierd.
i had to hardware reset+reflash one of the ATAs with the latest firmware ( which it was already running ) and start from scratch.
deleting just the config and redoing them didn't help. tried reconfiguring for freaking two weeks, trying everything in the book in the options.
flashing somehow fixed all this. no idea how i could have figured this out if i hadn't just said eff it and hard reset.
so moral of the story is even when you think you've looked at all possibilities, you still haven't.
