Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools


I'll admit it. I'm an early adopter of most technology. I've had a Vonage account since shortly after the company started. Recently, I added a second service, SunRocket, and upgraded my router to one that has a robust QOS engine. All of that technology was useless when I needed an operator to check on the status of a phone line.

My wife made her daily call to her elderly mother in Cincinnati to check in on her. The phone was busy - not unusual. She tried an hour later, and the phone was still busy - still possible since my mother-in-law is on dialup. My wife repeatedly called her mother throughout the day and was greeted by the same busy signal, so I suggested that she call the Verizon operator for a line check. That's when the problem started.

The Verizon operator looked up our account from our caller ID, and knew that we didn't have Verizon as our long distance carrier. In fact, on my Verizon line, I dropped all long distance and local extended calling services. I keep the line for incoming calls, and as a lifeline for the occasional power outage - even though my network, cable modem and VOIP TAs are all plugged into a large UPS. The Verizon operator informed us that she couldn't (wouldn't??) check the line since Verizon wasn't our long distance carrier. Never mind the fact that they own the copper and I pay them monthly for basic phone services. The operator suggested that I contact our long distance carrier for assistance.

I keep an MCI calling card for those limited times when for whatever reason I need to make a call on the traditional phone. Of course, there's no way to contact an operator on MCI - you dial an 800 number, put in your pin and dial your phone number.

Plan "B" - I tried calling customer service at both Vonage and SunRocket. Since they don't own the copper on the far end of the connection, all they could do for me was to dial the number and make sure that their network was routing the call properly. The customer service representative at each VOIP provider called my mother-in-law's number and both reported a buzy signal.

On to Plan "C" - I tried making the call with my Verizon Wireless cell phone, and, of course still got the busy signal. Like the Verizon operator, the Verizon wireless operator couldn't (wouldn't) check the line either.

Plan "D" - try to contact an operator in Cincinnati. An exhaustive search of the Cincinnati Bell web site yielded no usable numbers. Customer service had closed for the day.

Fearing the worst, we called the local township police department in Cincinnati and asked that they send an officer out to make sure that my mother-in-law was OK. A half hour later our phone rang. My wife's mother was fine. She had set down the cordless phone without disconnecting a call, so the line stayed open for close to 8 hours.

I'm not sure that there's a good solution to a problem like this. I fault my landline carrier, Verizon, probably the only ones that could to a line check, for not helping out. It's pretty stressful when you can't get in contact with an elderly parent it a distant city.

For now, I think I'm going to give my mother-in-law a pay-as-you-go cell phone for Christmas. I just hope she keeps it charged up and turned on.

Has anyone else had a similar experience using VOIP as their only long distance carrier?

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I have an N66u (Rmerlin 374.43_2) with the following vlan settings.robocfg vlan 20 ports "0t 8t"vconfig add eth0 20ifconfig vlan20 upbrctl addif br0 v... is a helpful utility script to manage DHCP static leases. The script is only compatible with 384.13 release. The script displays a m...
In AP mode, does the WAN port automatically get assigned to LAN (VLAN 1)? I do see that in Tools -> Sysinfo, the WAN port gets assigned to VLAN 1, yes...
For those of you fighting the issue of 5ghz problems -- particularly pauses and disconnects -- here's another thing to look for: Do you have a Fire TV...
Just got into the VPN game today using IPVanish and Openvpn on my ac3100 running 384.13. Am able to successfully access my LAN when connected through ...

Don't Miss These

  • 1
  • 2
  • 3