OBiTALK Community

General Support => New to Using the OBi / VoIP => Topic started by: JoeK on May 20, 2019, 01:31:34 PM

Title: Testing before porting number
Post by: JoeK on May 20, 2019, 01:31:34 PM
I would like to test the Obihai/Google setup before I port the landline number to Obitalk. Is it possible to set up and experiment with an existing Google number (which I have) and then change it over and port my landline number?
Title: Re: Testing before porting number
Post by: N7AS on May 20, 2019, 03:31:38 PM
Yes.
You don't port your landline number to Obitalk. You port it to Google Voice by first porting to a cellphone and then porting to Google Voice. If you have Google Voice setup on your OBi device you are already testing it.
Title: Re: Testing before porting number
Post by: JoeK on May 20, 2019, 06:48:03 PM
Right, I could have been more clear. I have a GV number and plan to use that to test Obitalk. If that works out and I port my "landline" to Google can I then update my Obi200 hardware and account from the old number to the new one?
Title: Re: Testing before porting number
Post by: N7AS on May 20, 2019, 06:54:57 PM
Once you port your landline to Google Voice via a cellphone first. You do not have to do anything to your OBi200. I assume your GV number is working on your OBi200.
Title: Re: Testing before porting number
Post by: JoeK on May 20, 2019, 07:03:33 PM
The number I will be testing is not going to be the "real" number I would like to use. So...
1) use GV number 123-4567 for testing
2) if successful
3) port 765-4321 to GV
4) change the Obi device to use 765-4321
5) delete 123-4567

Can this be done or is it not possible to change a number with the Obi device?
Title: Re: Testing before porting number
Post by: SteveInWA on May 20, 2019, 07:50:02 PM
You are not understanding the basic operation of Google Voice, vs. the role that an OBiTALK device plays.

Google Voice is a service, just like Gmail or Calendar or Contacts or Docs.  All Google services are accessed via a Google account (Gmail address).  When you set up Google Voice on the Google Voice website, you will first claim one of Google's free inbound phone numbers.  This is mandatory.  Then, you link various devices to that number, which act as forwarding destinations.  Inbound calls to a Google Voice phone number can forward to any combination of:

An OBiTALK device can act as a Google Voice VoIP forwarding destination.  To do that, you authorize one of the Service Provider (SPx) configuration slots on the device to use the Google Voice service on your Google account.

The device is authorized to the account, not to the phone number.  It doesn't matter if you subsequently add a second Google Voice number by porting in a number, or if you change the Google Voice number; it will simply work.

So, yes:  first start by following the instructions to link your OBiTALK device SP to your Google Voice account.  Now, it can make and receive calls using the free number you selected.  If you are satisfied with the service, then initiate porting in your desired phone number.  After the port completes, the ported in number becomes the primary number used for outbound calls.  Inbound calls to either number will ring the same destinations.  The original (free) GV number then goes into a pending-deletion state for 90 days.  During that time, you can either pay another $20 to keep that number, too (and thus have two different inbound GV numbers), or you can ignore it, and it will automatically be released back into the pool at the 90 day mark.

Here's a link to the Google Voice help page on porting:  https://support.google.com/voice/answer/1065667 (https://support.google.com/voice/answer/1065667)

Does that make sense now?
Title: Re: Testing before porting number
Post by: JoeK on May 20, 2019, 08:00:30 PM
Thanks Steve - the magic words - "The device is authorized to the account, not to the phone number." That's what I wanted to know!
Title: Re: Testing before porting number
Post by: Lavarock7 on May 20, 2019, 08:47:59 PM
Make sure that your current number is portable to GoogleVoice...