GV# forwarded to Anveo

<< < (3/3)

AlanB:
Quote from: MikeHObi on May 15, 2014, 05:01:38 pm

Quote from: Jackson on May 15, 2014, 05:59:24 am

Well I really want nothing to do with GV's VM.



If you are forwarding from GV to anything you are stuck with google voice mail.  The only way to avoid it is to answer the call before the google voice voice mail timeout period.   Noting that the clock for this period starts counting some time before Anveo may ring your obi.


Otherwise you will need to port your phone number.  I've been very happy with mine at Anveo.  I would suggest that you consider waiting on the port though.  I'm sure porting volumes are very high right now, so that probably means more likely to have a delay or error.  Perhaps live with GV Voicemail for a few more weeks until things quiet down if you decide to port.

Jackson:
Quote

forwarding from GV to anything you are stuck with google voice mailforwarding from GV to anything you are stuck with google voice mail
You are correct, just tried it. That's a drag that it can't be turned off.

kaborka:
The default delay time for Anveo VM is 25 seconds.  When I first started forwarding my GV to Anveo, the Anveo VM took the call before GV did.  In my case, I wanted to keep using GV VM, so I increased the delay in my Anveo call flow to 45 sec. I don't think you should have any problem using Anveo VM with GV forwarding.  It is probably worth a ticket to try to sort out what's going wrong in your case.

AlanB:
True. You can use Anveo VM but not turn off GV Voicemail so there is no guarantee GV VM won't pick up first. Don't waste a ticket.

Jackson:
FWIW getting GV to send VM notifications to my main Gmail account (my GV# was on another) was a bit of a pain as It would not allow another Gmail addy.  Had to use a filter forwarding from my GV accountto my main and all is fine now.

Navigation

[0] Message Index

[*] Previous page