can OBihai modify firmware within existing OBi devices to work with API and GV
Crow550:
Do we know for sure that the API uses WebRTC though?
Let's just take a breath and see what Obihai can do with the API.
justgrant:
Quote from: Crow550 on May 18, 2014, 03:22:54 pm
SNIP
Also justgrant. I was the one who posted the link. He just quoted what I had already posted above his. Next time double check. It even says "Quote from: Crow550".
In the post below his I said: "It kinda just came out of nowhere. I found it while reading the comments on the G+ post that I posted. Looks like it was added on the 15th. Even some of the commentors are pointing out that it's new."
Plus I also already made a separate Thread on this: http://www.obitalk.com/forum/index.php?topic=8092.0
Sorry about that, Crow550.
Correction noted.
justgrant
Rick:
Quote from: Crow550 on May 18, 2014, 10:06:43 pm
Do we know for sure that the API uses WebRTC though?
Let's just take a breath and see what Obihai can do with the API.
I'll bet a cup of coffee that they won't even look at it. They're done with the business of dealing with consumers directly. New phase is supplying boxes to third parties that do the configuration and support.
Crow550:
Quote from: justgrant on May 19, 2014, 06:44:02 am
Quote from: Crow550 on May 18, 2014, 03:22:54 pm
SNIP
Also justgrant. I was the one who posted the link. He just quoted what I had already posted above his. Next time double check. It even says "Quote from: Crow550".
In the post below his I said: "It kinda just came out of nowhere. I found it while reading the comments on the G+ post that I posted. Looks like it was added on the 15th. Even some of the commentors are pointing out that it's new."
Plus I also already made a separate Thread on this: http://www.obitalk.com/forum/index.php?topic=8092.0
Sorry about that, Crow550.
Correction noted.
justgrant
It's cool.
justgrant:
Quote from: giqcass on May 18, 2014, 09:15:18 pm
We have to consider the time/cost of bringing this kind of modification to a stable release. Integrating something like this is not plug an play. I think this can be done on the 2xx, 3xx, and 5xx series devices. I am not so sure about 1xx series. Obihai 2XX and 3xx series can do WebRTC already. I have used the Obi WebRTC call feature on my Obi202.
http://www.obitalk.com/obinet/login/ (Top middle of the page is the WebRTC button.)
Quote
This Call OBi button will allow you to call an OBi number directly from your web browser.*
Your call will ring the far-end phone(s) attached to the OBi device’s PHONE port(s).
If you are logged-in to your OBiTALK account, and use the Call OBi button to call an OBi device set-up in the same OBiTALK account or a device whose Circle of Trust you belong to, the OBi Attendant will answer and you will be able to bridge your web call to a regular number using Option 2.
* For the Call OBi feature to work, the web browser must support WebRTC and the user must allow the use of their microphone / speaker for the call. Google’s Chrome browser supports WebRTC. Only the OBi200, OBi202, OBi300 and OBi302 models may be called. The OBi device must have OBiTALK Service enabled.
EDIT: I see one MAJOR issue. This does not appear to be a web API. The API was meant for IOS and Android. IOS uses Objective C for apps Android uses Java for apps. My digging suggest the Obi uses at least some Javascript but that isn't the same as full Java. The API probably requires lower level access to part of the Android OS because it specifically requires 4.2.2 or greater. That suggest dependent functions are baked right into the OS. This might require reverse engineering of some libraries to operate on an Obi and that would be a violation of TOS. On the other hand this is good news for the Raspberry pi community. With an Android distribution being worked on full Hangout support will likely be possible in the near future.
Thank your extremely informative for your post, gigcass.
If my interpretation is correct, and it my not be, it appears that Firefox and Opera browsers will also work with WebRTC [http://www.webrtc.org/] . . .
WebRTC is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple JavaScript APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high quality, RTC applications to be developed in the browser via simple JavaScript APIs and HTML5.
The WebRTC initiative is a project supported by Google, Mozilla and Opera. This page is maintained by the Google Chrome team.
. . . it's a shame we cannot simply use our phone(s) connected to SP1/2 SP3/4 on OBi202's with WebRTC instead of audio out (from sound card or related device) for headphones/earphones, a boom mic/microphone, and an approved browser (as noted above).
Thanks again for your post, gigcass.
justgrant
Navigation
[0] Message Index
[#] Next page
[*] Previous page