# Note: actually, TLS & DTLS sessions can connect to the # TURN listener port for UDP and TCP (Default: 3478). Edit the file `/etc/nf`, un-comment listening-port=3478 and change it to listening-port=443 to have CoTURN server listen to port 443:.Edit the file /etc/default/coturn and un-comment TURNSERVER_ENABLED=1 to have CoTURN start on boot.Reboot the server from the EC2 dashboard or with sudo reboot.You will also need to add inbound rules to the TURN/STUN server EC2 security group in order to allow inbound connection from your Genymotion instance(s) to TCP (HTTPS) and UDP port 443: We recommend using an Ubuntu Server 20.04LTS (Focal) x86_64 instance for General purpose and instance type t3.micro: This tutorial will show you how to install and setup a STUN/TURN server on AWS. If using a public IP does not comply with your setup or security requirements, the solution is to use your own STUN/TURN server. As a result, you will not be able to get any display (black screen) if your instances don't have a public IP. This means that Genymotion instances require a public IP and access to the Internet to reach our STUN/TURN server. To palliate to this, our Android 8.0+ images forward all WebRTC connections to our own STUN/TURN server. With Android 8.0 and above Genymotion Device images (PaaS) on AWS, WebRTC connections require a STUN/TURN server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |