New Chrome HTTPs requirements for voice and video calls: Enhanced WebRTC has you covered
You may have heard that Google is increasing its security requirement for WebRTC and will be requiring all WebRTC sessions to be run over HTTPS connections. With an estimated launch date of December 2015, your end users will no longer be able to share their voice and video through your app.
If you are using the AT&T Enhanced WebRTC API, you are in good shape from a service perspective because it already supports HTTPS connections. Now, you have to take a look at your website, and make sure that it uses an HTTPS connection. If not, Google offers some best practices advice for updating your app to support this security standard.
In his November 2015 BlogGeek.me newsletter, Tsahi Levent-Levi, also provided a practical workaround for those developers who have added a click-to-call implementation of WebRTC on their website. In summary, he recommends updating the website to HTTPS, if possible. If that is not possible in the short-term, he writes that you can have the widget open up the voice/video in another window that is served off an HTTPS domain.
Best of luck in updating your apps to support HTTPS. If you are not already using the AT&T Enhanced WebRTC API and would like to learn more about it, there is an SDK and code snippets available on the AT&T Developer Program website.