Tag Archives: Google Voice

With the up-coming move, the question about what to do with our home phone was resolved by beginning an attempt to port our home Voice Over IP (VoIP) number, in a two-step process, to the Google Voice service. In Part 1 of this process, we successfully ported the number from our original Speakeasy VoIP provider to a pre-paid T-Mobile cell phone. This part was necessary because Google currently, by policy, will only port cell numbers.

Last night, after waiting a bit more than 24 hours after the T-Mobile port (and having experienced no overlapping service), we began part 2 of the process. As this number is going to become my wife’s Google Voice number, she logged into the Google Voice service, where she selected the number port. At this point a form came up which required information about the T-Mobile account. Because we had purchased a pre-paid cell phone, T-Mobile didn’t really have any information about us in the account (not even a name or address), and it wasn’t clear if the port would succeed, given that Google was asking for things like address details. To head off any potential problems or delays, we headed to T-Mobile’s site to set up the account and provide the details. I think I would have preferred not to have given T-Mobile this information, but wanting this to succeed the first time won.

We filled in the newly-provided T-Mobile information on the Google Voice form, and after clicking on about a half-dozen checkboxes warning us about different aspects and consequences of doing this port, things looked like they went through.

Next up was payment via the Google Checkout service: they charge $20 to port a cell number to Google Voice. It’s a little odd, as T-Mobile didn’t charge us to do the port from the VoIP service, but the end result makes it worth it in my opinion. We went through the details of the Checkout process and paid Google the $20.

At this point, what I had been reading had prepared me for the fact that the Google Voice port request form has no input box for the cell account PIN, and because of this, the initial attempt will fail. Fortunately, the email telling us this came right on the heals of the one confirming the submission of the port request. We went back to the form, added the PIN in the now-provided box (you would think Google would just add this to the original form?), and re-submitted. This time we got a confirmation email that it went through, and would take about 24 hours.

We should know later today if it succeeded, and I’ll post the update once we get that confirmation, but we’re optimistic that we’re about to be one of the group for whom this process worked.

Update (Thursday evening): Success! Michelle’s Google Voice number was updated to be our old home number, and she updated her profile so the calls will actually be routed somewhere. I couldn’t be happier that this worked, and if I would echo anything from what others have written about this process, it would be: make your you provide as much information as possible (and have it ready!), and then don’t push the process – let things happen, and give it time between steps.

We currently use Speakeasy’s voice-over-ip (VoIP) service for our house phone, and one of the goals we had in mind for this move was that we somehow retain our phone number. Area codes don’t really matter that much any more, and lots of people (some of whom we even want to keep in touch with!) know and use our current number. And then there’s the hassle of updating endless accounts (banks, credit card company, etc).

The solution that came immediately to mind was porting our number to Michelle’s as-yet unused Google Voice account. Some quick research showed that Google’s policy currently limits porting to cell phone numbers only. No landlines, and VoIP is considered a landline. Further investigation showed a work-around: some people have had success in first porting their landline/VoIP number to a pre-paid cell phone, and once the dust settles there, do a second port of what is now a cell number to Google Voice.

Armed with this possibility, we stopped by a local T-Mobile store (recommended by the author of the post I was following because it worked for him) last night and purchased a pre-paid cell phone. The cheapest phone was a $25 Nokia, and we paid an extra $10 for 10 minutes of time: we should be using this as our home phone for all of a day if everything works. Once back home, I called T-Mobile’s support line – for some reason, they couldn’t do this part in the store – and initiated the port of our home phone from Speakeasy/Level3 (the parent company) to our pre-paid cell.

Unless they need any more information from us, this first part of the process should take anywhere from one to six days, with potentially a day of overlapping service. Once everything is settled (the original post I read said that most problems arise when people jump the gun on part 2), we’ll create a new Google Voice account for Michelle, and attempt the second port.

The upshot of all of this is you can’t really lose: the port will happen or it won’t. If it does, we move on to step 2. If it doesn’t, our current service doesn’t change, and we’ll resign ourselves to changing our number.

Update (Thursday late afternoon): Got a call back from T-Mobile saying there was a hiccup in the transfer request. As we had a pre-paid cell phone with them, they didn’t have our address on file, and Speakeasy/Level3 was requiring that information as part of the transfer. Got that updated with the rep, and they re-sent the request, which was accepted. The new schedule has a day to “go through”, and then another business day for processing and turn-around, which puts us at Monday at the earliest. The tech mentioned we’d know when it went through as we’d get a text message to the cell phone.

Update (Tuesday afternoon): Success! We weren’t notified, but as of Tuesday afternoon calls to our home number were ringing the T-Mobile cell phone! And there doesn’t seem to be any service overlap. I’m going to officially cancel the Speakeasy VoIP service today, and we’re going to give it until tonight before going ahead with part 2. Stay tuned for the details (in a follow-up post, which you can now read here)!