Thanks for this thread! It helped me!
My inboundcallroute suddenly stopped working a few months ago, and a few nights ago I discovered this thread which turned out to be the problem. (discovered b/c it was linked from here:
http://www.obitalk.com/forum/index.php?topic=13969.0)
Unfortunately I had no default route to ph, all my routes were based on caller ID, so it
seemed as if the GV integration had just stopped entirely with no explanation. Turns out the call logs don't show a call if it ends up having no destination to ring to, which is extremely frustrating.
Also frustrating - at one point I noticed the caller ID had + in it, so I tried adding that to my inboundcallroute and it didn't work. I also tried adding "x." before the area code, which as I understand is supposed to be a wildcard... and that didn't work either. I think these were both just cases of the device being in a flaky state and requiring a manual reboot before the new setting would truly kick in (even though the local web GUI showed the new setting had been pulled down from obiexpert)
In general it seems 3.2.2 has a few flaky/intermittent bugs, which makes it tough to troubleshoot.