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
iftecanada wrote:Hi,
I am using CISCO SPA122. My Dial Plan: (911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
I am totally unable to make any outbound call. 30 sec after dialing I hear busy tone. All inbound calls are ok.
Hi there,
On your ATA config, please check caller ID name (display name) field.
Please make sure your device is configured as per the official guide, including my post below the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16294
Also, since your profile states you are using Rogers, please use the Rogers proxy: voip4.freephoneline.ca:6060. You may also need to change your SIP Port to a random number between 20000 and 65535. Let us know how things go.
Please try to change your PAP2's SIP Port to a random number between 20000 and 65535. Save, and test.
If that does not work, try to change your PAP2's Proxy from voip.freephoneline.ca to voip2.freephoneline.ca, or vice-versa. Save, and test.
If one of those works, let us know which one. Two workarounds, two different causes. If neither of these solves the problem, we will troubleshoot further.
Have had FPL for a few months now using the Grandstream HT701 ATA -- no problems whatsoever. Since yesterday, incoming caller IDs no longer appear on our Uniden cordless phones. Any suggestions? Let me know if I can provide any further details, too.
Have had FPL for a few months now using the Grandstream HT701 ATA -- no problems whatsoever. Since yesterday, incoming caller IDs no longer appear on our Uniden cordless phones. Any suggestions? Let me know if I can provide any further details, too.
Thanks!
I swore I posted this as a standalone thread? In any case, I just tried a test call from my cell to my FPL and my cell ID came up on my cordless. Not sure how this got fixed, but glad it is.
Please try to change your SPA's SIP Port to a random number between 20000 and 65535. Save, and test.
If that does not work, try to change your SPA's Proxy from voip.freephoneline.ca to voip2.freephoneline.ca, or vice-versa. Save, and test.
If one of those works, let us know which one. Two workarounds, two different causes. If neither of these solves the problem, we will troubleshoot further.
I'm glad to hear things are working. Next time, you can change your SPA's SIP Port if that is more convenient than a hard reset. That should achieve the same result.
These symptoms indicate a corrupted NAT connection in your router. If the problem returns, you can increase your SPA's Reg Retry Intvl to allow the corrupted connection to time out before the SPA attempts to re-register after a failed registration. Unfortunately, the correct interval to use may be a guessing game unless your router's UDP timeouts are in its manual - most aren't. As a first guess - perhaps you would like to try 600.
Just today I signed up, and installed the software in Windows.
I had not given anyone the number,
But already a few times, I heard a strange sound, like someone talking.
Just click on the answering machine, and then it stops.
What's this?
Hi, I'm not sure if there's an actual problem or not but after I upgraded to Android 5.0 on my Oneplus One phone the Fongo icon has been stuck on the green colour and says it's connecting to Fongo. It no longer turns white. The catch is, the service appears to be working fine. I can make and receive calls so I'm not sure if it's the app that has some compatibility issues with Android 5.0 or if it's the new version of Android for this particular phone that's the problem.
I've tried uninstalling and reinstalling the app and it's the same thing.
Hi, I'm not sure if there's an actual problem or not but after I upgraded to Android 5.0 on my Oneplus One phone the Fongo icon has been stuck on the green colour and says it's connecting to Fongo. It no longer turns white. The catch is, the service appears to be working fine. I can make and receive calls so I'm not sure if it's the app that has some compatibility issues with Android 5.0 or if it's the new version of Android for this particular phone that's the problem.
I've tried uninstalling and reinstalling the app and it's the same thing.
lobotiger wrote:Hi, I'm not sure if there's an actual problem or not but after I upgraded to Android 5.0 on my Oneplus One phone the Fongo icon has been stuck on the green colour and says it's connecting to Fongo. It no longer turns white. The catch is, the service appears to be working fine. I can make and receive calls so I'm not sure if it's the app that has some compatibility issues with Android 5.0 or if it's the new version of Android for this particular phone that's the problem.
I've tried uninstalling and reinstalling the app and it's the same thing.
Any tips would be appreciated.
LoboTiger
Hi,
I suggest to uninstall the Fongo app and then reboot device.
Once the device boots up again, visit Google play and download and install the latest version of the Fongo app that has all the fixes for OS 5.1
I just realized I'm not receiving calls on FPL. I have a Grandstream Ht701 with latest firmware and configured exactly like the PDF guide in these forums.
I read earlier posts from Mango who said to switch to the voip2 server for troubleshooting. I did so and my dialtone came back when I picked up.
Should I leave voip2 as my main server or switch back? Any other settings I should verify on the HT701? (Registration timeout, for example? Though my FPL account shows 3600).
It could have been a corrupted NAT connection on your router. If it happens again, first try to reboot your ATA to see if re-registering will solve the problem. If the ATA is still unable to register, try to change your Local SIP Port to a random number between 20000 and 65535. If that works, it confirms my guess that the router caused the problem.
A user on this forum had this problem a few days ago and discovered that assigning a static IP to his ATA was an effective workaround.
I am using my FPL account at pbxes.com, but recently, it doesn't work for receiving calls. It goes to the voicemail directly. I tried to register to sipsorcery.com, and can not receive calls either. It works on my PAP2 and eyeBeam software.
I tried voip.freephoneline.ca and voip2.freephoneline.ca.
I am using an FPL account registered at pbxes.com, but recently, I can not receive any calls. They go to the voicemail directly. I tried sipsorcery.com, and the situation is the same. The proxy servers I tried are voip.freephoneline.ca and voip2.freephoneline.ca, and the Register Expire is 3600. Anybody meets the same problem?
Pbxes should email you the message that your provider is out of line for more than 10 minutes. In this case because you are the free pbxes account holder you have to login to your pbxes.org again and make any change and click on the red top line and your account goes back on line.
Read the messages from Pbxes.org they giving you all the instructions what to do.
Hi I am trying to set up my obi200 ATA to work with FPL but it is not working. I can't receive calls. They go straight to voicemail.The status is listed as "Register Failed: No Response From Server" on OBi Dashboard. However, outgoing calls are working fine.
My phone number was ported from Primus to FPL on May 12. I am currently using Obi Talk's default configuration for FPL. I tried using the OBi 100 Setup Guide from this forum but had an identical result except on outgoing calls I received an 484 error message.
I have a similar problem with incoming. Outgoing is totally dysfonctionnal--after entering the first three digits, the phone goes busy. I'm also on an obi200. Any help would be really helpful.
Your outbound call problem is probably due to a misconfigured PHONE Port OutboundCallRoute. Be sure your device is configured as per the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16090
