Quote from: RFC3261 on May 12, 2018, 11:28:40 AM
Quote from: SteveInWA on May 11, 2018, 10:30:21 PMIt would be nice for that process (delete from portal, restore to factory defaults, add to ports, setup GV) for those with remaining issues to be a highlighted stickee topic at the top of the areas so that we (and when I say we, I mean mostly you) have to keep repeating that recommendation again and again as people manage to fall off the OBi GV wagon (especially in a month's time). If you can push any of your contacts, that would be a nice thing to see happen (and the internal motivation might just be fewer support tickets when GV pulls the plug on XMPP).
... then you will need to delete the device off of the OBiTALK web portal, restore it to factory defaults, add it back to the portal, and finally, set up Google Voice again.
Good idea, and thanks very much for your support. I hesitated to do that, only because it was a crude "shotgun" fix, and I don't know exactly what step fixes the underlying issue. But, the empirical evidence (forum posts here and on the GV forum) show that it solves the problem in most cases. I suspect that most of the devices that don't work right after the upgrade have some sort of expert-mode settings that borked up the conversion, and thus, factory-restoring them and re-attaching them fix it.
A surprisingly positive result was yesterday, when a friend who is NOT using Google Voice plugged in his 200, after it being powered off for a few weeks during a move, the device automatically got the 8589 firmware, with no action on his part. The device is off-warranty and has no paid support.
The rollout was supposed to complete yesterday or today. There may still be some stragglers into next week.
I'll look into writing a sticky post next week.
And, ha ha about nailing me with the doctor analogy!