update from my original post:
Did a lot more testing and went through 3 phone calls of troubleshooting with sprint. Bottom line is that the calls not ringing through, and call waiting not working comes down to google voice:
- this appears almost certainly to be an issue with google voice.*
- only resolution I have found is to disable the integration of google voice with your sprint number, and then possibly (at least in my case) take additional steps to ensure its cleared off of sprint's and GV's system. (in particular the call forwarding that it puts into sprint's system).* Then, everything works flawlessly again with sprint on its own.
- I absolutely do not recommend integrating google voice with sprint at this time, since it is so unreliable on multiple fronts.* That is, unless you are OK with not receiving any call waiting, and missing about 1 out of every 3 calls (on average-- sometimes more sometimes less in any given hour).
Also to know:
- The cooked rom doesn't seem to have anything to do with it (Vin's feb 10th rom for tp2). was completely independent of this.
- On the bright side, text messaging with gv/sprint still seemed to work reliably while everything else was dysfunctional.* but i didn't test too heavily.
- you can still get some value from google voice by using it separately for text messaging only.
- by keeping my google voice number separate, in my experience the ability to send text messaging and have it copy the texts to my sprint phone, is very reliable (over last 14+ months). saves a lot of time.* Minor issues of wierd formatting on some txt replies (if > 160 char) but overall its not bad.
Other technical details:
- when i initially reported this issue to sprint tech support last night, they said there was call forwarding still sitting on my account which never got properly cleared off. oddly, this was from a number (verizon) i temporarily forwarded to back in fall of 2009, and then had disconnected that number and turned off forwarding (in 09).* ultimately this doesn't seem to have anything to do with my GV issues, but its possible that google voice still had that forwarding number in thier system-- and at the time of integration that number carried into sprint's forwarding. * she said it was half cleared off and she proceeded to completely get rid of it. but that didn't fix the issue even after 12+ hours
- upon re-activating the integration of google voice with sprint,on the very first phone call just seconds after re-activating, the issues started up instantaneously,* (no call waiting, missed calls).
A bit of searching turned up this thread including the following:
http://www.google.com/support/forum/p/voice/thread?tid=702e1ef9bd361557&hl=en>
4/1/11
"I've been using (or trying to use) GV for a year and a half now. It's never been perfect. There's always been some problem or another, but I've always dealt with them in the hopes that the service just had some bugs to be worked out. I've had more missed calls, lost voicemails, undelivered/unreceived texts in the past month than I care to count.
It was a great idea, but after more than a year, the novelty has worn off. Google Voice is a farce."
==
I'm going to look into other voicemail transcription options or just live with the issues.* does anyone have recommendations for where to point me for alternatives for a voicemail transcription service?* I would be interested to hear about experiences with reliability of same.* I'll do a general search or post a new topic on that.