obi/google out, att in

<< < (2/2)

jiminalaska:
Quote

I find that google will not port it from tracfone to google voice

Why was Google unwilling to port it from the tracfone to google voice?

Quote from: gworona on May 12, 2011, 06:04:36 am

I think this kind of setup will work just fine, but being a newbie, I just wanted to make sure.

Originally, I wanted to eliminate the monthly charge to ATT for my land line by porting my number to tracfone and then to google voice and use the google voice/google chat/obi110 solution documented in this forum.  After porting my number to tracfone, I find that google will not port it from tracfone to google voice.  So if I go back to ATT but get a cheap, "no long distance" plan, can I configure/connect the obi such that:

1. when I call out can I just dial the number and it will go through google (no long distance charges, no special dialing sequences)
2. when someone calls my long-held home phone number, my home phone will ring just like before
3. 911 will call the local 911 dispatch center

lavarock7@gmail.com:
On reason may be that the person wishing to port lives in an area Google "does not support". Try to port any 808 area code to Google.

-- snipped from the Obi forum --

Msg: Ooops! This number appears to be from an area we don't currently support.
For some area codes, Google Voice does not support porting, e.g. Hawaii (808), Alaska (907). If you get this result when you enter your land line number, you will not be able to port you number to Google Voice. It is of no use to complete the steps below.

--

http://obihai.com/porttutorial.html

Navigation

[0] Message Index

[*] Previous page