GV# forwarded to Anveo
Jackson:
Well I really want nothing to do with GV's VM.
I did 2 things, removed GV from Obi and rebooted it.
That said things seem to now be fine (will find out later after a few more calls), no phantom VMs from a couple of chat's. I turned on my Uniden's answering machine and set it for 6 rings and had a test call/VM made, it worked fine. Previously with only GV even 4 rings would often result in GV VM picking up. Today I'll shut off the machine and do a test of Anveos's VM.
FWIW call quality seems very good (on both ends) forwarded thru my GV#. Will see if it remains that way.
Thanks to all who replied.
kaborka:
When I talked to the Anveo CSR before buying, he recommended porting, as some folks were allegedly having problems forwarding GV to Anveo DID. I didn't port, and I've been forwarding calls from GV for a couple weeks now. Never a glitch, and CQ seems better than the Obi GoogleChat client was.
Jackson:
Do you leave "Forwards calls to: Google Chat" still ticked? I left it ticked.
AlanB:
Quote from: Jackson on May 15, 2014, 02:56:27 pm
Do you leave "Forwards calls to: Google Chat" still ticked? I left it ticked.
No need for that option anymore.
MikeHObi:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page