Is it necessary to transfer GV number to Vestalink before May 14
cleith:
I have a question regarding the need or requirement to transfer my GV number over to Vestalink.
First let me describe what my setup is. I received an email over the weekend about GV shutting down support for OBi110 device. So I came to this forum and read up on what I needed to do.
I use the Obi110 device for home phone purposes with a coordless phone attached to it. I have a very good internet connection 50 mgbs and this provides for a stable landline type of phone.
I did the following:
1. I selected Vestalink as my Service Provider and created the 1 month free account. I will purchase a subscription once I fully test the quality and stability of the service.
2. I cleared the configuration of my OBi110 and then created Vestalink as my SP1 and defined as Primary Line for Outgoing Calls. (Status in ObiTalk = Registered)
3. I created SP2 as my previous GV account info. (Status in ObiTalk = Connected)
No problems with these first 3 steps. Everything configured correctly and everything is working.
4. I spoofed my Vestalink outbound number to be my Cell Phone Number.
5. I forwarded GV calls to Vestalink by adding my Vestalink (new number) to my existing GV account as new "another phone".
I performed the following tests:
6. I called my GV number and it rings on my home phone via OBi110. (Status = Working)
7. I called my Vestalink number and it rings on my on my home phone via OBi110. (Status = Working)
8. Performed E911 service and echo test. (Status = Correct number and Working)
9. I downloaded Google Hangouts on my PC, Tablet, and Smartphone.
Everything seems to be connected and working. So, I beleive that everything is working as it should. My questions are related to the Google Voice Service.
10. When GV disconinues support for the OBi110, does this mean that my GV number will go away, or will I continue to own the GV number as part of the Google Hangouts product?
11. If I want to keep my GV number, does this mean I have to transfer the GV number over to Vestalink before May 14th?
12. Once GV disconinues support for the OBi110, will I still receive calls on my GV number based on the above configuration, or do I need to transfer my GV number as defined in step 11?
I hope this message is clear and thanks in advance for your response.
cleith
MikeHObi:
Quote from: cleith on April 14, 2014, 09:15:15 am
Everything seems to be connected and working. So, I beleive that everything is working as it should. My questions are related to the Google Voice Service.
10. When GV disconinues support for the OBi110, does this mean that my GV number will go away, or will I continue to own the GV number as part of the Google Hangouts product?
11. If I want to keep my GV number, does this mean I have to transfer the GV number over to Vestalink before May 14th?
12. Once GV disconinues support for the OBi110, will I still receive calls on my GV number based on the above configuration, or do I need to transfer my GV number as defined in step 11?
I hope this message is clear and thanks in advance for your response.
The obi is leveraging federated chat services from Google to work with Google Voice. Google is shutting down the ability to have federated services outside their network. Thus Google voice will continue to work, you will continue to have the number, only the method Obi uses to talk with google will no longer function.
As long as forwarding your GV number to Vestalink is working there is no need to port your number. I ported because I was having problems with forwarding of my GV number. Some numbers have problems, others don't.
If you end up wanting to port your number (you do not have to) you may want to do so sooner rather than later as there is an expected rush for port requests to Google which could mean it takes longer than normal for the port to complete.
cleith:
MikeHObi,
Thanks for your fast response. You answer helps to clarify that its not necessary to trasfer my GV number.
But it also caused me to think about needing to make sure to test that the GV is definitely forwarding to Vestalink. So, I just performed one more test.
I deleted SP2 defined as GV and then called my GV number. It rang to my home phone OBi110 as it should confirming that forwarding is correctly working through GV as "forwarding" and was not occuring through the SP2 configuration.
When I originally tested my GV and Vestalink numbers I had both SP1 and SP2 configured, so it was not clear whether dialing my GV number was occuring because of the "forwarding" configuration or as a result of GV being defined as SP2 which would be using the federated services interface.
Does this test make sense and would you agree that this test confirms GV forwarding is working properly?
Thanks,
cleith
cleith:
Also, now that I think about this. Based on this last test, at this time it looks like I dont even need to configure SP2 as GV. Everything works as it should just using Vestalink as SP1 with GV forwarding to Vestalink.
Thanks,
cleith
Usetheforceobiwan:
I think it wise not to port out a GV number to another provider unless you have at least a 6 month track record with the other provider. You need that time to assess their call quality, how often there are outages, their tech support and also interaction with that provider with your own setup (i.e. ISP, router, Obi and other network devices).
Actually with the ability for caller ID spoofing which most SIP phone companies provide, there is no real reason to port your Google Voice number out period.
Navigation
[0] Message Index
[#] Next page