Is it necessary to transfer GV number to Vestalink before May 14

<< < (2/5) > >>

MikeHObi:
I would suggest that your test should include asking the people who contact you the most often to also try and call your GV number and verify that call completion occurs quickly.

My experience of problems was that I could call home on my cell or my office phone and get my home quickly.  But other friends and family calling my GV number would result in extremely slow call completion.  So long that the calls would often end up in google voice mail never ringing my obi.  As this was a google problem, there was no way to resolve other than to get a new DID or port to a different provider.  I ported to a different provider, someone I had been using for E911 for almost 2 years.

So if you can, have a few people call your GV number to verify things work.

And no, you do not need a GV SP configuration any longer since GV will not be directly connected to your device.  The only reason to keep it up right now would be if a failure in who you pick occurs, you can disable the forward and still get calls from GV, at least until May 15th.

cleith:

Usetheforceobiwan

You bring up a good point.  Makes sense not to port the GV otherwise you sort of get locked into the provider or must pay to port your number to another. It looks like my setup is the correct approach.

MikeHObi,

Thanks for this advice. I will make sure to do this. 

cleith

AlanB:
I agree with Usetheforceobiwan with one possible exception. If you have call quality issues on incoming calls you won't know whether it is related to VL or GV. So, if this situation occurs you may need to have some test calls made directly to you VL number.

Usetheforceobiwan:
One other factor, when you port you impact GV SMS.  As it is now, GV SMS is tied into your email which means you can send and receive SMS without using a phone.  So you lose the ability to send SMS from your phone number when you port out unless you port your number to a cell phone carrier.

murtazao:
I agree with the "Do not port" advice. Something else to consider, is that Google has not mentioned anything about stopping GV forwarding on May 15. Assuming that is the case, the current set up of forwarding to Vestalink + Spoofing on outbound calling should continue to work after that date.

The advantage of that, is that you continue to use the other GV features. Hangouts integration, GV SMS -(hopefully it will work for international SMS), voicemail and transcription etc.

If you don't need a lot of outbound calling or E911, you could even use a combination of GV --> Callcentric + Localphone/CircleNet for outbound

Navigation

[0] Message Index

[#] Next page

[*] Previous page