I hate to resurrect an old thread, but it's relevant, so I am.
Summary:
Had GV until May 2014, then switched to GV forwarding to Callcentric. Ran into issues last Fall where GV would not forward to CC in a timely manner, or at all. Tried paid DID at Callcentric with no different result. Tried getting Callcentric and Google Voice technical departments to talk and resolve the situation to no avail. Convinced it was, and is, a GV issue.
Received a recommend to obtain an Inum number, which I did via Callcentric. Then went to IPComms, got a free DID and forwarded it directly via INum. So GV => IPComms =>Callcentric which rings OBi. I predicted in this thread that this was not a long term solution.
Last Friday Inum stopped working. Research via Callcentric, IPComms, and Googling showed Inum was "not accepting the invites" per IPComms, who supplied data showing this. Attempting to contact INum, and the parent organization Voxbone, to no avail. INum appears to be someone's hobby that left Voxbone, or Voxbone inherited it and doesn't really want it. They apparently went to the
Google School of Customer Non-Support.
DSL Reports thread about Inum So today I went through the laborious and somewhat risky (bricking) task of updating my OBi's firmware to use GV the new way. I let OBiTalk try to do it, but it always updated to the prior version, so I did it manually. I then let OBiTalk provision both GV on SP1 and Callcentric on SP2. Took multiple tries for each, even after resetting the OBi110 to factory defaults. All in all a multi-hour process. I then went in to the OBi directly via IP and disabled Auto Firmware Update, ITSP Provisioning, and ObiTalk Provisioning so nothing can be changed without my knowledge.
One of the problems I ran into was that I had removed Google Chat from Google Voice, and had to put it back - but couldn't because I use Chrome 64 bit and the Google Voice Plug In doesn't work with it (imagine that, a non-compatibility with Google products, I never would have imagined that). It turned out to be easiest to do this on another PC versus trying to remove Chrome 64 bit and put Chrome 32 bit back.
I'm at the point that if I run into any glitches I'm going to port my GV numbers out to Callcentric and be done with this. We don't get many phone calls, I do make a lot but using the cell is perfectly fine and I can even make GV calls on it and not use my minutes. I suspect that in the next few months GV will again hiccup and I'll move on.
I posted this so that anyone else relying on Inum forwarding knows of issues.
I plan on launching Rick's Dixie Cup and String phone service, it would work better than many of the providers out there.
Throughout all of this Callcentric's support has been very helpful.