You may recall from yesterday that early adopters were having a variety of issues after activating (or attempting to activate)
Sprint's new
Google Voice integration feature. Well, a full day has passed, and we've had several calls with GV lead Vincent Paquet as well as Brian Smith, Sprint's director of product development. Both executives have said that their respective companies have been hard at work on resolutions to each of the issues we outlined Thursday night, and some customers we spoke to yesterday are now back online. Jump past the break for a quick summary of what's been fixed, and what remains on the to-do list.
 |
| Technology Geek |
Our primary concern yesterday was a voicemail security bug that inadvertently granted management-level access to people that one user called from the Google Voice web app. Google is not commenting on this vulnerability, but has confirmed that it's not a threat today. The second issue was that some GV customers who were up and running with Sprint integration suddenly found themselves unable to use the service. This issue has been pegged to the removal of an accounting code -- GGLVOICE -- that some Sprint reps have accidentally removed. The carrier is working to prevent this from occurring in the future, and those already affected should soon be able to call in for support. Next up, some international calls were being processed through Sprint, rather than through GV, even after users activated their integration. This has been tied to the accidental removal of the same accounting code, and Google has offered to reimburse affected individuals (see the update on
yesterday's post for full details).
