#Github jitsi android#

Thanks in .jetty.host=:: .jetty.port=443 .= .=/http-bind .= .=/usr/share/jitsi-meet ./config.js=/etc/jitsi/meet/ ./interface_config.js=/usr/share/jitsi-meet/interface_config.js ./logging_config.js=/usr/share/jitsi-meet/logging_config.js ./external_api.js=/usr/share/jitsi-meet/libs/external_ .=^/(+)$ .=/ .=/ .=443 _HARVESTER_PORT=443 .=/etc/jitsi/videobridge/ .=PASSWD .NAT_HARVESTER_LOCAL_ADDRESS=PRIV-IPv4-Addr .NAT_HARVESTER_PUBLIC_ADDRESS=PUBL-IPv4-Addr Public IP is translated to private IP with stateful NAT. Jitsi is running on our VMWare Cluster on Ubuntu 18.04.04 LTS VM. Local and public IP is set in '/etc/jitsi/videobridge/sip-communicator.properties' Environment details WebClient Users can be in different subnets or locations.

#Github jitsi android#

It does kill all sound or screen-sharing when a iOS or Android Client is joining the conference wich is not on the same subnet lika all other conference participiants(the web-client user).

We configured our server like this:įurthermore we've configured secure domains - exactly like the tutorial for internal authentication.Įverything is working fine when having conferences with WebClients(Chrome or Firefox). Firewall allows incomming traffic from tcp:80/443 and udp:10000. Sound, webcam and screen-sharing is availible after a few seconds, when App-User leaves the conference. When joining a conferece with iOS or Android App using our own hosted jitsi-server all sound, webcam and screen-sharing crashes.