I have my ooma voicemail set up, and I am seeing (or, more accurately: hearing) something really strange.
T-Mobile@Home VoIP is providing my existing phone service into the "Wall" connection on the Telo.
I have ooma Call Scanning turned "On"
My ooma Telo is the first device after my cable modem.
My T-Mobile@Home VoIP device is further down the chain, after my my router.
1) I call my ooma home number from my cell phone.
2) I wait until ooma Voicemail picks up.
3) I leave my message, and hang up my cell phone.
4) My cell phone is disconnected. However, I hear a busy signal coming from all my ooma phones.
6) I hear a clicking noise about once a second that never seems to end. I had the clicking run for another couple minutes before I hit the "playback stop" button on Telo.
At this point, I need to make sure that ooma Voicemail never picks up, or all my Telo handset batteries will be dead. Possibly the Telo speaker, too.
It appears that you have fallen into the landline integration trap when you registered your Ooma. If you search the forum using landline integration as the search keywords you will get a result spanning some 28 pages, and counting. Read all 28 pages and at the end of it all you will understand why most here recommend against using the landline integration option when you register your Ooma. If you decide you want to keep your landline separate, call customer service and ask them to remove landline integration and assign an Ooma number. If you later decide to port your landline number to Ooma it will replace your Ooma number once the port is complete.
That is impressive, and not in a good way.
Ooma needs to get their act together on this stuff. I have already had 2 tech calls in 3 days of ownership. I wonder how many people who are less tech-savvy return their ooma Telo within a week of purchase?
I have followed your advice, and acquired a Telo number for the interim. I have all my calls on my T-Mobile@Home service directly forwarded to my ooma number. It seems to be working better now.
Is there an option somewhere that will allow my Caller ID from my new ooma number be displayed as my T-Mobile@Home number?
Landline integration is an idea that is unique to Ooma, AFAIK; but its execution does not match their intentions. Now that you've separated the two services, you no longer need anything plugged into the Telo's wall port. Ooma does not allow CID spoofing for outbound calls (except as it exists as part of the Google Voice Extensions). If you are evaluating Ooma as a replacement for your Tmobile@Home number then the problem goes away once you port the number to Ooma. If you are looking at keeping both services, you may want to look into Google Voice as a front-end for all your numbers - that way you would only need to inform your contacts once regardless of what future services you use.
Groundhound wrote: Landline integration is an idea that is unique to Ooma, AFAIK; but its execution does not match their intentions. Now that you've separated the two services, you no longer need anything plugged into the Telo's wall port. Ooma does not allow CID spoofing for outbound calls (except as it exists as part of the Google Voice Extensions). If you are evaluating Ooma as a replacement for your Tmobile@Home number then the problem goes away once you port the number to Ooma. If you are looking at keeping both services, you may want to look into Google Voice as a front-end for all your numbers - that way you would only need to inform your contacts once regardless of what future services you use.
I totally agree with everthing Groundhound has said. As a GV user I find it to be an excellent front end for ooma - and you don't need Google Voice Extensions to reap the benefits.
I requested GV invitation on 5/21. We'll see how long it will take.