Ooma Forums

"Incoming" call outage fixed in Seattle area.

Still not working here in Charlotte...Did you reboot your Ooma?

Didn't have to reboot. 2 other Ooma friends didn't either.

Incoming call to (330) at 7:50 am EST worked! Did not reboot ooma. Let's hope the "fast busy" glitched is now fixed. Thank you Ooma support team.

I'm still having problems here in metro Atlanta (404 area code).

Still out in Durham NC

I'm also still having the exact same problem here in Charlotte, NC. Can receive incoming calls from Verizon Wireless, but CANNOT receive incoming calls from landline providers AT&T and Windstream. Also just tried from AT&T Wireless and no go.

From ooma service status:

8/17/2010 11:30PM Pacific: Our carrier partner has resolved call routing issues. Normal service should be restored to all affected customers. If you are still experiencing inbound calling issues, please contact our customer support.

I think twitter feed should go out about the fix too but hasn't yet. Next time maybe use the right one (ooma status) vs the general ooma twitter account.

Not fixed in PA, 610 area code as of 8/19 10:17 AM, has been ongoing for two days. All incoming calls are routed to Ooma.

Cheyenne wrote:Not fixed in PA, 610 area code as of 8/19 10:17 AM, has been ongoing for two days. All incoming calls are routed to Ooma.

Is the little envelope on your system illuminated? This would mean that your ooma is in Do Not Disturb and all calls are sent to voicemail. If there are no lights, you might want to check the volume know on the side (if a white hub) or the little "sun" button, center of top row (if the black Telo)