I have an integrated modem/router on a AT&T DSL line. We got the number from Ooma (so we did not have our phone number transferred onto the Ooma line) and have not had problems since we bought the device in September 08 until about 3 months ago. It looks like incoming calls can be made BUT two things do not work:
a) Outgoing calls: I can turn on my phone and hear the Ooma dial tone but after dialing either a 7 digit or 10 digit number, there is just a long silence. The call is not connecting to the other line.
b) If I press the VM button on the Ooma device (not Scout, just one hub is connected overall), I do not hear anything. The volume is already set to the max.
I have tried reconnecting the hub by scratch (i.e. doing an entire reinstall from the beginning) as well as simply resetting the device to manufacturer's settings by removing the power plug, pressing down on the Ooma tab and replugging. In the case of reconnecting, I saw the tab turn blue, but I still could not hear the call connecting to the other line.
I am not so concerned about the VM but hoped to provide extra information.
I feel like this is a problem on Ooma's side. My hardware seems to be working, but it is not routing outgoing calls. Can anyone please explain?
Thank you! Please provide several other solutions other than resetting the device.
I have confirmed that the internet connection is solid, the cables work, the connection to the modem works, I can tunnel into the hum and that connection to the internet works.
Today I tried several slow boots which had no impact on the problem.
Following a thread on the forum where someone reported a similar issue, I reset the hub to factory defaults and now the Ooma tab is blinking red, and the Lines 1 and 2 buttons are solid red. The Home page at setup.ooma.com says "ooma is waiting to register your phone line on the network" - all other status and indicators in the setup page show "connected".
Subsequent factory resets have not fixed the issue. So now I have no incoming calls either.
Anyone have any ideas?
Oomavet, has your problem been resolved?
The default for the MAC address is automatic and it probably changed when you did the reset.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
I have ooma behind router, and sometime just power cycle ooma is good enough for me; some other time, I flip all three, since I have them on UPS, just flipping a switch is easier.
Do you still experience the problem? If yes, I'd like to investigate, but I am unable to locate your Ooma account. Please email me your Ooma phone number or MAC address so we can take a look into the issue you are experiencing.
I have AT&T UVERSE 6mbps, so speed should not be a problem.
Well, well, after several hours trying to find out where the problem was, finally it has been resolved! Like I said, I am with AT&T UVERSE (Internet, TV, and VOIP phone), anyway, playing with the Firewall in the AT&T router, I decided to reset the firewall settings, and bingo! It works! Wow! I love it!
If anyone out there has problems with OOMA, look hard into the firewall settins of your router. I thought, OOMA cannot be selling a device that it has problems, or it's not fully operational. I was right.
OOMA Customer Service are very polite, with a deep desire to help, but is hard for them to know what the heck is going inside the routers.
My problem was not able to make outgoing calls, in coming calls were fine.
Next step: Porting my 25 years old number to OOMA!
Could it be this? I received an email from Ooma regarding my number porting and today was the scheduled day for cut-over. I'll wait another day before getting too upset.
[edit: a few hours later, looks like outbound calls are working again. I'm chalking it up to the phone number transfer.]