Localphone forwarding doesn't work

[GoogleCodeExporter]

I setup the Localphone account and integrated with GV based section 8 in Wiki. 
I setup the "always forward to" a cell phone. When I call the Direct Dial 
number associated with GV, it still ring the phone linked to the Direct Dial 
number not the forwarded cell phone. Where did I do wrong? Still a little 
confused about the forwarding thing.

Original issue reported on code.google.com by victor...@gmail.com on 20 Aug 2010 at 7:08

[GoogleCodeExporter]

Thanks for opening a ticket. Please be advised that any calls they forward to a 
phone number incur a per-minute fee. Even calls forwarded to US-based phone 
numbers. The only way to avoid incurring charges for every call is to forward 
your calls via VoIP. With that being said, how are you planning to use the 
service?

Localphone takes a unique approach to call forwarding. They map phone numbers 
in both directions. You have a list of phones that you own or manage (cell 
phone, home phone, work phone) and you also have a list of phone numbers that 
will call you. From what I can tell, EACH person who wants to call you gets a 
different phone number to call. When you add a contact to your address book, 
the system assigns them a number for reaching you and you give that number to 
them. When they call your number the Localphone system maps their number from 
caller id to the access number they are calling and the phone number where you 
are currently reachable drops out of the algorithm and starts ringing.

This is the reason why you lose all caller ID when you link GV to Localphone, 
at least when using regular phone numbers (not VoIP). When GV forwards calls, 
it normally sends the caller ID of the original caller. Even if you registered 
in Localphone everyone who could call your GV account, they would all arrive 
via the Localphone access number assigned to your GV account and Localphone 
wouldn't know how to map the call to your current preferred phone. You must 
shut off caller ID in GV so that every call that arrives on the access number 
assigned to GV appears to come FROM GV so that Localphone knows how to map the 
call to your current preferred phone.

Of course, none of the rules apply if you are only doing VoIP forwarding -- 
this is only if you want Localphone to transfer calls to regular phone numbers. 
This is what I've been able to glean so far from this thread 
http://bit.ly/54g7PS

You may wish to get used to the way things work via VoIP before trying out 
configurations that will cost you money for every call.

Original comment by easter...@gmail.com on 20 Aug 2010 at 12:29

• Changed state: Started
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Victor I know this is WAY OLD but did you ever find a solution for this?

Original comment by easter...@gmail.com on 8 Feb 2011 at 1:33

[GoogleCodeExporter]

I'm also looking for same solution. Any one?

http://tvc2.com | http://windows8releasedate.us

Original comment by pkfu...@gmail.com on 30 Nov 2011 at 6:00

[GoogleCodeExporter]

Any updates here? Victor? PK?

Original comment by easter...@gmail.com on 1 Mar 2012 at 10:43

[GoogleCodeExporter]

Still looking for a solution

Original comment by el1...@gmail.com on 13 Aug 2012 at 5:27

[GoogleCodeExporter]

el1212, at this point your best bet may be to hit the GV forum or the 
Localphone forums. I've never been happy with their solution, since only one 
person at a time can register their GV number with Localphone when using the 
analog call forwarding feature. 

The support forum we run at this site is largely for helping people use the 
Ruby scripts we develop here for use with a SIP Sorcery account. This is not a 
general purpose forum nor is it for help with any provider other than SIP 
Sorcery. Sorry I don't have a better answer for you, but I need you to go to 
Localphone or the GV forum where other people seem to have success using the 
service.

I'm closing this as Invalid not because you don't have a valid issue -- it's 
that the issue you're experiencing has nothing to do with our SIP Sorcery 
scripts. Sorry I couldn't be of more help with this.

Original comment by easter...@gmail.com on 13 Aug 2012 at 12:17

• Changed state: Invalid