This was previously discussed at great length, starting last summer, here:
http://www.obitalk.com/forum/index.php?topic=6069.0Yes, it was a circular firing squad of finger-pointing (how's that for a mixed metaphor)?
I nagged Google engineering several times to deal with it, but I never got an official response. Last week, after experimenting unsuccessfully with a POS IPKall DID (that magically started having one-way audio on all calls), I trashed IPKall and went back to using my CC free NY DID. GV-->CC-->OBi has been working fine for me, at least, for a week. So, perhaps one of the two sides changed their call-routing, and won't admit it, or perhaps it is just the luck of the draw.
As Mike pointed out, there are many paths and methods to route VoIP calls, to pinch pennies, and it won't be transparent to the user until it fails somehow.
Bottom line: all attempts to seek out the cheapest VoIP solution will be met by the immutable fact that you don't get what you don't pay for; reliability costs money, and from a statistical process control standpoint, the closer you try to get to six-sigma quality, the incremental cost increases become non-linear.
