Originally when I called my Ooma phone number I got a busy signal, but now I'm going directly to voice mail. It's not forwarding at all even though I set it up about 40 minutes ago. Any ideas on how to fix this?
View topic below for more information:
http://ooma.custhelp.com/app/answers/de ... d/143#Fail
Actually yes I was so that explains that. Thanks.lbmofo wrote:By any chance, are you calling using the phone your Ooma is supposed to forward to? viewtopic.php?t=1399
Doesn't explain why it took nearly a half hour to detect the Telo was offline though. Seems like that should be fairly instantaneous since the Telo obviously isn't responding at that point.
I've done testing on this and here is what I found.Morac wrote:I wouldn't expect instant, but I think anything over 15 minutes is getting to be on the long side. As it is, Ooma didn't recognize my Telo was offline for about 20 minutes and simply gave either a busy signal or a "call cannot be completed as dialed" message. That seems excessive.
From the time I cut off network from Telo to the time when forwarding started working was between 17 & 18 min.
In the meantime, I seldom got ringback before ending up in Ooma VM. A handful of times, I got "call can not be completed" from AT&T cell network. Most of the time, I got a subtle click after the intial ringing then dead air (no ringback/answer tone) then Ooma VM. Maybe this dead air is a bug? But if you wait long enough, the call does take you to your Ooma VM (I suppose after whatever duration you set to have your Ooma ring).