There have been several similar issues all with different resolutions so wanted to post my situation as well.
Activated ooma with a NEW phone number (and will keep any landline conversation out of this to help eliminate variables).
Have a 2Wire integrated DSL modem/router with SBC (ATT) service. With this, there's no choice but to have ooma behind the router. (trying to avoid swapping this out at this point)
Opened up all UDP and TCP ports required by ooma (per tech article) on router's firewall.
Restart all components and ooma tab blinks red while 1 and 2 remain solid red.
Notes: Router assigns 192.168.1.79 to ooma however ooma's IP range is in the 172s. Navigating to these IPs listed result in the same as navigating to setup.ooma.com where the status remains "registering ...". MAC addr. is correct.
Any thoughts in helping resolve this problem are greatly appreciated. Thank you.
Use a magnifying glass on the MAC address on the bottom the hub since B and 8 are easily confused.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
Saw in another thread that this info "would be something useful to display to the user" but did not know if implemented.
Thanks for the replies.
Not to beat a dead horse but this really needs to be addressed. The rep was able to look up my point of purchase etc. How about having the customer enter more than just MAC to check against? If you don't want S/N's flying all over the net, a simple checksum (plenty of MD5 samples out there) will do.
Well now I wait up to 48 hours for someone to be able to update the MAC over at ooma. Still looking forward to being part of the community - thanks for the replies.
It's perfectly ok to write hex number in lower case lether (abcdef), and ooma should consider this