Google Voice uses SIP, just like other ITSPs. The authentication method is different, in that it is not using a typical username/password. Instead, it's using a secure token that initially generated and stored on the device when you set up Google Voice on the device.
That said, I am pretty sure your issue is network-related. If you want to just be done with this, why not sign up for service with a simple SIP VoIP ITSP like Callcentric or
voip.ms, and then see how they perform over time.
Both services are low-priced, and have no contracts (paid by the month, and you can cancel any time).
I'd also suggest running a more meaningful test of your ITSP's ability to reliably handle end-to-end VoIP calls. The ordinary speed test websites are useless to diagnose VoIP issues.
Instead, use Visualware's BCS test. It simulates a true VoIP conversation between your computer and various other endpoints. Run it frequently, at different times of the day, and, if you have a call disconnect, then run it immediatly after that. It will report the results as a Mean Opinion Score, or MOS. You need a MOS of at least 4.0, and ideally, higher.
http://www.visualware.com/bcs/Finally, just because you are paying for Comcast's 200Mbps service doesn't mean you are getting it reliably. Cable systems are notorious for signal quality problems caused by corroded connectors, crimps or tears in the insulating jacket, or rodent damage. Comcast will do everything they can to tell you it's not their issue, but if you can document fluctuating MOS values, that points the finger at them.