Got something else to discuss that is not covered by the previous forums? Post it here!
#94566 by ohhma
Tue Apr 03, 2012 7:38 am
When we had this new OOMA, its PRIVACY feature [CALLER ID BLOCKING for outgoing numbers] WORKED 100% and was blocking our name and number to the called party. But SADLY that feature has no meaning now. Outgoing Calls PRIVACY>"Enabled" then “Disabled” many times, also did a hard RESET. Our number is seen by the called party regardless how we dial; with *67 or by checking the BOX or both ways. It blocks the NAME part only; which goes out as Anonymous but full number goes to called party. This happened only recently perhaps with Ooma’s new firmware.
We wonder why we should switch totally to Ooma from another provider when a very basic feature is out of order!
#94568 by lbmofo
Tue Apr 03, 2012 8:46 am
Not sure why this is for you. I've tried using 3 Ooma devices and they all seem to block outgoing callerid okay using *67 prefix. One thing about this feature, it doesn't block your outgoing callerid if calling another Ooma user.
#94569 by thunderbird
Tue Apr 03, 2012 9:11 am
ohhma wrote:When we had this new OOMA, its PRIVACY feature [CALLER ID BLOCKING for outgoing numbers] WORKED 100% and was blocking our name and number to the called party. But SADLY that feature has no meaning now. Outgoing Calls PRIVACY>"Enabled" then “Disabled” many times, also did a hard RESET. Our number is seen by the called party regardless how we dial; with *67 or by checking the BOX or both ways. It blocks the NAME part only; which goes out as Anonymous but full number goes to called party. This happened only recently perhaps with Ooma’s new firmware.
We wonder why we should switch totally to Ooma from another provider when a very basic feature is out of order!

Power off the Ooma device for 1 hour. This allows time for the Ooma servers to reload/reset/correct your Ooma profile. Then repower the Ooma device and test.
#94593 by thunderbird
Wed Apr 04, 2012 9:26 am
ohhma wrote:Looks like Ooma does not have their own techs and they hire from outside on per call basis. NOTHING has been resolved yet re: *67 or Outgoing Numbers Privacy feature issue..

Send Ooma Moderator (Engineer) Tom B. memberlist.php?mode=viewprofile&u=4164 , a personal E-mail outlining your problem.

The Ooma Moderators often don't return an E-mail to you, so after a reasonable period of time, check your problem and see if it improves.
#94598 by EX Bell
Wed Apr 04, 2012 12:13 pm
It sounds like you have not had your Telo that long, is that correct? You are using the temporary number and have not made the leap to porting your old number, is that also correct?

If you decide to keep the Telo and port your old number to Ooma, then it will take at least two weeks for the CNAM (caller name) to propagate through the various CNAM databases. Kind of like when you register a website domain name, it's not just out there and searchable instantly, it takes time to propagate before it can be found by various search engines. Further to the point, not every local phone provider will update their CNAM database immediately, so it could take up to several months before some carriers display your name with your CID.

If you decide to keep the Telo, but not port your number, then I would guess that Ooma is not going to submit your name to the registry until they're sure you're going to keep their device (60 days). They say they do it within 5 business days, but I wonder if that's actually so, because that wouldn't make sense for any company to do that. They would not be able to recycle the number very quickly if you decided not to keep the device because it would have the previous user's name on it in the CNAM databases until the new name propagated again. They may actually be referring to CNAM for ported numbers being submitted within 5 days of completing the port to Ooma.

If the CID number is not being blocked, then you obviously have an issue that needs to be resolved, but the name not showing up is just a matter of time. Some users have said that an error with the web interface caused certain options for them to not change, and it had to be manually switched on or off by customer support. Have you tried using a different browser to make the changes? I use Google Chrome on Mac and so far the options have changed status and worked as expected.

More info on CNAM databases with Ooma here

Who is online

Users browsing this forum: Majestic-12 [Bot] and 8 guests