TCP connection to 125.141.125.74 failed
mstbone67a:
well poop sticks. interesting read about using a rpi for a fix.
https://narahari.wordpress.com/2017/11/07/obi110-reuse-using-raspbx-how/
SteveInWA:
Quote from: mstbone67a on November 07, 2017, 04:32:19 pm
well poop sticks. interesting read about using a rpi for a fix.
https://narahari.wordpress.com/2017/11/07/obi110-reuse-using-raspbx-how/
Take note: that solution uses the outdated and less-secure Google account login method, with a userID and password stored on the Pi. Doing that gives that box full access to everything on that Google account. Google strongly discourages it.
By contrast, OBi devices and the Simonics GVGW use the Google-approved OAUTH 2.0 authentication, which only grants access to the XMPP service on the Google account. No Google account password is stored on the device.
omegastar:
So I take it ObiTalk is gonna screw all the OBI110 owners now. Cant see how they still sell this device but dont support it.
SteveInWA:
Quote from: omegastar on November 07, 2017, 07:03:29 pm
So I take it ObiTalk is gonna screw all the OBI110 owners now. Cant see how they still sell this device but dont support it.
They don't still sell the device. Any that you might find for sale are not being sold by authorized retailers.
I predict that a metric ton of used 100s and 110s will appear for sale on Craigslist and eBay soon.
GPz1100:
This solves the issue of Oauth 2 for the Raspberry Pi Zero W.
http://nerdvittles.com/?p=21777
The $6 gateway option will save you days in terms of configuration time.
Asterisk 14.7 and above already has direct support for oauth 2 (for manually edited config files). Presently it's a matter of the motif module getting updated to support this in freepbx flavors.
Navigation
[0] Message Index
[#] Next page
[*] Previous page