Number porting to GV - my experience
SteveInWA:
It's mostly Bandwidth's fault. They operate ring.to, and they're the primary CLEC (Competitive Local Exchange Carrier) for Google Voice. You added an additional mess to the process by porting into T-Mobile, and then porting to Google Voice. Somewhere along that process, Bandwidth didn't properly re-route your number's inbound calling to their switch.
ring.to and Google Voice numbers are treated as land lines for number porting purposes. Land line ports go through a different, and more complex process than a simple mobile carrier-->mobile carrier port. Mobile ports can be completed in minutes. Land line ports can take many days. The porting process into GV is mostly automated. If an error occurs, you would have seen the error notification on your Google Voice settings page, and could have clicked on it to attempt to correct the error.
I looked on the GV forum and didn't find any recent posts by username "Dixon".
Rant: since Bandwidth is shutting down ring.to for OBi users, they really ought to work out an automated and streamlined procedure to simply port the numbers into GV, upon their users' request. It's not rocket science.
Dixon:
Quote from: SteveInWA on December 24, 2015, 05:33:11 pm
It's mostly Bandwidth's fault. They operate ring.to, and they're the primary CLEC (Competitive Local Exchange Carrier) for Google Voice. You added an additional mess to the process by porting into T-Mobile, and then porting to Google Voice. Somewhere along that process, Bandwidth didn't properly re-route your number's inbound calling to their switch.
ring.to and Google Voice numbers are treated as land lines for number porting purposes. Land line ports go through a different, and more complex process than a simple mobile carrier-->mobile carrier port. Mobile ports can be completed in minutes. Land line ports can take many days. The porting process into GV is mostly automated. If an error occurs, you would have seen the error notification on your Google Voice settings page, and could have clicked on it to attempt to correct the error.
I looked on the GV forum and didn't find any recent posts by username "Dixon".
Rant: since Bandwidth is shutting down ring.to for OBi users, they really ought to work out an automated and streamlined procedure to simply port the numbers into GV, upon their users' request. It's not rocket science.
https://productforums.google.com/forum/#!topic/voice/it_8aI_qboM;context-place=topicsearchin/voice/category$3Aporting-a-number-to-google-voice
SteveInWA:
Quote from: Dixon on December 24, 2015, 05:37:24 pm
Quote from: SteveInWA on December 24, 2015, 05:33:11 pm
It's mostly Bandwidth's fault. They operate ring.to, and they're the primary CLEC (Competitive Local Exchange Carrier) for Google Voice. You added an additional mess to the process by porting into T-Mobile, and then porting to Google Voice. Somewhere along that process, Bandwidth didn't properly re-route your number's inbound calling to their switch.
ring.to and Google Voice numbers are treated as land lines for number porting purposes. Land line ports go through a different, and more complex process than a simple mobile carrier-->mobile carrier port. Mobile ports can be completed in minutes. Land line ports can take many days. The porting process into GV is mostly automated. If an error occurs, you would have seen the error notification on your Google Voice settings page, and could have clicked on it to attempt to correct the error.
I looked on the GV forum and didn't find any recent posts by username "Dixon".
Rant: since Bandwidth is shutting down ring.to for OBi users, they really ought to work out an automated and streamlined procedure to simply port the numbers into GV, upon their users' request. It's not rocket science.
https://productforums.google.com/forum/#!topic/voice/it_8aI_qboM;context-place=topicsearchin/voice/category$3Aporting-a-number-to-google-voice
"Dixon" is not "doctorwizz1". In any case, the person that responded to that post apparently didn't notice your last reply, where his next step would have been to escalate it to Google engineering.
Regardless, the information I posted above still applies, and you could have helped yourself by waiting a day or two longer after porting from ring.to to T-Mobile, setting a T-Mobile account PIN, adding funds, and ensuring that both inbound and outbound calling worked properly before initiating the subsequent port into GV. Then, you could have checked your own porting status and told Captain Chase what it was reporting, which would have zeroed in on the actual cause.
chilirock:
I am am in the process of porting my cable company provided phone number to GV. I have initiated the porting request to T-mobile. I have a question about timing after the T-mobile port / transfer is complete.
After I receive the text message from T-mobile indicating that the transfer is complete, do I need to wait any additional time before initiating the porting request to GV? Or can I initiate the GV transfer request as soon as I receive the confirmation from T-mobile and test both inbound and outbound calls on the T-mobile phone?
Thanks for your help.
transam98:
I didnt wait anytime (maybe like 1-2 hours).... and just make sure you REMEMBER your PIN # that TMOBILE Gave you (or you chose) as you need it when you initiate the GV Porting and pay GV their $20 !
Navigation
[0] Message Index
[#] Next page
[*] Previous page