Problems using My Ooma? Ideas on how we can make it better? You’ve come to the right place.
#54773 by southsound
Tue May 04, 2010 9:05 pm
Connect a computer to the home port of your ooma. From that computer, browse to setup.ooma.com. That will take you to the internal webserver in your ooma for the configuration pages. If that does not resolve, you can enter the IP address of the server: 172.27.35.1 From there, select the Network tab and where it gives you options for the MODEM Port MAC Address select Use Built In. Then click update and for good measure, I would reboot the ooma. Your problems should be cured.

And lest I forget, welcome to ooma and to the forum! You're going to like it here! :cool:
#54785 by chibitul
Wed May 05, 2010 3:10 am
Many thanks, I did update the MAC address to use built-in as you suggested (it was set for Automatic, but the MAC was identical with the built-in). Anyway, I update to use built-in and then I rebooted the Hub, now the light is blue. let's see how it works now. Any idea why this is happening?
#54801 by Aveamantium
Wed May 05, 2010 6:52 am
Can you tell if it starts blinking when the Hub renews its IP address. If you're connected to a router most give 24 hour leases which means the hub will try to renew every 12 hours. When connected directly to the modem you should get longer lease times, so do you notice that it is more stable when connected to the modem? What you could try is giving the Hub a Static IP from the router so it doesn't have to renew...
#54803 by chibitul
Wed May 05, 2010 8:39 am
thanks, will try that later (I don't have time now, lunch break is short and I need to go back to work... when I came home for lunch, the light was blinking red again).

I will try the static IP, and I will also try to connect the OOMA directly the the cable modem.

thanks, will post an update in a few days
#54805 by Aveamantium
Wed May 05, 2010 8:53 am
Sounds like a plan... If this doesn't work and you're still under warranty you might IM ntoy and see if an RMA may be in order?
#54806 by coldsteel
Wed May 05, 2010 8:58 am
Sounds like a problem I had awhile back - You didn't say anything about how you connect to the internet, but if it's Verizon you definitely should look at a thread that I started when I solved my problem (up and down at least once an hour one weekend) its over here: viewtopic.php?f=8&t=6962 even if it isn't Verizon 'my solution' will cost you nothing to try.
#54807 by ntoy
Wed May 05, 2010 8:59 am
Hello,

The static ip sounds like a good idea to try. Last log I show is 5/4. I took a look at some of hte archive logs & did not see anything out of the ordinary. Other otpion if possible is to take hub to another location to see if it is stable to rule out
enviornment. Hard to tell if cable provider(ISP) made config changes that affects Ooma.
#54834 by chibitul
Wed May 05, 2010 4:07 pm
thanks guys, all seem good ideas.

It's weird that when this happens, OOMA still has internet connection, I was able to surf when connected directly to OOMA.
Also I had the OOMA connected directly to cable modem and I still had the problem. It's so random that it's very hard to troubleshoot.

At lunch break I read your posts and I decided to reboot the Apple Airport Extreme Router, and when I came home at 6 PM the OOMA was happy and it stays happy ever since (blue light).

I will try to make a static IP and also use Open DNS next time I have the problem (could happen tonight, or in 3 weeks, you never know)

I have a second OOMA which I just got yesterday and maybe I activate that one this weekend and then watch them both to see if both go nuts at the same time or at random times.

One last thought, I have COMCAST internet, and they really push their triple play, which is VOIP for $33 (and 2 other things to make the total $99). I wonder if COMCAST is messing with other VOIP traffic to make people sign up to their own VOIP? would that be possible?

thanks again

Who is online

Users browsing this forum: Google [Bot] and 2 guests