My area code is 207 (Maine). I'm having some issues with incoming calls.

- Incoming calls are dropped whether I set my ooma voicemail pick-up time up for 3, 4, or 5 rings.
- Back on Aug 12 I received one incoming call on voicemail but there was no call screening, though the message was recorded.

If I pick up a call before the pick-up time then there's no problem. The only way I can tell if I've missed calls is to check the caller ID log of my phone. I've run several tests (whichvoip, RoadRunner speed test) and my connection is fine. My upstream internet speed is 384k, downstream unlimited, reserve is 130 (ooma default).

Problem:
We've had Ooma for over a year, and it just started acting up in the past month. Problem was sporatic at first, but now it is all the time. People call in, Ooma rings, but when we pick up, we cannot hear anyone. We can call out, we just can't hear anyone calling in.

Actions Taken:
1. To eliminate the possibility of a bad phone set, I replaced our existing set with a working spare - same problem.
2. I've rebooted Ooma (several times) and we do get the blue tab after the self diagnostic tests, and which according to their documentation tells me that the Ooma Hub is working properly.
3. I call my cell phone and it works fine. But when I call from my cell to my Ooma number, I hear it ring once (from cell), then a busy tone, then a no-longer-in-use tone, then it disconnects. At the same time, the Ooma Hub line 1 lights up, rings (3x or 4x), says who is calling, then hangs up.

Remarks:
I know that there are issues connected to this in the east coast, but I hope that I am not the only one out here in CA that is being affected. I don't know if it means anything, but the no-longer-in-use tone was an odd surprise. I hope this gets resolved soon.

I see that it looks like most of the east coast is being affected....I understand this happens....HOWEVER

I would hope there would be some "place" where updates can be found. I saw (somewhere) a reboot worked. I drove back home and rebooted. It seems like I can make outbound calls fine.

The next issue, incoming calls ring but when I pick up, there is nothing. I thought I had setup some sort of a back up number to my cell. I have my system setup to rinh here and my cell at the same time. The issue is, I pick up and hear nothing. I tried it, there is no ring and just silence to the inbound caller.

Really, if this happens I thought the call would just go to my cell and "no harm no foul." At least I got the call and like many cell carriers, non of this 21st century stuff is 100%...it's just when it does, our like goes off the charts because we rely on it, think we have a back up plan that should work and we are good.

The problem today is there should be a way to quickly find out what is up, what is the status, and a "best guess" of houw long the problem will be around. Short of not knowing when we will be back up, should be some sort of "we need to get X and then restore Y and then...." Get the hint, a little communication goes a long way.

The other thing (and I don't know if you can contol this) is when a network outage of this scale happens, why can't the calls go to the "alternate" or backup number and forget trying to send them into the Ooma cloud. Right now, if some one calls (I get caller ID on the cell too), and I pick up either my ooma or cell phone...nothing, silence etc. The drag is, I call back and the caller doesn't know what's up and calls back 2 or 3 (or 8 this morning) times before they give up. I should have just been able to get my cell and take the call.

Frustrated in SRQ

PS. I posted the same in another forum this moring and now it locked and the post was deleted...not cool.

Mine is having issues as well. It was acting up last night, but I didn't really look into it until today. Calls to my Ooma just here 3 beeps (like a fast buys signal) and then nothing. This sounds similar to the other people in this forum.

The Ooma status says the issue is mostly affecting people on the East US, but I'm on the West Coast near Seattle, Washington (425 area code). I have Comcast Cable, using the same hardware and settings I have for years. I tried to reboot everything a few minutes ago, but the problem still exists.