Ooma Forums

What I'm seeing...

In Tampa, FL, had several people complain about about not being able to get through. One is getting a message from Verizon Wireless, that "This Verizon wireless number is out of service". But that might just be a manifestation of their wireless service not being able to route the number.

Calling the VoIP from my land line causes 15-30 secs of silence followed by a busy signal. On the Ooma side I hear a second of my outgoing voice mail message from my Ooma Hub, as if during the silence the call is getting routed and "silent ringing", and then getting cut off when the busy signal occurs.

-BitHearder

Jay521 wrote:I'm in New York and my incoming service is out. I am beginning to miss my landline

Earlier this year our landline was almost useless because rodents had chewed through the fiber cable that serves our area. It took Qwest almost a week to restore reliable service. During that time, my ooma systems worked flawlessly. This is not to in any way disregard the inconvenience of ooma having problems and the impact it has on subscribers - I just wanted to say it happens with landlines too.

Same problem as everyone else here. Silence then a fast busy signal. I'm in NY if that helps. Once in a while calls get through. We can make outgoing calls without a problem.

Same issue here, all inbound calls get "circuits busy". None of the various call forward or DND settings help. The phone rings but no one is there for normal inbound and forwarded inbound. Enabling DND does not send the call to VM.

wpwood3 wrote:

demaximis wrote:It was nice to know, but it would also be nice to know what affected the service and when it is back up -- preferably in an easy to check location on the main site. Having to dig through the forums for the information, and piece it together via customer-by-cusomter complaints is a little customer-service unfriendly.

I agree 100%
Ooma needs a "Service Status" webpage that can be checked and has RRS (or something similar) to automatically notify customers when there is an outage. This is crazy!

There is such a page - http://www.ooma.com/forums/viewtopic.php?f=10&t=26

It wasn't updated earlier, but depending on how soon the problem is identified it will determine how soon the page is updated.

It currently lists the following update on network status.

Status: DOWN mostly in the Eastern U.S. region.
8/17/2010 9:00AM Pacific: We are currently experiencing an issue with inbound calling affecting customers mostly in the Eastern U.S. region. Please check the forums updates, we do apologize for any inconvenience this my cause.

Just received a call from a landline in Phoenix, AZ - first call of
the day that went through.

Still not receiving calls from the Eastern US

VoIP wrote:
There is such a page - http://www.ooma.com/forums/viewtopic.php?f=10&t=26

It wasn't updated earlier, but depending on how soon the problem is identified it will determine how soon the page is updated.

It currently lists the following update on network status.

Status: DOWN mostly in the Eastern U.S. region.
8/17/2010 9:00AM Pacific: We are currently experiencing an issue with inbound calling affecting customers mostly in the Eastern U.S. region. Please check the forums updates, we do apologize for any inconvenience this my cause.

Yes, but that page was not updated until 2 hours after I made my post. The outage was going on for half a day before anyone at Ooma bothered to update that status page! That's NOT acceptable!

Same problem here. Live near Seattle Washington (425 area code). There is another thread in the forums that has a bunch of reports as well...

http://www.ooma.com/forums/viewtopic.php?f=9&t=8927

Sounds like Ooma knows about it, so I guess I'll just wait. Honestly, I kind of like the silence at the house ... but, the rest of the family would like their phone back.

Same problem in Northern NJ. No incoming calls at all.

Having the same problem in 314 area code. Call comes in, no one on the other side..the caller gets busy signal.