Ok.
This all started within the past few weeks. It's not constant, and it's difficult to replicate. I don't know what the root cause is. But it's making me consider removing the Google Voice mapping altogether and just do a forward.
History:
I've had my Google Voice account since it was GrandCentral - YEARS ago. Before Google got their hands on it, the service was clean but lacking functionality. Google came in and added some cool stuff but in the process mucked up what was otherwise a "just works" feature.
It's always used to route calls to my cell phones, receive and send text messages, and provides me a consistent way to put my contact information on all of the tons of applications and what not I end up completing. So my Google Voice number is pretty much essential at this point.
I was stoked to see that Google Voice now had an approved way to connect to OBi. Used to have the very first one - that one that looked like a 56k modem - and when it stopped working I was rather bothered. But then the OBi1032 with the slicker integration came along.
I'm noticing, whenever I call out, the call will be fine for the first few minutes. But then one of two things will happen: The call will go silent (it's still connected, I see the timer going but it's dead air), or the caller can't hear me but I can hear them. Most common is the former. Happens an awful lot when dialing into WebEx meetings and happens 100% of the time dialing Hawaii numbers for some bizarre reason.
Now, I can make an outbound call via my cell phone through Google Voice and it'll work fine the whole time through. But of course then, you're not really using Google Voice to dial; you're using your phone plan thanks to their schemes. Makes me think that it's Google Voice itself that's the issue.
If I do the same call with my Anveo line, it works perfect. Of course, there are limited minutes on that line so I try not to dial out with it.
Is anyone else experiencing the same?
