Quote from: nmstough on November 05, 2014, 12:46:33 PM
OK, followed all those steps. The software on the device is 4367. Status is now connected.
But I thought that putting your gmail password into the device configuration was a security hole, which was avoided by using the Obitalk and logging into gmail method?
This. That is the main reason that Google told third-party companies to stop using Google customer's user IDs and passwords to gain direct access. Obihai developed a new authentication method, using Google's approved OAUTH 2.0 protocol, to now access users' accounts without directly signing in with their password.
Don't use the local web page method to set up Google Voice (Chat) access.Instead, troubleshoot the separate issue of why your device isn't being recognized by the portal; it's likely to cause other issues with using your OBi, so you might as well diagnose and fix it. It could be a DNS or firewall issue, for example. Also, if your router has a setting for SIP ALG, then DISable that setting. You should not put your OBi in the DMZ, nor would you need to do this to solve the problem.
Personally, I'd do a paper-clip reset on the OBi device, then download the 4420 firmware from Obihai, access the OBi via the local web interface (username/password is admin/admin after a reset), upload the new firmware, then try again to access the portal.
http://fw.obihai.com/OBi202-3-0-1-4420.fw