The solution really depends on the details of your use case and the acceptable delay it would require. You can go for a P2P mesh topology, or you can just use streaming media servers in the backend ; in that case you will use WebRTC from your web app to the server, then the server route/transcode/optimize the distribution of the stream to the clients.
WebRTC on IE & Safari > Today, no other choice than a Plugin.
As far as I know, only one enable WebRTC locally, unbundled from any platform:
http://Skylink.io/plugin
Real time communications can be challenging: browsers, network, hardware and operating systems need to successfully perform complex tasks for a call to be successful.
Understanding what goes wrong, often on the far end, is challenging for developers.
test.webrtc.org captures media from the microphone and camera at various resolutions and sends it back to itself through a TURN relay server, all encrypted.
Once the media is back, Javascript code looks for various issues such as black video frames and silent audio as well as testing network capabilities.
If an issue is discovered, users can easily download or upload the report. When the latter is chosen, a unique URL is created, which can be used when filing issues.
We encourage developers to take the code from github and integrate similar functionality in their own UX. This should be part of any "support request" flow. We also encourage developers to contribute!
Disruptive Analysis has now published the WebRTC Industry Status & Forecasts Report, 2014 Edition. It is the most detailed study on WebRTC, based on primary research and detailed quantitative market modelling. It extends the analysis the original report issued in February 2013 and several interim updates.
The report contains the most detailed & comprehensive forecasts on WebRTC adoption available from any analyst firm:
* WebRTC-capable device numbers, by PC/phone/tablet/M2M & geographic region
* Consumer WebRTC users for standalone & embedded voice/video
* Business WebRTC users for contact centres, UC and app-embedded communications
* Telco WebRTC users for VoIP/VoLTE extension, Telco-OTT services & cable/IPTV
* M2M/IoT estimates for WebRTC integration
The research has presented a range of new findings:
By 2019, there will be more than 6bn WebRTC-supporting devices & 2bn+ individual users (around 60% of the total Internet population). Some will be regular users, for example where it is embedded into a primary communication app or service, while others will just use it occasionally – perhaps in a B2C customer service & support context.
http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
Enterprise use of WebRTC is the most widely-commercialised today. But there is more action in new cloud-based offers for collaboration and conferencing, rather than upgrades of the existing installed base of UC/PBX “seats”. There are also new platforms emerging to integrate voice/video into apps and workflows. This means that WebRTC will “dis-unify” aspects of business communications, even while it helps other moves towards UC continue.
http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
By the end of 2015, there will be more mobile devices supporting WebRTC than PCs. This is part-driven by Chrome and Android Webview, but also WebRTC integration into apps using 3rd party frameworks or SDKs.
More than 10 telecom operators have commercial offers involving WebRTC in some way, with many more in development or nearing launch. Although IMS-integration of WebRTC gets most airtime, the majority of deployments are standalone Internet/app/OTT-style or even integrated with TV/cable platforms. Overall, telcos could have up to 500M WebRTC users by end-2019
http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
Guys, would you like to present at the next SF WebRTC Meetup on April 28th? http://www.meetup.com/SF-WebRTC/events/229430038/