Android smartphone as client phone for Google Voice
unoriginal:
Quote from: Stewart on April 01, 2012, 01:07:43 am
I use a free PBXes account to interface IP phones to the OBi. SP2 (with X_SpoofCallerID on) registers as a sub-PBX; the IP phones register as normal extensions. The OBi sends inbound calls to a PBXes Ring Group, which PBXes forks to the phones. On outbound, PBXes routes the calls to the OBi trunk and the OBi routes them to my pseudo-landline, in your case, you'd send them to GV.
Finally got around to trying this. Predictably, calls now come into the Droid with the format <12345678901>@pbxes.org, where <12345678901> is the 11-digit number of the original caller.
So, to review, with X_SpoofCallerID on:
With SP2 set as the 127.0.0.1 SIP handler, with GetOnSip.com relaying to the Droid, calls come into the Droid as <12345678901>@127.0.0.1.With SP2 set as the 127.0.0.1 SIP handler, with CallCentric.com relaying to the Droid, calls, if they come into the Droid at all, come in as <12345678901>@127.0.0.1With SP2 set to a free callcentric account, with GetOnSip.com relaying to the Droid, calls come into the Droid as <12345678901>@in.callcentric.com.With SP2 set as a sub-pbx of an account at PBXes.com/PBXes.org/PBXes.xxx or whatever, and the Droid set as an extension, calls come into the Droid as <12345678901>@pbxes.org.
unoriginal:
Upon further review, it would seem the Obitalk ITSP web provisioning wasn't fully propagating to my device. Wonderful!
With the PBXes stuff configured on the unit directly, I now get <USERNAME-of-SUBPBX>@<IP-ADDRESS-of-SOME-PBXES.COM-SERVER> coming into the Droid, whether SpoofCallerID is on or not. Even better!
Sadly Google Voice does not know how to return a call to testaccount@173.95.243.43. Apparently that's not a valid number. Hogwash!
Stewart:
Get a free New York Callcentric DID for the account to which your Android phone is registered. Set up GV to forward your calls there (turn off forking in the OBi). You should now see correct caller ID and with luck, you'll even get the caller's name. Use a different account on the Droid for making outbound calls through the OBi.
unoriginal:
Quote from: Stewart on June 23, 2012, 03:22:30 am
Get a free New York Callcentric DID for the account to which your Android phone is registered. Set up GV to forward your calls there (turn off forking in the OBi). You should now see correct caller ID and with luck, you'll even get the caller's name. Use a different account on the Droid for making outbound calls through the OBi.
I want to specifically thank you for your repeated attempts to help solve this problem, and I'm sure that this solution, similar to my original #5 option, would work, or come near enough to working. And I've seen elsewhere that you've been trying to get CSipSimple working on unregistered LAN SIP calls (i.e. from a VOIP-enabled WiFi phone to an Obihai unit), which is a large part of what I've been trying to do here. So again thank you for helping fight the good fight.
But I think I've got this thing working now, without having to rely on Callcentric (or SipGate), which seem to have problems on smartphones due to the DNS resolving etc. etc. See next post.
Navigation
[0] Message Index
[*] Previous page