Seeking advice on how to accomplish this...
CoalMinerRetired:
Quote from: Hollywood on January 14, 2013, 08:49:27 pm
You posted all good questions and did a lot of homework. I too want to transfer my number to Google Voice and am watching how this goes for you. You pointed out that you realize the CallerID is number only. I read conflicting stories and am more confused as to if it can be solved for CallerID Name? Also GV doesn't support 911, but you can get a $49 NetTalk to plug into the Line port of the Obi110 to solve that.
I'll be watching too. Great Thread here! :)
GV does Caller ID number only, no name (CNAM). I've never heard of NetTalk, but for $49 you're much better off paying the $1.50 per month for a CC (CallCentric) number that gets you CNAM plus 911 or E911 where available (plus gets you the full GV audio call ID/audio call screening if so desired). See the famous threads on here where all this is discussed and answered:
http://www.obitalk.com/forum/index.php?topic=3609.0
http://www.obitalk.com/forum/index.php?topic=3640.0
GV porting:
http://www.obitalk.com/forum/index.php?topic=1051.0
johnpane:
Quote
Also GV doesn't support 911, but you can get a $49 NetTalk to plug into the Line port of the Obi110 to solve that.
I also see you can get E911 from http://www.gv911.com for $12/year.
johnpane:
Quote
Call flow is explained here on the website of this quasi-regulatory body for all LNP in the US: http://www.npac.com/number-portability/how-lnp-works. I read it to mean all calls to a ported number do in fact flow through the CO switch where the number was 'born.'
My interpretation is contrary to yours, based on the text below.
Quote
When a call is made to the ported telephone number, the initiating service provider switch launches a query to its LNP call routing database to determine whether the telephone number has been ported. If it has, the database response provides the switch with the LRN needed to properly route the call.
CoalMinerRetired:
It also says this:
Quote
....An LRN is assigned to each ported telephone number and is used to route calls through the PSTN to the switch serving the ported number. The LRN is intended only as the network address of the serving switch, however, and is not intended to convey any rate area information such as would be used determine whether a call is local or long distance. The same ten-digit LRN can be used for every ported number served from the switch to which the LRN's NPA-NXX is assigned.
For a number that started life as a landline in a given NPA-NXX, that CO switch is never going to change, calls to it will always get routed to that CO switch. That's now I understand it.
johnpane:
This page provides further evidence I will not be able to port my number to GV:
http://www.obihai.com/porttutorial.html
According to this, the error message I get from GV ("Ooops! This number appears to be from an area we don't currently support.") indicates I will not be able to port the number. The page says I would get a different error message if I would be able to port to GV after first porting it to a mobile number.
So....back to my original question:
Quote
OBJECTIVE: Cancel my landline service but keep the number; have Google Voice handle all incoming calls to that number.
My idea is to port my landline number to some service, call it X. X forwards all incoming calls to my google voice number. I don't think I need any other services from X.
Then I integrate Google Voice with my Obi:
• google voice manages incoming calls; those I want to ring at home are directed to the OBi
• outgoing calls on the OBi are routed through Google Voice. I realize that outgoing caller-id will show my Google Voice number and not my landline number. I may be willing to accept this if there isn't a way to solve it.
I am seeking recommendations for the way to accomplish my objective, including the best choice for X if such a service is needed?
Depending on the cost and features of the solution to this problem, another possibility might be to route outgoing calls through X, which would also get me the correct caller id.
Navigation
[0] Message Index
[#] Next page
[*] Previous page