Quote from: Stewart on April 01, 2012, 10:53:01 AM
A quick test with CSipSimple on my Samsung Captivate, registered to Callcentric, showed a correct (spoofed) caller ID when called from a Linksys ATA speed dial pointed at in.callcentric.com. I don't want to test this on the OBi; it's far away and loss of control would mean asking a friend to reset it.
After playing with this for two nights, I just can't make this work.
First, as noted elsewhere (
http://www.obitalk.com/forum/index.php?topic=2711.0), Callcentric (seemingly recently) requires stupidly frequent re-registration in order for whatever phone is associated with it to work, otherwise calls disappear into the ether. On the OBi, this necessitates certain workarounds involving Keep-Alive, Secondary Registration and Proxy Redundancy to keep the registration from conking out (
http://www.obitalk.com/forum/index.php?topic=2840.0). My Droid, lacking many of the twiddly knobs found on the OBi, and having a battery to conserve besides, won't keep up with the deluge of REGISTER requests CallCentric sends its way. So even if the rest worked... it wouldn't work.
Second, during the few minutes I had CallCentric working on the Droid before registration was lost, calls forked to
1777xxxxxxx@in.callcentric.com from the 127.0.0.1 SIP handler on the OBi gave me a CallerID of INCOMING-NUMBER@127.0.0.1, just like with GetOnSip.
Third, when I tore out the OBi's SIP handler and put the CallCentric account in its SPx, and put GetOnSip back on the Droid, the INCOMING -> Google Voice -> CallCentric -> GetOnSip chain gave me
INCOMING-NUMBER@callcentric.com on the Droid. Nothing I couldn't have done by setting UserAgentDomain myself.
So it would appear that no matter what, INCOMING -> Google Voice -> SIP FORK -> SIP MOUTH will wind up with either FORK'S user@domain or INCOMING's number@FORK'S domain, depending on whether or not CallerID Spoofing is set on SIP FORK.
There has got to be a setting on the OBi for this crap.