Ported out of GV to Vestalink and experiencing major problems

<< < (2/5) > >>

Holysmoke:
I made a thread at Google.  We shall see, thanks.

dudly:
Hi Holysmoke,

I ported a number from Google Voice to Callcentric.  After it was ported and working on Callcentric, it remained in my Google Voice account for about a week or so and then disappeared.  I did nothing to help it along, it just went away.  Good luck.

giqcass:
When a number is ported to and from any service "successfully" some features may not work correctly for a few days.  I suspect this issue is more about Google allowing extra time to be sure the changes have propagated before deleting a number from their service entirely.  That way errant calls and SMS misrouted by the CLEC would still be received.

Marty.ba.calif.usa:
Also, since this is internet, there are DNS propagation delays in some cases.  DNS lookups are cached at various places, and may take some time to get cleared out.

Can the GV voicemail be disabled?  I don't know if that would help, though.  I never actually used GV for anything other an extra number, and for SMS messages via an Android app before I had unlimited cell phone messages.

Holysmoke:
as of today the GV number is alive and well in my google account and still does not go to Vestalink properly.

I still have the poor GV dropped calls problem when and if it does go to Vestalink.

I thank God for the 30 day money back guarantee at Vestalink but I wasted $13 on porting and now I have lost a GV number I have used for 6 years unless I pay google $20 to port it back and why do that when they are dropping Obi.

Navigation

[0] Message Index

[#] Next page

[*] Previous page