dklane01 wrote:Well, in its current state, the Ooma voicemail works and dialing the *#486 to get to gve voicemail gives a fast busy. This is exactly what I want... both voice mails working, but the outbound caller ID being the GV number.
Actually, it is *#483 (*#GVE). However, it does seem like it is broke giving busy signal.
If you call your virtual number, you shouldn't get to Ooma voicemail. It will give you busy after a while. I have my virtual number assigned to a private handset so maybe that's the difference but even if your virtual number is in the main account, calling it should not end up in your Ooma voicemail. For my private handset, if calling from outside, will end up with busy signal but handset calling virtual number will end up in Ooma voicemail (this shouldn't happen; Ooma VM associated with virtual number should not exist).
I noticed that using private handset, **0, **1 prefix still uses GV as outgoing callerid....not certain if this is the problem but this shouldn't be the case.
Using main account handset, **1 still uses GV as outgoing callerid; this definitely should not happen.
I'll ask one of the mods to look into this.
Once the bug is fixed, *#GVE to check GV VM should work okay given setup correctly.
https://www.ooma.com/app/support/google ... extensions
I tried to use my Google Voicemail with my Ooma Telo and it's not working. How can I fix it?
Your Google Voice account must be set up to allow direct access to voicemail from your Ooma Telo. You can do this by following these instructions:
1.Navigate to the Google Voice Settings page
2.Look for your Google Voice Virtual Number and click "Edit"
3.Click on "Show Advanced Settings"
4.Choose the "Yes" and "PIN required" options for the "Direct access to voicemail when calling your Google number from this phone?" setting
NOTE: If you don't have a PIN set up yet, you will need to configure it on the Voicemail & SMS settings page.