Here we had an issue with self-signed certificates used with Android Chrome browser for WebRTC calls
Now the issue is completely fixed in Google Chrome, and you do not need any CA signed certificates for Android Chrome or Firefox browsers.
It will work without any additional configuration, using Flashphoner’s built in certificates generated on the fly.
It is enough save because these certificates will be generated each launch of the WCS server, therefore there is no way to reuse them.
Fixed issue with self-signed certificates for Android and WebRTC
WCS3
771
27 May 2014