I was helping a friend with her OBi200 and something we did with setting up Google Voice on it triggered a firmware update to OBi202-3-0-1-4412.fw
I was able to download it myself manually via browser by editing the URL for an earlier version to reflect the new 4412 build.
If you try to make any changes to your Google Voice SP slot in your OBi200 it will require upgrading to the new firmware.
I don't know whether I screwed something up on my friends OBi, but we couldn't get it to ring when her GV number was set to forward to Google chat. I have a funny feeling this new firmware disables GV from ringing an OBi. Could this be the end of XMPP support on these devices? I hope not.
Obi202 is in the title then you discuss Obi200, can you clarify?
I have noticed that my Obi202 has been updating even though everything is disabled. Not a happy customer and would not recommend Obi products to anyone anymore.
Quote from: jjtricket on July 30, 2014, 08:20:37 PM
Obi202 is in the title then you discuss Obi200, can you clarify?
202 is in the name of the firmware but they are talking about an Obi200. The 200 ans 202 use the same firmware.
The OBi200/202 take the same firmware and they are all named OBi202-3-0-1-xxxx.fw where xxxx is the build number.
We have OBi200s.
Ran into the same thing tonight. I had to remove and then re-add google voice as a service provider before it worked again. I no longer have the option for voicemail notification either.
Will see how things work tomorrow. Are there release notes for this update?
Not related to the new firmware, as I have not had my OBi updated to it yet, I have noticed that using callbacks to make an outgoing call with Google Talk as the callback path no longer works.
Release notes? Not yet and this firmware isn't even available via link here in the forum or via ***6 on the phone.
Quote from: gderf on July 31, 2014, 06:41:52 AM
Release notes?
Past performance suggests that the "Release notes" will contain one line:
Various bug fixes and enhancements
I would be very pleased to be wrong, with detailed release notes of all bugs fixed, and documenting remaining bugs known to not be fixed (with workarounds if known).
When I deliberately triggered the update for my 100 I was taken through a terms of service agreement and app access approval process that seemed like anything but the end of GV. I had to delete GV and then start over but it works normally and I still get voice mail notifications by email.
Ceg3, do you still get MWI from Google?
Quote from: cluckercreek on August 01, 2014, 07:28:37 AM
Ceg3, do you still get MWI from Google?
I do not. I wasn't thinking about it when I got the email notice, but I just left two messages on my GV line and no stutter tone or flash. :o
Does anybody know if this new firmware will prevent using more than one GV setup on the same device?
I have traveled a bit this summer, moving from different houses, different Obi's, moving the registration of one of my GV #'s to a different Obi as I travel. Today, I had to update firmware as your first post describes. Now only one GV # apparently is able to be registered on my 202. Waiting for a response from Obi support about this "new feature" :-\
That's what I was afraid of. Hopefully it's just a configuration problem, and not a limitation. Let us know what OBi support says.
Quote from: cluckercreek on August 01, 2014, 07:28:37 AM
Ceg3, do you still get MWI from Google?
I tried to enable it manually with no joy. I have submitted a ticket to Obihai to see what they say about maybe getting it back.
Response from Obihai support:
MWI will not work for Google Voice now.
Regards,
Obihai Technology
Sounds like the slow demise of GV. :'(
reply from Obihai Support Team ... "You can add more than one Google Voice"
Didn't seem to work for me after firmware update on 202. only after I removed one of two GV #'s did one of them work.. (have Vestalink and IPcomms for other Service providers)
Will try it again
Quote from: giqcass on August 04, 2014, 11:54:12 AM
Sounds like the slow demise of GV. :'(
Me doth thinkith the heard is being directed to Ring.to in a psuedo subtle way.
Speaking of Ring.to, has anyone tried more than one Ring.to DID on a 110 or 202? I can't remember if E911 was mandatory with them, if so then the 110 is out but it is doable on a 202. Just curious if that is possible.
Me doth thinkith I heard you said heard
do you herd me? ;)
Quote from: dircom on August 04, 2014, 04:01:43 PM
Me doth thinkith I heard you said heard
do you herd me? ;)
Damn, I was so close. My Old English isn't what it usithed to be:
Origin of herd....
Old English heord
http://www.oxforddictionaries.com/us/definition/american_english/herd
Quote from: gderf on July 31, 2014, 06:41:52 AM
Release notes? Not yet
And still no acknowledgement in the official firmware forum. I wonder if the new firmware is related, in any way, to their new IP phone release.
The IP phone seems to run a different firmware than the 202s, not really surprising.
So there's three firmwares now:
One for 100/110
Another for 200/202/300/302
And of course the IP phone, 1032
So I doubt this update has much to do with the IP phones, unless it's to implement new interoperability features of some kind.
Quote from: Trev on August 18, 2014, 01:34:57 PM
The IP phone seems to run a different firmware than the 202s, not really surprising.
So there's three firmwares now:
One for 100/110
Another for 200/202/300/302
And of course the IP phone, 1032
So I doubt this update has much to do with the IP phones, unless it's to implement new interoperability features of some kind.
You forgot the 500 series firmware. That's a business style PBx. There will be 2 models of the Obi IP phone coming out if they stick to the plan.
1xx series
2xx series (302 is a locked 202 without GV)
5xx series
Obi10xx series?
right, the Obi1032, followed by
Obi 1062 (with Gigabit-ethernet, built in wifi and bluetooth)
Quote from: dircom on August 18, 2014, 06:16:29 PM
right, the Obi1032, followed by
Obi 1062 (with Gigabit-ethernet, built in wifi and bluetooth)
Yeah I read the datasheet just after I posted. These look very interesting. I also went through the demo UI (http://www.obihai.com/uidemos/obiphone/i).
I don't have the change log, but I can clarify the speculation:
One significant change in this release (and, by "this release", I am referring to the set of releases corresponding to each individual ATA, not just 4412), is the introduction of OAUTH 2.0 authentication for Google accounts, which is a security upgrade. This change applies to the OBi products that access Google: the 1xx and 2xx ATAs and the new IP phone.
You can read about it in my post here:
http://www.obitalk.com/forum/index.php?topic=8443.msg55493#msg55493
Note also: On the OBi 110 (and I assume on the 100, although I don't have a sample to test), if you dial ***6, you may hear that a firmware update is NOT available. But, the OAUTH change is actually pushed automatically when a user adds (or deletes and re-adds) a GV account to one of the SP slots. You can confirm that this has been pushed by the change of the auto-attendant voice from male to female.
RE: "But, the OAUTH change is actually pushed automatically when a user adds (or deletes and re-adds) a GV account to one of the SP slots."
The update is also triggered when updating the configuration on an existing Google Voice account. I was prompted to update the firmware on my OBi201, OBi110 and OBi100 when I updated the configuration a few days ago.
At this point, I would strongly encourage everyone who has not already done so, to go through the update. The easiest way to do this, if you have not done it via another method, is to delete your GV configuration, and then add it again.
This will remove your user ID and password from your OBi device and from the portal, and will instead authenticate via the more secure OAUTH method.
Just be aware that after the update MWI will no longer work, though I don't know if it still works for OBi's not yet updated.
The new firmware seems to have broken the OBi PhonePower . It keeps erroring out. I've deleted and resynced a half dozen times already. But no problems with GV, works perfectly and I love the ease of the new OAuth support.
(http://i.imgur.com/yzqZ1qy.png)
I have two GV lines connected along with 4 CallCallcentric ones on the OBi 1032. Loving this phone so far, but haven't spent anytime digging through the options. Sound quality on both handset and speakerphone are just as good as high end Cisco VOIP phones at a fraction of the cost.