Quote from: madhatter on June 17, 2018, 07:26:25 AM
I went to add a new OBI200 this week and ran into some weirdness I haven't seen before.
First, when trying to add the OBI I couldn't get past the NEXT screen after calling the server # and keying in the server code. I reset the 200 (which was new out of the box) until the green light turned red.
After the restart I was able to continue with the OBI registration.
Regardless if it was "new out of the box", it didn't have the very latest firmware (as with all electronic gizmos, there's a time lag between manufacturing, shipping, distributing, selling, shipping again, etc.). Sometimes the initial addition of the device to the portal goes awry for some unknown reason, and resetting it properly updates the firmware and all's well.
Quote
Second, when I added my GV email to the SP1 record, the OBI came back with the wrong GV phone number. For snicks I dialed the # and got VM for another person.
The OBiTALK device has no idea what the phone number is for Google Voice. You authenticate to a Google account. The Google account has the Google Voice service. All you're doing is authorizing OBiTALK to access that service, with whatever phone number might be assigned to it. I can't imagine how you accomplished that scenario, unless your Google Voice configuration has an old, abandoned linked/forwarding phone number on it, which was re-issued by the carrier, to some other customer.