Page 19 of 19

Re: Some incoming calls go straight to voicemail

Posted: Thu Apr 07, 2011 6:43 pm
by CodeMasterG
I just experienced this problem. Got a call from a cell phone caller, it rang once then went to voicemail so I know it's not

- voicemail configuration (set for 4 rings)
- a blacklist issue (if it was, my phone would not have rang)
- do not disturb being set (which is was not)
- anonymous caller being sent to voicemail (it's not enabled)

I made a test call from my Google account and was not able to reproduce the problem.

Come on Ooma -- being able to CONSISTENTLY receive a call is such a basic expectation for any telephone service consumer. This appears to be a an on-going issue, I sincerely hope this can be corrected.

Re: Some incoming calls go straight to voicemail

Posted: Thu Apr 07, 2011 6:48 pm
by lbmofo
CodeMasterG, by any chance, do you have multi-ring to your cell enabled?
If so, take a look here: viewtopic.php?f=5&t=10773&start=20#p75028

Re: Some incoming calls go straight to voicemail

Posted: Thu Apr 07, 2011 6:58 pm
by CodeMasterG
lbmofo wrote:CodeMasterG, by any chance, do you have multi-ring to your cell enabled?
If so, take a look here: viewtopic.php?f=5&t=10773&start=20#p75028
No - I do not. I have it set so that on a network / telo outage, calls will go to my cell. In this case there was not outage and the call did not get forwarded to me cell.

Re: Some incoming calls go straight to voicemail

Posted: Thu Apr 07, 2011 7:01 pm
by lbmofo
That's a strange one then. Since you know what call that was, write down the pertinent call info such as number calling you, datetime and then open a ticket with customer service or write support@oomacare.com to have them investigate why the call would ring once and go into VM.

Re: Some incoming calls go straight to voicemail

Posted: Thu Apr 07, 2011 7:10 pm
by CodeMasterG
Good advice, just submitted details to customer support, hopefully they can figure it out.

Thanks.

Re: Some incoming calls go straight to voicemail

Posted: Wed Aug 06, 2014 9:49 am
by mrmichaeljkelly
I had this problem with a second line connected to a Linx. Rebooting the Linx (just unplug it and plug it back in) fixed it.