Having trouble placing or receiving calls or using your voicemail system on Ooma Telo VoIP Phones? Post your questions here.
#51367 by Stackowax
Fri Mar 26, 2010 6:42 am
Both my wife and I are having trouble retrieving our voicemail from work via our Ooma phoneline. We keep getting a message that the security code we entered is incorrect. After repeated tries it sometimes works. But then we'll get a message that the extension number we input is incorrect. Again, after repeated tries, it sometimes works.

There is no problem when retrieving messages our cell phone.

Does anybody else have this problem? Any thoughts on why this is happening?
#51369 by murphy
Fri Mar 26, 2010 6:46 am
Stackowax wrote:Both my wife and I are having trouble retrieving our voicemail from work via our Ooma phoneline. We keep getting a message that the security code we entered is incorrect. After repeated tries it sometimes works. But then we'll get a message that the extension number we input is incorrect. Again, after repeated tries, it sometimes works.

There is no problem when retrieving messages our cell phone.

Does anybody else have this problem? Any thoughts on why this is happening?

Have you disabled the connection tone?
Many systems interpret it as a touchtone which can be problematic.
#51370 by Stackowax
Fri Mar 26, 2010 6:59 am
[[/quote]
Have you disabled the connection tone?
Many systems interpret it as a touchtone which can be problematic.[/quote]

Haven't done that. How do I do that?--Never mind. I figure out how to disable it. We'll see if it works.
#51371 by murphy
Fri Mar 26, 2010 7:08 am
Stackowax wrote:[

Have you disabled the connection tone?
Many systems interpret it as a touchtone which can be problematic.[/quote]

Haven't done that. How do I do that?--Never mind. I figure out how to disable it. We'll see if it works.[/quote]
my.ooma.com

Preferences -> System
Attachments
P1.jpg
P1.jpg (50.31 KiB) Viewed 2816 times
#51395 by coldsteel
Fri Mar 26, 2010 10:25 am
Stackowax wrote:Both my wife and I are having trouble retrieving our voicemail from work via our Ooma phoneline. We keep getting a message that the security code we entered is incorrect. After repeated tries it sometimes works......


I may be misunderstanding what is happening but you can look at the forums here under discussions for Alarm systems and Faxes. The OOMA Hub and Scout (not sure about the Telo) does not really pass touch tone codes through the system (hence that's why a lot of alarm systems don't work). This doesn't affect me a lot but has definitely tripped me up on more than 1 conference call and webinar where I needed to use the keypad. This would be the biggest OOMA failing that I've encountered - but then again if I remember before I start the call - I'll use my cell phone then.
#51398 by southsound
Fri Mar 26, 2010 10:36 am
coldsteel wrote:I may be misunderstanding what is happening but you can look at the forums here under discussions for Alarm systems and Faxes. The OOMA Hub and Scout (not sure about the Telo) does not really pass touch tone codes through the system (hence that's why a lot of alarm systems don't work). This doesn't affect me a lot but has definitely tripped me up on more than 1 conference call and webinar where I needed to use the keypad. This would be the biggest OOMA failing that I've encountered - but then again if I remember before I start the call - I'll use my cell phone then.

Woahhh!! Lots of incorrect information here. Good intentions I'm sure - just wrong conclusions. Let me try to address some of the points that fall into that category:

- All ooma systems pass OUTGOING DTMF (touchtones) just fine. The problem lies with incoming DTMF. It will never be possible with the hub, it may be possible with the Telo in the future. But OUTGOING works well. I use it on both systems to communicate with my bank, my stock broker, various autoattendants, etc.

- The connection tone (as Murphy described so well) can trick some systsems into asking you for accounts, passwords, etc. This happens most offen with ATT voicemail, but it can affect other systems like the OP has.

- Alarm systems have nothing to do with DTMF. The failure of some alarm systems with ooma is largely due to either (1) the ooma being connected incorrectly so that when the alarm system tries to take control of the line it disconnects the ooma or (2) the panel is not finding an adequate quality signal to "handshake" with the central office. This problem can be fixed in most cases by using *99, pause, pause before dialing the reporting number. It causes the ooma to use a different codec that is better at passing modem signals like faxes or alarms use.
#51442 by coldsteel
Fri Mar 26, 2010 3:57 pm
The DTMF problem that I mentioned is from experience. My Gemini P3200 alarm was disconnected a month ago. The alarm tech spent nearly 2 hours at my house wiring it up from the alarm panel back up to the jack where the OOMA is located so that the alarm would seize the line correctly etc and that worked. We setup the *99 and pause for dialing etc - the problem occurred after the alarm connected to the central security station - the initial handshake worked - the central alarm saw my unit. When my alarm sent what was supposed to be the DTMF tones identifying the reason for the alarm being tripped (zone&cause fire, tripped sensor etc) the central alarm could not understand the tones being received. Nothing the alarm tech could do got around that fact and I ended up dropping the service.

Second scenario, you're probably correct as it was a conference call so you could make the case that the caller that I conferenced in was making (incoming) DTMF tones to OOMA even though the DTMF tones were for the third party on the call not for the OOMA unit but on that conference call I could not enter the DTMF tones (to enter SSN, ID etc) from my phone either. Ended up doing that call from my cell-phone - In general DTMF works but in my experience not in every situation.

Who is online

Users browsing this forum: No registered users and 12 guests