Connect Failed: No Response (as of today 3/9) Across MULTIPLE OBI 508's
volkswagner:
I just requested Amazon remove all of Obihai's product listings until the fix the lies
on current product listings.
Clearly 504 and 508 devices will never work with GV again.
Class action is certainly in order, at least for anyone that purchased after March 2019.
transam98:
This is perfect !! If you could provide a link to where you asked AMAZON Ill do the same, as I also purchased from AMAZON and am also screwed by this company... HUNDREDS down the drain also and im a VERIFIED Purchaser with AMZ on a 508.
dlarson54:
Has the 504 and or the 508 been discontinued?
waldo22:
Is there any official word from Obi/Polycom regarding discontinuing GV with the 504/508 devices?
It hasn't worked with our 508 since March.
The 504/508 devices aren't even listed on the Polycom Google hardware page:
https://www.polycom.com/partners/find-a-partner/cloud-video-partner/google.html
I'm OK switching to a SIP provider, but our usage is super low and GV was a good solution. (a handful of calls per day on about 5 lines; so low that I didn't hear about it until June)
It's certainly their prerogative to not support GV on these devices, but an official announcement would be nice instead of keeping everyone guessing about why it's broken.
waldo22:
According to DSLReports the Obi504vs and Obi508vs both do not work because Obi/Polycom used an IP address for their TLS/OAuth connection instead of a domain.
From the post:
Quote
The 50x fw implemented the oauth2 and SIP extensions required by GVSIP to work with GV, except that the implementation missed specifying the TLS hostname for the connection [...] Everything worked fine until March 2019 when google did some hostname-based routing (i.e. obihai.telephony.goog vs fi.telephony.goog) which exposed obi50x's shitty hostname-less implementation.
I kinda figured obi/poly might release an updated stock fw with the trivial 1-line change (which is already correct in [firmwares] for obi20x and obi10xx) for their $300 devices, but I guess I was wrong...
So a 1-line fix. And in 10 months, Obi/Polycom hasn't so much as acknowledged that it is broken.
I'm pretty disappointed.
Navigation
[0] Message Index
[*] Previous page