Why is it that Fongo has no router setup tips?

[M_Stewart]

I don't understand why Fongo doesn't supply standard setup guides for common routers from Rogers, Bell, Shaw etc. 80% of users have these common devices. I spent two weeks getting this home phone to receive calls for more than a few hours. I suspected that it was the router. Searching for advice on the forum was really just a wild goose chase. Some good ideas and a lot of irrelevant stuff. All provided with good intentions.The Cisco DPC3825 was not as simple to setup as it appeared initially. Settings were changing/missing after being entered. It is fixed now.

Fongo is dropping the ball by letting it's customer forum provide the support . Every Roger/Shaw customer will have these routers to setup. It would benefit Fongo and customers to have some standard router setup guides. I was very close to going elsewhere for VOIP.

FWIW, I did call support and they let me know what ports to forward. After that I felt that I was on my own.

[FONGO_steve]

I'll have to see if we can get a community supported route config section in the forum along side the community supported third party device configurations!


http://forum.fongo.com/viewforum.php?f=15

[Bloodsong]

The short answer is that there are literally HUNDREDS of different routers in use, and that each home network may be configured slightly differently. It is far easier to reference material already in existence than it is to maintain a library of our own router configurations. To this end most router configuration for VoIP is primarily focused on the Port Forward aspect of the set-up, for which people are most often referred to http://portforward.com

And while you may consider that Bell/Rogers/Shaw/Cogeco/TekSavvy etc. all supply people with specific hardware in various configurations, that these providers are technically in DIRECT competition with FPL, as FPL is also a DSL broad-band internet provider with unlimited bandwidth packages.

Though I would point out that as people often see me do, additional set-up about the ATA and Router with a static IP address on the internal network would be a good idea, you can't expect a company to support it's competitor's equipment.

Realize also, even with Rogers/Shaw or Bell (Cisco DPC or 2wire modem/router combos) you tend to be on your own for support, if you call your provider for router/routing support they will tell you to call the hardware vendor more often than not. This is compounded by the fact that most of their policies are still written from the days when a modem was a modem and a router was a router. (Which is still how I run my networks if I can.) And generally results from the variety of equipment and possible configurations of a network that simply cannot be seen from a remote location. Though most onsite techs will be more helpful esp. where Rogers is concerned.

I myself am a Rogers Cable internet customer, and they recently forced me to "upgrade" to a Cisco 2-in-1 modem/router. Truth is the Motorolla Surfboard does support DOCSIS 3 and Rogers is flat-out lying to it's customers. My Cisco modem now runs in Bridge mode acting as a modem only, and my router, on DD-WRT, handles my network.

[M_Stewart]

If Fongo is to become more mainstream over time, easy setup is essential.

I do realize that there are many routers out there for those who take an interest. I am one of those people.

When I look at my neighbours and relatives, they are not advanced users of computers/networking. Almost all are using Bell routers from 2-wire or Rogers with Cisco. How can I recommend Fongo to them unless the setup is very straightforward? I am just posting this to provide feedback to support.

Easy setup = more customers.

[ret]

The short answer is that there are literally HUNDREDS of different routers in use, and that each home network may be configured slightly differently. It is far easier to reference material already in existence than it is to maintain a library of our own router configurations. To this end most router configuration for VoIP is primarily focused on the Port Forward aspect of the set-up, for which people are most often referred to http://portforward.com

And while you may consider that Bell/Rogers/Shaw/Cogeco/TekSavvy etc. all supply people with specific hardware in various configurations, that these providers are technically in DIRECT competition with FPL, as FPL is also a DSL broad-band internet provider with unlimited bandwidth packages.

Though I would point out that as people often see me do, additional set-up about the ATA and Router with a static IP address on the internal network would be a good idea, you can't expect a company to support it's competitor's equipment.

Realize also, even with Rogers/Shaw or Bell (Cisco DPC or 2wire modem/router combos) you tend to be on your own for support, if you call your provider for router/routing support they will tell you to call the hardware vendor more often than not. This is compounded by the fact that most of their policies are still written from the days when a modem was a modem and a router was a router. (Which is still how I run my networks if I can.) And generally results from the variety of equipment and possible configurations of a network that simply cannot be seen from a remote location. Though most onsite techs will be more helpful esp. where Rogers is concerned.

I myself am a Rogers Cable internet customer, and they recently forced me to "upgrade" to a Cisco 2-in-1 modem/router. Truth is the Motorolla Surfboard does support DOCSIS 3 and Rogers is flat-out lying to it's customers. My Cisco modem now runs in Bridge mode acting as a modem only, and my router, on DD-WRT, handles my network.

I had the 2-in-1 Rogers modem and I couldn't get FPL to work for 4 weeks. I could call out but no incoming calls would ring, just go straight to voice mail. I tried everything(router config & SIP settings). I ended up buying a Asus RT-NI6, upgraded the firmware to dd-wrt and had no issues. Since then I also switched to Teksavvy which I am very happy with.

[MikeV]

