I am implementing a camera device and thinking using WebRTC as the video/audio streaming protocol with the app. And I would like to stream the video/audio to Google Nest Hub. But from all the documents I can find, I didn't find any information that is related to WebRTC? So, I am curious if Google Nest Hub or Chromecast supports WebRTC or not? If yes, where can I find the related sample or document?
Google Nest Hub now supports WebRTC protocol. More information in regards to
this can be found here. Currently Chromecast does not support WebRTC, but we are constantly working on improving the capabilities of our ecosystem
Related
I'm looking at my options to control the Sonos Port at https://developer.sonos.com/reference/. I read about some UPnP control of other Sonos devices, but I can't seem to find any official information about this online. Is UPnP control of the Sonos Port possible?
Sonos uses UPnP for some calls internally, but we never publicly supported this protocol. We encourage you to use the Control API to control Sonos devices. See Connected Home: Get Started for details. Let us know if you see anything missing that you'd like us to add.
You can control any Sonos device via UPnP. The documentation for this used to be on the musicpartners site but access was exceedingly difficult. much of it is standard UPnP, documented at https://openconnectivity.org/developer/specifications/upnp-resources/upnp/ . There are many open source codebases that use it. It is much more powerful than the documented Cloud API in most regards.
I see WebRTC is the the best way for developing it. But there are some paid frameworks in market for establisting video chat between wide range of clients like Web-Web, Web-Mobile(IOS, Andriod, Windows, etc.,).
Web-Web communication flow is very simple to implement. Now, I want the same for Web-to-Mobile and vice versa without using any external frameworks built on top of Native WebRTC. Please suggest me some best approach to achieve this.
The latest Chrome on Android is WebRTC friendly, that means if you have a web app that implements WebRTC. It will be working on Android's Chrome.
If you decided to create you own native app that implements WebRTC. Here are some great sources.
iOS WebRTC: https://webrtc.org/native-code/ios/
Android WebRTC: https://webrtc.org/native-code/android/
Follow the instructions in each allow you to build the native WebRTC framework that you can later on import them into your native projects.
The WebRTC APIs are somewhat related to the ones you are using in your web application. You need to do more documentation reading for those as you are using the official framework that built from the source, not a third library.
Before starting you need to review and test platform to make sure it works fine for all your target user categories. You can do that by reviewing references and also testing some existing apps for user types you plan to support.
As you mentioned wide range of clients, you need to identify the limitations of WebRTC technology. You can also evaluate other technologies: in example you could reliably serve most client types with mobile and web apps that use RTMP.
I want to add video chat option in my website please guide me how i do this task and what should i required for doing this.How much it's cost if i will make it for my website and also it's maintenance(Like server ETC).
You are looking for something like rtchub.com
If you want it free, you can develop it yourself, using WebRTC:
WebRTC is a free, open project that provides browsers and mobile
applications with Real-Time Communications (RTC) capabilities via
simple APIs. The WebRTC components have been optimized to best serve
this purpose.
See WebRTC Tutorial
On client side you use JavaScript (jQuery), and clients communication directly using browser, but you need server part and signaling mechanism, and you can use for example SignalR or Node.js.
As example you can look at my site: SignalRTC.
P.S. WebRTC works only on selected browsers, for example Chrome, FireFox, unfortunately not on IE or Edge.
Trying to use the webrtc widget on an ipad and it is saying that the browser does not support webrtc.
Is there a work around that people are using for this? A number that people can call into on their phone.
What are the approaches taken to get people on a mobile device into the conference.
Currently there's no support for WebRTC on most mobile platforms, the notable exception at the moment is the latest version of Android running the Chrome browser.
Additionally, WebRTC does not have any native support for phone dial-in, however providers such as Twilio have begun development of WebRTC - phone interfaces (https://www.twilio.com/docs/client). Also, development of a dial-in feature would require the addition of a server to handle the authentication credentials associated with a service such as Twilio.
Video chat on the iPad/iPhone will likely be supported as soon as Apple's Safari browser adopts the WebRTC specification. However, telephone dial-in is not currently something on our immediate roadmap for the video chat widget.
As stated in the Google Talk for Developers site, you can use the provided APIs to build a client that connects to the Google Talk service.
I would like to know if it's possible (or it will be in the near future) to build a similar client to the google hangouts.
What we pretend is to build something similar to cloud print, that provides printing services to the cloud, but for audio/video streaming: a camera and microphone would replace the
printer.
Thanks a lot.
Talk and all the XMPP stuff is going to be put down soon.
The new Hangouts infrastructure is proprietary. It only has API to integrate Hangouts into web pages and applications, but no API or protocol to create an alternative Hangouts client software.
https://github.com/tdryer/hangups is a library that does exactly that, with a command-line client for Linux.
https://github.com/xmikos/qhangups is a PyQt-based cross-platform app that aims to provide an open-source alternative to the Chrome-based official desktop app. Unfortunately it's not working at the time of posting, but the author is investigating the issue.