Obi110 Can't Connect/Setup with Google Voice
sirwatkyn:
OK, here's the latest:
I have factory reset the Obi110. I have deleted and added again the device to the ObiTalk portal. The ObiTalk portal can configure my VOIP.MS account, no problem. BUT, it still refuses to add my Googe account, instead constantly returning with the warning that my device or software may be out of date. Yet, this is after flashing the latest firmware, as provided in your link (http://fw.obihai.com/OBi110-1-3-0-2872.fw). I'm assuming this is the correct firmware?
In any case, I can't imagine what else to do, as the unit has been reset from scratch and re-added to ObiTalk. Since the VOIP.MS account works perfectly, I'm assuming I have no hardware problem.
If you have another good idea to try, I'm happy to hear it.
P.S. Would it be of any use to go back to the Google security settings and re-enable using "secure" settings, rather than the option for older "insecure" devices?
SteveInWA:
Quote from: sirwatkyn on June 24, 2016, 10:07:28 am
OK, here's the latest:
I have factory reset the Obi110. I have deleted and added again the device to the ObiTalk portal. The ObiTalk portal can configure my VOIP.MS account, no problem. BUT, it still refuses to add my Googe account, instead constantly returning with the warning that my device or software may be out of date. Yet, this is after flashing the latest firmware, as provided in your link (http://fw.obihai.com/OBi110-1-3-0-2872.fw). I'm assuming this is the correct firmware?
In any case, I can't imagine what else to do, as the unit has been reset from scratch and re-added to ObiTalk. Since the VOIP.MS account works perfectly, I'm assuming I have no hardware problem.
If you have another good idea to try, I'm happy to hear it.
P.S. Would it be of any use to go back to the Google security settings and re-enable using "secure" settings, rather than the option for older "insecure" devices?
By now, there are a bazillion different threads about this issue, and unfortunatelyh, you read an old, and now-out-of-date link. The firmware build you need is 2886. If you followed my instructions, which I linked in my last post, you would have updated to the "latest" build, which is 2886.
http://fw.obihai.com/OBi-latest.fw
sirwatkyn:
Thanks for that updated firmware link.
Well, now, progress to report, but a new problem. Google has been properly provisioned and is working perfectly on SP1, but, now, after the firmware update, my VOIP.MS account refuses to register correctly, and ObiTalk reports: "Failure: 403 Forbidden." I have checked the login credentials and passord, and they're correct, and I have chosen several of the different server options listed by Obitalk for this provider, but none register correctly and all return the above warning.
Any idea on what's wrong now and how I should proceed?
Many thanks. I really appreciate your help and patience.
SteveInWA:
That error message most likely means that you didn't enter the correct SIP user name and password. These may be different than a user name and password to access your voip.ms account portal page. I don't use voip.ms, so one of the other folks here might be able to answer that.
Meanwhile, you ought to be able to log into your voip.ms account and look at your SIP user name and change the password, and then use those values.
sirwatkyn:
Steve:
Many thanks. Now successful all around.
It turned out that the problem was that VOIP.MS had updated their password requirement to 8 digits from 6, but would accept logins from existing devices. So it worked until the Obi firmware was updated and ObiTalk tried to reprovision the system using the old 6-digit password. Once I established a new 8-digit password, everything worked perfectly.
Thanks again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page