I am on Rogers Cable with Cisco DPC3825 2-in-1 modem/router.
I currently have VoIP phone from Acanac with SPA2102 ATA phone adapter, and it works just fine.
I wanted to switch to Freephoneline and tried to setup the same ATA device for freephoneline and I got the same issue people complain about here - I can call, they can hear me, but I don't hear them ! I can't make this configuration (Cisco DPC3825 2-in-1 modem/router + SPA2102 ATA) work for freephoneline - tried everything, opening the suggested ports, assigning static IP to ATA adapter and setting it as DMZ - nothing helps. No additional setup was needed in the router for Acanac VoIP - Acanac simply worked with the same setup. So it seems it is really something besides opening the ports and freehoneline tech support needs to look at this !

As additional info, I also set up Freephoneline ATA for my mother - she had separate cable modem and router devices. What I noticed, if I connect router to cable modem and SPA2102 ATA to the router, I get the same issue - only hear one way, no matter what I do in the router - opening the ports, setting DMZ, etc. However if I connect SPA2102 directly to cable modem, then it works just fine. The problem is, I still need my router for WiFi spot and other network devices like IPTV box, so I have to connect router to SPA2102 to get everything working together, but the SPA2102 in this configuration significantly downgrades the network bandwidth (from 30Mbps to ~7 Mbps), which is not acceptable either.

So it looks like this "one way hearing" problem is generic for network configuration when ATA adapter is connected behind the router, and this seems specific to Freephoneline as other VoIP providers (like Acanac in my case) don't have this issue in the same configuration.

[bridonca]

This is a hard one to explain through because you have such a mess for a setup. Right now, you are behind a double NAT. Your ATA has to go through 2 routers, the modem which acts as a horrible router, and the router, which might or might be awful, and the packets have to be routed through both, and hopefully get to it's destination, the ATA. The problem is, if the firmware is not up to scratch, or something is misconfigured, your ATA, which BTW has firmware as old at 2006, will do nothing to help you.

Almost universally, "smart" modems have awful routers. You do not want to navigate packets through a double NAT. Best you can do is put the modem in bridge mode so as to disable the router feature.

Then there is your router. Many, even new router, are still poor at routing packets. Some firmware is so bad they will not even accept forwarded ports, even though you punch them in. Because of how cheap some new good routers are, sometimes landfill is the best option for the old router. If you have the ability to flash the router with a 3rd party firmware like DD-WRT. please do so. DD-WRT is an extremely stable, sane firmware, I strongly recommend. You next router should have the ability to flash to DD-WRT. So you have options if the default firmware is not up to snuff.

I have to remind you, Freephoneline, or any SIP VOIP, provider has no control as to where to route the packets as soon as they get to your modem. the ATA sends a request, tell freephoneline what RTP ports it wants, and freephoneline send the info on those ports. It is up to the router to decide where to send the ports. Some VOIP providers do use some non standard tricks, and I believe freephoneline have servers that do that also. But the problem is, they are not a permanent solution, and eventually you will get one way audio until you reset devices.

Here is my solution, get that modem into bridge mode. Do not use any of the ethernet ports except the one connected to the router. That gets rid of the double NAT. Next, with your ATA connected to your router, forward some RTP ports to the ATA. I believe the 16384-16482 are the default of what your ATA uses. Hope that works.

[Fongo Support]

I am on Rogers Cable with Cisco DPC3825 2-in-1 modem/router.
I currently have VoIP phone from Acanac with SPA2102 ATA phone adapter, and it works just fine.
I wanted to switch to Freephoneline and tried to setup the same ATA device for freephoneline and I got the same issue people complain about here - I can call, they can hear me, but I don't hear them ! I can't make this configuration (Cisco DPC3825 2-in-1 modem/router + SPA2102 ATA) work for freephoneline - tried everything, opening the suggested ports, assigning static IP to ATA adapter and setting it as DMZ - nothing helps. No additional setup was needed in the router for Acanac VoIP - Acanac simply worked with the same setup. So it seems it is really something besides opening the ports and freehoneline tech support needs to look at this !

As additional info, I also set up Freephoneline ATA for my mother - she had separate cable modem and router devices. What I noticed, if I connect router to cable modem and SPA2102 ATA to the router, I get the same issue - only hear one way, no matter what I do in the router - opening the ports, setting DMZ, etc. However if I connect SPA2102 directly to cable modem, then it works just fine. The problem is, I still need my router for WiFi spot and other network devices like IPTV box, so I have to connect router to SPA2102 to get everything working together, but the SPA2102 in this configuration significantly downgrades the network bandwidth (from 30Mbps to ~7 Mbps), which is not acceptable either.

So it looks like this "one way hearing" problem is generic for network configuration when ATA adapter is connected behind the router, and this seems specific to Freephoneline as other VoIP providers (like Acanac in my case) don't have this issue in the same configuration.

Hi there,

I suggest to open a support ticket for this issue.

Please send me a PM once you have the ticket#

Thanks,