can OBihai modify firmware within existing OBi devices to work with API and GV
Ostracus:
Quote from: Rick on May 19, 2014, 10:51:51 am
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.
Hopefully their level of support is better for third parties than it has been for consumers, otherwise nothing gets better, and maybe worse.
giqcass:
Quote from: justgrant on May 20, 2014, 04:47:58 am
. . . 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).
If/When WebRTC becomes more common place I expect to see plenty of services that combine the SIP and WebRTC in a way that will make this possible. That's just speculation on my part but it seems quite likely assuming WebRTC becomes widely adopted. Their appear to be companies already testing this cross compatibility. You of course could get a nice Bluetooth handset to make things a little more convenient in the interim.
http://www.youtube.com/watch?v=0p9mc1KSpzk
http://www.youtube.com/watch?v=FayPPU6ame8
Quote from: justgrant on May 20, 2014, 04:47:58 am
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.
There is nothing wrong with your interpretation. It's more a matter of implementation. It seems that despite the hype the companies supporting WebRTC can not agree on all aspects. All browsers are not compatible with each other due to the codecs they use. All Chrome users can call each other but it may be a problem for a Chrome user to call an Internet Explorer user for example.
Navigation
[0] Message Index
[*] Previous page